coilyco-flight-deck/agent-compose
coilyco-flight-deck/agent-compose
Watch
2
0
Code Issues 20 Pull requests Projects Releases 161 Packages Wiki Activity Actions

Run contract: complete the Agent Compose v1.x issue suite #115

New issue
Closed
opened 2026-07-27 22:11:48 +00:00 by coilyco-ops · 9 comments
coilyco-ops commented 2026-07-27 22:11:48 +00:00
Member
Copy link

Goal

Run the complete Agent Compose v1.x migration as one uninterrupted program and
finish with zero open issues in this repository.

The run uses multiple independently validated commits. “One shot” means one
owned program with no return to an ambiguous backlog. It does not mean one
giant commit or one unbounded implementation diff.

Baseline

Canonical releases have already passed v1.0.0 and reached at least v1.32.0. The
run records current canonical main and its latest verified release as the
pre-migration baseline. The run does not create or recreate a v1.0.0 tag.

Every change remains additive within v1.x and preserves the documented legacy
read paths.

Ordered program

1. Resolve the profile graph

  • #111 - selected profile plus composable personality libraries

2. Resolve authored content and personality discovery

  • #110 - authored assets leave Go for their owning engine, profile, or library
  • #112 - aliases, provenance, affinity derivation, and compact index

3. Resolve role doctrine

  • #121 - role definitions become canonical skills with compact startup identity
  • #116 - Engineer and Ops ownership wording lands in those canonical role skills
  • #128 - conditional QA fixture-verification doctrine lands in the QA role skill
    and shared sealed-role asset

4. Complete QA fixture enforcement and proof

  • coilyco-flight-deck/ward#1617 - provider-neutral, fail-closed fixture mode
  • coilyco-flight-deck/agentic-os#781 - coilyco deployment binding and real
    director to engineer to QA proof

The agent-compose doctrine lands first. Ward enforcement lands second. AOS
binding and proof land third. The run does not treat role prose as authority.

5. Complete the external-profile feature set

  • #123 - generalized seats
  • #124 - copy contracts
  • #125 - custom evaluation matrices and result v2
  • #126 - catalogue commands
  • #127 - bundle export and content-aware diff
  • #122 - final executable external-profile example and arbitrary-role vertical
  • #114 - integrated parent closes after every child passes

6. Refresh immutable evaluation evidence

  • #109 - generate all required responses serially and have independent QA score
    every rubric criterion

7. Close the program

  • Re-run final repository validation from canonical main.
  • Map every issue acceptance item to a commit, test, generated artifact,
    evaluation record, or documentation surface.
  • Close every completed child and parent issue.
  • Confirm the repository has zero open issues.
  • Close #115 last.

Execution rules

  • The goal agent lands each independently verified slice before starting work
    that depends on it.
  • The run fixes in-scope discoveries inside the owning slice rather than filing
    deferrals to manufacture tracker zero.
  • A newly discovered independent product idea does not enter this run unless it
    is required for an existing acceptance criterion.
  • The run does not parallelize model evaluation calls.
  • Independent QA reviews #109. Kai reviews only an ambiguity that the rubric
    cannot resolve.
  • Consumer-specific authoring and repositories remain out of scope.
  • The run performs no live deployment or consumer-system mutation.
  • The AOS fixture proof is the only live verification action in this program.
    It runs inside Ward's admitted disposable fixture mode and leaves complete
    cleanup evidence.

Done condition

  • Every issue named above is implemented or explicitly superseded by landed
    equivalent behavior with an acceptance mapping.
  • Every required validation passes on final canonical main.
  • Every release consequence required by landed commits completes through the
    canonical pipeline.
  • Ward #1617 and AOS #781 are closed with enforcement and proof evidence.
  • The final issue query returns zero open issues.
  • #115 closes last with the complete evidence audit.
