From 693a8aaa4ea8ad8161eb9b947c99b000ca7ac9b9 Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 25 Feb 2026 01:51:02 -0700 Subject: [PATCH 1/2] docs: move roadmap files into docs/roadmap/ Move BACKLOG.md, ROADMAP.md, and llm-integration.md from docs/ to docs/roadmap/ for better organization. Update references in README.md, STABILITY.md, and BACKLOG.md. --- README.md | 2 +- STABILITY.md | 2 +- docs/{ => roadmap}/BACKLOG.md | 2 +- docs/{ => roadmap}/ROADMAP.md | 0 docs/{ => roadmap}/llm-integration.md | 0 5 files changed, 3 insertions(+), 3 deletions(-) rename docs/{ => roadmap}/BACKLOG.md (98%) rename docs/{ => roadmap}/ROADMAP.md (100%) rename docs/{ => roadmap}/llm-integration.md (100%) diff --git a/README.md b/README.md index 2891050c..537fa178 100644 --- a/README.md +++ b/README.md @@ -604,7 +604,7 @@ const { results: fused } = await multiSearchData( ## πŸ—ΊοΈ Roadmap -See **[ROADMAP.md](ROADMAP.md)** for the full development roadmap and **[STABILITY.md](STABILITY.md)** for the stability policy and versioning guarantees. Current plan: +See **[ROADMAP.md](docs/roadmap/ROADMAP.md)** for the full development roadmap and **[STABILITY.md](STABILITY.md)** for the stability policy and versioning guarantees. Current plan: 1. ~~**Rust Core**~~ β€” **Complete** (v1.3.0) β€” native tree-sitter parsing via napi-rs, parallel multi-core parsing, incremental re-parsing, import resolution & cycle detection in Rust 2. ~~**Foundation Hardening**~~ β€” **Complete** (v1.4.0) β€” parser registry, 12-tool MCP server with multi-repo support, test coverage 62%β†’75%, `apiKeyCommand` secret resolution, global repo registry diff --git a/STABILITY.md b/STABILITY.md index de0f7de4..a5d4b2a4 100644 --- a/STABILITY.md +++ b/STABILITY.md @@ -1,7 +1,7 @@ # Stability Policy > **Status: Anticipated β€” not yet active.** -> This policy describes the stability guarantees codegraph *will* provide once the public API surface stabilizes after [Phase 3 β€” Architectural Refactoring](ROADMAP.md). Until then, breaking changes may still land in minor releases as the internal architecture is restructured. +> This policy describes the stability guarantees codegraph *will* provide once the public API surface stabilizes after [Phase 3 β€” Architectural Refactoring](docs/roadmap/ROADMAP.md). Until then, breaking changes may still land in minor releases as the internal architecture is restructured. --- diff --git a/docs/BACKLOG.md b/docs/roadmap/BACKLOG.md similarity index 98% rename from docs/BACKLOG.md rename to docs/roadmap/BACKLOG.md index 5084b8d9..b10af104 100644 --- a/docs/BACKLOG.md +++ b/docs/roadmap/BACKLOG.md @@ -1,7 +1,7 @@ # Codegraph Feature Backlog **Last updated:** 2026-02-25 -**Source:** Features derived from [COMPETITIVE_ANALYSIS.md](../generated/COMPETITIVE_ANALYSIS.md) and internal roadmap discussions. +**Source:** Features derived from [COMPETITIVE_ANALYSIS.md](../../generated/COMPETITIVE_ANALYSIS.md) and internal roadmap discussions. --- diff --git a/docs/ROADMAP.md b/docs/roadmap/ROADMAP.md similarity index 100% rename from docs/ROADMAP.md rename to docs/roadmap/ROADMAP.md diff --git a/docs/llm-integration.md b/docs/roadmap/llm-integration.md similarity index 100% rename from docs/llm-integration.md rename to docs/roadmap/llm-integration.md From dc08aee9aa8a19c996ef706aa0a8cef7563c3d5c Mon Sep 17 00:00:00 2001 From: "github-actions[bot]" Date: Wed, 25 Feb 2026 02:01:17 -0700 Subject: [PATCH 2/2] fix: correct broken FOUNDATION.md relative link in BACKLOG.md --- docs/roadmap/BACKLOG.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/roadmap/BACKLOG.md b/docs/roadmap/BACKLOG.md index b10af104..efd66c29 100644 --- a/docs/roadmap/BACKLOG.md +++ b/docs/roadmap/BACKLOG.md @@ -12,7 +12,7 @@ Each item has a short title, description, category, expected benefit, and four a | Column | Meaning | |--------|---------| | **Zero-dep** | Can this feature be implemented without adding new runtime dependencies to the project? A checkmark means it builds entirely on what we already ship (tree-sitter, SQLite, existing AST). Blank means it needs evaluation. Features that require new deps raise the install footprint and maintenance burden β€” they need stronger justification. | -| **Foundation-aligned** | Does this feature align with the [FOUNDATION.md](../FOUNDATION.md) core principles? Specifically: does it keep the graph always-current (P1), maintain zero-cost core with optional LLM enhancement (P4), respect embeddable-first design (P5), and stay honest about what we are β€” a code intelligence engine, not an application (P8)? A checkmark means full alignment. An X means it conflicts with at least one principle and needs a deliberate exception. | +| **Foundation-aligned** | Does this feature align with the [FOUNDATION.md](../../FOUNDATION.md) core principles? Specifically: does it keep the graph always-current (P1), maintain zero-cost core with optional LLM enhancement (P4), respect embeddable-first design (P5), and stay honest about what we are β€” a code intelligence engine, not an application (P8)? A checkmark means full alignment. An X means it conflicts with at least one principle and needs a deliberate exception. | | **Problem-fit (1-5)** | How directly does this feature address the core problem from our README: *AI coding assistants waste tokens re-orienting themselves in large codebases, hallucinate dependencies, and miss blast radius.* A 5 means it directly reduces token waste, prevents hallucinated deps, or catches breakage. A 1 means it's tangential β€” nice to have but doesn't solve the stated problem. | | **Breaking** | Is this a breaking change? `Yes` means existing CLI output, API signatures, DB schema, or MCP tool contracts change in incompatible ways. `No` means it's purely additive. Breaking changes require a major version bump. |