[IAmJSD]

In the Purchase History table, a failed row carrying an ops_hint returned early with only the hint badge, so it lost its retry-chain links ("↻ Retried as #..." / "↻ Retry #N"). Since #967, executions the backend will never re-drive also carry a permanent hint, so a legacy row retried before the re-drive gate no longer linked to its successor. This PR renders the hint and the lineage links together; Retry stays hidden.

Closes #1040

What changed

• frontend/src/history.ts: the lineage-link markup moves out of renderActionCell into a renderLineageLinks(p) helper (which keeps main's Number() coercion of retry_attempt_n from fix(frontend): escape the remaining raw values in innerHTML templates #1318, so the ops-hint path gets it too), and the ops-hint branch returns the badge followed by those links (space-joined, like the existing lineage plus action composition). The decision-tree comment is updated.
• frontend/src/__tests__/history-retry-button.test.ts: two cases. A redrive_unsafe row with ops_hint, retry_execution_id and retry_attempt_n renders the hint, the "Retried as" link with the right href, the "Retry sec(iac): rename-proof OIDC deploy trust + branch-restricted environments for the split platform repo #2" badge and no Retry button; a hint-only row renders no lineage.

Why this approach

It is the issue's suggested fix. Extracting the helper avoids duplicating the link markup in two branches. Only the ops-hint branch changes. The plain Retry-button branch also returns early without lineage, but a retried row normally isn't retryable again, and that branch is outside the issue, so it is left alone.

Screenshots

Screenshots were taken before this branch was merged with main; before = main at a14dc8f. The failed-row rendering shown is unchanged on current main. After is this branch. Both are headless Chromium at 1440x900 against the repo's mocked e2e API. The row is a failed Azure savings-plan execution with the permanent re-drive hint and a successor execution.

Before	After
The failed row shows only the permanent hint, with no link to its retry.	The hint plus a "↻ Retried as #bbbbbbbb" link to the successor row (no Retry button).

Verification

Run on this branch's head 91f426b8, from frontend/:

• Merged with main at 51aa5b1; conflicts in frontend/src/history.ts resolved, see the merge commit.
• npm run lint: 0 errors. Typecheck and build pass.
• Jest: 3916 of 3917 passed, 1 skipped. The new test fails against main's history.ts and passes on this branch. history-retry-button.test.ts now has 23 tests; before the merge it passed with --randomize.
• Playwright (e2e-local.sh): 208 passed. No new spec; this rendering-only change is covered by jest.
• Secrets scan clean (planted key flagged); scripts/test-git-secrets-allowlist.sh: 137 PASS, 0 FAIL.

Notes for review

The link renders inline right after the hint text and wraps in the narrow Plan column. Putting it on its own line would be a small markup/CSS change.

Overlaps

• chore(frontend): replace mixed Unicode glyphs with one SVG icon set #751 (SVG icon set) conflicts textually in history.ts.
• history.ts is also touched by Sweep toISOString().split('T')[0] -> toLocalDateInputValue across frontend date inputs #51, fix(frontend): impossible/placeholder values surfaced for scheduled and pending purchases #181, feat(frontend): Load more on the History view, Approval Queue from all loaded pages #676, fix(frontend): low-severity copy, toast, confirm and stale-state fixes #728, fix(frontend): status badges use four shapes and conflicting colors per status #737 and fix(frontend): three money formatters, mixed placeholders, left-aligned money columns #739; history-retry-button.test.ts also by fix(frontend): low-severity copy, toast, confirm and stale-state fixes #728 and fix(frontend): three money formatters, mixed placeholders, left-aligned money columns #739. These merge cleanly with this branch.

Note for the UI owner

This changes UI code that @cristim owns. IAmJSD reviewed the before/after screenshots and asked for it to be merged; any design point you disagree with can be a follow-up.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

• Run on-demand review

_{This review includes 2 billable files and costs up to $0.50.}

Or wait 59 minutes for your next included review.

Check out review usage here.

View limit details

Limit details: You’ve used the included review currently available.

Learn how review limits work.

Review configuration:

Run configuration

• Source mode: Auto
• Repository: LeanerCloud/cloud-commitments-platform
• Branch: main
• File: .coderabbit.yaml
• Commit: 51aa5b1
• Layers: Repository YAML
• Review profile: CHILL
• Plan: Advanced
• Run ID: d587784a-04d9-4e41-9de1-4e2fd2cf283f

Commits

Reviewing files that changed from the base of the PR and between 51aa5b1 and 91f426b.

Files selected for processing: 2

• frontend/src/__tests__/history-retry-button.test.ts
• frontend/src/history.ts

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[IAmJSD]

Independent review (IAmJSD's agent, fresh context, given only the diff, the issue and the PR text): APPROVE 91f426b82fe4e3ccda0ec0b3b9f27a9a27c5f3c1

Blocking:

• none
  Non-blocking:
• frontend/src/history.ts:946-961: the merge put renderActionCell's "Decision tree" comment directly on top of the new renderLineageLinks doc comment, with no blank line. The tree now reads as if it documents the helper, about 40 lines from renderActionCell (980). It also still says "mutually exclusive", but the ops-hint branch now composes the hint with lineage links. Fix: move the helper above the tree, or add a separator line, and drop "mutually exclusive".
• frontend/src/history.ts:1003-1008: the plain Retry and over-threshold Retry branches still return early without lineage. So a retryable failed row that is itself a retry (retry_attempt_n > 0) shows no "Retry #N" badge. Pre-existing and admitted in the body; a possible follow-up.
  Attacked: The branch is one fix commit (4d545a8) plus merge 91f426b; its merge-base equals origin/main 51aa5b1. git diff merge^2 merge on history.ts is byte-identical to origin/main...HEAD. merge^1->merge keeps all of main's newer work: the feat(frontend): de-duplicate the Purchases approval surface (Approval queue repeats Purchase History rows) #183 queue link and wireApprovalQueueLinks, sec(frontend): low-severity RBAC and input hardening from the 2026-09-02 audit #320 fail-closed _fourEyesMode, fix(frontend): offer Revoke on scheduled AWS and GCP executions, not only Azure #924/fix(frontend): align history Revoke and dual-control gates with backend #1347/fix(frontend): offer Revoke on scheduled AWS and GCP executions #1393 scheduled revoke and RBAC, chore(frontend): low money-path findings from the 2026-09-02 audit #318 upfrontCell and cent-reconciled fees, fix(frontend): History and Approval Queue filter popovers collide on shared column ids #281 filter scopes, and fix(frontend): escape the remaining raw values in innerHTML templates #1318 count escaping with Number() on the over-threshold label. fix(frontend): escape the remaining raw values in innerHTML templates #1318's retry_attempt_n coercion moved into the helper (974), so the ops-hint path gets it too.
  ops_hint and shortExecID are escaped, the href uses encodeURIComponent, the title is a constant, and there are no inline styles or new listeners. No tests were removed or loosened. Scratch jest: 14 history suites / 188 tests passed. The new hint+lineage test fails on main's early return.

[IAmJSD]

Local verification at 91f426b8 merged onto current main (6bd08509; merge-tree d3ae6c83; Linux, Node, headless Chromium):

• This branch's own checks passed at this head: lint, typecheck, build, the full jest suite, the full Playwright e2e suite, and the git-secrets checks (see Verification in the PR body).
• The combined tree of every UI PR in this merge wave (tree dc090cc2, main plus 17 PRs) passes npm ci, lint, typecheck, build, jest (1 skipped, 4097 passed, 4098 total), and the full Playwright suite (232 passed).
• CI is green on 91f426b8 (CI Success, Run pre-commit hooks).
• The independent review above approves this exact head.
• Nothing was applied to any cloud.

[IAmJSD]

Marked ready and merged by IAmJSD's agent, at IAmJSD's request (IAmJSD reviewed the before/after screenshots; cristim is traveling), after the independent review and local verification above, all at 91f426b8.