## Goal Run the complete Agent Compose v1.x migration as one uninterrupted program and finish with zero open issues in this repository. The run uses multiple independently validated commits. “One shot” means one owned program with no return to an ambiguous backlog. It does not mean one giant commit or one unbounded implementation diff. ## Baseline Canonical releases have already passed v1.0.0 and reached at least v1.32.0. The run records current canonical `main` and its latest verified release as the pre-migration baseline. The run does not create or recreate a v1.0.0 tag. Every change remains additive within v1.x and preserves the documented legacy read paths. ## Ordered program ### 1. Resolve the profile graph * #111 - selected profile plus composable personality libraries ### 2. Resolve authored content and personality discovery * #110 - authored assets leave Go for their owning engine, profile, or library * #112 - aliases, provenance, affinity derivation, and compact index ### 3. Resolve role doctrine * #121 - role definitions become canonical skills with compact startup identity * #116 - Engineer and Ops ownership wording lands in those canonical role skills * #128 - conditional QA fixture-verification doctrine lands in the QA role skill and shared sealed-role asset ### 4. Complete QA fixture enforcement and proof * `coilyco-flight-deck/ward#1617` - provider-neutral, fail-closed fixture mode * `coilyco-flight-deck/agentic-os#781` - coilyco deployment binding and real director to engineer to QA proof The agent-compose doctrine lands first. Ward enforcement lands second. AOS binding and proof land third. The run does not treat role prose as authority. ### 5. Complete the external-profile feature set * #123 - generalized seats * #124 - copy contracts * #125 - custom evaluation matrices and result v2 * #126 - catalogue commands * #127 - bundle export and content-aware diff * #122 - final executable external-profile example and arbitrary-role vertical * #114 - integrated parent closes after every child passes ### 6. Refresh immutable evaluation evidence * #109 - generate all required responses serially and have independent QA score every rubric criterion ### 7. Close the program * Re-run final repository validation from canonical `main`. * Map every issue acceptance item to a commit, test, generated artifact, evaluation record, or documentation surface. * Close every completed child and parent issue. * Confirm the repository has zero open issues. * Close #115 last. ## Execution rules * The goal agent lands each independently verified slice before starting work that depends on it. * The run fixes in-scope discoveries inside the owning slice rather than filing deferrals to manufacture tracker zero. * A newly discovered independent product idea does not enter this run unless it is required for an existing acceptance criterion. * The run does not parallelize model evaluation calls. * Independent QA reviews #109. Kai reviews only an ambiguity that the rubric cannot resolve. * Consumer-specific authoring and repositories remain out of scope. * The run performs no live deployment or consumer-system mutation. * The AOS fixture proof is the only live verification action in this program. It runs inside Ward's admitted disposable fixture mode and leaves complete cleanup evidence. ## Done condition * Every issue named above is implemented or explicitly superseded by landed equivalent behavior with an acceptance mapping. * Every required validation passes on final canonical `main`. * Every release consequence required by landed commits completes through the canonical pipeline. * Ward #1617 and AOS #781 are closed with enforcement and proof evidence. * The final issue query returns zero open issues. * #115 closes last with the complete evidence audit.
coilyco-ops commented 2026-07-29 06:30:33 +00:00
Author
Member
Copy link

Acceptance audit, 2026-07-28:

  • Baseline: the run began from canonical v1.32.0 and preserved v1.x read compatibility.
  • #110, #111, and #112: authored-content ownership, profile and library composition, aliases, provenance, and affinities landed in daa9996.
  • #121, #116, and #128: canonical role skills, compact startup identity, Engineer and Ops symmetry, and QA fixture doctrine landed in cd99a44.
  • #123, #124, #125, #126, #127, and #122: generalized seats, copy contracts, complete custom matrices, result v2, catalogue inspection, verified export and diff, and the executable external profile vertical landed in daa9996.
  • #129: the CEO portfolio operating model landed in ef75fa4.
  • #109: 44 serial isolated responses, independent QA criterion evidence, exact pack digests, and retry provenance landed in fca7468. QA scored frontier 19/22 and OSS 0/22, preserving every failure.
  • #114: every implementation child is closed. The integrated example covers compose, evaluation, overlay, roster, catalogue, describe, export, diff, and verification. Legacy package, seat, result, and snapshot formats remain readable.
  • Cross-repo enforcement: Ward #1617 is closed at 2d58c641. AOS fixture admission landed at 8e5c7a75.
  • Validation: ward exec test and ward exec smoke pass from clean, synced canonical Agent Compose main at fca7468.

