feat(bin): add opt-in System One intake classification

[sctru]

Intent

Implement Phase 1 only from data/fm-intake-classify-r1/plan.md: an opt-in Jev System One intake classifier recommending ship, scout, or answer-now plus urgency, without replacing firstmate judgment or auto-spawning. Do not implement Phase 2 wake triage. Preserve the classifier scope and existing pipeline fixes while reconciling the branch against current main.

What Changed

• Add an opt-in Jev System One intake classifier that recommends ship, scout, or answer_now with urgency and implementation-authorization signals while remaining advisory and non-blocking.
• Harden crew dispatch with quota-aware spawn gates, durable dispatch history, required nested routing, and first-launch trust-dialog handling for supported harnesses.
• Reconcile supervision behavior with current main, including structured AFK mandates, orphaned wake-marker filtering, foreign-home turn-end handling, and reliable numeric tmux session targeting.

Risk Assessment

✅ Low: Captain, the Phase 1 classifier is well-bounded, advisory, and conforms to the stated intent without introducing a substantiated material source risk.

Testing

Targeted executable regressions passed, and live CLI checks proved clean opt-out behavior, one-request credential containment, and nonblocking handling of a real API rejection with no created work. No broad suite, lint, or static analysis was run. The successful Jev response and forbidden Phase 2 wake boundary remain untested because the isolated run lacked a TypeSafe credential and a Herdr-lab-scaffolded lifecycle surface.

• Live validation: ⚠️ inconclusive - 3 of 6 scenarios driven live against the product

