Skip to content

feat: recover rich rendering and require delivery acceptance - #20

Merged
Codename-11 merged 7 commits into
mainfrom
codex/rich-rendering-delivery-recovery
Jul 13, 2026
Merged

Codename-11 merged 7 commits into
mainfrom
codex/rich-rendering-delivery-recovery

Conversation

@Codename-11

Copy link
Copy Markdown
Owner

Summary

  • recover the completed AXI-95–99 rich-rendering work from the isolated Codex bridge clone onto current production main
  • render issue descriptions, comments, and Focus content through the shared safe rich renderer with bounded media/provider previews
  • keep goals active after execution completes until a human accepts an outcome summary with durable delivery evidence
  • add audited goal reopen/acceptance operations and an outcome-review health state
  • expose obvious Comment and Ask @agent actions on plan steps, reusing mention-aware dispatch and orchestration context
  • prepare v0.10.0 release notes and migration 0099

Root cause corrected

Execution-step completion was treated as proof of delivery, allowing a plan to complete and its parent goal to become achieved before branch publication, PR review, merge, deployment, or smoke verification. The delivery lane is now an explicit human acceptance gate and is intentionally unavailable to agents over MCP.

Verification

  • pnpm lint (existing warnings only)
  • pnpm typecheck
  • full Vitest suite: 1,159 passed, 1 skipped
  • fresh Next.js production build
  • full Playwright suite: 37 passed
  • git diff --check

@Codename-11
Codename-11 merged commit 0571add into main Jul 13, 2026
2 of 3 checks passed
@Codename-11
Codename-11 deleted the codex/rich-rendering-delivery-recovery branch July 13, 2026 17:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant