1
0
Fork 0
Code Issues Pull requests Projects Releases 2 Packages Wiki Activity Actions Pages

Close Milestone 5 for release

This commit is contained in:
Andraxion 2026-07-29 16:57:44 -04:00
parent 49e1a87c13
commit f9a05f868e
8 changed files with 83 additions and 75 deletions

View file

@ -20,7 +20,7 @@ evidence-based delegation and the milestone release actions frozen in `ACTIVE_SL
authorization does not widen the project, production-binding, or external-publication boundaries
recorded there.
## Milestone 5 — active: stabilization and first DocForge2 release
## Milestone 5 — complete: stabilization and first DocForge2 release
Milestone 5 starts from the clean, merged, and pushed Milestone 4 closeout
`6d06195950d33bcd2d712f8819bbfb3d6652ad03`. The candidate version is `1.4.0`, subject to the full
@ -71,10 +71,17 @@ bytes. Both workflows answer all three reviewed questions exactly. Graph-assiste
responses are smaller, so the evidence claims reduced inspected source and faster maintained task
latency rather than a universal response-size advantage.
Documentation closeout is now being prepared against this frozen lineage. Milestone 5 remains
active until the final documentation-bearing commit is pushed, passes the exact fresh-clone
rehearsal, and is published through one annotated `v1.4.0` tag and Forgejo release. PyPI remains
excluded.
### Release closeout
Documentation candidate `49e1a87c138cdc63fb5abb85fc6eb2cf9f4a9d73` passed the complete
release gate with 378 tests plus 422 subtests, all three accessibility flows, every focused
Milestone 5 gate, fresh-wheel adoption, reproducible artifacts, both secret scans, and every full
Milestone 0 through Milestone 4 benchmark.
The final documentation-only descendant synchronizes `main` and `dev`, passes the anonymous exact-
commit clone rehearsal, and is identified by annotated tag `v1.4.0`. The public Forgejo release
attaches the reproducible wheel, source distribution, and machine-readable release-identity
evidence. PyPI remains excluded.
## Milestone 0 — complete