This is the epics index. Every umbrella task: issue is linked here. GitHub only allows 3 pinned issues, so rather than pin individual epics we pin this one index so all of them stay visible at the top of the issue list. Each umbrella holds its own checklist of sub-issues.

Epics (umbrella tasks)

Stability & correctness

• task: Stability — crashes, segfaults, and memory safety during indexing (14 issues) #390 — Stability: crashes, segfaults, and memory safety during indexing
• task: Silent index corruption / incomplete index reported as success (3 issues) #391 — Silent index corruption / incomplete index reported as success
• task: Performance & memory on large repositories #593 — Performance & memory on large repositories (new)

Extraction & query quality

• task: Parsing & extraction quality — language/format coverage gaps #592 — Parsing & extraction quality: language/format coverage gaps (new)
• task: Graph queries & trace_path resolution #594 — Graph queries & trace_path resolution (new)

Platform & integration

• task: Windows platform issues (8 bugs) #394 — Windows platform issues
• task: Editor / agent / MCP-client integration (6 issues) #395 — Editor / agent / MCP-client integration

UX & architecture

• task: UX, install, watcher, docs & small features (15 issues) #396 — UX, install, watcher, docs & small features
• task: Architecture — workspaces, cross-repo, worktrees, benchmarks (6 issues) #398 — Architecture: workspaces, cross-repo, worktrees, benchmarks

Conventions

• Issues with an open PR are tracked via that PR (the PR is the unit of work) and are listed under each umbrella's "Tracked via open PR" section rather than as open checklist items.
• A sub-issue is checked off here/in its umbrella only when fixed-and-merged or closed with rationale.

Release trains

• GitHub milestones are the release-routing source of truth; we do not duplicate them with version labels.
• All current bug and stability work, including items awaiting reporter feedback, targets 0.10.0-rc. The next feature and architecture train is 0.11.0-rc unless work has already been accepted into 0.10.0-rc.
• Patch versions are reserved for narrow, compatible fixes. Substantial architecture, feature, behavior, and stabilization work advances the minor version and uses -rc.N previews before stable.
• The published v0.9.1-rc.1 remains an immutable historical release. Future previews use v0.10.0-rc.N, followed later by v0.11.0-rc.N.

Stale watch — automated via awaiting-reporter (PR #596)

Issues where the reporter owes the next step are labeled awaiting-reporter. Once PR #596 merges, the stale bot warns at 21 days idle and closes at 35 (a reporter comment resets it). Labeled 2026-06-24:

Not awaiting-reporter (owner-action-pending — we owe the work, do not auto-close): #382 (Java AST props — "will investigate"), #408 (workspace zero-edges — reporter already supplied the repro).