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

Document the DocForge 1.0 release

Browse source
This commit is contained in:
Andraxion 2026-07-25 18:33:42 -04:00
parent 593c173b45
commit 82b3b90521
7 changed files with 38 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/CONTRACT.md
View file

@ -19,7 +19,7 @@ commit when Git is available; it cannot change repository state.
- Result envelope: `schemas/result.schema.json`, version 1.
- Changeset schema: `schemas/changeset.schema.json`, version 1.
- Index schema: version 1, disposable and reproducible.
- Core, CLI, and MCP server: version 0.15.0.
- Core, CLI, and MCP server: version 1.0.0.
Schema files describe the generic interchange contract. Runtime validation remains responsible for
path confinement, source hashing, relationship resolution, dependency cycles, project limits, stale

6
docs/MCP_CONTRACT.md
View file

@ -103,8 +103,10 @@ disconnected by a hidden node while retaining descendants that still lead to the
actions open the indexed source path
and navigate to recognized anchors. Nodes presents the
bounded neighborhood with relation-specific colors, line patterns, directional symbols, and a
visible key. Its navigation groups the focus, nodes reachable through outgoing edges, and remaining
incoming or lateral context. Flow presents semantic ancestry with relation-aware direction.
visible key. Semantic cards identify the focus and relation-derived Structure, Behavior,
Dependency, Execution, Data, Evidence, Context, and Related contributors. Cards display readable
leaf names and node kinds without truncation; complete qualified identities remain available in
tooltips and inspectors. Flow presents semantic ancestry with relation-aware direction.
Web follows bounded structural, dependency, execution, evidence, and contextual contributors into
the focus. Direct focus-owned members and execution dependencies become adjacent contributor
branches without expanding unrelated siblings. The relationship key is regenerated from each

6
docs/USER_MANUAL.md
View file

@ -5,6 +5,10 @@ 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.
DocForge 1.0.0 is the first stable product release. It includes the project-scoped graph,
CLI and MCP query surfaces, hash-approved proposal application, generic and project-owned adapters,
declared rendering, and the Nodes/Flow/Web visualization model documented below.
## Features
- Project-bound Markdown and TOML documentation graphs with stable node IDs.
@ -562,7 +566,7 @@ ambiguous adapter evidence.
### Full inspector content does not fit
DocForge 0.15 uses a fixed header and footer with a scrollable inspector body. If an older page is
DocForge 1.0 uses a fixed header and footer with a scrollable inspector body. If an older page is
still open, stop and reopen the visualization so it loads the current `graph-browser@15` template.
### Render output is stale