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

Close Milestone 5 for release

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

28
ACTIVE_SLICE.md
View file

@ -1,22 +1,22 @@
# Milestone state
```text
Last completed milestone: 4 — adapter SDK and product documentation.
Baseline: 6d06195950d33bcd2d712f8819bbfb3d6652ad03 on main, dev, origin/main, and origin/dev.
Active milestone: 5 — stabilization and first DocForge2 release.
Last completed milestone: 5 — stabilization and first DocForge2 release.
Baseline: annotated v1.4.0 release commit on main, dev, origin/main, and origin/dev.
Active milestone: none.
Outcome: Compatibility, determinism, recovery, security, performance, and representative task advantage are proven for the first successor release.
Status: Active.
Release candidate: 1.4.0, subject to every gate below.
Status: Complete.
Release: 1.4.0.
```
## Authority
This contract activates Milestone 5 from the clean, merged, and pushed Milestone 4 closeout. The
This contract activated Milestone 5 from the clean, merged, and pushed Milestone 4 closeout. The
roadmap in `/home/andraxion/.openclaw/workspace/DocForgeOutline.md` supplies direction; this file
freezes the executable scope and acceptance criteria.
`main` remains the Milestone 4 baseline until the complete Milestone 5 release candidate passes.
Implementation occurs on `dev`.
The completed release synchronizes `main` and `dev` at the documentation-bearing commit identified
by annotated tag `v1.4.0`.
## Required release evidence
@ -123,6 +123,12 @@ source-only answers for all reviewed tasks.
The later proof-only recovery commit adds four maintained tests without changing executable
product code. The current recovery aggregate passes 72 tests plus 62 subtests.
Milestone 5 remains active. Documentation closeout, final branch synchronization, a fresh
anonymous clone at the exact documentation-bearing remote commit, final artifact checksums, the
annotated `v1.4.0` tag, and the Forgejo release are still pending. No PyPI publication is planned.
The documentation-bearing candidate `49e1a87c138cdc63fb5abb85fc6eb2cf9f4a9d73` passed the complete
local release gate with 378 tests plus 422 subtests, all three accessibility flows, and every
focused and full gate above. Its final documentation-only descendant is the commit identified by
annotated tag `v1.4.0`; that exact remote commit passes the anonymous fresh-clone rehearsal before
tagging.
The public Forgejo release publishes the reproducible wheel, source distribution, and
machine-readable release-identity evidence from the tagged commit. `main`, `dev`, `origin/main`,
and `origin/dev` resolve to that same commit. No PyPI publication was performed.