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

Release DocForge 2.0.0

Browse source
This commit is contained in:
Andraxion 2026-08-02 20:52:36 -04:00
parent 7b21541ab3
commit 3d5fa4e9e8
12 changed files with 86 additions and 37 deletions
Download patch file Download diff file Expand all files Collapse all files

35
ACTIVE_SLICE.md
View file

@ -2,16 +2,20 @@
```text
Last completed milestone: 5 - stabilization and first DocForge2 release.
Release: 1.4.0.
Release: 2.0.0.
Active milestone: none.
Maintenance: Current product documentation boundary cleanup complete.
Maintenance: DocForge2 version identity and cross-identity proposal acceptance released.
Status: Complete.
```
## Current state
DocForge2 `1.4.0` is the released product baseline. Current behavior is defined by the contracts and
guides under `docs/`. `SLICE_HISTORY.md` contains DocForge2 milestone summaries only.
DocForge2 `2.0.0` is the released product baseline. Current behavior is defined by the contracts
and guides under `docs/`. `SLICE_HISTORY.md` contains DocForge2 milestone summaries only.
The release adds an explicit accepted-writer allowlist for project-owned canonical appliers.
Same-identity application remains the default. Contributor processes receive no application tool,
and successful receipts record both the proposal creator and applier.
The live documentation set contains current product contracts, current operating guidance, and
current successor milestone evidence. Superseded product plans and policy notes remain available
@ -28,7 +32,26 @@ only through repository history and are not part of normal documentation validat
graph passed.
- Focused adapter and changeset verification passed 45 tests plus 2 subtests.
## Maintenance proof - 2026-08-02
- Compared exact released commit `f9a05f868eec6c35e2b74a69467459e6ff2190bf` with exact development
commit `7b21541ab37c35dc9f3d47f631fef0c1884f9525` in isolated locked environments.
- The development repository gate passed formatting, Ruff, web lint, strict Pyright, compilation,
142 contract tests plus 272 subtests, 381 complete tests plus 422 subtests, three accessibility
flows, dependency, build, documentation, and five smoke benchmark gates.
- Compatibility passed 116 tests plus 263 subtests, concurrency and application passed 31 tests
plus 2 subtests, recovery passed 72 tests plus 62 subtests, offline fresh-wheel adoption passed,
reproducible artifact checks passed, and Git plus directory secret scans found no leaks.
- All six full maintained benchmark tracks passed. Across 66 multi-sample operations, the median
absolute development-versus-release difference was 0.71%; 65 remained within 5%, and the only
larger difference was 0.062 ms on a 1.156 ms viewer-overview operation.
- Reference-adapter graph and Logic evidence and representative-task semantic evidence matched the
release exactly. All six representative tasks retained exact answers.
- Anonymous exact-commit fresh clones of both revisions completed the full release gate offline and
remained clean. The development rehearsal completed in 283.490 seconds versus 282.091 seconds for
the release.
## Next gate
No implementation milestone is active. Create one explicit bounded contract before changing
product behavior, version identity, release state, or public integration.
No implementation milestone is active. Any additional product behavior, version identity change,
release, or public integration requires its own bounded contract.