One program condition remains. AOS #781 is open because infrastructure #685 must restore publisher registry authentication before Ops can bootstrap the disposable fixture image and QA can return the real director-to-engineer-to-QA proof. Engineer authority cannot initiate that live action. #115 therefore remains open and closes last after those two external issues return proof and the Agent Compose open-issue query reaches zero.

Acceptance audit, 2026-07-28: * Baseline: the run began from canonical v1.32.0 and preserved v1.x read compatibility. * #110, #111, and #112: authored-content ownership, profile and library composition, aliases, provenance, and affinities landed in daa9996. * #121, #116, and #128: canonical role skills, compact startup identity, Engineer and Ops symmetry, and QA fixture doctrine landed in cd99a44. * #123, #124, #125, #126, #127, and #122: generalized seats, copy contracts, complete custom matrices, result v2, catalogue inspection, verified export and diff, and the executable external profile vertical landed in daa9996. * #129: the CEO portfolio operating model landed in ef75fa4. * #109: 44 serial isolated responses, independent QA criterion evidence, exact pack digests, and retry provenance landed in fca7468. QA scored frontier 19/22 and OSS 0/22, preserving every failure. * #114: every implementation child is closed. The integrated example covers compose, evaluation, overlay, roster, catalogue, describe, export, diff, and verification. Legacy package, seat, result, and snapshot formats remain readable. * Cross-repo enforcement: Ward #1617 is closed at 2d58c641. AOS fixture admission landed at 8e5c7a75. * Validation: ward exec test and ward exec smoke pass from clean, synced canonical Agent Compose main at fca7468. One program condition remains. AOS #781 is open because infrastructure #685 must restore publisher registry authentication before Ops can bootstrap the disposable fixture image and QA can return the real director-to-engineer-to-QA proof. Engineer authority cannot initiate that live action. #115 therefore remains open and closes last after those two external issues return proof and the Agent Compose open-issue query reaches zero.
coilyco-ops commented 2026-07-29 12:33:42 +00:00
Author
Member
Copy link

WARD-WORKFLOW: blocked 🛑

details

workflow: merge-remote-main; review summary: skipped — no candidate commit. The in-container review gate was intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit.

Blocked: infrastructure#685 still owes the attended org-secret sync and verified dev-base publication; AOS#781 therefore still owes the required disposable director→engineer→QA proof. Agent Compose has no acceptance gap: all children are closed, v1.39.0 is published, and ward exec test plus ward exec smoke pass on canonical 72c3b25. Closing #115 would violate its run contract.

Felt: clean and conclusive locally, hard-stopped at the intended authority boundary. Confidence: high. Surprise: the external gate remained open. Follow-up: Ops completes #685, QA closes #781 with proof, then rerun #115 for the closing trailer, tracker-zero audit, merge, and push.

— Codex

WARD-WORKFLOW: blocked 🛑 <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped — no candidate commit. The in-container review gate was intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit. Blocked: infrastructure#685 still owes the attended org-secret sync and verified dev-base publication; AOS#781 therefore still owes the required disposable director→engineer→QA proof. Agent Compose has no acceptance gap: all children are closed, v1.39.0 is published, and `ward exec test` plus `ward exec smoke` pass on canonical `72c3b25`. Closing #115 would violate its run contract. Felt: clean and conclusive locally, hard-stopped at the intended authority boundary. Confidence: high. Surprise: the external gate remained open. Follow-up: Ops completes #685, QA closes #781 with proof, then rerun #115 for the closing trailer, tracker-zero audit, merge, and push. — Codex </details>
coilyco-ops commented 2026-07-29 12:33:53 +00:00
Author
Member
Copy link

WARD-WORKFLOW: blocked 🛑

salvage details

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for coilyco-flight-deck/agent-compose#115 never reached main). Recover from the salvage branch below.

  • Repo: coilyco-flight-deck/agent-compose
  • Salvage branch: ward-salvage/agent-compose-74e37165
  • Pull request: not opened - salvage branch has no diff against main
  • Reason: missing same-repo closing reference
  • Container uptime at reap: 3m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Cleanup diagnostics

