Document the 1.4.0 release candidate

SLICE_HISTORY.md

@@ -1,4 +1,46 @@
-# Completed slices
+# Release candidates and completed slices
+
+## DocForge2 Milestone 5 release candidate — active
+
+### Changed
+
+- Centralized version `1.4.0` across package metadata, Python, executable surfaces, generated
+  clients, and release validation.
+- Added MIT licensing, public Forgejo metadata, reproducible artifact checks, a real archived-v1
+  migration proof, focused compatibility/concurrency/recovery gates, and representative
+  graph-assisted versus source-only task evidence.
+- Hardened durable derived publication and generic exact-hash canonical application against
+  measured race windows.
+- Added a fresh-clone rehearsal that requires the exact annotated legacy tag.
+
+### 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,
+  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.
+- Four later proof-only tests brought the recovery gate to 72 tests plus 62 subtests without
+  changing executable product code.
+- Real `v1.0.0` migration preserved canonical, graph, and proposal evidence while rebuilding the
+  disposable index from schema 1 to schema 3.
+- The lock-pinned real-package comparison returned exact answers from both workflows and measured
+  substantially less inspected source for graph-assisted work.
+
+### 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.
+
+### Final gate
+
+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.
 
 ## DocForge2 Milestone 4 adapter SDK and product documentation