Repository navigation
Read a meeting's state in the window's language (#3114) - #3267
Conversation
Docs-not-needed: three dictionary keys and one t() in the Project board; no component structure changes.
|
Written-by: Dev 实测(本机工作副本,tip
停下等复核,不入队、不合。 |
Enqueue evidence — #3267 (Cut 35, T1)Read 2026-11-20T12:31Z–12:34Z UTC through Tip Seven spot checks (measured here, not copied from the body)
Red first → green (run twice here)
Tier (computed here, not copied)
CI and gate state at the tip24 check-runs, all terminal: 18 success, 4 cancelled (one duplicate suite each of |
Written-by: Dev
Fixes #3265
Part of #3114
Owner: Dev
Reviewer: Reviewer
Docs-not-needed: three dictionary keys and one t() in the Project board; no component structure changes.
What changed
Before: in a zh window the Project board's 「未决定」 record rows drew the host's meeting status id bare —
open/deliberating/blocked. After: the same cell drawst(meeting.status), so a zh window reads 「待讨论 / 讨论中 / 待答复」, while an English window is byte for byte unchanged. The three ids become dictionary keys of their own besiderunning/stalled, the same shape this screen already uses fornot-started/in-progress/doneandordinary/major/severe.Two hand-written product files: the third argument of the one
bt-project-statusspan (core/src/client/project-board.js:663, +1/−1) and three bare keys with a two-line comment (core/src/client/i18n.js, +5/−0).data-status(:656) anddata-level(:642) stay the host ids — the new case asserts all four rows keep them. The question, the@speaker, the level badge and the blocking question are host data and untranslated.core/src/host/**is untouched: the host still owns the lifecycle and the read model still only emits those three pending statuses.The case also carries an
on-holdrow the host never emits: a status the dictionary cannot name is drawn as it came, so the change is a lookup, never a guess or a mapping table.Verification at the tip
Tip SHA:
c7b0560acf7dbdf2a50cc37aee2bfc73f39a2c28(treed07e09c5bce30918436749340256d4655f00f185)Ran at this tip:
Red first — only the test added (file 39), implementation still at the merge base
641faf10:cd core && TZ=UTC node --test test/project-board-view.test.js→# tests 39 / # pass 38 / # fail 1; case 39 stopped at'open' !== '待讨论'. Clean main on the same file is38/38/0.At the tip: the same command →
39 / 39 / 0. The five i18n gates stay41/41/0; the four baselines12 / 9 / 46 / 2are byte-identical (no--writewas run,git diff --name-only origin/main...HEAD | grep -c baseline.json→ 0).cd core && npm run buildregeneratedcore/client.js;node scripts/ds-bot-patches.mjs generatetwice (zero diff the second time);git status --porcelainempty;patches/ds-bot/topics.jsonuntouched.Risk gate on the nine changed paths, objects carrying
patch(the shape the PR files API serves):T1 0 46 4 5— hand-written 46 lines / 4 files, 5 generated paths. The two traps were confirmed on the same diff: 9 bare filename strings →T0 0 0 9 0, objects withoutpatch→T3 4 46 4 5. Budget leaves 354 lines / 16 files. The forbidden surface regex hits 0 (core/src/host/,about.js,capability-settings.js,sidebar.js,topics.json,i18n-*.baseline.json), and the positive control on the same regex hits 3.Not run (and why): the full
TZ=UTC npm run verify. This box has onlyesbuildin the sharedcore/node_modulessymlink (no@deepseek-ai/*harness packages, and the brief forbidsnpm ci), so the core suite cannot start here; CI at this tip carries the full suite. The affected test file, the five i18n gates, the bundle check and the patch checks were all run at this tip.Checkpoint
{ "pr": 3267, "claim": "Dev", "issue": 3265, "summary": "In a zh window the Project board's pending-meeting rows drew host ids open / deliberating / blocked; they now read 待讨论 / 讨论中 / 待答复. One drawn child now calls t(meeting.status), and three bare dictionary keys beside running / stalled name those ids. data-status, data-level and the host text stay host data; core/src/host/** is untouched and an unknown status (on-hold) is drawn as it came. One test (39th) covers both windows, the attribute and pass-through: red 39/38/1, fix 39/39/0. The bundle and the five generated patch artifacts were regenerated.", "files": [ "changelog.d/3114-cut-35-meeting-status.fixed.md", "core/client.js", "core/src/client/i18n.js", "core/src/client/project-board.js", "core/test/project-board-view.test.js", "patches/ds-bot/0001-core-fixes.patch", "patches/ds-bot/0008-client-bundle.patch", "patches/ds-bot/files/src/client/project-board.js", "patches/ds-bot/files/test/project-board-view.test.js" ], "checks": { "ran": "project-board-view 39/38/1 then 39/39/0; five i18n gates 41/41/0; baselines 12/9/46/2; build + ds-bot-patches generate/canonical/check; build-client --check; changelog 16; mojibake 1785; arch-docs OK (9); risk gate T1 0 46 4 5", "result": "green", "at": "c7b0560acf7dbdf2a50cc37aee2bfc73f39a2c28" }, "next": "none — ready for review" }