ledger: count issue-tagged commits and repo seat messages (#1506)
This commit is contained in:
@@ -2152,3 +2152,48 @@ one scan; the seat's attempt to agent-send back to `control-board` was
|
||||
refused, correctly, since the board has no pane. Fix: every board message
|
||||
ends with a fixed trailer saying to answer in the seat's own session.
|
||||
|
||||
|
||||
## 2026-09-12 — Ledger piece 3 intake (#1506)
|
||||
|
||||
Before: no numeric report ties issue-tagged refactor commits to repo seat user
|
||||
messages. Darkwing owns packages/ledger and fixtures; independent review precedes
|
||||
commit/push to refactor. Brief and Gate D remain on the control-board plan page.
|
||||
Single-request constraint: Gitea caps issue lists at 50. Query issues updated
|
||||
since the start date, reject a full page as potentially incomplete, and show
|
||||
unknown metadata for commit-referenced issues absent from that response.
|
||||
The live date-range query returned 19 issues; the unfiltered query hit the cap.
|
||||
No pagination, credential inspection, fleet reads, or unrelated source changes.
|
||||
|
||||
## 2026-09-12 — Ledger implementation ready for review (#1506)
|
||||
|
||||
After: packages/ledger provides the read-only CLI, two tables, JSON and explicit
|
||||
unknown values. Fixtures pass 20/20; combined ledger, board, seat and registry
|
||||
Node suites pass 202/202. Syntax and diff whitespace checks pass. No root CI
|
||||
workflow exists, and no live/task/release suite or deployment is claimed.
|
||||
Live run for September 6 through 12 succeeded after fixing the existing
|
||||
gitea-api.sh cleanup trap: a no-body GET used to return 1 even on HTTP 200.
|
||||
The one-line fix has offline GET 200, POST 201 and GET 403 regressions.
|
||||
LEDGER-1506-R1 sent to Filbert on default socket via agent-send.sh, exit 0,
|
||||
transport dispatched with application acceptance unknown. Exact candidates and
|
||||
pre-publication totals are in reviews/2026-09-12_ledger-review-request.md.
|
||||
Waiting for his verdict before publication; he owns the reply wake. No timer.
|
||||
|
||||
Ledger verification addendum #1506: clean HEAD-plus-candidate Node suite 202/202.
|
||||
First clean copy omitted tools/tmux, so the board executable-presence test failed;
|
||||
restoring that tracked dependency fixed the test setup, with no source change.
|
||||
Concurrent control-board planning commit db0d784b included the CURRENT intake
|
||||
line while adding DEFERRED.md. Reconciled and preserved it; candidate source
|
||||
hashes unchanged. Gitea progress comment 26061 records review and test status.
|
||||
|
||||
## 2026-09-12 — Ledger independent approval and publication gate (#1506)
|
||||
|
||||
Filbert APPROVED LEDGER-1506-R1, independently ran 20/20 offline fixtures,
|
||||
verified all six pinned SHA-256 hashes, and reproduced the GET cleanup defect.
|
||||
Darkwing reverified those hashes and the shared worktree before integration.
|
||||
Review: docs/plans/reviews/2026-09-12_ledger-verdict.md. Helper hardening is
|
||||
recorded in DEFERRED.md, not silently added to the reviewed patch. Correction
|
||||
to the review provenance wording: db0d784b also includes the CURRENT intake
|
||||
line, not only DEFERRED.md; its diff on the six candidate paths is still empty.
|
||||
Publication is authorized to refactor only. Gate D and #1506 closure await
|
||||
Jason writing a sentence with a measured number into CURRENT.md. No WebUI,
|
||||
fleet, live deployment, role changes or unrelated files are part of this commit.
|
||||
|
||||
Reference in New Issue
Block a user