v0.3.11 — Sidebar hydration on activate

Sidebar hydration on activate (DG-103 A). Closes a real-world UX bug reported in feedback after using v0.3.10 on a 105-finding project: when you closed the workspace and reopened it later, the SYNAPTIC Sentinel sidebar always showed the empty state (Run "Scan Workspace" to see findings here) — as if no scan had ever run — even though the previous scan + triage + cost data was sitting in <workspace>/.sentinel/colony.db.

After v0.3.11, the sidebar rehydrates automatically on activate from the cached colony.db, with cost: 0 (no scanners re-run, no LLM re-invoked).

Added

• Sidebar hydration on activate — when the extension activates in a workspace whose .sentinel/colony.db (or legacy .synaptic-sentinel/colony.db) already contains a previous scan, the sidebar restores silently:
  • All findings from the latest scan grouped into the four buckets (To fix · TP / Inconclusive / Untriaged / Already false positive)
  • The triage verdict + context + remediation on every previously-triaged finding
  • The cost card from the last triage session
  • Diagnostics in the editor and the status bar counter
• synaptic-sentinel show CLI command — reconstructs the tome of the latest scan from colony.db without running scanners or LLM (cost: 0). Used internally by the hydration above; also exposed for scripting:
  • synaptic-sentinel show --path <dir> → JSON tome to stdout
  • synaptic-sentinel show --path <dir> --export <file> → JSON tome to a file

Notes

• Scope only DG-103 A. No changes to the Scout Layer, Brain Layer adapters, benchmark runner, sidebar layout, or colony.db schema.
• The hydration is best-effort defensive: if colony.db is missing, corrupted, has a schema mismatch, or any other read failure, the sidebar falls back to the empty state silently. A hydration failure will never crash the extension activation (try/catch is doubled).
• The hydration is async after activate() returns, so there can be a sub-second moment where the sidebar shows the empty state before snapping to the hydrated view.
• The hydration runs once per activation (not on file change). To get a fresh scan after editing code outside the extension, run Scan Workspace as usual.

How to validate empirically

If you already have a workspace with previous scan + triage data in <workspace>/.sentinel/colony.db:

1. Uninstall the previous version (code --uninstall-extension RealGoLab.synaptic-sentinel)
2. Install v0.3.11: code --install-extension synaptic-sentinel-0.3.11.vsix
3. Close the project folder entirely (File → Close Folder)
4. Reopen the same folder (File → Open Folder)

You should see the SYNAPTIC Sentinel sidebar fully populated without running anything: summary card, cost card, four bucketed sections, diagnostics, status bar — all restored from the cache.

Known Issues

Unchanged from v0.3.10 — 1 caveat structurally closed:

1. Ground truth dataset is AI-drafted (DG-075 caveat heredado, DG-095 A structured in v0.3.7). External citation remains blocked until the corpus reaches ≥ 10 human-reviewed entries.

Install

Download synaptic-sentinel-0.3.11.vsix and run:

code --install-extension synaptic-sentinel-0.3.11.vsix

Or use Install from VSIX... in the VS Code Extensions view.

SHA-256: 417260686e30c7454c067956e9ee03d52b3afd7d88ef97a0cdbca80569ded428

The Marketplace listing remains at v0.3.3 until the publisher uploads with their PAT — semver permits skipping intermediate versions, so a future upload may go from v0.3.3 directly to v0.3.11 (8 versions skipped).