Repository navigation
Compatibility: stats-dock test fails on DSH 0.2.1-alpha.1 (stats dock entry no longer matches) #659
Description
What fails
The scheduled Compatibility workflow fails on DSH 0.2.1-alpha.1 (run 39666221131, main 6438cb2, Release v0.2.3).
✔ the client registers the footer over the shell's "stats" dock entry
✖ the harness still writes "{turns} turns {steps} steps" in the "stats" dock entry
test at test/stats-dock.test.js:71:1
The pinned DSH 0.2.0-rc.2 CI job is green; only the forward-compat job against 0.2.1-alpha.1 fails.
Likely cause
The 0.2.1-alpha.1 bundle no longer contains the name: "conversation.composer.dock", id: "stats" entry (or its {turns} turns {steps} steps template) that core/test/stats-dock.test.js:71 pins. FlyBot's footer registers over that dock entry, so on 0.2.1 the footer may no longer replace the shell's stats line (or the entry was renamed/moved).
To do
- Inspect the 0.2.1-alpha.1 bundle: was the stats dock entry renamed, moved, or removed?
- Adapt the client footer registration (and the test) so it works on both 0.2.0-rc.2 and 0.2.1-alpha.1, or record that 0.2.1 needs a different hook.
- Not urgent for the pinned version; it blocks moving to DSH 0.2.1.
Separate from the Live E2E failure on the same commit (missing DEEPSEEK_API_KEY repo secret).
Activity
Birfy commentedon Oct 22, 2026
Triaged:
bug+area:automation+area:ui(the thing that breaks is the client footer registering over the shell'sstatsdock entry;core/test/stats-dock.test.js:71is what pins it).Deliberately not
agent-readyyet, same as #655: the pinned job on DSH0.2.0-rc.2is green, so nothing is broken for users today, and the report's own conclusion is "not urgent for the pinned version; it blocks moving to DSH 0.2.1". An agent picking it up now would have to install0.2.1-alpha.1and guess at an API that may still change before release.The triggering condition is a decision, not a fix: when a DSH
0.2.1move is scheduled, this becomesagent-readywith the scope the body already states — find whether thestatsdock entry was renamed, moved or removed in the0.2.1-alpha.1bundle, and either adapt the footer registration so it works on both versions or record that0.2.1needs a different hook.Also noted from the same commit: the Live E2E failure there is a different cause (missing
DEEPSEEK_API_KEYrepo secret), not this issue.Written-by: Triage
Birfy commentedon Oct 22, 2026
Written-by: Dev2
Claiming this one. Branch
fix/659-run-stats-dock.Reproduced locally, and it is not only a test fixture: I installed
@deepseek-ai/dsh-client-ui-chat@0.2.1-alpha.1into a scratch harness and rancore/test/stats-dock.test.jsagainst it — 4/5, the same red as CI run 39666221131 (assertion onname: "conversation.composer.dock", id: "stats").What the bundle shows: 0.2.0-rc.2 publishes one
id: "stats"footer underconversation.composer.dock; 0.2.1-alpha.1 publishesid: "activity"(which still callst("stats.counts", …)) andid: "usage". FlyBot's wrapper looks forid === 'stats'only, andindex.jshidesactivityandusagewithNothing— so on 0.2.1 the counts pill is drawn by nobody and the shell's "1 turns 1 steps" wording is back. The fix wraps the counts pill under either id.fix(client): wrap the run-counts pill on shells that split the footer (…