Skip to content
This repository was archived by the owner on Oct 9, 2026. It is now read-only.
This repository was archived by the owner on Oct 9, 2026. It is now read-only.

Sync TUI, Guardian, and CI substrate #308

Closed

Description

@shiny-code-bot

Objective

Complete the convergence program by adopting compatible upstream TUI, Guardian/approval-review lifecycle, app-server presentation, generated client, packaging, and CI changes after their protocol, state, auth, and tool dependencies are stable.

Finish Line

The Codex Lab TUI/Desktop-facing lifecycle and build pipeline are aligned with the selected upstream substrate, preserve Every Code product UX, and produce a provenance-visible binary that passes the final dogfood gates.

Current Status

State: Complete.

PR #495 merged into #428's candidate as 5ae93aee76aca2f498150f9a5dd3cc70f4633612 on July 29, 2026. It restores the owned, bounded codex exec Background Review wait and records the current Auto Review and Guardian suites as converged upstream evidence while preserving Background Review as a distinct Every Code workflow.

Final lane evidence on exact source dd231f3560199d6afcc60d109030002bb312d12d: all 148 codex-exec tests, 3,312 TUI tests, 296 app-server-protocol tests, 137 focused initialize/thread/app-list/review/interrupt/strict-config app-server tests, and all seven restored exec-harness scenarios passed. Schema regeneration produced no diff. The exact debug binary recorded clean provenance and digest 6deaf6a50e59971f89fdaf91432087cee64a0970fd95defc9d34e77f46e26f24. PR #495's 15 checks were terminal and green, including blocking CI and the macOS ARM64 app build. Strict convergence validation passed with 366 guarded paths, zero violations, zero stale waivers, and four reproducible historical snapshots.

A broader non-required app-server sweep passed 1,061 of 1,068 tests. Four failures were caused by fixture binaries not built by the package-only invocation; the remaining executor/host-skill failures are routed to downstream #83's paired skills-quality audit rather than hidden as #308 lifecycle failures.

Next action: activate #83 on candidate head 5ae93aee76aca2f498150f9a5dd3cc70f4633612 and resolve its exact skills-quality evidence.

Blocked by: nothing.
Last verified: July 29, 2026.

Scope

  • In: TUI rendering and lifecycle, tab/diff behavior, account/agent/review/validation surfaces, Guardian interruption/idle semantics, app-server notifications, generated clients, packaging, macOS app build, and CI workflows.
  • Out: redefining Guardian as code review, replacing Every Code account/agent UX with upstream defaults, and landing generated or CI churn before owning source behavior is stable.

Acceptance Criteria

  • TUI changes follow the settled protocol/core/auth/tool contracts and preserve Every Code account, agent, Code Bridge, Background Review, and validation UX.
  • Guardian remains approval and safety review; interrupted turns emit the correct terminal and idle lifecycle without hanging clients.
  • Current compatible upstream leaf fixes, including diff-tab rendering, are adopted or explicitly rejected in Define Every Code-owned convergence contracts #126.
  • Strict app-server/Desktop clients handle all new lifecycle variants and notifications.
  • Generated schemas, clients, snapshots, lockfiles, and packaging outputs are regenerated from final source state.
  • The launch/install path exposes exact build provenance so dogfood evidence cannot come from a stale binary.
  • Focused TUI snapshots, app-server lifecycle tests, exec harness, macOS ARM64 app build, and required CI pass.
  • Final dogfood covers foreground Review, Background Review, Approval Review, validation, Code Bridge, accounts, and external agents as distinct workflows.

Relationships

Validation

  • TUI snapshot and interaction tests.
  • App-server protocol/schema and lifecycle integration tests.
  • Full Desktop Compatibility Gate from codex-rs/app-server/README.md: regenerate schema, prove the schema path has no diff or untracked files, run just test -p codex-app-server-protocol, and run the targeted app-server initialize/thread/app-list plus CLI strict-config tests.
  • Exec-harness scenario sweep and macOS ARM64 app build.
  • Repository-required CI and regenerated-artifact checks.
  • Rebuilt-current-binary dogfood with exact Make dogfood build provenance visible #311 commit provenance.

Decisions

  • Guardian is approval safety, not the general code-review findings engine.
  • CI/generated/package changes land last, after source contracts settle.

Open Questions

  • Which upstream TUI additions are product-compatible versus reference-only for Every Code UX.

Activity

  1. added
    planDurable planning issue
    plan:blockedPlan blocked by an open native dependency issue
    on Jul 11, 2026
  2. cbusillo commented on Jul 26, 2026

    @cbusillo
    Owner

    Update 2026-07-26: the provenance dependency from #311 is implemented and green in draft PR #475. TUI /debug-config now shows exact build provenance without adding model-visible context; the verified launcher and bounded candidate/staging retention are restored as well. Blocking CI and the macOS ARM64 Codex Lab app build both pass at head 07053d796d.

    This remains stacked on PR #465 and should be counted as ready-for-integration, not yet merged evidence.

  3. added
    plan:activePlan is actionable now
    and removed
    plan:blockedPlan blocked by an open native dependency issue
    on Jul 29, 2026
  4. added
    plan:donePlan completed or superseded
    and removed
    plan:activePlan is actionable now
    on Jul 29, 2026
  5. shiny-code-bot commented on Jul 29, 2026

    @shiny-code-bot
    CollaboratorAuthor

    Completed through PR #495, merged into the #428 candidate at 5ae93aee76aca2f498150f9a5dd3cc70f4633612.

    The final evidence is recorded in Current Status: exact-binary exec harness, full TUI, protocol/schema, focused app-server lifecycle, Guardian/Auto Review, macOS ARM64 app, blocking CI, and convergence controls are green. Skills-specific failures from the intentionally broader app-server sweep are handed to downstream #83.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    planDurable planning issueplan:donePlan completed or superseded

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions