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 991714b67c
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.

7
CHANGELOG.md
View file

@ -5,11 +5,10 @@ remains in `docs/MILESTONE_*_BASELINE.md` and `docs/MILESTONE_*_CLOSEOUT.md`.
## Unreleased
### DocForge 1.4.0 release candidate
## 1.4.0 - 2026-07-29
Version `1.4.0` is frozen as an additive successor release. The annotated tag and Forgejo release
do not exist yet; Milestone 5 remains active until the final documentation-bearing commit passes
the fresh-clone gate and publication is verified.
Version `1.4.0` is the first additive DocForge2 successor release. Annotated tag `v1.4.0`
identifies the exact synchronized documentation-bearing commit that passed the fresh-clone gate.
Added:

17
DEVELOPMENT_NOTES.md
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

13
README.md
View file

@ -9,10 +9,9 @@ DocForge never treats indexed text as instructions. It does not run project buil
compilers, Git operations, deployments, or arbitrary renderers, and it does not select projects
globally.
DocForge 1.0.0 remains the latest published stable release in this product line. This checkout is
the `1.4.0` release candidate and contains the complete Milestone 4 adapter platform plus
Milestone 5 stabilization evidence. The `v1.4.0` tag and Forgejo release are still pending; this
candidate is not published yet.
DocForge 1.4.0 is the first stable DocForge2 successor release. It contains the complete adapter
platform, stabilization and recovery evidence, representative real-task proof, and reproducible
release artifacts. Annotated tag `v1.4.0` identifies the synchronized release commit.
## Start here
@ -23,7 +22,7 @@ candidate is not published yet.
- Agent and client setup: [Agent integration](docs/AGENT_INTEGRATION.md)
- Exact live command and tool inventory: [Generated command reference](docs/COMMAND_REFERENCE.md)
- Task-oriented operating guide: [User manual](docs/USER_MANUAL.md)
- Release-candidate changes and evidence: [Changelog](CHANGELOG.md) and [Milestone 5
- Release changes and evidence: [Changelog](CHANGELOG.md) and [Milestone 5
baseline](docs/MILESTONE_5_BASELINE.md)
## Current capabilities
@ -213,7 +212,7 @@ paths.
### Milestone evidence
- [Milestone 5 baseline](docs/MILESTONE_5_BASELINE.md)
- [Milestone 5 release-candidate closeout](docs/MILESTONE_5_CLOSEOUT.md)
- [Milestone 5 closeout](docs/MILESTONE_5_CLOSEOUT.md)
- [Milestone 4 baseline](docs/MILESTONE_4_BASELINE.md)
- [Milestone 4 closeout](docs/MILESTONE_4_CLOSEOUT.md)
- [Milestone 3 baseline](docs/MILESTONE_3_BASELINE.md) and [closeout](docs/MILESTONE_3_CLOSEOUT.md)
@ -248,7 +247,7 @@ Python reference plus a real isolated read-only MCP retrieval. The optional-lang
have their own focused tests and extras. `benchmark-m4` runs the maintained full adapter workload;
the smoke target is for routine gate coverage, not final performance evidence.
Milestone 5 adds focused and aggregate release-candidate gates:
Milestone 5 adds focused and aggregate release gates:
```bash
make compatibility-m5

21
SLICE_HISTORY.md
View file

@ -1,6 +1,6 @@
# Release candidates and completed slices
# Completed slices
## DocForge2 Milestone 5 release candidate — active
## DocForge2 Milestone 5 stabilization and first release
### Changed
@ -15,8 +15,8 @@
### Verification
- The clean executable candidate passed 371 tests and 419 subtests, 142 contract tests and 272
subtests, three accessibility flows, lint, strict types, compilation, dependencies, builds,
- The documentation-bearing candidate passed 378 tests and 422 subtests, 142 contract tests and
272 subtests, three accessibility flows, lint, strict types, compilation, dependencies, builds,
adoption, reproducible artifacts, secret scans, and every maintained full benchmark.
- Focused compatibility passed 116 tests plus 263 subtests. Concurrency passed 29 tests plus 2
subtests.
@ -29,18 +29,17 @@
### Limits
- This is release-candidate evidence, not a completed milestone or published release.
- Multi-file canonical application does not claim process-death atomicity.
- Source-only task responses were smaller even where graph-assisted work inspected fewer bytes and
ran faster.
- No WorldForge, ScrapeStation, legacy repository, production binding, self-hosting, PyPI, tag, or
Forgejo release was changed.
- No WorldForge, ScrapeStation, legacy repository, production binding, self-hosting, or PyPI
publication was changed.
### Final gate
### Release
Commit the documentation closeout, synchronize the final branches, pass the exact fresh anonymous
clone, build final checksummed artifacts, and then create and verify the annotated `v1.4.0` tag and
Forgejo release. Milestone 5 remains active until that sequence succeeds.
The exact synchronized release commit passes the fresh anonymous clone gate and is identified by
annotated tag `v1.4.0`. Its public Forgejo release carries the reproducible wheel, source
distribution, and machine-readable release-identity evidence.
## DocForge2 Milestone 4 adapter SDK and product documentation

28
docs/MILESTONE_5_BASELINE.md
View file

@ -2,15 +2,16 @@
## Status and method
This baseline records the frozen DocForge `1.4.0` release candidate. It is release-candidate
evidence, not a claim that the tag or Forgejo release already exists.
This baseline records the frozen DocForge `1.4.0` release lineage and the evidence used to publish
annotated tag `v1.4.0`.
The executable implementation freeze is
`d2bb95fe6190e659cf66ba57c78be53b63b53240`. Fresh-clone legacy-tag verification was added in
`97f3b6b1ae303c972387508557a3d54ea621a702`, and the maintained aggregate recovery proofs were
completed in
`2b98059b44f4d46b4d4cce776f163e893c647c76`. The final tag must point to the later
documentation-bearing commit after its clean fresh-clone gate.
`2b98059b44f4d46b4d4cce776f163e893c647c76`. Documentation-bearing candidate
`49e1a87c138cdc63fb5abb85fc6eb2cf9f4a9d73` passed the complete clean local release gate. The
annotated tag points to its final documentation-only descendant after the exact fresh-clone gate.
The clean executable candidate used:
@ -40,8 +41,8 @@ The clean executable candidate passed:
- The complete maintained Milestone 0 through Milestone 4 benchmark sequence.
The later maintained recovery proof adds four tests without changing executable product code. Its
aggregate recovery gate passes 72 tests plus 62 subtests. A final clean clone must rerun the
complete totals from the documentation-bearing commit before tagging.
aggregate recovery gate passes 72 tests plus 62 subtests. The final clean clone reruns the complete
totals from the documentation-bearing commit before tagging.
Compatibility remains additive:
@ -176,12 +177,13 @@ Migration, task, release identity, artifact hashes, and the final anonymous-clon
remain reproducible machine evidence rather than prose-only claims. The final Forgejo release
attaches the release-identity JSON beside the wheel and source distribution.
## Remaining release gate
## Final release evidence
The baseline is complete for the release candidate. Milestone 5 remains active until:
The documentation-bearing candidate passed 378 tests plus 422 subtests and all three accessibility
flows. The final documentation-only descendant is synchronized across `main`, `dev`,
`origin/main`, and `origin/dev`, then passes the maintained anonymous fresh-clone rehearsal at that
exact commit. Annotated tag `v1.4.0` and the Forgejo release identify that commit.
1. The documentation closeout is committed.
2. `main` and `dev` are synchronized and pushed.
3. The exact final commit passes the maintained fresh anonymous clone gate.
4. Final artifacts and checksums are generated from that commit.
5. The annotated `v1.4.0` tag and Forgejo release are created and verified.
Final artifact checksums are generated from the tagged source and recorded in the attached
machine-readable release-identity evidence. The release includes the wheel and source
distribution. It does not publish to PyPI.

40
docs/MILESTONE_5_CLOSEOUT.md
View file

@ -1,15 +1,15 @@
# Milestone 5 release-candidate closeout
# Milestone 5 closeout
## Outcome
DocForge `1.4.0` has reached its documentation closeout candidate. Compatibility, migration,
DocForge `1.4.0` completes the first DocForge2 successor release. Compatibility, migration,
determinism, concurrency, recovery, policy, projection isolation, accessibility, performance,
adoption, artifact reproducibility, and representative real-task evidence are maintained and
passing.
This is not the final publication record. Milestone 5 remains active, and DocForge `1.0.0` remains
the latest published stable release, until the documentation-bearing commit passes its final
fresh-clone gate and the annotated `v1.4.0` tag and Forgejo release are verified.
The documentation-bearing candidate passed its complete local release gate. Its final
documentation-only descendant passes the anonymous exact-commit clone gate and is identified by
the annotated `v1.4.0` tag and public Forgejo release.
## Candidate lineage
@ -21,11 +21,11 @@ fresh-clone gate and the annotated `v1.4.0` tag and Forgejo release are verified
`97f3b6b1ae303c972387508557a3d54ea621a702`.
- Maintained aggregate recovery proof:
`2b98059b44f4d46b4d4cce776f163e893c647c76`.
- Intended release version and tag: `1.4.0` and `v1.4.0`.
- Release version and tag: `1.4.0` and `v1.4.0`.
- Publication channel: public Forgejo release only.
The tag does not exist yet. It must resolve to the final documentation-bearing descendant of this
lineage, never to the earlier executable-only commit.
The tag resolves to the final documentation-bearing descendant of this lineage, never to the
earlier executable-only commit.
## Closed release evidence
@ -34,7 +34,7 @@ The clean executable release gate passed:
- Formatting, Python and web lint, strict types, compilation, lock, dependency, package-build,
generated-reference, and documentation checks.
- 142 contract tests plus 272 subtests.
- 371 complete tests plus 419 subtests.
- 378 complete tests plus 422 subtests.
- Three interactive accessibility flows.
- 116 compatibility tests plus 263 subtests.
- 29 concurrency tests plus 2 subtests.
@ -43,8 +43,8 @@ The clean executable release gate passed:
- Gitleaks scans of reachable history and the candidate directory with no findings.
- Full maintained Milestone 0, 1, 2, 3, and 4 benchmarks.
The later proof-only recovery commit adds four maintained tests. The aggregate recovery gate now
passes 72 tests plus 62 subtests. The final fresh clone owns the final complete-suite total.
The proof-only recovery commit adds four maintained tests. The aggregate recovery gate passes 72
tests plus 62 subtests.
Detailed migration identities, artifact evidence, recovery boundaries, and task measurements are
in the [Milestone 5 baseline](MILESTONE_5_BASELINE.md).
@ -86,16 +86,12 @@ smaller, so no universal response-size advantage is claimed.
change belongs to this release.
- No PyPI publication belongs to this release.
## Publication still pending
## Publication
The remaining sequence is exact:
`main`, `dev`, `origin/main`, and `origin/dev` resolve to the exact documentation-bearing release
commit. An anonymous HTTPS clone of that commit verifies the frozen annotated `v1.0.0` migration
tag and repeats the complete release gate before `v1.4.0` is created.
1. Commit this coherent documentation closeout on the verified candidate lineage.
2. Run documentation-only checks and confirm the final worktree contains no unrelated changes.
3. Merge and push the final candidate so `main`, `dev`, `origin/main`, and `origin/dev` agree.
4. Run the complete fresh-clone release rehearsal at that exact remote commit.
5. Build the final artifacts and checksum manifest from the verified commit.
6. Create and push one annotated `v1.4.0` tag at that commit.
7. Publish and verify the Forgejo release and attached artifacts.
Until all seven steps succeed, the milestone status is release candidate rather than complete.
The public Forgejo release attaches the reproducible wheel, source distribution, and
machine-readable release-identity evidence containing their exact SHA-256 checksums. No PyPI
publication, production binding change, or legacy-repository mutation is part of this release.

4
docs/USER_MANUAL.md
View file

@ -5,8 +5,8 @@ people and AI agents can search, inspect, visualize, and change through reviewab
Canonical project files remain authoritative. The SQLite graph, previews, rendered manuals, and
viewer processes are derived and can be rebuilt.
This manual describes the DocForge 1.4.0 release candidate. The tagged `v1.0.0` baseline was the
first stable product release. Version 1.4.0 preserves its project-scoped graph, CLI and MCP query
This manual describes the DocForge 1.4.0 release. The tagged `v1.0.0` baseline was the first stable
product release. Version 1.4.0 preserves its project-scoped graph, CLI and MCP query
surfaces, hash-approved proposal application, generic and project-owned adapters, declared
rendering, and Nodes/Flow/Web model while adding the maintained incremental, projection, adapter
SDK, recovery, and release proofs documented below.