Repository navigation
fix(web): align approval readiness and task capability entries - #288
Merged
Merged
Conversation
This was referenced Oct 7, 2026
5 tasks done
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes #287.
The execution-environment and review-check panels rejected valid backend readiness responses because the frontend still required five permission choices. The backend now returns Ask / Auto / Full. This change aligns the parser and current fixtures, and checks a real Go HTTP response against the fixture parsed by APIClient.
Task review exposes batch delivery, advanced Git, GitHub review and UI evidence through 更多交付工具. Panels load on demand for the selected Run. Exact Git/GitHub review results survive approval/check navigation; changing Run clears them. Missing historical Runs fail closed. Permission, Debug and network descriptions reflect the current independent controls, and unavailable UI-evidence/batch capabilities explain their configuration requirements. A missing UI-evidence reader remains unknown history rather than an empty ledger.
Historical five-mode permission readers remain supported; writable choices stay at three, as specified by ADR 0165. Go execution authority and startup defaults are unchanged.
Validation at current head
65de06592d96aaa51e10ba9e0bea46009deac2ea:198aff354d3bb38f09ea7305d8542b314c69e796: 176 files / 1,720 frontend tests and TypeScript passed, including historical Run → GitHub preview → approvals/delivery → exact execution. The branches merge without conflicts.b1a0782f) passed 316 frontend tests, TypeScript and the two Go 1.26.9 HTTP readiness fixture/stable-facts tests.The original implementation also had an isolated Chromium/API acceptance run covering real readiness rendering, all four tool entries, unavailable capability messages and narrow layout. That browser experiment was not repeated for the documentation merge and fixture-only update. Scope and historical evidence: acceptance record. It did not perform model execution, GitHub writes, host validation or managed browser launches. The existing large-chunk build warning remains.