Driver

PR #33 implemented the web↔api communication decision (REST + OpenAPI + generated types/Zod) but never recorded it in the canonical docs/agdr/ location. A retro code review of #33 flagged the gap — the decision lives only in the PR body and a docs/superpowers/specs/ design doc, so /agdr search can't surface it and the REST-vs-tRPC/GraphQL reasoning risks being silently re-litigated.

Scope

• Add docs/agdr/AgDR-0001-web-api-communication.md (first AgDR for marsa)
• Condense the existing design spec (docs/superpowers/specs/2026-05-26-web-api-communication-design.md) into the standard AgDR template: Context, Options Considered (tRPC / GraphQL / types-only / full SDK), Decision, Consequences, Artifacts
• Docs-only — no code or behaviour change

Acceptance Criteria

• docs/agdr/AgDR-0001-web-api-communication.md exists and renders on GitHub
• All five AgDR template sections present (Context, Options Considered, Decision, Consequences, Artifacts)
• Artifact links resolve (feat: typed REST communication layer between web and api (#11) #33, Decide on a communication method between WEB/API #11, spec + plan paths)
• Decision is discoverable via the portfolio /agdr search

Risks / Dependencies

Links back to closed #11 ("Decide on a communication method between WEB/API") and #33. No code risk — documentation only.

Glossary