Skip to content

feat(ui): unblock from the browser — why it's blocked · what you can do, bulk-retire attempts for closed Issues, loop panel for any loop (#243) - #273

Merged
DanielNetzer merged 2 commits into
mainfrom
forgecell/issue-243-1d9ca15341dcf56bf69a14f0
Oct 27, 2026
Merged

DanielNetzer merged 2 commits into
mainfrom
forgecell/issue-243-1d9ca15341dcf56bf69a14f0

Conversation

@DanielNetzer

Copy link
Copy Markdown
Owner

Implements issue #243.

Molecule: mol-243-9cfda09b5c5bcee22f4180c4
Formula: forgecell-github-issue
Base: 5a638555bff15af112ab3fa92ab4bb8ceacaee8e
Delivery: b47af04c0f16f87dba8c9918f280e6ee82f3d2d8

Awaiting exact-commit CI and human review. Harness-reported checks are not independent CI evidence. No merge, deployment or issue closure is authorized.

Daniel Netzer and others added 2 commits October 27, 2026 19:14
…do, bulk-retire attempts for closed Issues, loop panel for any loop (#243)
…rver.go

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@DanielNetzer

Copy link
Copy Markdown
Owner Author

Adversarial review (2026-10-27): no HIGH. Fixed in this slice: recover-then-amend failure reports recovered-not-amended; accept-failures is bound to a hash of the shown test list; loop selector defaults to milestone: (oldest only as a labelled fallback); CLI/UI digest parity tests for all three action kinds + RecoverFirst; scope-change posts raw ledger paths; bulk retire runs under an overall deadline and reports 'not attempted'. Remaining LOW: fresh intake button doesn't name the Issue.

Merged main (fe1b6ae) to resolve server.go conflicts with #272 (#263 setup mode): union of the header comment, handler fields, handler literal and the POST-route check (gate || drive || setup || action). Verified on the merged tree: build, vet, go test -count=1 ./internal/ui/... ./internal/molecule/... ./internal/cli/... (1,771 passed).

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.

1 participant