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

4.7 KiB
Raw Blame History

DocForge2 completed milestones

This file records DocForge2 milestones only. Product behavior is defined by the current contracts under docs/, not by milestone notes.

2026-07-31 - live-documentation boundary cleanup

  • Replaced the historical application-decision memo with the current canonical-application contract.
  • Removed predecessor rollout chronology and transition-only repository notes from the live documentation tree. Repository history remains the archive.
  • Updated live documentation references and validation requirements.
  • Formatting, lint, command-reference, web, and 33-page documentation checks passed. Focused adapter and changeset tests passed 45 tests plus 2 subtests.

Milestone 5 - stabilization and first release

  • Released DocForge2 1.4.0 from synchronized main and dev branches.
  • Centralized version identity across package metadata, Python, CLI, MCP, generated client configuration, and release evidence.
  • Proved compatibility, deterministic output, recovery, concurrency, security, representative task advantage, reproducible artifacts, fresh-wheel adoption, and fresh-clone installation.
  • Hardened derived publication and exact-hash canonical application against measured race windows.
  • Published the Forgejo release with reproducible wheel, source distribution, and machine-readable identity evidence.

The final documentation-bearing candidate passed 378 tests plus 422 subtests, all maintained quality and benchmark gates, three accessibility flows, secret scans, artifact reproduction, and the anonymous fresh-clone rehearsal.

Milestone 4 - adapter SDK and product documentation

  • Added the stable docforge.adapter_sdk authoring surface and complete/incremental conformance helper.
  • Added bounded Python, JavaScript, TypeScript, and C++ reference integrations.
  • Added a closed reference-adapter descriptor and fixed read-only reference MCP server.
  • Added deterministic client configuration generation for custom project adapters.
  • Generated CLI and MCP references from live implementation metadata.
  • Added onboarding, authority, descriptor, policy, adapter, rendering, security, recovery, and agent-integration documentation.

The candidate passed 347 tests plus 402 subtests, strict typing and lint gates, all maintained benchmarks, package adoption, and three accessibility flows.

Milestone 3 - independent projections

  • Separated manual rendering, portable graph rendering, and live visualization policy.
  • Added immutable render plans and packages, fixed detached workers, content-addressed publication, receipts, recovery, and accessibility gates.
  • Added semantic manual fragments with deterministic full-render equivalence.
  • Pinned live viewer reads to one validated index generation.
  • Replaced recursive cycle planning with an iterative traversal proven at 10,000 nodes.

The complete gate passed 281 tests plus 272 subtests and all maintained scale, response-size, determinism, no-work, package, and browser checks.

Milestone 2 - project policy and task-shaped context

  • Added capability-aware bootstrap, effective policy, retrieval plans, bounded context capsules, transition receipts, deterministic client fragments, and read-only diagnostics.
  • Kept normal MCP work project-bound and explicit about enabled read, proposal, application, rendering, and viewer capabilities.
  • Added fixed configuration, policy, response-size, counter, and memory contracts.

The complete gate passed 205 tests plus 120 subtests, strict types and lint, package builds, and all maintained milestone benchmarks.

Milestone 1 - fast observable core

  • Removed repeated whole-project parsing from routine warm reads.
  • Added versioned generation receipts and generation-pinned SQLite retrieval.
  • Kept complete loading and deep validation as recovery and equivalence oracles.
  • Added structured work counters proving that retrieval and status calls do not hide builds, parsing, rendering, or complete-project hashing.

The maintained 1,000-node benchmark kept exact retrieval, search, filtering, traversal, context, render status, and visualization status within their recorded latency and response-size gates.

Milestone 0 - successor foundation

  • Established the public DocForge2 repository and its main and dev workflow.
  • Froze package, CLI, MCP, adapter, schema, changeset, rendering, safety, and no-AST compatibility contracts.
  • Added repository-native aggregate, contract, build, and performance gates.
  • Recorded cold and warm latency, startup, memory, rendering, response-size, incremental, and pinned-SQLite baselines.

The aggregate gate passed formatting, Python and web lint, strict types, compilation, public contract checks, tests, dependency validation, package builds, and the maintained benchmark.