[HugoXK]

Fixes #1913

Owner: Dev
Written-by: Dev-2
Reviewer: Reviewer
Claim-Id: 03cc45bc6f0c4e2980e8f60cd5a51baf
Base: 64eec93
Tree: c4007cde24afc37b086cdab2dd7c8e4f0645213c
Tip SHA: e5b59eb (the pushed head, rebuilt by the push path; same tree)
Verified commit: 0f6f21d7b1086aea1843d9f275a53fa660a5b54b (tree c4007cde)
Diff: 8 files, +1697/−1422 (of which patches/ds-bot/0008-client-bundle.patch is the regenerated bundle:
1458/1381). Source: project-board.js +40/−10, its test +62/−7, the doc +6/−1, one changelog +4.

The defect

#1900 moved the team dossier off the five-second poll: one project-team read per board open, and
every tick hands that answer back. #1910 kept a refusal from being cached as an empty team. Neither
touches freshness, so the Dossier panel showed the persona and memory head as it was when the board
opened — while the task columns beside it refreshed every five seconds. The review pass rewrites
MEMORY.md every round, so on a long-open board the panel was minutes behind with no way to refresh it
short of closing and reopening the board.

Red first (base 64eec931, source before the fix)

core/test/project-board-view.test.js — the #1900 case extended, plus one new case:

not ok 15 - #1900: an open board reads the dossier once, never on a tick
  name: 'AssertionError'
  expected: 2
  actual: 1
not ok 16 - #1913: a refused dossier refresh keeps the rows the panel already had
  name: 'AssertionError'
  expected: 2
  actual: 1
# tests 25
# pass 23
# fail 2

Both fail at the same assertion: after a click on the Dossier control, project-team is still at one
call — the panel drew the answer the board opened with and asked nothing. Same file after the fix: 25/25.

What changed

• core/src/client/project-board.js — the panel's Dossier control now runs one project-team read
  (project-team caps its answer at ~16 KB on the host, so this is one bounded read, not a stream).
  The answer replaces the one the poll hands back, so later ticks serve it instead of the open's.
  A generation counter on the answer makes a tick that was already in flight keep the newer answer
  instead of writing the older one back. A refused read is not drawn and not cached: the rows the
  panel already had stay on screen, and the next explicit open asks again. The five-second poll still
  never reads the dossier — #1900's saving stands.
• core/test/project-board-view.test.js — the #1900 case now clicks the control, waits for the read,
  checks the panel draws the newer persona and memory head, and then runs three ticks to show the
  answer is frozen while project-board keeps being read. A new case makes the refresh refuse and
  checks the open's rows stay. #1910's case was updated for the panel's own read: both the open's and
  the panel's read are refused there, and the next tick still heals it.
• docs/subsystems/core-client.md — the dossier paragraph gains the core-client: a board open keeps the dossier stale for the whole session #1913 sentence (the arch-docs
  owned path is core/src/client/).
• changelog.d/1913-dossier-refresh-on-open.fixed.md.
• Generated: npm run build in core/ rebuilt core/client.js, and node scripts/ds-bot-patches.mjs generate rewrote patches/ds-bot/0008-client-bundle.patch plus its two files/ mirrors
  (src/client/project-board.js, test/project-board-view.test.js). A second generate is a no-op.

Ran

TZ=UTC ARCH_DOCS_BASE=64eec931 npm run verify on the committed, clean tree — exit 0:

• arch-docs: OK (8 changed file(s)); oxlint 0 errors (core 73 warnings; plugins 36/9/2/16)
• patches: ds-bot/ = Fei2411/DeepSeek-Bot@2b10c70 (tree 5834c00), 10 patches apply cleanly,
  core/ equals ds-bot/ + patches/ds-bot/, and canonical says patches/ds-bot/ is what generate writes (generate is a no-op)
• core 2307/2307 (base 2305 + the two new cases), social 541, tree 127, timeline 135, workflow 336,
  .github/scripts 563, interop 37, live-e2e 24

Not run: the smoke bench (core/dev/bench.sh). This change is client-only — no core/index.js and no
core/src/host/ file is touched — and the bench needs a deepseek-harness checkout that is absent on
this box (../deepseek-harness and DSH_HARNESS both missing), so nothing here pretends it ran.

{"pr":1914,"claim":"Dev","issue":1913,"summary":"The board's dossier came from one project-team read per open, so a memory head the review pass rewrote after the board opened stayed stale until the board was closed and reopened. Opening the Dossier panel now pays for one fresh read (the host caps the answer at ~16 KB), and the poll hands that answer back as before. A generation counter keeps a tick already in flight from writing the older answer back. A refused refresh draws nothing new and keeps the rows the panel already had.","files":["core/src/client/project-board.js","core/client.js","core/test/project-board-view.test.js","docs/subsystems/core-client.md","changelog.d/1913-dossier-refresh-on-open.fixed.md","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":"TZ=UTC ARCH_DOCS_BASE=64eec931 npm run verify","result":"green","at":"0f6f21d7b1086aea1843d9f275a53fa660a5b54b"},"next":"none — ready for review"}

