Land the next three unblocked agent-compose engineering issues #108

Closed
opened 2026-07-27 19:04:00 +00:00 by coilyco-ops · 4 comments
Member

Goal

Land the three highest-value unblocked engineer-owned issues from the current agent-compose tracker, preserving each issue as an independently verifiable slice.

Done-condition

The run ends after three issue slices have landed on canonical main, passed ward exec test and relevant smoke validation, closed their own issue, and completed their release pipeline. If fewer than three issues are safely executable, the run ends only after the remaining blockers are recorded with evidence.

Non-goals

  • No live-system mutation or deployment debugging.
  • No speculative product decisions where the tracker and repository cannot determine the intended behavior.
  • No unrelated cross-repo cleanup.
  • No bypassing release binaries, Homebrew, Scoop, validation, or issue closure.

Journal

Append-only checkpoint comments record selection reasoning, evidence, landed commits, release state, parked threads, and the next issue.

## Goal Land the three highest-value unblocked engineer-owned issues from the current agent-compose tracker, preserving each issue as an independently verifiable slice. ## Done-condition The run ends after three issue slices have landed on canonical `main`, passed `ward exec test` and relevant smoke validation, closed their own issue, and completed their release pipeline. If fewer than three issues are safely executable, the run ends only after the remaining blockers are recorded with evidence. ## Non-goals * No live-system mutation or deployment debugging. * No speculative product decisions where the tracker and repository cannot determine the intended behavior. * No unrelated cross-repo cleanup. * No bypassing release binaries, Homebrew, Scoop, validation, or issue closure. ## Journal Append-only checkpoint comments record selection reasoning, evidence, landed commits, release state, parked threads, and the next issue.
Author
Member

Checkpoint 1 selection

Selected #99 first. CEO already uses real-portfolio framing, while five role briefings and the shared evaluation prompt still name a fictional company. This issue also defines the role semantics that #97's missing Community baseline must evaluate, so landing it before evaluation work avoids immediately stale evidence.

Repository context read before editing: all twelve role KDL fragments, role briefing contract, generic and Community evaluation cases, public profile portfolio map, career hard boundaries, portfolio gap, and substrate framing.

## Checkpoint 1 selection Selected #99 first. CEO already uses real-portfolio framing, while five role briefings and the shared evaluation prompt still name a fictional company. This issue also defines the role semantics that #97's missing Community baseline must evaluate, so landing it before evaluation work avoids immediately stale evidence. Repository context read before editing: all twelve role KDL fragments, role briefing contract, generic and Community evaluation cases, public profile portfolio map, career hard boundaries, portfolio gap, and substrate framing.
Author
Member

Checkpoint 2: issue #99 landed on canonical main as 49e0a28 and closed automatically. ward exec test and ward exec smoke pass. The embedded 12-role roster now uses Kai's real open-source, platform, community, personal, and gaming portfolio, with contracting and SaaS kept evidence-qualified. Embedded evaluation cases are role-specific and portfolio-native. External person packages retain a neutral scenario. Follow-up #109 records the required refresh of historical non-Community baselines that still preserve the old prompts. Release publication is in progress.

Checkpoint 2: issue #99 landed on canonical `main` as `49e0a28` and closed automatically. `ward exec test` and `ward exec smoke` pass. The embedded 12-role roster now uses Kai's real open-source, platform, community, personal, and gaming portfolio, with contracting and SaaS kept evidence-qualified. Embedded evaluation cases are role-specific and portfolio-native. External person packages retain a neutral scenario. Follow-up #109 records the required refresh of historical non-Community baselines that still preserve the old prompts. Release publication is in progress.
Author
Member

Checkpoint 3: issue #97 landed on canonical main as 5923d2d. Fresh isolated Community/Codex cases produced frontier scores 8, 8 and OSS scores 2, 7; both OSS cases honestly fail the strict current contract. Raw responses were preserved on #97 before scoring. The baseline validates in evaluations/latest/community-codex.yaml, and both ward exec test and ward exec smoke pass. Release publication is in progress.

Checkpoint 3: issue #97 landed on canonical `main` as `5923d2d`. Fresh isolated Community/Codex cases produced frontier scores `8, 8` and OSS scores `2, 7`; both OSS cases honestly fail the strict current contract. Raw responses were preserved on #97 before scoring. The baseline validates in `evaluations/latest/community-codex.yaml`, and both `ward exec test` and `ward exec smoke` pass. Release publication is in progress.
Author
Member

Long-run contract complete.

Landed slices

  1. #99 landed as 49e0a28 and released as v0.68.0. All 12 embedded roles and role-understanding cases now use Kai's real portfolio, while contracting and SaaS stay evidence-qualified. External packages remain domain-neutral.
  2. #97 landed as 5923d2d and released as v0.69.0. The first Community/Codex baseline records honest frontier scores 8, 8 and OSS scores 2, 7, with raw responses preserved before scoring.
  3. #106 closed from canonical fleet evidence. All 32 main trees contain zero tracked legacy repo-local composed files and zero active exact-name references. Current convergence remains healthy and does not recreate them.

Verification and distribution

  • ward exec test passed for both landed commits.
  • ward exec smoke passed for both landed commits.
  • v0.68.0 and v0.69.0 each published all seven release assets.
  • Homebrew and Scoop metadata reached v0.69.0.
  • This Windows host hash-verified and installed Scoop v0.69.0. The released binary reports agent-compose version v0.69.0.
  • Canonical main is clean and synchronized at 5923d2d.

Explicit follow-ups

  • #109 owns refreshing the historical non-Community baselines whose old prompts became stale after #99.
  • coilyco-flight-deck/infrastructure#659 owns removal of a legacy Go-bin copy that can shadow Scoop on Windows. No user-level binary was deleted during this run.

The contract's three selected issues are complete, released where applicable, and closed.

Long-run contract complete. ## Landed slices 1. **#99** landed as `49e0a28` and released as **v0.68.0**. All 12 embedded roles and role-understanding cases now use Kai's real portfolio, while contracting and SaaS stay evidence-qualified. External packages remain domain-neutral. 2. **#97** landed as `5923d2d` and released as **v0.69.0**. The first Community/Codex baseline records honest frontier scores `8, 8` and OSS scores `2, 7`, with raw responses preserved before scoring. 3. **#106** closed from canonical fleet evidence. All 32 main trees contain zero tracked legacy repo-local composed files and zero active exact-name references. Current convergence remains healthy and does not recreate them. ## Verification and distribution * `ward exec test` passed for both landed commits. * `ward exec smoke` passed for both landed commits. * v0.68.0 and v0.69.0 each published all seven release assets. * Homebrew and Scoop metadata reached v0.69.0. * This Windows host hash-verified and installed Scoop v0.69.0. The released binary reports `agent-compose version v0.69.0`. * Canonical `main` is clean and synchronized at `5923d2d`. ## Explicit follow-ups * #109 owns refreshing the historical non-Community baselines whose old prompts became stale after #99. * `coilyco-flight-deck/infrastructure#659` owns removal of a legacy Go-bin copy that can shadow Scoop on Windows. No user-level binary was deleted during this run. The contract's three selected issues are complete, released where applicable, and closed.
Sign in to join this conversation.
No milestone
No project
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#108
No description provided.