Repository navigation
test(F117): queue chip claims stop matching the panel's own header - #195
Merged
Merged
Conversation
Why: five web tests fail on develop_base (52b80e1). They assert that the Queue Panel shows no '排队等待' author-intent chip, which F117 (f426fb7) removed, but they read the whole panel text, and the panel header itself reads '排队等待中' (6392172). So they fail even though no chip renders, and a fork PR's full gate fails at the web unit stage. The assertions now read the panel text without that one header label; the chip-specific checks (data-testid intent-chip-* is null) are unchanged. Before: f264-queue-ux-hierarchy 4 failed, queue-panel-steer 1 failed. After: both files 44/44; web tsc clean. [宪宪/claude-opus-5-5🐾] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mindfn
added a commit
that referenced
this pull request
Sep 26, 2026
Why: record the Phase 3 status per the roadmap rule. The Queue-row owner of the first design was replaced by the dispatch-state design Fable ruled on (…000201); #196 implements it with carrier consumption evidence, a waiting ref, read/unread settlement, the Queue Panel rows and an honest recall refusal. Build and API full comparison clean; the whole web suite is still running. Also notes #194/#195, the two F117 test leftovers that blocked every fork gate. [宪宪/claude-opus-5-5🐾] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mindfn
added a commit
that referenced
this pull request
Sep 26, 2026
Why: roadmap rule — record each PR's status and the SHA 3001 runs. kimi approved #196 at 84a40d1 (…000403) and accepted the rollback trade-off; the web full-suite comparison is on the PR (5848460811). 3001 still runs 9aa0c01, so the next restart loads 2c, #194, #195 and Phase 3 together. [宪宪/claude-opus-5-5🐾] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
mindfn
added a commit
that referenced
this pull request
Sep 27, 2026
Why: roadmap rule — record each PR's status and the SHA 3001 runs. kimi approved #200 at d70dc35 (…000595) with no P1/P2; his one note (a direct call without a Queue slot no longer has the 2x cap) only concerns tests and scripts, since the Queue is production's single dispatch entry. 3001 still runs 9aa0c01, so the next restart loads 2c, #194, #195, Phase 3, #197, #198 and Phase 4 together. [宪宪/claude-opus-5-5🐾] Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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
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.
Why
On develop_base
52b80e1f6, five web tests fail even though the behavior they check is correct:f264-queue-ux-hierarchy.test.tsx: 4 testsqueue-panel-steer.test.ts: 1 testEach one asserts that the Queue Panel text does not contain
排队等待, meaning no author-intent chip is rendered. F117 (f426fb790) removed those chips. But the assertion reads the text of the whole panel, and the panel's own header reads排队等待中(63921725d). So the tests fail even though no chip is there. As a result, a fork PR's full gate fails at the web unit stage. This is the same kind of F117 leftover as #194.What
Test-only change. The five assertions now read the panel text with that single header label removed. The chip-specific checks, such as
[data-testid="intent-chip-…"]being null, are unchanged.Verification
52b80e1f6)tsc --noEmitUnrelated and not touched here:
src/hooks/__tests__/f232-artifact-content.test.tsxalso fails on develop_base. It expectsdocs/BACKLOG.mdbut the hook fetchesdocs/ROADMAP.md. That is a fork-level divergence, not F117.[宪宪/claude-opus-5-5🐾]
🤖 Generated with Claude Code