Skip to content

v0.3.13 — Re-triage controls + cost card freshness timestamp (DG-107 A)

Choose a tag to compare

@golab-arch golab-arch released this 29 May 00:26

Re-triage controls + cost card freshness timestamp (DG-107 A). Closes 2 UX issues reported in empirical feedback after installing v0.3.12 and running Sentinel on a real workspace where the user changed the Brain provider mid-flow (in .sentinel/agents.yaml).

The feedback backlog vacío milestone declared in the v0.3.12 release notes lasted ~30 minutes — a strong validation of the explicit anti-optimismo declared back then ("the feedback received is not exhaustive; other users could uncover new UX issues").

Added

  • Re-triage all button in the sidebar (Issue #1): when there are already-triaged findings in the current scan, a new Re-triage all button appears in the sidebar summary card next to Triage N untriaged. Clicking it shows a modal warning dialog with the exact count of verdicts that will be overwritten plus a caveat about LLM cost being incurred again. False positives marked manually (mark-fp) and the cost history rollup are preserved. Use case: after switching the Brain provider in .sentinel/agents.yaml, click Re-triage all to re-evaluate the same findings with the new provider.

  • synaptic-sentinel triage --re-triage CLI flag (Issue #1): equivalent to the sidebar button. Clears triage_verdicts + context_explanations + remediation_suggestions for the scan's findings (transactional, batches of 500 for large workspaces) before running the full triage pipeline. Preserves fp_known and triage_token_usage.

  • Cost card freshness timestamp (Issue #2): cost card in the sidebar now shows as of YYYY-MM-DD HH:MM (UTC) in its header when there's at least one record in triage_token_usage. Surfaces the case where the current triage run made 0 LLM calls (e.g. provider changed and everything was already triaged) and the cost card would otherwise look "fresh" even though it's showing data from a previous session.

Notes

  • Scope only DG-107 A. No changes to Scout Layer, Brain Layer adapters, benchmark runner, sidebar layout, or colony.db schema.
  • The destructive Re-triage all action only clears the 3 enrichment tables (triage_verdicts + context_explanations + remediation_suggestions). It does NOT touch fp_known (manual FP marks survive), triage_token_usage (cost history accumulates), or learning_records (colony memory persists).
  • The MODAL warning is opt-in. There is no "soft mode" / preview — the count is shown but not the per-finding breakdown.
  • Anti-optimismo: the IMPACT validates only by reproducing the flow below.
  • Deferred — provider-reported badge per-row: same deferral as v0.3.12. The cost card now has both workflow ordering (v0.3.12) and freshness timestamp (this release), but doesn't yet distinguish per-row whether tokens came from the provider's usage field (real) or chars/4 proxy. Surfacing it per-row requires a triage_token_usage v5 → v6 schema migration; will land if there's empirical demand.

How to validate empirically

If you have a workspace with previous scan + triage data in <workspace>/.sentinel/colony.db (e.g. where you ran v0.3.12):

  1. Uninstall the previous version (Ctrl+Shift+P → Extensions: Uninstall Extension, pick SYNAPTIC Sentinel; or code --uninstall-extension RealGoLab.synaptic-sentinel)
  2. Install v0.3.13:
    • Download synaptic-sentinel-0.3.13.vsix from this release
    • code --install-extension synaptic-sentinel-0.3.13.vsix (or use Install from VSIX... in the Extensions view)
  3. Edit <workspace>/.sentinel/agents.yaml and switch the triage agent provider (e.g. from deepseek/v4-flash to anthropic/claude-sonnet-4-6)
  4. Reload the VS Code window (Ctrl+Shift+P → Developer: Reload Window) so the sidebar rehydrates from cache (DG-103 A)
  5. In the SYNAPTIC Sentinel sidebar, you should see the Re-triage all button in the summary card (because findings are triaged). Click it → confirm the MODAL → the triage pipeline runs again with the new provider. Inspect the cost card after: the as of timestamp updates to the new session, and the new provider/model appears in the breakdown.

Known Issues

The Known Issues section is unchanged from v0.3.12 — 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.

Asset: synaptic-sentinel-0.3.13.vsix (1838 files / 3.15 MB / SHA-256 f889c9d96d128fac09095f172473cfba6c062068e6ccd1641d45119dda58b4f1).

Marketplace upload status: vsce publish to the VS Code Marketplace is not part of this release. To install in VS Code, download the .vsix and use code --install-extension synaptic-sentinel-0.3.13.vsix (or Install from VSIX... in the Extensions view).