Architecture decision records

ADRs capture the why behind non-obvious choices. The index lives at docs/adr/.

Current ADRs

• 0001-bootstrap-conventions — workspace layout, lint policy, release pipeline.
• 0002-chromium-version-range — exact-pin replaced by MIN_SUPPORTED_CHROMIUM_MAJOR..=MAX_SUPPORTED_CHROMIUM_MAJOR, with the contract for moving the upper bound.
• 0006-slsa-attestation-verification-path — by-digest gh attestation verify is the canonical path; the bare /attestations endpoint is not a list endpoint and is expected to 404.

When to write an ADR

• Adding a new crate to the workspace.
• Changing the dependency hierarchy or lint policy.
• Introducing a new dependency with a non-MIT/Apache license.
• Adding a [patch.crates-io] entry.
• Changing the MCP protocol surface or output format in a non-backwards-compatible way.
• Any decision you’d want to re-justify 6 months from now.

Small bug fixes and straightforward features don’t need an ADR.