--- reap diagnostics ---
ward version:      v0.856.0
version source:    pinned via WARD_VERSION/--ward-version (v0.856.0)
HEAD:              72c3b25f91aa
origin/main:       72c3b25f91aa
ancestry:          HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature)
decision gate:     missing same-repo closing reference on already-landed merge-remote-main run
reason:            missing same-repo closing reference
provenance:        present
run-owned landed:  no
working tree:      clean
container uptime:  3m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose.git ward-salvage/agent-compose-74e37165
git checkout -b ward-salvage/agent-compose-74e37165 FETCH_HEAD

This salvage was blocked by a missing closing reference. To recover, amend or cherry-pick the salvaged work so the landing commit message includes closes coilyco-flight-deck/agent-compose#115, or add a small empty trailer commit with closes coilyco-flight-deck/agent-compose#115, then land the branch.

— Codex, via ward agent

WARD-WORKFLOW: blocked 🛑 <details><summary>salvage details</summary> An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for coilyco-flight-deck/agent-compose#115 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/agent-compose` - **Salvage branch:** `ward-salvage/agent-compose-74e37165` - **Pull request:** not opened - salvage branch has no diff against main - **Reason:** missing same-repo closing reference - **Container uptime at reap:** 3m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Cleanup diagnostics ``` --- reap diagnostics --- ward version: v0.856.0 version source: pinned via WARD_VERSION/--ward-version (v0.856.0) HEAD: 72c3b25f91aa origin/main: 72c3b25f91aa ancestry: HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature) decision gate: missing same-repo closing reference on already-landed merge-remote-main run reason: missing same-repo closing reference provenance: present run-owned landed: no working tree: clean container uptime: 3m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose.git ward-salvage/agent-compose-74e37165 git checkout -b ward-salvage/agent-compose-74e37165 FETCH_HEAD ``` This salvage was blocked by a missing closing reference. To recover, amend or cherry-pick the salvaged work so the landing commit message includes `closes coilyco-flight-deck/agent-compose#115`, or add a small empty trailer commit with `closes coilyco-flight-deck/agent-compose#115`, then land the branch. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-29 12:33:53 +00:00
Author
Member
Copy link

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-agent-compose-115 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: blocked 🛑`. `ward container reap` released container `engineer-codex-agent-compose-115` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-29 16:08:54 +00:00
Author
Member
Copy link

WARD-WORKFLOW: blocked 🛑

details

workflow: merge-remote-main; review summary: skipped — no candidate commit. The in-container review gate was intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit.

Blocked: canonical Agent Compose main at 72c3b25 passes ward exec test and ward exec smoke, every local child is closed, v1.39.0 is published, and #115 is its only open issue. Infrastructure #685 still owes the attended org-secret sync and verified dev-base publication; AOS #781 therefore still owes the required disposable director→engineer→QA proof. No closing commit was created because that would violate the run contract.

Felt: locally complete, cleanly stopped at the authority boundary. Confidence: high. Surprise: the external gate was unchanged after redispatch. Follow-up: Ops closes #685, QA closes #781 with proof, then rerun #115 for the closing trailer and tracker-zero audit.

— Codex

WARD-WORKFLOW: blocked 🛑 <details><summary>details</summary> workflow: merge-remote-main; review summary: skipped — no candidate commit. The in-container review gate was intentionally skipped because implementation and QA are role-separated; QA is a separate, opt-in exact-commit verification role bound to the exact candidate commit. Blocked: canonical Agent Compose `main` at `72c3b25` passes `ward exec test` and `ward exec smoke`, every local child is closed, v1.39.0 is published, and #115 is its only open issue. Infrastructure #685 still owes the attended org-secret sync and verified dev-base publication; AOS #781 therefore still owes the required disposable director→engineer→QA proof. No closing commit was created because that would violate the run contract. Felt: locally complete, cleanly stopped at the authority boundary. Confidence: high. Surprise: the external gate was unchanged after redispatch. Follow-up: Ops closes #685, QA closes #781 with proof, then rerun #115 for the closing trailer and tracker-zero audit. — Codex </details>
coilyco-ops commented 2026-07-29 16:09:05 +00:00
Author
Member
Copy link

WARD-WORKFLOW: blocked 🛑

salvage details

An ephemeral ward container (codex mode) dispatched for this issue finished but its work was not merged to main, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for coilyco-flight-deck/agent-compose#115 never reached main). Recover from the salvage branch below.

  • Repo: coilyco-flight-deck/agent-compose
  • Salvage branch: ward-salvage/agent-compose-078db83c
  • Pull request: not opened - salvage branch has no diff against main
  • Reason: missing same-repo closing reference
  • Container uptime at reap: 3m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token)

Cleanup diagnostics

--- reap diagnostics ---
ward version:      v0.856.0
version source:    pinned via WARD_VERSION/--ward-version (v0.856.0)
HEAD:              72c3b25f91aa
origin/main:       72c3b25f91aa
ancestry:          HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature)
decision gate:     missing same-repo closing reference on already-landed merge-remote-main run
reason:            missing same-repo closing reference
provenance:        present
run-owned landed:  no
working tree:      clean
container uptime:  3m (baked Forgejo PAT age proxy)
--- end reap diagnostics ---

Recover

git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose.git ward-salvage/agent-compose-078db83c
git checkout -b ward-salvage/agent-compose-078db83c FETCH_HEAD

This salvage was blocked by a missing closing reference. To recover, amend or cherry-pick the salvaged work so the landing commit message includes closes coilyco-flight-deck/agent-compose#115, or add a small empty trailer commit with closes coilyco-flight-deck/agent-compose#115, then land the branch.

— Codex, via ward agent

WARD-WORKFLOW: blocked 🛑 <details><summary>salvage details</summary> An ephemeral `ward container` (codex mode) dispatched for this issue finished but its work was **not merged to `main`**, so cleanup preserved it on a branch before teardown and reopened the issue (a closing reference for coilyco-flight-deck/agent-compose#115 never reached `main`). Recover from the salvage branch below. - **Repo:** `coilyco-flight-deck/agent-compose` - **Salvage branch:** `ward-salvage/agent-compose-078db83c` - **Pull request:** not opened - salvage branch has no diff against main - **Reason:** missing same-repo closing reference - **Container uptime at reap:** 3m (age of the baked Forgejo PAT snapshot; a long-lived container is likelier to carry a rotated token) ## Cleanup diagnostics ``` --- reap diagnostics --- ward version: v0.856.0 version source: pinned via WARD_VERSION/--ward-version (v0.856.0) HEAD: 72c3b25f91aa origin/main: 72c3b25f91aa ancestry: HEAD is ALREADY on origin/main - a salvage here is a FALSE salvage (ward#504 signature) decision gate: missing same-repo closing reference on already-landed merge-remote-main run reason: missing same-repo closing reference provenance: present run-owned landed: no working tree: clean container uptime: 3m (baked Forgejo PAT age proxy) --- end reap diagnostics --- ``` ## Recover ```bash git fetch https://forgejo.coilysiren.me/coilyco-flight-deck/agent-compose.git ward-salvage/agent-compose-078db83c git checkout -b ward-salvage/agent-compose-078db83c FETCH_HEAD ``` This salvage was blocked by a missing closing reference. To recover, amend or cherry-pick the salvaged work so the landing commit message includes `closes coilyco-flight-deck/agent-compose#115`, or add a small empty trailer commit with `closes coilyco-flight-deck/agent-compose#115`, then land the branch. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-29 16:09:05 +00:00
Author
Member
Copy link

WARD-WORKFLOW: reservation-released

release details

Run finished with WARD-WORKFLOW: blocked 🛑.

ward container reap released container engineer-codex-agent-compose-115 (--harness codex): the terminal outcome supersedes the reservation, so a later redispatch no longer needs --override-reservation.

— Codex, via ward agent

<!-- ward-agent-reservation-released --> WARD-WORKFLOW: reservation-released <details><summary>release details</summary> Run finished with `WARD-WORKFLOW: blocked 🛑`. `ward container reap` released container `engineer-codex-agent-compose-115` (`--harness codex`): the terminal outcome supersedes the reservation, so a later redispatch no longer needs `--override-reservation`. </details> <!-- ward-agent-signature --> — Codex, via `ward agent`
coilyco-ops commented 2026-07-30 09:56:46 +00:00
Author
Member
Copy link

Program update: #137 landed on canonical main at e1ac4f7 and is closed. #138 has a remotely recoverable Engineer checkpoint at caed7d4 on issue-138-designer-visual-web, with deterministic checks passing and independent Designer evaluation evidence still required before landing. The previously recorded external gates also remain open: infrastructure#685 still owes the attended org Actions-secret sync and verified dev-base publication, then agentic-os#781 owes the disposable director-to-engineer-to-QA proof. #115 therefore remains open. Its closing audit must wait for #138, infrastructure#685, and agentic-os#781, then rerun final validation and confirm tracker zero.

Program update: #137 landed on canonical main at e1ac4f7 and is closed. #138 has a remotely recoverable Engineer checkpoint at caed7d4 on issue-138-designer-visual-web, with deterministic checks passing and independent Designer evaluation evidence still required before landing. The previously recorded external gates also remain open: infrastructure#685 still owes the attended org Actions-secret sync and verified dev-base publication, then agentic-os#781 owes the disposable director-to-engineer-to-QA proof. #115 therefore remains open. Its closing audit must wait for #138, infrastructure#685, and agentic-os#781, then rerun final validation and confirm tracker zero.
coilyco-ops commented 2026-07-30 11:26:27 +00:00
Author
Member
Copy link

Superseded by the approved Agent Compose v2 program. The original v1.x tracker-zero contract no longer describes the desired product boundary or roster, so this issue is closing as superseded rather than completed. The replacement program retains a baked Core Roster, moves remote catalogue hydration plus native MCP and approval projection into AOS, cuts a major release, reduces the roster, removes unused personalities, and establishes an evaluation-led minor cadence.

Superseded by the approved Agent Compose v2 program. The original v1.x tracker-zero contract no longer describes the desired product boundary or roster, so this issue is closing as superseded rather than completed. The replacement program retains a baked Core Roster, moves remote catalogue hydration plus native MCP and approval projection into AOS, cuts a major release, reduces the roster, removes unused personalities, and establishes an evaluation-led minor cadence.
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
feat/gamedev-role
feat/boundary-omit
aos/claude/eval-context
aos/claude/eval-current-state
aos/claude/eval-refs-restore
aos/claude/eval-docs-one-page
aos/claude/personality-anchors
aos/claude/favorite-color-spread
aos/claude/personality-catalog-gaps
aos/claude/gh297-binding-skill-selector
aos/claude/personality-prose-distinctiveness
aos/claude/gh56-adopt-aos-eval
aos/claude/aw85-bands
aos/claude/xu59-just
aos/claude/xu59-eval-export
aos/claude/xu59-comment-caps
aos/claude/xu59-pr-ci
aos/claude/xu59-role-attribution
aos/claude/ck78-banner
aos/claude/mg96-fm
rescue/precommit-v0.18-uncommitted
evals/262-board-run
claude/agents-temp-clone-note
assets/compose-mark
adjacency/262-role-adjacents
chore/precommit-bump
prose/257-258-233-second-person
boundary/254-primitive-rename
fix/acompose-undefined-role-bindings
comms/rescope-counterpart
native-home/968-user-scope-projection
meld/248-evidence-acquisition
meld/231-shared-role-melds
evals/240-baseline
evals/240-model-arms
spike/claude-native-ui-surfaces
issue-225-compact-director-eval
issue-210
issue-218
issue-215-remove-context-levels
codex/luna-medium-ai-evaluation
issue-206-align-role-tiers
codex/luna-medium-roster-prose
issue-196-remove-legacy-role-providers
issue-197-role-provider-graph
feat/model-tiers
feat/remove-context-levels
issue-187
issue-178-content-communication-ownership
issue-163-designer-evals
codex/issue-794-preserve-canonical-projections
issue-163-ornith-direct-eval
issue-163-design-current-eval
issue-150-v2-baseline
issue-156-content-code
issue-150-v2-evidence
issue-150-v2-evaluation
issue-154-v2-main-integration
issue-148-remove-v1-integrations
issue-146-core-roster
issue-144-aos-catalogue-manifest
issue-152-release-classifier
issue-139-role-metadata-last
issue-138-designer-visual-web
issue-785-first-person
ward-salvage/agent-compose-078db83c
ward-salvage/agent-compose-74e37165
issue-130
recovery/2026-07-27-local-work
v2.39.0
v2.38.0
v2.37.0
v2.36.0
v2.35.0
v2.34.0
v2.33.0
v2.32.0
v2.31.0
v2.30.0
v2.29.0
v2.28.0
v2.27.0
v2.26.0
v2.25.0
v2.24.0
v2.23.0
v2.22.0
v2.21.0
v2.20.0
v2.19.0
v2.18.0
v2.17.0
v2.16.0
v2.15.0
v2.14.0
v2.13.0
v2.12.0
v2.11.0
v2.10.0
v2.9.0
v2.8.0
v2.7.0
v2.6.0
v2.5.0
v2.4.0
v2.3.0
v2.2.0
v2.1.0
v2.0.0
v1.49.0
v1.48.0
v1.47.0
v1.46.0
v1.45.0
v1.44.0
v1.43.0
v1.42.0
v1.41.0
v1.40.0
v1.39.0
v1.38.0
v1.37.0
v1.36.0
v1.35.0
v1.34.0
v1.33.0
v1.32.0
v1.31.0
v1.30.0
v1.29.0
v1.28.0
v1.27.0
v1.26.0
v1.25.0
v1.24.0
v1.23.0
v1.22.0
v1.21.0
v1.20.0
v1.19.0
v1.18.0
v1.17.0
v1.16.0
v1.15.0
v1.14.0
v1.13.0
v1.12.0
v1.11.0
v1.10.0
v1.9.0
v1.8.0
v1.7.0
v1.6.0
v1.5.0
v1.4.0
v1.3.0
v1.2.0
v1.1.0
v1.0.0
v0.70.0
v0.69.0
v0.68.0
v0.67.0
v0.66.0
v0.65.0
v0.64.0
v0.63.0
v0.62.0
v0.61.0
v0.60.0
v0.59.0
v0.58.0
v0.57.0
v0.56.0
v0.55.0
v0.54.0
v0.53.0
v0.52.0
v0.51.0
v0.50.0
v0.49.0
v0.48.0
v0.47.0
v0.46.0
v0.45.0
v0.44.0
v0.43.0
v0.42.0
v0.41.0
v0.40.0
v0.39.0
v0.38.0
v0.37.0
v0.36.0
v0.35.0
v0.34.0
v0.33.0
v0.32.0
v0.31.0
v0.30.0
v0.29.0
v0.28.0
v0.27.0
v0.26.0
v0.25.0
v0.24.0
v0.23.0
v0.22.0
v0.21.0
v0.20.0
v0.19.0
v0.18.0
v0.17.0
v0.16.0
v0.15.0
v0.14.0
v0.13.0
v0.12.0
v0.11.0
v0.10.0
v0.9.0
v0.8.0
v0.7.0
v0.6.0
v0.5.0
v0.4.1
v0.4.0
v0.3.0
v0.2.1
v0.2.0
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels
  
autonomy
async-consult
 A human needs to consult on the issue to upgrade it to headless

  
autonomy
epic
 This issue has many units of sub work - its size makes it meaningfully exclusive with other autonomy types

  
autonomy
headless
 The agent can perform the work on its own

  
autonomy
live-collab
 The agent and the human need to work together in realtime

  
coherence-core
Core review set for the warded control plane coherence milestone. These issues form the release spine; adjacent milestone issues are stretch or supporting work.

  
priority
P0
 priority tier

  
priority
P1
 priority tier

  
priority
P2
 priority tier

  
priority
P3
 priority tier

  
priority
P4
 priority tier

  
qa-fixture
Disposable issue admitted to the bounded Ward QA verification lane.

  
role/ai
requires work from the AI Engineer role

  
role/creator
requires work from Content Creator role

  
role/design
requires work from the design role

  
role/director
requires work from the director role

  
role/engineer
requires work from the engineer role

  
role/exec
requires work from the exec role

  
role/human
requires a person, and specifically not an agent seat

  
role/ops
requires work from the ops role

  
role/qa
requires work from the QA role

No labels
autonomy
async-consult
autonomy
epic
autonomy
headless
autonomy
live-collab
coherence-core
priority
P0
priority
P1
priority
P2
priority
P3
priority
P4
qa-fixture
role/ai
role/creator
role/design
role/director
role/engineer
role/exec
role/human
role/ops
role/qa
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
coilyco-flight-deck/agent-compose#115
No description provided.