User problem
Git history and graph refresh take seconds, making the extension too slow to become the default view for fast AI-agent-driven development.
Direction
Git history is deterministic local data and must not wait on model-oriented analysis. Graph work must be cached, incremental, cancellable, and observable.
Acceptance criteria
- Use native Git/VS Code Git API for history; no AI/semantic CLI dependency.
- Do not unconditionally refetch after showing a warm cache.
- Content-address cache inputs and invalidate from repository/ref/index/worktree events.
- Debounce/coalesce concurrent refreshes and cancel stale work.
- Keep the previous usable graph visible until replacement succeeds.
- Add phase timing and a reproducible benchmark harness.
- Initial budgets: warm history <300 ms, cached graph first paint <500 ms, small structural diff <2 s, cancellation acknowledgement <250 ms (refine with evidence).
- Benchmark cold/warm behavior on representative repositories and publish results.
User problem
Git history and graph refresh take seconds, making the extension too slow to become the default view for fast AI-agent-driven development.
Direction
Git history is deterministic local data and must not wait on model-oriented analysis. Graph work must be cached, incremental, cancellable, and observable.
Acceptance criteria