Technical roadmap #8

New issue

Open

opened 2026-09-21 01:14:14 +00:00 by barrettruth · 0 comments

barrettruth commented

2026-09-21 01:14:14 +00:00

Owner

Original issue: source #8
Original author: barrettruth
Original date: 2026-08-26T07:00:58Z

Capability epics, ordered by the shared state they require:

Bazelrc 8.7 authoring — #6. The v0.2.0 milestone; independent of the main-language semantic catalog.
BUILD/Starlark semantic authoring — #26. One immutable rule/attribute catalog unlocks completion, hover, and signature help.
Correctness and repair — #3. Explicit resolution states precede diagnostics and code actions.
Refactoring — a snapshot-based planner precedes file/package move edits.
Distribution — editor integration #9 and packaging #15 follow a stable user-facing surface.

Established foundations include bounded request work, immutable request snapshots, filesystem refresh, the Bazel actor, evaluated graph/repository publication, and the Bazelrc 8.7 parser/catalog/router. Repository architecture invariants live in AGENTS.md; dependency detail lives in ROADMAP.md.

Wrong is worse than absent: no Bazel or filesystem operation runs in a request handler, the server remains useful without Bazel, and an unavailable answer is not presented as a proven negative.

> Original issue: source #8 > Original author: `barrettruth` > Original date: 2026-08-26T07:00:58Z Capability epics, ordered by the shared state they require: 1. **Bazelrc 8.7 authoring** — #6. The v0.2.0 milestone; independent of the main-language semantic catalog. 2. **BUILD/Starlark semantic authoring** — #26. One immutable rule/attribute catalog unlocks completion, hover, and signature help. 3. **Correctness and repair** — #3. Explicit resolution states precede diagnostics and code actions. 4. **Refactoring** — a snapshot-based planner precedes file/package move edits. 5. **Distribution** — editor integration #9 and packaging #15 follow a stable user-facing surface. Established foundations include bounded request work, immutable request snapshots, filesystem refresh, the Bazel actor, evaluated graph/repository publication, and the Bazelrc 8.7 parser/catalog/router. Repository architecture invariants live in `AGENTS.md`; dependency detail lives in `ROADMAP.md`. Wrong is worse than absent: no Bazel or filesystem operation runs in a request handler, the server remains useful without Bazel, and an unavailable answer is not presented as a proven negative.

barrettruth added the

epic

label

2026-09-21 01:14:14 +00:00