Release v0.26.0 — Artifact Studio and trustworthy completion

[Codename-11]

Release

Coordinates current main as Forge v0.26.0: AXI-86 Artifact Studio, AXI-113 trustworthy completion evidence, and the AXI-112 production-smoke hotfix.

Included

• collaborative artifact authoring, revisions, previews, assets, token-scoped sharing, workspace settings, and API-key controls
• structured completion evidence states, fact-level diagnostics, freshness, retry timing, and source links
• webhook, queue, sweep, visibility, focus, and manual evidence refresh triggers
• fail-closed automatic completion plus an explicit audited Mark done anyway override
• BullMQ-safe webhook delivery-drain dedupe IDs restoring automatic retry queueing
• release-unique changelog seen state so same-day releases remain detectable and collision-free

Validation

• AXI-86 implementation PR AXI-86: Ship Artifact Studio collaboration and previews #56 merged with its full gate
• AXI-113 implementation PR Improve completion evidence freshness and override UX (AXI-113) #54 merged with its full gate
• AXI-112 hotfix PR Fix webhook delivery drain job IDs (AXI-112) #55 merged after focused regression, lint, typecheck, and all three GitHub CI jobs passed
• PR Release v0.26.0 — Artifact Studio and trustworthy completion #57 rebased onto exact current main after AXI-86 merged; CI and updated Codex review rerun on the new head

Target tag: v0.26.0

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 74d061b150

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Make same-day release notes detectable

When a user already opened What's New after v0.25.0 on July 16, this new entry reuses the same parsed changelog date, so WhatsNewTile compares new Date("2026-07-16") against that later changelogSeenAt timestamp and never shows the unseen indicator for v0.26.0; the workspace What's New page also keys sections by entry.version, so the duplicate 2026-07-16 value collides. Either the parser/seen state needs a release-unique version/timestamp, or this metadata needs to stay unique for same-day releases.

Useful? React with 👍 / 👎.

[Codename-11]

@codex review

[chatgpt-codex-connector]

Codex Review: Didn't find any major issues. 🚀

Reviewed commit: d38a0bd659

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".