Skip to content

Close child: merge the Chief of Staff delegation epic to main #511

Closed

Description

@barelyworkingcode

Child of #507, its close child. Filed with needs-review: it waits for the owner's approval with the epic. It runs after #508, #509 and #510 have merged into epic/507-cos-delegation.

User story

As the owner, I want the delegation epic merged to main only after its full checks pass on the epic head, so that main stays green.

Acceptance criteria

  • The repo suite (npx playwright test) passes on the epic head after main is merged in.
  • The devboxverify stack run passes on a stack e507 built from that epic head.
  • A Verified: line on this issue names that head, the repo-suite and devboxverify results and the log.
  • Each other child is closed with a comment that names its PR.
  • merge-check passes on the epic PR to main, and it merges.
  • After the merge, Chief of Staff acts for the owner while the owner is away, under a standing delegation #507 is closed and epic/507-cos-delegation is deleted.

What I'd notice

Nothing. It changes nothing a user sees.

Tasks

The close lines of the global flow, step 1. Line 1 runs after line 4.

  1. Verification task on the epic head, after line 4 (main synced in). No devlock, no console.
    1. In a checkout <wt> of the epic head: npx playwright test.
    2. Unlock the devid signing keychain (the machine notes name it), and run npm ci in <wt>.
    3. In devboxWorld: ./stack-up.sh e507 --relay <relay main checkout> --eve <wt>. It prints STACK up e507 <stack.json>.
    4. In <wt>: node devboxverify/main.js --checkout <wt> --stack <stack.json>.
    5. In devboxWorld: ./stack-down.sh e507.
    6. Post on this issue: Verified: <head sha> · repo-suite: <result> · devboxverify: <result> · log: <path>, results as the tools print them.
    7. A failure seen only against the mock macMCP: rerun the stack run with main's checkouts (global flow, step 7). Red there too: file it, and the PR may go on. Green there: the epic's bug.
  2. Any push after line 1 runs line 1 again on the new head, on a fresh stack.
  3. Every child is merged to the epic branch, with review and evidence lines in place.
  4. main is merged into the epic branch by a sync PR into that branch whose body says Closes #511. Its head is a branch sync/507-main that holds main merged in, and conflicts are resolved on it.
  5. Close each child but this one with a comment naming its PR. A child dropped on purpose is closed as not planned, and the parent carries a line Dropped: barelyworkingcode/eve#<N>: <why>. merge-check FAILs the epic PR to main while any sub-issue of Chief of Staff acts for the owner while the owner is away, under a standing delegation #507 is open, except this one.
  6. Mark the epic PR to main ready. merge-check passes on it.
  7. Merge the epic PR; its Closes #511 closes this issue. Confirm main is still green, close Chief of Staff acts for the owner while the owner is away, under a standing delegation #507 with one comment listing the merged PRs, delete the epic branch.
  8. Write the run report's final body (run-report finish).

Contract

Merge order and interfaces: #507. No code of its own.

File ownership

The union of the children's paths, for the sync PR and the epic PR only:

  • chief-of-staff-delegation.js, chief-of-staff-actions.js, chief-of-staff-provenance.js, chief-of-staff-model.js, chief-of-staff-prompt.js, chief-of-staff.js, mcp/cos.js
  • public/chief-of-staff-page.js, public/apple/chief-of-staff.css
  • docs/design-chief-of-staff.md, docs/api.md, docs/FEATURES.md
  • devboxverify/journeys-cos-delegation.js, devboxverify/journeys.js, devboxverify/README.md
  • test/static/frozen.json (Amendment 1, from Chief of Staff delegation: conditional replies matched by the model, and the devbox journey #510)
  • test/e2e/g6-cos-delegation.spec.js, test/e2e/g6-cos-delegation-act.spec.js, test/e2e/g6-cos-delegation-match.spec.js
    Plus whatever main brings into the sync PR, which merge-check judges on the files that differ from main.

Test surface

The repo suite and the devboxverify stack run on the epic head, after main is merged in. No CI runs on a PR. After merge: the owner's interactive pass of example 1 on the devbox, on the merged-for-review list.

Waits

  • Repo suite: the npx playwright test process exit.
  • Stack: the STACK up e507 <stack.json> line and the stack-up.sh exit; the devboxverify process exit; the stack-down.sh exit.
  • Sync and epic merges: merge-check's exit.

Budget

No code. Any change beyond conflict resolution in the sync PR is a stop and ask.

Amendment 1 (2026-10-18): tasks and criteria rewritten to the current close lines. No CI and no workflow_dispatch step; the full run is the repo suite plus the devboxverify stack run on slot e507, closed with a Verified: line on this issue. test/static/frozen.json added to the union.

Activity

  1. barelyworkingcode commented on Oct 18, 2026

    @barelyworkingcode
    OwnerAuthor

    Coordinator approval: owner asked, 2026-10-18. Owner is away until morning; the coordinator works to merge on main. Open questions were answered in the epic's comments (action cap: 50 sends per session).

  2. barelyworkingcode commented on Oct 18, 2026

    @barelyworkingcode
    OwnerAuthor

    Planner amendment 1 (2026-10-18): the tasks and criteria now follow the current close lines. There is no CI or workflow_dispatch step. Verification is the repo suite plus the devboxverify stack run on slot e507 on the synced epic head, closed with a Verified: line here. test/static/frozen.json was added to the union.

  3. barelyworkingcode commented on Oct 19, 2026

    @barelyworkingcode
    OwnerAuthor

    Verified: 9104ca5 · repo-suite: 762 passed · devboxverify: SUMMARY pass=42 fail=0 blocked=0 notrun=10 (screen journeys, nightly) · log: devboxverify stack runs/e507 on the test machine

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

    enhancementNew feature or requesttaskOne batch of an epic

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions