Fault-Injection Coverage Map

Fault-Injection Coverage Map An architecture diagram generated by Archify. Stress runner + CI gates · Full deck • watchdogs · Architecture component · ENTRY Stress runner + CI gates Full deck • watchdogs ENTRY Web registry · 128 portable scenarios • HTTP + batchexecute · Architecture component · WEB Web registry 128 portable scenarios • HTTP + batchexecute WEB Android registry · 74 portable scenarios • local gRPC + HTTP · Architecture component · ANDROID Android registry 74 portable scenarios • local gRPC + HTTP ANDROID Native curl registry · 10 separate Web cases • TLS + logical routing · Architecture component · REAL CURL Native curl registry 10 separate Web cases • TLS + logical routing REAL CURL R1–R14 acceptance contracts · Backend tags show implemented scope · Architecture component · CONTRACT MAP R1–R14 acceptance contracts Backend tags show implemented scope CONTRACT MAP Replay, auth & deadlines · Web + Android • R1–R2 · Architecture component · WEB + ANDROID Replay, auth & deadlines Web + Android • R1–R2 WEB + ANDROID Transfers, streams & content · Web + Android • R3–R5, R9 · Architecture component · WEB + ANDROID Transfers, streams & content Web + Android • R3–R5, R9 WEB + ANDROID Admission & shared work · Web + Android • R7–R8 · Architecture component · WEB + ANDROID Admission & shared work Web + Android • R7–R8 WEB + ANDROID Workflow state & readback · Web • R10–R11 · Architecture component · WEB Workflow state & readback Web • R10–R11 WEB Connections & TLS routing · Web + curl • R13 · Architecture component · WEB + REAL CURL Connections & TLS routing Web + curl • R13 WEB + REAL CURL REST / MCP / CLI projection · Web • R14 · Architecture component · WEB ONLY REST / MCP / CLI projection Web • R14 WEB ONLY portable selection portable selection separate job registered scenarios registered scenarios Legend Frontend Backend Database Cloud Security Message bus External

Registry coverage

  • • Portable deck: 202 unique scenarios = 128 Web + 74 Android.
  • • Native curl: 10 additional Web scenarios selected in a separate job.
  • • CI uses --require-all-scenarios so selected, executed, and skipped remain explicit.

Evidence and claim boundary • revision 02303a4de

  • • Production clients cross local sockets; every scenario records required checks, plan, fault, commit, and cleanup evidence.
  • • R6 chat is Web; R12 Drive is Android; other transfer checks span both. Adapter projections are Web only.
  • • R1–R14 are behavior contracts, not exhaustive backend promises. Cassettes and live tests remain the service-agreement authority.