docs(adr): adopt released truth for public documentation

[JimCollinson]

Summary

Proposes ADR-0016: public developer documentation should describe stable software the public can obtain, rather than unreleased default-branch code. A release is the explicit, auditable stake against which public claims are written and verified.

Decision

• Public documentation uses an explicit released baseline with exact provenance.
• Multi-component claims identify compatible released components, shipped dependencies, and relevant deployed-network state.
• Unreleased source may prepare future documentation but cannot support default public claims.
• Known defects and unsupported tasks are represented honestly.
• Pre-release documentation, if published, remains separate.
• A separate developer skill is outside this ADR.
• Implementation details and sequencing belong in a reviewed specification and planning documents.

Scope

This draft PR contains Proposed ADR-0016, the historical audit that motivated it, and GSD review evidence. It does not implement the policy, update rendered documentation, decide skill ownership, accept the ADR, or authorize a merge.

The ADR is 481 words including metadata and headings. It partially supersedes only the public source-selection/provenance clauses in ADR-0003, ADR-0004, and ADR-0006.

Evidence

• ADR governance and 20 governance tests pass locally.
• Exact-head ADR Governance and GitBook checks pass on this draft PR.
• Prose/sweep checks return success as branch-scope no-ops, not substantive coverage.
• Fresh concise-ADR code review passed with no findings.
• Final goal reverification passed 12/12.
• Adversarial review returned READY-WITH-NITS with no blocking findings; its wording nit was corrected and re-reviewed.
• Craft Review passed with no findings.
• Controlled Claude clean-context did not run because the panel harness refused its required caller-owned brief before inference. Jim explicitly waived clean-context for ADR-0016 only. No substitute reviewer was used.

Current gate

ADR-0016 remains Proposed and is ready for Jim’s explicit acceptance or rejection. The clean-context waiver does not authorize acceptance, merge, or implementation. A fresh release audit is required before implementation. No merge or implementation action is authorized by this draft PR.