# `docs/archive/2026/` — archived workspace docs

**Per `DOC-11`:** this directory holds living-tracker docs and
one-shot audits that have been **fully closed** and have sat
for at least one release cycle without movement. They live
here to keep `docs/inprogress/` focused on **active**
maintainer work without losing the historical record of how
the library got to where it is.

Each file moved here SHOULD:

- Have a `✅ closed <date>` header line.
- Carry a §6 (or equivalent) summary explaining what shipped
  from it.
- Cross-link the commit SHAs that closed its items where
  available.

## Index

| File | Closed | Summary |
|---|---|---|
| [`STANDARDS_AUDIT_2026-05-15.md`](STANDARDS_AUDIT_2026-05-15.md) | 2026-05-15 | Pass A — *"Does the library follow the standards?"* — walked all 14 standards docs; 5 docs got fixes, 9 were clean. Findings rolled into `docs/STANDARDS_COMPLIANCE.md`. |
| [`STANDARDS_AUDIT_2026-05-15B.md`](STANDARDS_AUDIT_2026-05-15B.md) | 2026-05-15 | Pass B — *"Do the standards earn their weight?"* — sharpened-lens review; cut 115 lines (3 docs of consumer-specific gap-closure-plan bloat) + 5 wording / markdown fixes. Rules cut: 0; rules merged: 0 (the 148-MUST set all earned its place). |
| [`SECURITY_HARDENING.md`](SECURITY_HARDENING.md) | 2026-05-14 | Library security tracker — all eight SH-* items (SH-01..SH-08, P0/P1/P2) closed in commits `ffdfeb8` / `2b6c765` / `5c7402f` / `6eefed6` and follow-ons. Covered crash-report redaction, runtime-snapshot file mode, redactor depth limit, atomic source-mutating writes, secret-scanner gate, SBOM, repr-vs-str hardening, env-var trust documentation. |
| [`v1_0_stability_audit.md`](v1_0_stability_audit.md) | 2026-05-20 | Wave-4 / E1 stability audit — AP-09 stability-tier promotion proposal. Maintainer signed off Q-11; 50 names promoted in 0.39.0. §3 resolution note captures what actually shipped vs the original 0.37.0 snapshot. |
| [`SUPERVISOR_ROLLOUT.md`](SUPERVISOR_ROLLOUT.md) | 2026-05-26 | Federation test-supervisor rollout — all 7 siblings adopted via copy-paste; supervisor then extracted to standalone sibling `mgf-test-supervisor` v0.1.0 (Codeberg); all consumers migrated to the published library; no in-tree `scripts/_mtest/` copies remain. |
| [`PROPOSAL_test_supervisor.md`](PROPOSAL_test_supervisor.md) | 2026-05-26 | Proposal answering *"library or sibling?"* for the mgf-hrb supervisor. Accepted, codified as TS-22..TS-27 in `TESTING.md`, implemented + extracted per `SUPERVISOR_ROLLOUT.md`. |
| [`V2_6_NOTIFICATION.md`](V2_6_NOTIFICATION.md) | 2026-05 | Cross-project rollout notification — project-shape taxonomy (cornerstone / sibling / consumer) + `LICENSE` as universal-four. Rollout complete. |
| [`V2_7_NOTIFICATION.md`](V2_7_NOTIFICATION.md) | 2026-05 | Cross-project rollout notification — new `DEPLOYMENT.md` standard with DEP-01..DEP-11. Rollout complete. |
| [`V2_8_NOTIFICATION.md`](V2_8_NOTIFICATION.md) | 2026-05 | Cross-project rollout notification — FEEDBACK.md as universal-five (DOC-13 + FB-01..04) + companion `DOCUMENTATION.md` additions, shipped in mgf-common 0.35.0. Rollout complete. |
| [`pre_release_check.md`](pre_release_check.md) | 2026-05-18 | Federation v1.0-readiness check, first pass 2026-05-17. Superseded by the Wave-1..4 docs (see §9 retrospective): remaining v1.0 blockers re-keyed into `v1_0_quality_gates.md` (Q-1..Q-11). Retained for the §10 PyPI-token-state ledger + the methodology. |

## How to add a doc here

The mechanics live in `docs/inprogress/README.md` —
"Promotion / demotion mechanics" table.

The shape is:

1. Confirm closure (all items ✅ OR formally deferred to a
   next-pass tracker).
2. Update the tracker's status header line.
3. `git mv docs/inprogress/<name>.md docs/archive/<year>/<name>.md`
4. Add a row above to this README.
5. Remove the row from `docs/inprogress/README.md` index.
6. Commit + push.
