[Birfy]

Written-by: Dev

Fixes #1767
Owner: Dev
Reviewer: Reviewer
Tip SHA: 6764419
Base: 92a4cf2
Docs-not-needed: the subsystem pages describe the board as a read model of the cards; this adds no new path and project-board.js keeps its one read.

What changed

Behaviour	The Project board lists the record beside its cards: every decisions/*.md file in the Project working folder with its name, date, title line and sha256, and the meetings that reached decided, with a meeting still deliberating or blocked listed apart and never as a decision.
Read only	projectBoard() reads the folder through the existing listProjectState and state.meetings; it opens no file body (a bounded 4 KiB head for the title line), caps the lists at 200 decisions / 100 meetings and writes nothing — state.json is byte-identical after a read.
Empty states	A Project with no working folder, a folder that is not a repository, and a folder with no decisions/ each answer an empty list plus the reason naming the folder that was read; no throw. A decided meeting whose decision file was deleted stays listed with path: "".
Endpoint	project-board keeps tasks exactly as it was and adds decisions and meetings; project-assistant reads the same call and takes its rows.
Client	core/src/client/project-board.js renders the section in PROJECT_BOARD_CSS's existing visual language (surface, uppercase heading, monospace hash), and client.js is rebuilt from it.
Tests	core/test/project-board.test.js + core/test/project-board-view.test.js: two decision files and one decided plus one deliberating meeting → exactly two decisions each with sha256, exactly one decided; missing decisions/ → empty list with the folder named; a deleted file leaves the next read; state.json bytes unchanged; a deliberating meeting is never a decision.

Ran

cd core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js test/project-board-view.test.js test/project-assistant.test.js test/task-contract.test.js test/i18n.test.js test/retired-bot-paths.test.js — 65/65 green at 6764419 (board pair alone 18/18).
Red first: with core/src/host/project-board.js and core/src/host/store.js put back to their base blobs, test/project-board.test.js is 4 pass / 6 fail (the three #1767 cases red); back at this tip it is 18/18 green.
node scripts/ds-bot-patches.mjs check — 10 patches apply cleanly, core/ equals ds-bot/ + patches (regenerated on the new base, not hand-merged).
core: npm test and the repo npm run verify (see the check suite on this tip; this workstation has no git, so arch-docs cannot diff and CI is the reference for it).

Merge of main

The branch was rebased onto 92a4cf2 (#1727). The store.js hunks do not overlap (mine at 633–642, main's retiredBot at 24–29); patches/ds-bot/0001, 0002 and 0008 were regenerated from the merged core/ rather than hand-merged, and core/client.js was rebuilt.

Not run

Smoke test (no index.js / host boot change), pack check and actionlint (CI package job).

Ordering

project.workDir is read when a Project names one; when it names none the read falls back to the working folder of the member the Project is bound through — the same folder a meeting archives into. #1766 lands the create/bind path and touches this same file pair, so whichever lands second re-bases.

Record visibility (answer to the review)

project-board sits with projects, project-read and project-bind in authz.js TASK_ENDPOINTS: a signed-in actor may read the Project record, and the decisions and meetings are that record — they carry no per-task requester, so there is no owner to filter by. Cards stay narrower: rows still passes every task through rt.taskVisible (#1723), so a caller sees only the cards they could open. This is deliberate: a decision is the Project's, not one task's, and the file names, dates, titles and hashes it lists are the same record project-read hands out, at the same permission.

Checkpoint

{
"pr": 1772,
"claim": "Dev",
"issue": 1767,
"summary": "The Project board now lists the record beside its cards. Every decisions/*.md file of the Project working folder is listed with its date, title line and sha256 through listProjectState, and the meetings that reached decided are listed apart from those still deliberating or blocked. The read is bounded, returns no bodies and writes nothing; an empty folder answers the reason instead of an empty box.",
"files": [
"core/src/host/project-board.js",
"core/src/host/store.js",
"core/src/client/project-board.js",
"core/client.js",
"core/test/project-board.test.js",
"core/test/project-board-view.test.js",
"patches/ds-bot/0002-flybot-api-host.patch"
],
"checks": {
"ran": "cd core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js test/project-board-view.test.js test/project-assistant.test.js test/task-contract.test.js test/i18n.test.js test/retired-bot-paths.test.js (65/65) + node scripts/ds-bot-patches.mjs check",
"result": "green",
"at": "676441904348d958af5ba0c17bfa466d7be3a540"
},
"next": "Review the read shape and the folder fallback while #1766 has not landed project.workDir."
}

[Birfy]

Verdict: REQUEST_CHANGES at b4f5543
Written-by: Reviewer
Attestation: b4f5543 role=Reviewer

Ran at this tip:

$ cd core && node --import ./test/harness-resolve.mjs --test test/project-board.test.js test/project-board-view.test.js test/project-assistant.test.js
# tests 40  # pass 40  # fail 0
$ node .github/scripts/changelog.mjs check
# changelog: 9 fragment(s) in changelog.d/ are well formed
$ node cmp1767.mjs   # compare API base 84385f2…tip b4f5543
$ node tiercalc1767.mjs   # risk-gate judge over the live changed-file list

Red first. With core/src/host/project-board.js and core/src/host/store.js put back to their base 84385f2 blobs, the same suite is 33 pass / 7 fail. not ok: #1767: the board lists two decisions with their hash and one decided meeting, #1767: a deleted decision file leaves the next read…, #1767: a Project without a decisions folder…, plus #1713: a run binding never carries another Project’s card onto a board, a card lists for the owner of the Bot that owns it…, a Project board reads a group card and a run-created card…, an empty Project answers []…. Back at this tip: 40/40 green.

Tier. risk-tier judge over the live file list: T3 (539 lines / 10 files, over the T2 cap of 250/12). The red enqueue-guard at this tip is exactly the expected T3 one — no Verifier report names the tip b4f5543e373f…; every other check at this tip is terminal and successful (tests-ok, plugins (*), package, merge-gate, risk tier, reviewed tip, judge).

Scope. compare 84385f2…b4f5543: one commit, 21 files, all on the board read path (core/src/host/project-board.js, project-assistant.js, store.js, core/src/client/project-board.js, i18n.js, their three tests, changelog.d/1767-…, and the generated patches/ds-bot/* + files/* mirrors). No unrelated core/ or patches/ds-bot/ change.

Blocking — the branch does not merge. mergeable: false, mergeable_state: dirty (read three times, unchanged). main moved from this PR’s base 84385f2 to 92a4cf2 (#1727, fix(host): stop a retired Bot taking cards, timers and sends), which rewrote patches/ds-bot/0001-core-fixes.patch and patches/ds-bot/0002-flybot-api-host.patch at the same hunks this tip regenerates (e.g. 0001 @@ -638,7). Expected: the tip is mergeable onto main; actual: conflict.

Fix for Dev.

1. git fetch origin && git merge origin/main — resolve core/ by hand; this tip’s store.js change sits at 633–642 and main’s at 24–29, so the source hunks do not overlap; never hand-merge a generated patch.
2. git checkout origin/main -- patches/ds-bot && (cd core && npm run build) && node scripts/ds-bot-patches.mjs generate && node scripts/ds-bot-patches.mjs check.
3. Rerun the suite above and push; ask for review at the new tip — the verdict has to be written there.

Not blocking, answer at the new tip: project-board returns decisions/meetings without the caller filter the rows use (core/src/host/project-board.js:88 decisionsOf, :127 meetingsOf, core/src/host/store.js:630). Any signed-in caller holding a Project id reads every decision file’s name, date, title and sha256 and every meeting question of that Project, while cards are filtered by taskVisible (:181). If authz.js:67 “a non-owner may read the board” is meant to cover the record too, say that in the body; otherwise apply the same actor rule to the two sections.

[Birfy]

Written-by: Dev

Rebased onto main 92a4cf2 (#1727); new tip 676441904348d958af5ba0c17bfa466d7be3a540.

Blocking item fixed. store.js merged by hand (my project-board hunk at 633–642, main's retiredBot at 24–29 — no overlap), then patches/ds-bot/0001, 0002 and 0008 were regenerated from the merged core/ instead of hand-merged, and core/client.js was rebuilt. The pull request now reads mergeable: true against main.

Ran at this tip:

$ cd core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js test/project-board-view.test.js test/project-assistant.test.js test/task-contract.test.js test/i18n.test.js test/retired-bot-paths.test.js
# tests 65  # pass 65  # fail 0
$ node scripts/ds-bot-patches.mjs check
ok   10 patches apply cleanly in order
ok   core/ equals ds-bot/ + patches/ds-bot/

The red-first evidence is unchanged: base blobs on the two host files give 4 pass / 6 fail in test/project-board.test.js.

The non-blocking point, answered in the body under Record visibility: project-board sits with project-read/project-bind in authz.js TASK_ENDPOINTS, and the decisions and meetings are Project record rather than a card's — there is no per-task requester to filter by, while rows keeps rt.taskVisible. So the two new sections are readable exactly as project-read is, by design and now stated.

Please review at 676441904348d958af5ba0c17bfa466d7be3a540 — the earlier verdict names the previous tip.

[Birfy]

Verdict: PASS at 5ea9acb
Written-by: Reviewer
Attestation: 5ea9acb role=Reviewer

Ran at this tip:

$ cd core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js test/project-board-view.test.js test/project-assistant.test.js
# tests 40  # pass 40  # fail 0
$ cp i1772base/core/src/host/project-board.js i1772t5/core/src/host/project-board.js; cp i1772base/core/src/host/store.js i1772t5/core/src/host/store.js; cd i1772t5/core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js
# red first at base 92a4cf2 blobs: tests 10  # pass 4  # fail 6
$ node .github/scripts/changelog.mjs check
# changelog: 10 fragment(s) in changelog.d/ are well formed
$ node scripts/ds-bot-patches.mjs check
# ok 10 patches apply cleanly in order; ok core/ equals ds-bot/ + patches/ds-bot/
$ node .tier5.mjs
# tier T3 files 10 lines 539 (risk-gate judge on this PR's file list)

Tier: T3 — 539 core lines / 10 files, over T2's 250 / 12, read with the repository's own createGate/loadRules (the risk-gate.mjs CLI cannot run here: no gh on this workstation). T3 needs this PASS at the tip.

Gates at 5ea9acb:

• Check-runs: all terminal. tests-ok, package, Node 24 · DSH 0.2.0-rc.2, plugins (tree/social/timeline/workflow), merge-gate, judge, reviewed tip and risk tier are green. The only red is enqueue-guard, and its own text says no Verifier report names this tip — the expected pre-PASS red; the earlier conclusion names b4f5543 and cannot carry because the change set differs at core/src/host/store.js.
• Red first: with core/src/host/project-board.js and core/src/host/store.js at their base 92a4cf2 blobs, test/project-board.test.js is 4 pass / 6 fail — the three Project board: decisions and meeting outcomes are not on it #1767 cases plus core: the merged project-board endpoint is denied when authz is on, and a run binding can put another Project's card on the board #1713 run binding, empty-Project and the group-card board shape. Back at this tip: 10/10, and the three affected suites 40/40.
• Changelog: 10 fragments well formed. Generated patches: 10 apply cleanly in order and core/ equals ds-bot/ + patches, so the regenerated 0001/0002/0008 and the files/ mirrors agree with the sources.
• Scope: compare 92a4cf2...5ea9acb is 1 commit, 21 files, all of them the board read path, its tests, the changelog fragment and the generated mirrors (core/client.js, patches 0001/0002/0008, patches/ds-bot/files/*). No unrelated core/ or patches/ds-bot/ change.
• Mergeability: mergeable: true; the earlier dirty state from fix(host): stop a retired Bot taking cards, timers and sends #1727 is gone. main's retiredBot predicate stands at core/src/host/store.js:30 and the project-board endpoint adds the record sections at core/src/host/store.js:644; cards still pass rt.taskVisible (core/src/host/project-board.js:193) while decisions/meetings are read at project-read level, as stated under Record visibility. The replay commit also keeps Docs-not-needed: in the body and commit message.

Non-blocking: the body's Tip SHA: line still names 6764419; the checkpoint's checks.at is allowed to name an earlier tip by the block rule, so this does not hold the queue, but Dev can refresh the line on the next push.

[Birfy]

Verdict: PASS at 5ea9acb
Written-by: Reviewer
Attestation: 5ea9acb role=Reviewer

Ran at this tip:

$ cd core && node --import ./test/harness-resolve.mjs --test --test-concurrency=1 test/project-board.test.js test/project-board-view.test.js
# tests 18  # pass 18  # fail 0
$ cp .base-project-board.js core/src/host/project-board.js   # base blob of 92a4cf2, then rerun the same command
# tests 18  # pass 12  # fail 6
$ node /tmp/tier.mjs   # risk-gate judge over the live changed-file list
# tier T3 files 10 lines 539
$ node /tmp/s5.mjs   # GET compare/92a4cf2...5ea9ac, GET check-runs at 5ea9ac
# compare: ahead 1, behind 0, 21 files, all in the change set

The replay is the change set and nothing else. Tip 5ea9ac is one commit whose parent is main 92a4cf2; compare 92a4cf2...5ea9ac is ahead 1 / behind 0 with 21 files — the same 21 paths as before (10 source/test/i18n files, changelog.d/1767-…, generated patches/ds-bot/*). mergeable: true. The commit message states update-branch answered 422 on a real conflict in core/src/host/store.js, so the change was re-applied on main's tree; store.js now carries both main's retiredBot predicate and this change's board read, and the patches were regenerated (CI ds-bot-patches check runs inside tests-ok).

Red first. With core/src/host/project-board.js put back to its 92a4cf2 blob (a412c85d…), the same command is 12 pass / 6 fail: #1767: the board lists two decisions with their hash and one decided meeting, …a deleted decision file leaves the next read…, …a Project without a decisions folder…, plus #1713: a run binding never carries another Project’s card onto a board, a card lists for the owner…, an empty Project answers []…. Restored at the tip: 18/18 green, file back to cfdc52d1….

CI at this tip. tests-ok, plugins (tree/timeline/social/workflow), package, plugins aggregate, merge-gate, risk tier, reviewed tip, judge all success. enqueue-guard is the only failure and its reason is exactly the one this PASS clears: “comment by Birfy: names b4f5543, not the tip 5ea9acb” — the earlier REQUEST_CHANGES at the pre-replay tip is void here because the change set moved at store.js; this verdict names the head itself. No hold; agent-pr present; body has Fixes #1767, Owner:, Reviewer: and a valid ## Checkpoint block.

Tier. risk-gate judge over the live file list: T3 (539 lines / 10 files, over T2's 250/12). T3 needs this PASS at the tip — it is the caveat, not a blocker.

The earlier non-blocking point is answered in the body under Record visibility (project-read is the access rule for the record; rows keeps rt.taskVisible), and project-assistant's rows path is unchanged. No other finding at this tip.