Skip to content

feat(ui): Reconstruction Contract table + retry-handler catch fix - #186

Merged
slittycode merged 1 commit into
mainfrom
claude/asa-contract-table-retry-catch
Jun 24, 2026
Merged

feat(ui): Reconstruction Contract table + retry-handler catch fix#186
slittycode merged 1 commit into
mainfrom
claude/asa-contract-table-retry-catch

Conversation

@slittycode

Copy link
Copy Markdown
Owner

Off current main, this lands the two parts of the closed #185 that aren't already on main. (The per-card recommendations.v1 signal #185 set out to add already landed via the UI-overhaul series #169#184 — more richly, as per-card contractEntries — so that workstream is dropped.)

1. Reconstruction Contract table (ReconstructionContractPanel.tsx)

main pairs each device card with its contract entry inline (ContractValidatedBadge / ContractEntriesBlock). This adds the complementary single machine-view: a collapsible flat table of the whole recommendations.v1 envelope — Device · Parameter · Value · Working range · Cited measurements — i.e. the exact, schema-validated, citation-gated set exported to the asa-ableton .als generator and the phase2-export envelope. Every row carries ≥1 cited measurement by construction.

  • Built on the CollapsibleCard + DataTable primitives; reuses main's formatContractValue / formatContractRange (no duplicate projection logic).
  • Renders nothing when the envelope is absent (older runs, stem_summary) or empty. Mounted after the Secret Sauce section, V2 only.

2. Retry-handler catch fix (App.tsx)

handleRetryPitchNoteExtraction / handleRetryInterpretation are try/finally with no catch. The monitor's onError only covers errors surfaced through polling; the awaited create*Attempt POST runs before the monitor, so a reject (backend down / 4xx) stopped the spinner with no error shown + an unhandled rejection. Added a guarded catch to both, mirroring handleStartAnalysis plus onError's shouldIgnoreRun guard (so an ignored/cancelled run isn't re-surfaced).

Verification

  • npm run lint (tsc) + npm run build clean
  • tests/services: 830 passed (62 files; main's suite unaffected — the panel is a presentational wrapper over already-tested helpers)
  • DOM behavior (collapse, table rows, retry error banner) is covered by the Playwright smoke gate in CI's Frontend job — needs the live stack, not bootable in this worktree.

Context: #185 was closed as superseded/stale (built 26 commits behind the refactor); this is the clean re-do off main.

https://claude.ai/code/session_01YB5QFBLL4nbqPSdtcnxrLy

🤖 Generated with Claude Code


Generated by Claude Code

Two changes off current main, salvaged from the superseded #185 (its per-card
recommendations.v1 signal already landed via the UI-overhaul series, more
richly, as contractEntries):

- ReconstructionContractPanel: a collapsible single machine-view of the
  recommendations.v1 envelope (device · parameter · value · working range ·
  cited measurements) — the verbatim, schema-validated, citation-gated set
  exported to the asa-ableton .als generator. main pairs the contract per-card;
  this is the complementary flat table. Built on the CollapsibleCard + DataTable
  primitives, reusing main's formatContractValue/formatContractRange (no
  duplicate projection). Renders nothing when the envelope is absent/empty.
  Mounted after Secret Sauce (V2 only).
- Retry-handler catch: handleRetryPitchNoteExtraction / handleRetryInterpretation
  were try/finally with no catch, so a failed pre-monitor create*Attempt POST
  (backend down / 4xx) stopped the spinner with no error + an unhandled
  rejection. Added a guarded catch mirroring handleStartAnalysis + onError's
  shouldIgnoreRun guard.

Verified: npm run lint + build clean; tests/services 830 green. DOM behavior
(collapse, retry error banner) covered by the Playwright smoke gate in CI.

https://claude.ai/code/session_01YB5QFBLL4nbqPSdtcnxrLy
@slittycode
slittycode merged commit 5757219 into main Jun 24, 2026
5 checks passed
@slittycode
slittycode deleted the claude/asa-contract-table-retry-catch branch June 24, 2026 07:33
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