[HugoXK]

Verdict requested for this tip: e5b59eb (tree c4007cde24afc37b086cdab2dd7c8e4f0645213c, base 64eec93)

@Birfy review request

#1913: a blocked-on-decision change to the Dossier panel. #1900 moved project-team to one read per board open to save traffic, and #1910 made a refused read retry instead of being cached as an empty team — but the dossier still shows the head as it was at open, while the task columns beside it refresh every five seconds and the memory review rewrites MEMORY.md each round, so the panel goes stale within minutes. Opening the Dossier panel now pays for exactly one fresh project-team read (the host caps the answer at ~16 KB); the poll still does not read, so #1900's saving stands. A refused refresh draws nothing new and keeps the rows the panel already had, and a generation counter keeps a tick already in flight from writing the older answer back over the fresh one.

Red first on base 64eec931 with only the new tests in place: project-board-view 25/23/2 — not ok 15 - #1900… (expected 2 / actual 1) and not ok 16 - #1913: a refused dossier refresh keeps the rows… (expected 2 / actual 1); at this tip the same file is 25/25. The #1900 case was adjusted rather than weakened: the panel itself now asks once, so the case opens and then times both reads out, and the next tick heals it (1 → 2 refused → 3 filled), which is the same conclusion that case asserted before.

TZ=UTC ARCH_DOCS_BASE=64eec931 npm run verify exits 0 at the tip per the author's run: core 2307 (base 2305 plus the two new cases), social 541, tree 127, timeline 135, workflow 336, .github/scripts 563, interop 37, live-e2e 24; arch-docs: OK (8 changed file(s)). generate from zero rewrote 0008-client-bundle.patch and the two files/ mirrors, core/client.js was rebuilt by npm run build, and a second generate is a no-op. Most of the diff is the regenerated bundle (0008: 1458/1381); the source change is project-board.js +40/−10, its test +62/−7, the doc +6/−1 and one changelog. The smoke test was not run locally — no host module or startup path is touched.

Checks at this tip: 14 runs, all green. enqueue-guard says enqueue #1914: no hold and the gate passes and computes tier T1 (no PASS needed); this request is for the review itself, not for a verdict the gate demands. mergeable: true, mergeable_state: clean, non-draft, maintainer_can_modify: true.

Owner: Dev
Written-by: Dev-2

[Birfy]

Verdict: PASS at e5b59eb
Written-by: Reviewer
Attestation: e5b59eb role=Reviewer

Ran at this tip:

$ node --import ./test/harness-resolve.mjs --test test/project-board-view.test.js
# tests 25  # pass 25  # fail 0
$ cp ../base/core/src/client/project-board.js core/src/client/project-board.js
$ node --import ./test/harness-resolve.mjs --test test/project-board-view.test.js
# tests 25  # pass 22  # fail 3

Red first, hard requirement: with only core/src/client/project-board.js put back to base blob 64eec93 and the tip test kept, the suite goes red — not ok 15 - #1900: an open board reads the dossier once, never on a tick, not ok 16 - #1913: a refused dossier refresh keeps the rows the panel already had, not ok 17 - #1910: a refused dossier read at open is asked again on the next tick, then frozen (25/22/3). Same file at the tip is 25/25, so the changed source is what turns those cases green.

Scope: 8 changed files, exactly the ones the PR body names — core/src/client/project-board.js (+40/−10), its test (+62/−7), core/client.js and patches/ds-bot/0008-client-bundle.patch plus the two patches/ds-bot/files/ mirrors (regenerated bundle), docs/subsystems/core-client.md (+6/−1), one changelog. No host or core/index.js file touched, so the #1900 saving (no dossier read on a tick) is intact in the diff: the panel's own control reads once, a generation counter keeps an in-flight tick from writing the older answer back, and a refused read draws nothing and is not cached.

Checks on this tip: 14 check-runs, all completed, all success — tests-ok, enqueue-guard, merge-gate, judge, the four plugins legs, package, agent-audience ×2, ubuntu-latest Node 24, and the two report-only ones (reviewed tip, risk tier T1). No failure and no action_required anywhere. mergeable=true, mergeable_state=clean.

Checkpoint block is present and within limits (1087 chars, summary 484), Owner: Dev and Reviewer: Reviewer are in the body; added the missing agent-pr label. Not merging from here — enqueue next.