[HugoXK]

Fixes #2278

What was wrong

core/test/readonly-window-reads.test.js (#2269) is the only guard against a read name falling out of channel.js's READS whitelist, but it asserted only "the answer is not refused with bot/read-only". An answer that is past the gate and dry still passed, so the guard was green on a tree where a read-only window draws those screens empty. Measured on the tree of this PR's base with the file as it shipped:

read	what it actually answered
folder-list	{"ok":false,"error":{"code":"bot/refused","message":"This DeepSeek Harness cannot list folders"}}
connector-app-status	{"ok":false,"error":{"code":"bot/refused","message":"Connect Composio first"}}
project-decision	{"ok":true,"value":{"ok":true,…}} — the "nothing listed" half
project-of	{"ok":true,"value":{"project":null}}
project-board	…"reason":"no working folder: this Project names none"
folders	{"ok":true,"value":{"team":null,"picker":null,"folders":[]}}

Six reads were dry; the old file was # tests 3 / # pass 3 / # fail 0 on that same tree.

What this changes

Test-only: no source change, no shared fixture.

• core/test/readonly-window-reads.test.js — each of the 11 READS rows now checks the values its screen draws, not the shape of the answer, so a dry answer is red instead of passing for "not refused". What each row proves: the row itself (tasks, projects, project-read, project-of, project-read's project, project-decision's file text and the decisions the board listed), the count beside it and its numbers (project-board: tasks plus counts.waiting === 1 / inflight 0 / blocked 0; metrics.ok === false with reason no-credentials and every metric null, 项目看板：7 个指标卡 + 在跑任务表 #1829), the people (project-team: a Chief row with botId === 'a', not rows: [] or [null, null], Project board shows each Project Bot's dossier (persona, memory, skills), and the owner opens their agent from their own chat #1864), the memory entry (project-memory: a decision whose text is A decision, not an empty record, Stage 2.5: the Project Assistant, minimal version (private memory + daily 09:00 digest) #1712), the folder rows and the chooser kind (folders: picker === 'browse' plus the working folder; folder-list: an entry named decisions), and the connector's app state (connector-app-status: gmail === 'ready'). A row's payload may be a function of the answers above it, used only by project-decision, which opens a name the board itself listed (Project board decision rows can be listed but never opened #2041) rather than one this file made up. A refusal as bot/read-only (the whitelist lost the name) and a dry answer (past the gate, no data) are reported as two separate lists, so a red names which defect it is.
• Fixtures inside that file make the data real: a directoryPicker of the browse kind on the fake context for the folder rows; a signed-in Composio session (state seed + COMPOSIO_API_KEY in secrets.json, with only https://backend.composio.dev/ stubbed and the real fetch restored on stop) for the connector row; a Project working folder holding decisions/2026-01-01-x.md for the decision and board rows.
• patches/ds-bot/files/test/readonly-window-reads.test.js — the same bytes. core/ is carried as ds-bot/ + patches, and this test file is one of the whole-file overlay entries, so a change under core/test/ is only consistent once the overlay copy is regenerated. package step ds-bot/ matches the pin, patches apply, core/ is ds-bot/ + patches (#34) caught exactly that (core/test/readonly-window-reads.test.js: differs from ds-bot/ + patches) before this file was regenerated in.

Red first, then green

• Before: the file as shipped, same base tree — # tests 3 / # pass 3 / # fail 0. The six dry answers above went unnoticed (false green).
• After: # tests 3 / # pass 3 / # fail 0, run twice with the same counts.
• Counter-proof (whitelist): deleting one name from channel.js's READS makes the read-only case red and names it — 'folder-list' removed → # tests 3 / # pass 2 / # fail 1, not ok 1 - … a read-only window still answers these reads: folder-list. The same shape was reproduced for connector-app-status and project-decision. channel.js was restored and the tree of this commit (below) re-verified green afterwards.
• Counter-proof (data): with the dossier's Chief, the memory record, the card's status/queueRole and the browse chooser stripped from the fixtures — i.e. exactly the four dry answers that shape-only checks used to accept — the same case is red and names those four rows: project-board, project-team ({"rows":[null,null]}), project-memory ("decisions":[]) and folders ("picker":"native"), plus folder-list because a native chooser has no listing: # tests 3 / # pass 1 / # fail 2. Restored, then green again.

What I ran

• TZ=UTC node --import ./test/harness-resolve.mjs --test test/readonly-window-reads.test.js — # tests 3 / # pass 3 / # fail 0 (twice, and once more after the patch overlay was regenerated).
• The counter-proof above, then git checkout -- core/src/host/channel.js and a green run on the restored tree.
• node scripts/ds-bot-patches.mjs generate — 307 overlay files written, of which exactly one changed (patches/ds-bot/files/test/readonly-window-reads.test.js, +84/−33); no .patch file changed.
• node scripts/ds-bot-patches.mjs check — ok core/ equals ds-bot/ + patches/ds-bot/; node scripts/ds-bot-patches.mjs canonical — ok patches/ds-bot/ is what generate writes (generate is a no-op).
• Rebased onto the new main b451e3b3 (this PR's base moved after core: a read-only window's create entries no longer open the scheduled-task form #2246 merged), then node scripts/ds-bot-patches.mjs generate again — it wrote nothing (no overlay or patch file changed), check and canonical still green, and the affected suite re-ran green on the rebased tree.
• ARCH_DOCS_BASE=b451e3b3 npm run lint — Found 74 warnings and 0 errors (warnings pre-existing), arch-docs: OK (2 changed file(s)).
• git show --stat — 2 files, +216/−68 (the test and its overlay copy, same 142-line diff each).

What I did not run

• npm run verify — not run in this worktree. The change is test-only with no source edit; the affected suite, the patch checks above and lint were run directly.
• No build; no changelog.d/ fragment and no subsystem doc (test-only, no user-visible change).
• No other test file touched, and no source file touched.

Verified head: e6bb416cc52c0583348469d8a94b656f4e5ab8d1 (tree b201349f4c5d170b4b9a1db48ed6207404d938a5, single parent b451e3b361771e85db156845f89a254c62ac275d) — the pushed tip, whose tree is byte-for-byte the tree the run counts above were taken on.

[HugoXK]

@Birfy — #2280 is ready at this tip e6bb416cc52c0583348469d8a94b656f4e5ab8d1 (base b451e3b3, 2 files, mcm true, mergeable_state clean).

enqueue-guard is green at this exact tip (enqueue #2280: no hold and the gate passes), and this is T1 (core/test/** plus its generated mirror), so no approval is needed — the tip may enter the queue as it stands.

What it does: the read-only reads test now checks the values each screen draws instead of the shape of the answer. Before this change a dry answer passed: the guard only asked "not refused with bot/read-only". The four rows that used to pass on a dry answer now fail on it — project-team (the dossier's own Chief row), project-memory (the seeded decision text), project-board (counts/metrics, including the 0-vs-null shape from #1829) and folders (picker === 'browse') — and Fixes #2278 is in the body.

Self-test: the four rows go red when their seeded data is removed, and again when the readers are made to answer dry; deleting a name from the channel's read list reddens the row that names it (folders → 2 pass / 1 fail, the failure names folders); the writable cases stay green under every one of those mutations. verify on the tip: 4603/4603/0, arch-docs OK, 10 patches clean, generate no-op.