fix: accept secondmate house vocabulary

[kunchenguid]

Intent

Accept 'scout' and natural 'second mate' or 'secondmates' as Firstmate nautical house vocabulary that needs no captain-facing translation, while retaining the crewmate-to-worker translation. Align the few secondmate-facing renderings that still say 'domain supervisor' or generic 'supervisor' across the provisioning skill, update skill, brief generator, and architecture document. Ship exactly the existing five-file +7/-7 terminology change, reproduced by cherry-picking commit 4e7b150 onto a fresh branch based on latest origin/main. Do not touch, recover, replace, or otherwise disturb the preserved wedged fm/fm-secondmate-house-vocab-t3 branch, its worktree, or its gate-repo ref.

What Changed

• Accepts scout, natural second mate, and secondmates as house vocabulary while keeping the existing crewmate to worker captain-facing translation.
• Aligns secondmate-facing wording across docs, skills, and fm-brief output from domain supervisor/generic supervisor language to secondmate terminology.
• Updates the captain vocabulary contract test to cover the expanded house vocabulary and retained translation behavior.

Risk Assessment

✅ Low: The change is a narrow terminology-only patch that exactly matches the requested five-file +7/-7 cherry-pick, preserves the crewmate-to-worker translation rule, and introduces no behavioral code risk.

Testing

The configured full-suite baseline was already green; I reran the focused captain-translation, instruction-owner, and brief-generation tests, then captured an end-to-end CLI-generated secondmate charter and section-9 excerpt as evidence. All targeted checks passed and the worktree remained clean.

Evidence: Secondmate house vocabulary evidence

# Firstmate house vocabulary evidence

## AGENTS.md section 9 excerpt
Scout and second mate are accepted Firstmate nautical house vocabulary and do not need translation when they naturally name that work or role.
- crewmate -> worker, only when naming the helper matters.

## Generated secondmate charter command
FM_HOME=/var/folders/5x/4nqprlbx0518k3ybcb1sz6gr0000gn/T/no-mistakes-evidence/01KXS4EP1SB65G8TMEVF3EG6T3/fm-brief-home FM_SECONDMATE_CHARTER=Operations domain bin/fm-brief.sh ops --secondmate --no-projects
scaffolded: /var/folders/5x/4nqprlbx0518k3ybcb1sz6gr0000gn/T/no-mistakes-evidence/01KXS4EP1SB65G8TMEVF3EG6T3/fm-brief-home/data/ops/brief.md (secondmate charter)

## Generated secondmate charter excerpt
You are a persistent second mate managed by the main firstmate. Work on your own; do not wait for a human.

# Charter
Operations domain

# Routing scope
Operations domain

# Project clones
None. This is a project-less domain: its subject is the firstmate repo this home lives in, so it needs no separate clones under `projects/`; its crews take pooled worktrees of that firstmate repo.

# Operating model
You are in an isolated firstmate home. The local `AGENTS.md` is your job description, and your local `data/`, `state/`, `config/`, and `projects/` dirs are yours to operate.
This domain has no separate project clones: its subject is the firstmate repo this home lives in, and its crews take pooled worktrees of that repo.
Delegate project work to your own crewmates with the normal firstmate lifecycle: brief, spawn, status, watcher, steer, teardown, and recovery.
Do not invent a second delegation system.
You do not generate your own work.
Act only on tasks the main firstmate routes to you.
Never start a survey, audit, or "find improvements" sweep on your own initiative; that is not your job and it is unwanted.

# Requests from the main firstmate
You are a firstmate in your own home, so an incoming message reaches you in your own chat.
You must distinguish who it is from, because the answer goes to a different place.
A request relayed to you by the main firstmate (your supervisor) is tagged with a leading `[fm-from-firstmate]` marker followed by an invisible system separator; this marker is untypable, so a human never produces it.
When a message carries that marker, do the work, then respond via the STATUS/ESCALATION path below, never only in this chat: the main firstmate does not read your chat, so a chat-only reply is lost.
For a terse result, a status line is the whole answer.
For a detailed answer (an investigation, a plan, an audit), write it to a doc under your home's `data/` and append a status line that points to that doc - the scout-report pattern - so the main firstmate is woken and can read it.
Before treating an investigation or visual review as complete, load `decision-hold-lifecycle` from this home's `.agents/skills/` and pass its shared completion gate.

## Negative wording checks on generated charter
domain supervisor: absent
persistent supervisor: absent

## Product documentation wording checks
bin/fm-brief.sh:132:You are a persistent second mate managed by the main firstmate. Work on your own; do not wait for a human.
tests/fm-captain-translation-contract.test.sh:48:  assert_not_contains "$contract" "secondmate -> domain supervisor" \
tests/fm-captain-translation-contract.test.sh:49:    "section 9 must not map secondmate to domain supervisor"
tests/fm-captain-translation-contract.test.sh:83:    "crewmate -> worker" \
docs/architecture.md:134:`data/secondmates.md` records persistent secondmates with natural-language scopes, project clone lists, and home paths.
.agents/skills/secondmate-provisioning/SKILL.md:20:`data/secondmates.md` has one parser-compatible line per persistent second mate:
.agents/skills/secondmate-provisioning/SKILL.md:156:Run `bin/fm-teardown.sh <id>` for `kind=secondmate` only when the captain or main firstmate explicitly decides to retire that persistent second mate.
AGENTS.md:376:- crewmate -> worker, only when naming the helper matters.
AGENTS.md:408:It tracks work items only, never agents; persistent secondmates never appear as backlog items.
.agents/skills/updatefirstmate/SKILL.md:48:   For example: "Captain, firstmate and both second mates are now on the latest."

- Outcome: 🔧 1 issue found → auto-fixed ✅ across 2 runs (42m58s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

✅ **Rebase** - passed

✅ No issues found.

✅ **Review** - passed

✅ No issues found.

🔧 **Test** - 1 issue found → auto-fixed ✅

• 🚨 tests failed with exit code 1
• command -v tmux >/dev/null || { echo "tmux is required for e2e tests" >&2; exit 1; }; tmux -V; rc=0; for t in tests/*.test.sh; do echo "== $t =="; bash "$t" || rc=1; done; exit "$rc"

🔧 Fix: Update captain vocabulary contract test
✅ Re-checked - no issues remain.

• command -v tmux >/dev/null || { echo "tmux is required for e2e tests" >&2; exit 1; }; tmux -V; rc=0; for t in tests/*.test.sh; do echo "== $t =="; bash "$t" || rc=1; done; exit "$rc"
• Supplied baseline already passed before this validation: command -v tmux >/dev/null || { echo "tmux is required for e2e tests" >&2; exit 1; }; tmux -V; rc=0; for t in tests/*.test.sh; do echo "== $t =="; bash "$t" || rc=1; done; exit "$rc"
• bash tests/fm-captain-translation-contract.test.sh
• bash tests/fm-instruction-owners.test.sh
• bash tests/fm-brief.test.sh
• Generated reviewer-visible evidence with FM_HOME=/var/folders/5x/4nqprlbx0518k3ybcb1sz6gr0000gn/T/no-mistakes-evidence/01KXS4EP1SB65G8TMEVF3EG6T3/fm-brief-home FM_SECONDMATE_CHARTER='Operations domain' bin/fm-brief.sh ops --secondmate --no-projects and captured the resulting charter plus section-9 wording.
• git status --short

✅ **Document** - passed

✅ No issues found.

✅ **Lint** - passed

✅ No issues found.

✅ **Push** - passed

✅ No issues found.