Skip to content

feat(ui): auto-show deterministic impact on drift, LLM narration on demand - #40

Merged
AusafMo merged 1 commit into
mainfrom
feat/ui-auto-impact
Aug 2, 2026
Merged

feat(ui): auto-show deterministic impact on drift, LLM narration on demand#40
AusafMo merged 1 commit into
mainfrom
feat/ui-auto-impact

Conversation

@AusafMo

@AusafMo AusafMo commented Aug 2, 2026

Copy link
Copy Markdown
Owner

Opening a drift record now auto-renders the System impact panel (risk, changed paths, affected records) computed locally — no LLM call. Narration is opt-in.

What changed

  • Auto-show deterministic impact when you open a drift record (was click-only).
  • Narration is opt-in via a Narrate with LLM button that sends this record's diff to the configured provider. Copy now says that plainly instead of the misleading "no data left your machine".
  • Spinner + disabled state on both the top Analyze impact button and the in-panel Narrate button during the multi-second call (they looked frozen before).
  • Version-to-version impact stays click-to-run.

Verification (e2e, in-browser)

  • Open drift record → panel auto-shows, impact call fires with use_llm:false (no provider call).
  • Click Narrate with LLM → fires the LLM call, button spins, Gemini narration renders.
  • Full suite 158 passed; ruff clean; JS syntax-checked with node --check (this caught a duplicate-const regression that Python-side ast/ruff can't see).

Answers the two asks: keep Analyze impact open by default (deterministic, no per-open cost) + fix the frozen/misleading narrate button.

…emand

Opening a drift record now auto-renders the System impact panel (risk, changed
paths, affected records) computed locally — no LLM call. Narration is opt-in via
a 'Narrate with LLM' button that sends this record's diff to the configured
provider; the copy says so plainly instead of the misleading 'no data left your
machine'. Both the top Analyze-impact button and the in-panel Narrate button now
show a spinner + disabled state during the (multi-second) call so they don't look
frozen. Version-to-version impact stays click-to-run.

Verified in-browser: panel auto-shows with use_llm:false (no provider call),
narrate fires the LLM call and renders, and the buttons spin. JS syntax-checked
with node --check (caught a duplicate-const regression the Python-side checks
can't see).
@AusafMo
AusafMo merged commit 6819eaa into main Aug 2, 2026
2 checks passed
@AusafMo
AusafMo deleted the feat/ui-auto-impact branch August 2, 2026 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants