Skip to content

feat: add a read-only IDE context coverage and conflict panel #57

Description

@AjnasNB

User problem

Developers can query Qarinah from the CLI and supported agent hosts, but they cannot quickly see whether the current task has direct evidence, conflicting decisions, stale project structure, or a near-exhausted context budget before an agent runs.

Proposed contract

Add a read-only editor status surface, beginning with VS Code, that shows:

  • workspace trust and capture mode;
  • verified ledger and derived-state health;
  • selected context-pack size and remaining budget;
  • direct, partial, or missing evidence coverage;
  • conflicts, superseded decisions, and stale structure scans;
  • cited source event IDs and digests;
  • one-click copy of the bounded CLI query needed to reproduce the view.

The extension should call documented read-only APIs or MCP diagnostics. It must not create trust, enable content capture, append events, execute retrieved text, or silently change project files.

Acceptance criteria

  • Explicit workspace-root selection with no parent fallback.
  • No telemetry or network dependency by default.
  • Clear empty, corrupt, revoked, and coverage-failure states.
  • Keyboard-accessible UI and screen-reader labels.
  • Packed extension smoke test plus a manual compatibility matrix.
  • Documentation for Codex, Claude Code, and plain CLI handoff from the same workspace.

Metadata

Metadata

Assignees

No one assigned

    Labels

    enhancementNew feature or requesthelp wantedExtra attention is neededintegrationAgent, governance, crawler, or platform integrationroadmapPlanned beyond the initial foundation

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions