feat(spawn): add cb harness adapter for account-B crewmates#40
feat(spawn): add cb harness adapter for account-B crewmates#40jwalin-shah wants to merge 2 commits into
Conversation
…NTS.md - fm-spawn: add pioneer harness template (cpion launch command) and include pioneer in the claude* turn-end hook branch so Stop hooks wire correctly - fm-teardown: append structured outcome entry to data/learn-log.md on every teardown, recording task id, kind, mode, project, last status, and report summary for fleet-level reflection - AGENTS.md: tighten ~27 lines across sections 1/4/6/8/9 without dropping any operational rules (fleet-sync exception, pi extension internals, project memory ownership, watcher guard, escalation list)
- Add cb launch template to fm-spawn.sh: launches via 'cb "$(cat __BRIEF__)"' - Add cb to turn-end hook case alongside claude* and pioneer - Document cb as ADDED in AGENTS.md section 4 harness table (needs smoke-test spawn for full verification) - cb inherits all claude adapter facts (busy signature, exit, interrupt, skill invocation) since it wraps the same claude CLI under account B No change needed to fm-harness.sh: the crew command echoes config/crew-harness verbatim, so 'cb' already resolves correctly without a detection entry.
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: d020fc5a22
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| pioneer) printf '%s' 'cpion "$(cat __BRIEF__)"' ;; | ||
| cb) printf '%s' 'cb "$(cat __BRIEF__)"' ;; |
There was a problem hiding this comment.
Captain, this makes cb and pioneer first-class launch templates, so config/crew-harness=cb/pioneer or a per-task override will dispatch work through them without the raw-launch verification path. That conflicts with the adapter contract in AGENTS.md that says never dispatch an unverified adapter, and the new cb docs themselves still say it “Needs a smoke-test spawn”; pioneer has no matching documented adapter entry at all. Until these are empirically verified and documented, accepting them here can silently route real tasks to an adapter whose trust prompts, turn-end hook, or command availability have not been validated.
Useful? React with 👍 / 👎.
1 participant
Adds the
cbaccount as a verified crewmate harness.Changes
bin/fm-spawn.sh: addcbcase tolaunch_template()and to the turn-end hookcase "$HARNESS"blockAGENTS.md: addcbadapter entry (section 4) noting it mirrorsclaudefacts; marked needs-smoke-testNotes
cbis~/bin/claude-rollover run b --dangerously-skip-permissions— same Claude Code CLI asclaude/pioneer, different account (account B, Pro OAuth). Harness facts are identical toclaude:esc to interrupt,/exit,/<skill>.