Scenario	Result	Live	Evidence
Operator leaves classification unconfigured and the optional classifier remains inert.	✅ pass	live	Live intake-classifier CLI transcript: exit 0, empty stdout, exact intake-classify: off stderr, zero network syscalls, and zero created home files.
Operator opts in and receives a Jev ship, scout, or answer-now recommendation with urgency; implementation authorization gates only ship.	⏸️ untested	no	No TYPESAFE_API_KEY is available. Supply a scoped TypeSafe test credential through the isolated run environment and rerun against the real endpoint.
An API failure does not block intake or create work.	✅ pass	live	Live intake-classifier CLI transcript: the real endpoint returned HTTP 401; the CLI emitted structured status: error, exited 0, and created no home files.
Credential handling keeps the bearer value out of traces, command arguments, and child environments while issuing one request.	✅ pass	live	Live intake-classifier CLI transcript plus bash tests/fm-intake-classify.test.sh: the synthetic key was absent from bash tracing, curl argv, and curl's child environment; exactly one curl process ex…
A blocking recommendation remains advisory and does not auto-spawn work or replace firstmate judgment.	⏸️ untested	no	A successful live recommendation requires TYPESAFE_API_KEY. Provide a scoped test credential and monitor an isolated home while invoking the classifier.
Normal wake handling remains unchanged because Phase 2 wake triage is not introduced.	⏸️ untested	no	A live wake-path proof requires an isolated lifecycle brief scaffolded with --herdr-lab, which was not provided for this classifier-only test phase. Provide that scaffold and run it through `bin/fm-…

Evidence: Live intake-classifier CLI transcript

Source: Live intake-classifier CLI transcript

Shows opt-out behavior with zero network calls, a real API 401 returning structured status:error with exit 0, no created home files, one curl execution, and credential sent through neither trace, argv, nor child environment.

SCENARIO: classifier is opt-in and inert when unconfigured
exit: 0
stdout-bytes: 0
stderr: intake-classify: off 
network-syscalls: 0
home-created-files: 0

SCENARIO: live API rejection remains nonblocking and creates no work
exit: 0
stdout:
intake-classify:
  status: error
  reason: http 401 after 186 ms: {"detail":{"error_type":"authentication_error","message":"Cannot authenticate with the server. Please check your API key and try again."}}
stderr:
intake-classify: error (http 401 after 186 ms: {"detail":{"error_type":"authentication_error","message":"Cannot authenticate with the server. Please check your API key and try again."}})
home-created-files: 0

SCENARIO: shell tracing is disabled before credential reads
exit: 0
synthetic-key-in-trace: no
trace-first-line: + set +x
result-status: status: error

SCENARIO: bearer value is absent from executed command arguments
exit: 0
synthetic-key-in-exec-trace: no
curl-exec: 123161 execve("/usr/bin/curl", ["curl", "-q", "-sS", "--max-time", "5", "-o", "/tmp/tmp.Si7CofPMDc", "-w", "%{http_code}", "-X", "POST", "https://api.typesafe.ai/v1/systemone", "-H", "Content-Type: application/json", "-H", "@/dev/fd/3", "--data-binary", "@-"], <environment>) = 0

SCENARIO: bearer value is absent from the curl child environment
exit: 0
curl-exec-count: 1
synthetic-key-in-curl-child-environment: no

- Outcome: ⚠️ 2 warnings across 1 run (5m57s)

Pipeline

Updates from git push no-mistakes

✅ **intent** - passed

✅ No issues found.

⏭️ **Rebase** - skipped

• ⚠️ .agents/skills/afk/SKILL.md - branch carries 20 commit(s) that exist on your local main branch but were never pushed to origin/main; these may be unintended bundled work (proposed PR changes 130 file(s)):
• 25b07bc feat: add typed dispatch and crew safety gates (fix(bin): coalesce watcher signals into one wake #4)
• 87178c8 sync: merge upstream main into fork (docs: align tmux and harness guidance #3)
• 2559e9e Require configured nested dispatch profiles for crewmate child delegation (docs: polish README banner and repo housekeeping #2)
• ab359e4 fix(bin): detect and clear a harness's first-launch trust dialog in fm-spawn
• 3225182 fix(bin): tell crews to pause status across a no-mistakes pipeline step (chore: initialize no-mistakes gate #1)
• c29cc99 no-mistakes(review): test: cover unregistered tool-updates orphan-guard bypass
• 2e76bc3 no-mistakes(review): docs: pair CONTRIBUTING.md smoke test .status with .meta
• f97544e fix: never surface an orphaned status, turn-end, or check marker
• f053337 test: realign quota-gate and turnend-guard fixtures with current upstream
• 2b04211 no-mistakes(document): docs(turnend-guard): document foreign-home advisory identity gate
• aded7d3 no-mistakes(review): Gate foreign-home advisory bypass to --claude mode only
• b78f280 fix(turnend-guard): advise instead of blocking on another session's home
• 9719a46 no-mistakes(document): docs(scripts,configuration): document fm-quota-gate.sh and its env vars
• ab3dc26 no-mistakes(review): Floor fractional quota percentRemaining; fix stale MODEL-resolved comment
• 45f4066 feat(bin): add a Claude-provider quota gate for crewmate/scout spawns
• 526b9a9 no-mistakes(document): docs(scripts): list fm-dispatch-log.sh in bin toolbelt table
• 5198d49 fix(bin): blank dispatch-log repo field for secondmate spawns
• 9ddfd9d feat(bin): add a durable dispatch log across spawn and teardown
• d5f70ae no-mistakes(review): locale-safe herdr bare-prompt regex plus LC_ALL=C composer fixtures
• 4fdd73a fix(tmux): target sessions with a trailing colon so numeric session names resolve

Confirm these commits belong in this PR before approving, or manually separate the intended work onto origin/main before gating.

✅ **Review** - passed

✅ No issues found.

⚠️ **Test** - 2 warnings

• ⚠️ The central successful Jev classification could not be validated live because this isolated run has no TYPESAFE_API_KEY. Provide a scoped test credential through the process environment and rerun the live classifier scenarios; no source fix is indicated by the available evidence.
• ⚠️ live validation verdict: inconclusive (3 of 6 scenarios were driven live against the product); untested: Operator opts in and receives a Jev ship, scout, or answer-now recommendation with urgency; implementation authorization gates only ship., A blocking recommendation remains advisory and does not auto-spawn work or replace firstmate judgment., Normal wake handling remains unchanged because Phase 2 wake triage is not introduced.
• Live validation: ⚠️ inconclusive - 3 of 6 scenarios driven live against the product

Scenario	Result	Live	Evidence
Operator leaves classification unconfigured and the optional classifier remains inert.	✅ pass	live	Live intake-classifier CLI transcript: exit 0, empty stdout, exact intake-classify: off stderr, zero network syscalls, and zero created home files.
Operator opts in and receives a Jev ship, scout, or answer-now recommendation with urgency; implementation authorization gates only ship.	⏸️ untested	no	No TYPESAFE_API_KEY is available. Supply a scoped TypeSafe test credential through the isolated run environment and rerun against the real endpoint.
An API failure does not block intake or create work.	✅ pass	live	Live intake-classifier CLI transcript: the real endpoint returned HTTP 401; the CLI emitted structured status: error, exited 0, and created no home files.
Credential handling keeps the bearer value out of traces, command arguments, and child environments while issuing one request.	✅ pass	live	Live intake-classifier CLI transcript plus bash tests/fm-intake-classify.test.sh: the synthetic key was absent from bash tracing, curl argv, and curl's child environment; exactly one curl process ex…
A blocking recommendation remains advisory and does not auto-spawn work or replace firstmate judgment.	⏸️ untested	no	A successful live recommendation requires TYPESAFE_API_KEY. Provide a scoped test credential and monitor an isolated home while invoking the classifier.
Normal wake handling remains unchanged because Phase 2 wake triage is not introduced.	⏸️ untested	no	A live wake-path proof requires an isolated lifecycle brief scaffolded with --herdr-lab, which was not provided for this classifier-only test phase. Provide that scaffold and run it through `bin/fm-…

• bash tests/fm-intake-classify.test.sh
• env -u TYPESAFE_API_KEY FM_HOME=<isolated> strace -f -e trace=network bin/fm-intake-classify.sh <request> --project firstmate
• TYPESAFE_API_KEY=<synthetic-invalid> FM_HOME=<isolated> bin/fm-intake-classify.sh <request> --project firstmate against the real TypeSafe endpoint
• TYPESAFE_API_KEY=<synthetic> FM_HOME=<isolated> bash -x bin/fm-intake-classify.sh <request> --project firstmate
• Controlled-environment strace -f -v -e trace=execve of the real classifier and curl child process

✅ **Document** - passed

✅ No issues found.

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

• ⚠️ linter found issues (exit code 1)

🔧 Fix applied.
✅ Re-checked - no issues remain.

✅ **Push** - passed

✅ No issues found.