feat: agent-capability gate for coupled features — typed StatusError + Supports probe/cache + netstorage add gate (option-1)
- agentapi: non-2xx GETs now surface as typed *StatusError (same text); features.go
adds Feature/SupportState/SupportCache (route probe, TTL 5m, Yes/No cached,
Unknown never cached or refused) + Client.Supports
- web: handleNetStorageAdd refuses up front (412, code agent_outdated, Hungarian
message) when the agent predates /netstorage/verify-status (= pre-0.81 add
semantics); gate runs BEFORE the single-flight claim; SupportUnknown passes
through to the existing agent-error paths
- netAddSupport page-render helper lands here; its template consumer follows
- tests: T1 gate refusal (job never starts, slot free), T2 unchanged happy path +
warm-cache negative assertion, T3 indeterminate never 'too old', T4
classification incl. the string-match trap, T6 TTL, wire-level 404-typing;
red-proofs RP1-RP4 run and reverted
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PSK5g6qYLknKj8u3QAFEr6
admin
d347dc48d2