Skip to content

fix(ui): pin running, succeeded, and cancelled next actions (v0.87.3) - #187

Closed
cursor[bot] wants to merge 1 commit into
feat/role-responsibility-agent-ontologyfrom
cursor/bc-ab40fdc2-3b8a-4fde-80b4-91a4738c7c25-feb0
Closed

fix(ui): pin running, succeeded, and cancelled next actions (v0.87.3)#187
cursor[bot] wants to merge 1 commit into
feat/role-responsibility-agent-ontologyfrom
cursor/bc-ab40fdc2-3b8a-4fde-80b4-91a4738c7c25-feb0

Conversation

@cursor

@cursor cursor Bot commented Aug 16, 2026

Copy link
Copy Markdown
Contributor

Home analysis-run rows already told the operator what to do next when a run was Pending or Failed. Running, Succeeded, and Cancelled returned no next click, so the seeded Succeeded lineage row and any in-flight or cancelled row were a dead end.

This slice pins kind-specific copy for those statuses (ADR 0014):

  • Refresh a running row, then open it when the status changes. A running TEPP row is not a calibrated result.
  • Open a succeeded lineage run and compare each live title with the cutoff before treating the body as reconstructed evidence.
  • Treat a succeeded TEPP title list as the measurement corpus, not a reconstruction.
  • After cancel, request or rebuild from a current snapshot — still kind-specific.

Verify

cd frontend && pnpm run test — 61 passed. oxlint clean. tsc -b clean.

Out of scope

Does not fold #177 reconstruction-child purge, start reconstruction, person-catalog, or hidden-run 404. Does not invent a TEPP theta. Does not expose retention purge on HTTP.

Open in Web View Automation 

Home analysis-run rows now tell the operator the next click for every
registered status. A running TEPP row is still not a calibrated result.

Co-authored-by: Seongho Bae <seonghobae@users.noreply.github.com>
@seonghobae seonghobae closed this Aug 17, 2026
@seonghobae

Copy link
Copy Markdown
Contributor

Superseded by later analysis-run next-action copy already on #74 (pending/kind-specific + period-report landing through v0.99.0). Closing this older v0.87.3 vehicle.

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