ledger: count issue-tagged commits and repo seat messages (#1506)
This commit is contained in:
+15
-6
@@ -50,12 +50,21 @@ Gate C passed 2026-09-12 on 867619dc (logged by Jason at 4f830680):
|
||||
answered in its own session with no send attempt, and the row showed the
|
||||
answer on the next scan. #1505 is closed.
|
||||
|
||||
Next action: Darkwing is building piece 3, the ledger, under #1506. Jason approved it on 2026-09-12 and
|
||||
the brief is on the plan page, section "Piece 3: ledger (numbers for the
|
||||
rails)": `packages/ledger`, read-only CLI over the local git log, Gitea
|
||||
issues and the repo seats' session logs, with Gate D (Jason writes one
|
||||
sentence with one number from it into this file). Open the Gitea issue
|
||||
first. Then the WebUI on Dewey's Console design absorbs the board as its
|
||||
Next action: Jason runs Gate D for piece 3, the ledger, under #1506:
|
||||
`node packages/ledger/src/cli.mjs --since 2026-09-06 --until 2026-09-12`.
|
||||
Choose one number to move next week and write that sentence with the number
|
||||
into this file. Do not infer acceptance from the implementation or tests.
|
||||
|
||||
`packages/ledger` is implemented: read-only local refactor subjects, one
|
||||
Gitea issue request, repo seats' user messages, two tables and JSON. Ledger
|
||||
fixtures 20/20; ledger, board, seat and registry suites 202/202, also checked
|
||||
in a clean candidate copy. Filbert independently APPROVED all six pinned
|
||||
source/test/doc files in `reviews/2026-09-12_ledger-verdict.md`. The helper's
|
||||
no-body GET cleanup exit defect is fixed and regression-tested. Counting
|
||||
rules, one-page refusal and unknown metadata limits are in the package README.
|
||||
Jason authorized commit/push to refactor; #1506 stays open for Gate D.
|
||||
The brief remains in the plan page under "Piece 3: ledger (numbers for the rails)".
|
||||
After Gate D, the WebUI on Dewey's Console design absorbs the board as its
|
||||
first screen. Close #1503 when Jason says the page answers "who
|
||||
is waiting on me" without him opening a terminal. Out of scope until he
|
||||
asks: auth or provider registry, roster schema changes, hooks/plugins, comms,
|
||||
|
||||
Reference in New Issue
Block a user