feat: cwd hard gate, test hermeticity, opus parity withdrawal (0.0.47)

[okisdev]

summary

• both companions now reject a dispatch whose working directory was implicitly inherited and sits below the git repository root, before any job record exists; the rejection carries the shared input failure kind and names both remedies, --cwd <toplevel> to target the repository root or --cwd <subdirectory> to confirm the narrow root deliberately. the 0.0.41 post-run warning surface and the codex explicitCwd stamping leave as dead code, and grok, which had no detection at all, gains the same gate
• every terminal footer now names its sandbox root (sandbox: <cwd> between job: and the delivery lines, documented in the shared companion contract), and the orchestration rules require an explicit --cwd "<absolute workspace root>" on every dispatch that starts an engine run, current workspace included, so a drifted shell fails loudly at dispatch instead of silently sandboxing to a subtree
• the test suite stops failing on environment denials that are not regressions: a processInspectionAvailable() probe in the companion harness lets 128 job-creating tests skip with a reason when the environment denies process inspection (COMPANION_TEST_NO_PROCESS_INSPECTION=1 forces the path for verification), and gitIsolation becomes a function that injects commit.gpgsign=false with a sandbox-local home and empty template dir so host signing config cannot abort fixtures
• the 0.0.38 opus 5 parity treatment is withdrawn after production use showed opus 5 orchestrating well below fable; the rules preamble, README, and doctor now name fable the intended orchestrator with opus 5 as a fallback seat, while the mechanical invariant stays that no gate, posture, or width decision conditions on the session model

test plan

already verified

• npm test -> 1074 tests, 1073 pass, 0 fail, 1 pre-existing skip
• companion suites under COMPANION_TEST_NO_PROCESS_INSPECTION=1 -> 43 pass, 128 skipped with reason, 0 fail
• full suite under a hostile GIT_CONFIG_GLOBAL (gpgsign on, nonexistent ssh signer) -> identical to the clean run
• implicit subdirectory dispatch rejected pre-record for codex task, review, and adversarial-review and grok task and review, with explicit --cwd of toplevel or subdirectory accepted (companion suite cases)

reviewer should verify

• from a repository subdirectory, run the codex companion task subcommand without --cwd and confirm it fails with failure: input, names both --cwd remedies, and creates no job record
• confirm a foreground result footer shows sandbox: <cwd> between job: and delivery:

notes

• the sandbox: footer line is additive, but any external parser pinned to the exact footer block shape should learn it; both contract docs show the new block
• installed environments pick this up via a plugin cache refresh plus /fusion:setup to sync the rules copy