67 lines
3.3 KiB
Markdown
67 lines
3.3 KiB
Markdown
# Changelog
|
|
|
|
Notable changes in the DocForge product line are recorded here. Historical milestone evidence
|
|
remains in `docs/MILESTONE_*_BASELINE.md` and `docs/MILESTONE_*_CLOSEOUT.md`.
|
|
|
|
## Unreleased
|
|
|
|
## 2.0.0 - 2026-08-02
|
|
|
|
- Established `2.0.0` as the unambiguous package, Python, CLI, MCP, viewer-manager, and generated
|
|
client identity for DocForge2 without changing descriptor, result, adapter, or index schemas.
|
|
- Project-owned MCP servers can explicitly authorize a canonical applier to accept exact-hash
|
|
changesets from additional configured proposal writers. The default remains same-identity
|
|
application, contributor processes receive no application tool, and application receipts record
|
|
both the proposal creator and applier.
|
|
- Retained the full DocForge 1.4 compatibility, recovery, migration, benchmark, and reproducible
|
|
artifact gates.
|
|
|
|
## 1.4.0 - 2026-07-29
|
|
|
|
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:
|
|
|
|
- One authoritative version shared by package metadata, Python, CLI, generic MCP, reference MCP,
|
|
viewer manager, generated client bindings, and release checks.
|
|
- Public adapter SDK and complete graph-plus-Logic conformance checks.
|
|
- Base Python and optional JavaScript, TypeScript, and C++ reference adapters.
|
|
- Task-shaped retrieval, generation diffs, generated client configuration, doctor checks, and
|
|
bounded response continuation.
|
|
- Independent manual, portable-graph, and live-viewer projections with immutable packages,
|
|
receipts, policy enforcement, and accessibility gates.
|
|
- Maintained compatibility, migration, concurrency, recovery, representative-task,
|
|
fresh-wheel, artifact-reproducibility, secret-scan, and benchmark gates.
|
|
- MIT licensing and Forgejo repository metadata.
|
|
|
|
Changed:
|
|
|
|
- Warm graph reads use generation-bound SQLite state without reparsing canonical project sources.
|
|
- Incremental adapters use bounded extraction caches while retaining a complete-build equivalence
|
|
oracle.
|
|
- Generated client configuration is bound to the exact DocForge version.
|
|
- Derived publication uses durable atomic replacement and fails closed on malformed, foreign,
|
|
stale, oversized, or incompatible state.
|
|
- Generic canonical application uses project-owned locking, compare-and-swap publication, and
|
|
exact-hash proposal checks while preserving raced source data.
|
|
|
|
Compatibility:
|
|
|
|
- The `docforge` distribution and Python package, `docforge` CLI, `docforge-mcp`, MCP tool names,
|
|
legacy one-method adapters, generic projects, and descriptor schema version 1 remain supported.
|
|
- Version `1.4.0` rebuilds disposable version-1 indexes as version 3 without rewriting canonical
|
|
source or active proposal bytes.
|
|
- The base wheel has no Tree-sitter dependency. Optional language extras remain explicit.
|
|
|
|
Release channels:
|
|
|
|
- The intended release channel is the public Forgejo repository and its release artifacts.
|
|
- PyPI publication is not planned because the `docforge` name is occupied by an unrelated
|
|
project.
|
|
|
|
## 1.0.0 - 2026-07-25
|
|
|
|
The first stable release established the project-scoped graph, generic Markdown/TOML adapter,
|
|
SQLite index, project-bound CLI and MCP server, reviewable exact-hash changesets, declared manual
|
|
rendering, visualization, and the original versioned compatibility surface.
|