fix(adapters): bound the conformance probe, honor declared timeouts, scratch cwd

[pacphi]

Summary

adrianco ran a real Hermes adapter against ak host adapters conformance on alpha.42 (PR #131 follow-up) and found the activity-routing tier can't pass on a local model:

• Bounded probe — the probe prompt ("conformance harness probe") is open-ended, so an agentic host reads it as a task and does real work (4+ minutes) instead of proving the transport. Now "Reply with exactly: OK".
• Declared timeout honored — the outer runner budget was hardcoded to the 120s default regardless of the manifest's own declared execution.run.hook.timeoutMs, so a local-model adapter with a longer declared budget could never use it. Now honored by default; ak host adapters conformance --timeout <ms> is available as an explicit override.
• Scratch cwd — activity-routing/primary-eligible now run their worker in a throwaway temp directory instead of the operator's process.cwd().

Also documents two things from his report that need no code fix: the nativeMcpConfig/nativeGuidance author-trap (capabilities describe what the adapter wires, not what the host can do in principle), and that AK_WORKER_CWD is advisory, not a sandbox boundary.

Held for a follow-up branch, pending his design input requested in the PR #131 comment: detection.binPath (his venv-install finding) and hook-content hash pinning (his consent-drift finding).

Test plan

• pnpm run check (typecheck + lint + markdownlint + build + full test suite) — 1993/1998 passed, 0 failures (5 skips are win32-only)
• New tests: bounded probe prompt reaches the real hook, scratch cwd is real+isolated+cleaned-up, explicit --timeout override reaches the worker, declared manifest timeout is honored without an override, CLI --timeout flag parses/forwards/rejects invalid input

🤖 Generated with Claude Code