Issue #17948 · Open
Closure reasonHistorical assessment at head 324a1127200111b4fd372cd55e9d09c8ccf3b93c: Intentional partial draft: fixes only item 1 of the four-item automation issue. The required HUMAN note and description check remain unfinished; it does not claim to solve the other three items. Current head 0f812ac68902d2c71896568311bffb8aa6f216a6 has not been independently reviewed by this metadata refresh.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed. The current head differs from the originally audited head and is independently unverified by this metadata refresh.
Evidence and review limits
Current GitHub head: 0f812ac68902d2c71896568311bffb8aa6f216a6.
Original audited head: 324a1127200111b4fd372cd55e9d09c8ccf3b93c. The current head differs from the earlier audit and was not independently reviewed during this metadata refresh.
- The following source and runtime assessment limits belong to the originally audited head, not a fresh verification of the current head.
- Mock-Canvas before/after screenshots and 26 focused tests are supplied; do not say no evidence exists. No code defect established.
Issue #18161 · Open
Closure reasonOnly the original Slack probe failure screenshot is attached. There is no branch-specific install/Test/Retry evidence showing fetch failures and timeouts become connectivity-only, with credentials explicitly not verified.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: f500de4b326cef594d88f47be9db090402c2347e.
Original audited head: f500de4b326cef594d88f47be9db090402c2347e. The current head matches the earlier code audit.
- Focused tests and code CI pass; this is an evidence/readiness closure, not a demonstrated credential-classification defect.
Issue #18160 · Open
Closure reasonNo running-branch evidence distinguishes quiet bootstrap recovery from genuine post-bootstrap errors. The change silences these model/version queries in every app state, and the configured-backend failure test now expects silence.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: c485c41b4296491870b9c4c9fd6ef387afbf9615.
Original audited head: c485c41b4296491870b9c4c9fd6ef387afbf9615. The current head matches the earlier code audit.
- The global error handler is unchanged; no global error-reporting regression has been established. The screenshot shows the original first-run contrast, not repaired returning-user recovery.
Issue #17959 · Open
Closure reasonThe only screenshot repeats the original blank template-search result. There is no running-branch evidence for the no-results message, Clear action, optional-integration count or rendered singular/plural wording.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 3441b93aa8ebf47da89b9d11716e1d9a670a8230.
Original audited head: 3441b93aa8ebf47da89b9d11716e1d9a670a8230. The current head matches the earlier code audit.
- Bounded code and route/component regression tests look plausible, and current code CI passes. No introduced defect established.
Issue #18123 · Open
Closure reasonThe click diagnostic snapshots defaultPrevented in capture phase, before later handlers can cancel it; click failures also bypass its diagnostic catch. Actual cross-connect success and a deliberately forced no-tab failure have not been demonstrated.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 07f0bfbe0fe09767e4aba683e2eb4e43ebe3b1f1.
Original audited head: 07f0bfbe0fe09767e4aba683e2eb4e43ebe3b1f1. The current head matches the earlier code audit.
- A prior local jsdom control confirmed the capture-phase cancellation mismatch; click/wait ordering is source-reviewed. No new runtime tests were run for this refresh. Current code/description CI passes.
Issue #18063 · Open
Closure reasonLocal before/after composer screenshots exist, but this is a partial fix: the expanded Tools-menu scope is untouched, and the viewport matrix, Code/Plan, profile/link activation and visible keyboard-focus behavior are not established.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: f8890f07e433bbd55e702c73d2f0941f76484bf6.
Original audited head: f8890f07e433bbd55e702c73d2f0941f76484bf6. The current head matches the earlier code audit.
- The original report allowed Macros to be split out; the later AI triage explicitly includes Tools menus. A maintainer could narrow scope and retain this bounded fix. Local before/after screenshots exist; do not call all evidence absent.
Issue #18062 · Open
Closure reasonUbuntu CI still fails because an existing test mock lacks getErrorStatus. The detail-toast correction has unit coverage, but its author explicitly says the requested real-stack replay/recording is unfinished; earlier live review tested the previous head.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 9a831278b5fd79bfdd7646db33bb81f824beadc8.
Original audited head: 9a831278b5fd79bfdd7646db33bb81f824beadc8. The current head matches the earlier code audit.
- The test-mock failure is a specific CI repair, not proof of a production regression. Prior real-stack dashboard/home and non-404 checks succeeded before the correction.
Issue #17955 · Closed
Closure reasonLinked issue #17955 is closed by merged PR #18422 (enyst). This still-open proposal is superseded; close without merge. No changes from this proposal will be reused.
GitHub’s latest issue-closing event identifies merged PR #18422 as the closer. The original audit and evidence remain historical; this refresh did not verify product behavior or submit a closure.
Evidence and review limits
Current GitHub head: feffce0c4a4a6e3950b9550ea66f5b770e09eb72.
Original audited head: feffce0c4a4a6e3950b9550ea66f5b770e09eb72. The current head matches the earlier code audit.
- Same-head review found the displayed-value fix sound and treats hidden-field inheritance as non-blocking. Do not imply demonstrated credential leakage or data corruption.
Issue #17900 · Open
Closure reasonStill Draft with the requested HUMAN note unanswered and description validation failing. Close under the review-ready policy; the switch implementation already has published real-stack Tab/Space and focus evidence.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: cb43883c4a0aec10958ae37c3847ffbc5cbb4357.
Original audited head: cb43883c4a0aec10958ae37c3847ffbc5cbb4357. The current head matches the earlier code audit.
- Real AgentServer browser recordings, DOM/keyboard/state data and focused tests are supplied. No code defect established; absence of human review is not evidence the account is non-human.
Issue #17898 · Open
Closure reasonHistorical assessment at head 0cf65d442003f7ecd52971d266903bc746f99130: Still Draft with the requested HUMAN note unanswered and description validation failing. Close under the review-ready policy; the DNT fix already has published real-stack network/storage comparison evidence. Current head d7e78af478ec07586876d4847556b5436860635b has not been independently reviewed by this metadata refresh.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed. The current head differs from the originally audited head and is independently unverified by this metadata refresh.
Evidence and review limits
Current GitHub head: d7e78af478ec07586876d4847556b5436860635b.
Original audited head: 0cf65d442003f7ecd52971d266903bc746f99130. The current head differs from the earlier audit and was not independently reviewed during this metadata refresh.
- The following source and runtime assessment limits belong to the originally audited head, not a fresh verification of the current head.
- The author supplies base/head recordings and real AgentServer runs claiming six analytics attempts before versus zero after. These were not independently replayed in this refresh. No code defect established.
- Then-current GitHub head d7e78af478ec07586876d4847556b5436860635b differs from original audited head 0cf65d442003f7ecd52971d266903bc746f99130; this refresh did not review or execute the new code.
Issue #17564 · Open
Closure reasonCurrently conflicts with main and has not supplied the requested after-fix browser captures at 320px, 390px and desktop. Its jsdom class assertions cannot prove readable wrapping, reachable buttons or no viewport overflow.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 2562990c8604f3f90bed90ee7c9a4c1c8d9cc165.
Original audited head: 2562990c8604f3f90bed90ee7c9a4c1c8d9cc165. The current head matches the earlier code audit.
- The HUMAN note claims those viewport checks, but the PR attaches only the original Before screenshot. Same-head review found no code defect; code CI passes on its unchanged head.
Issue #17215 · Open
Closure reasonIncomplete portal acceptance: CSS variables supplied through the public style prop do not reach the body-level modal host. The required one-root/two-theme browser evidence is absent and description validation fails.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: f0474d5411281e1ec422832df7e7d0fb77ac7095.
Original audited head: f0474d5411281e1ec422832df7e7d0fb77ac7095. The current head matches the earlier code audit.
- Same-head review labels the style-prop omission non-blocking and reports 13 focused tests passing. The author claims manual two-root verification but explicitly attaches no artifact.
Issue #17563 · Open
Closure reasonDescription validation still fails with an empty HUMAN note, and the author explicitly provides no post-fix mobile browser capture. Scrollable fields and close/save/cancel reachability at 390×844 remain unproven in a running app.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: f6457ec3a49ea242c18a5409293659cb40c189a5.
Original audited head: f6457ec3a49ea242c18a5409293659cb40c189a5. The current head matches the earlier code audit.
- Same-head review found the CSS change correct and minimal and mutation-checked its regression test. No introduced defect established.
Issue #17566 · Open
Closure reasonCurrently conflicts with main, fails description validation and has no post-fix reload capture. Hydration only handles the initial history tail and stops once any terminal entry exists; older-page and later REST-history restoration need completion or an explicitly narrowed scope.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 148f8ce66610fbb3eed828715f5e2a08ed0629a9.
Original audited head: 148f8ce66610fbb3eed828715f5e2a08ed0629a9. The current head matches the earlier code audit.
- Older-page omission is source-reviewed; the later-REST/WebSocket race is a source-derived sequence, not a reproduced runtime failure. Existing tests and same-head review support recent-tail reload/dedup behavior.
Issue #16947 · Open
Closure reasonAlready approved by koriyoshi2041, with strong deterministic tests, successful negative controls and green CI. Closure here is solely under the required running-conversation evidence policy: its before/after artifacts are unit-test output, and live page-boundary replay is listed as optional.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 543cd5afdf58e7a0c151534bdc876a21201768ea.
Original audited head: 543cd5afdf58e7a0c151534bdc876a21201768ea. The current head matches the earlier code audit.
- There is an existing approval from koriyoshi2041, strong deterministic store tests, successful negative controls and green CI. Same-head review found the code sound and explicitly says maintainers may accept that proof; this closure is policy-based, not proof of a defect.
Issue #16953 · Open
Closure reasonExplicit partial Draft: it leaves stale client/i18n globals after both sibling roots unmount and excludes async-origin ownership and the full instance-scoping work. The HUMAN note and description validation remain unfinished.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 607971c0def84d28b09949f535f6af2eb95f465a.
Original audited head: 607971c0def84d28b09949f535f6af2eb95f465a. The current head matches the earlier code audit.
- The residual global-state limit is openly disclosed and is not claimed as a new regression. The issue is marked Part of, not Fixes. No UI recording is required merely for this nonvisual provider fix.
Issue #17217 · Open
Closure reasonCurrently conflicts with main, and the core Configure → save → ask_oracle → delete/ghost flow remains unverified against a real Agent Server. Mock screenshots only show the entry/editor, and the author explicitly defers the save/tool payoff.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 5934d9ce1f72b9c42d85395743024ebb628e30b9.
Original audited head: 5934d9ce1f72b9c42d85395743024ebb628e30b9. The current head matches the earlier code audit.
- The newer same-head review confirms the earlier reserved-name guard-test gap is fixed and reports 155 focused tests passing. Do not repeat the older absent-tests finding or stale CI warnings. No code/security defect established.
Issue #16949 · Open
Closure reasonCurrently conflicts with main. Its explicit unit-only verification and terminal SVG do not show running Cloud/Local Files refresh, file-edit invalidation or the retained-path Changes status update before and after.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: 034a003ed04200c06dd4a272e3000020f638f575.
Original audited head: 034a003ed04200c06dd4a272e3000020f638f575. The current head matches the earlier code audit.
- Same-head review finds both source-driven fixes sound and reports focused tests/CI green. An old failure comment references a previous head and is not a current code-CI failure.
Issue #16107 · Open
Closure reasonStill Draft, currently conflicts with main and lacks issue ready-for-dev; the sessionStorage-versus-memory dismissal choice remains for maintainer decision. Published configured-Local screenshots and mock-LLM E2E do not establish the full unconfigured/Cloud/backend-switch runtime matrix.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: fa05e8b1c94993c12c4df9b68e696703ebc0600b.
Original audited head: fa05e8b1c94993c12c4df9b68e696703ebc0600b. The current head matches the earlier code audit.
- There is real configured-Local before/after evidence and 62 successful mock-LLM E2E cases; do not claim no runtime evidence exists. Broad scope or a competing implementation alone is not a code-defect finding.
Issue #15677 · Open
Closure reasonCurrently conflicts with main; the required PR template and screenshot remain absent, and description/artifact checks fail. The small default preference change needs a refreshed submission before merge review.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: d3e6b0ba744ebf9d12035825e9081b7f441c2ed5.
Original audited head: d3e6b0ba744ebf9d12035825e9081b7f441c2ed5. The current head matches the earlier code audit.
- Same-head review found no changed-line defect and reports 66 focused tests passing. The artifact-check failure is a GitHub API permissions error, not a product-code failure.
Issue #16257 · Open
Closure reasonStill Draft, currently conflicts with main and has unresolved HUMAN/issue/validator readiness. Close the unfinished submission; its signal-lifecycle fix already has real child-process shutdown and mutation-test support.
The earlier audit recommendation and its evidence limits are retained. Current issue/PR state, reviews and checks were read from GitHub; no code or runtime verification was performed.
Evidence and review limits
Current GitHub head: ff38ad9c2b4fea247f5f8508a3de5b27d42f1ac7.
Original audited head: ff38ad9c2b4fea247f5f8508a3de5b27d42f1ac7. The current head matches the earlier code audit.
- The latest validator failure is an unsupported --files-file argument, not a failed lifecycle test. Earlier substantive SIGHUP/import gaps were repaired and independently checked; no UI recording is needed for this nonvisual change.
