Repository navigation
feat(history): history.db, usage projections, simlock stats, GET /v1/stats and console figures (#623) - #626
Merged
Merged
Conversation
V3RON
marked this pull request as ready for review
October 16, 2026 11:34
This was referenced Oct 16, 2026
Closed
Closed
V3RON
added this pull request to stack #691
October 18, 2026 16:34
This was referenced Oct 19, 2026
… total rows, and sizes the file on disk
…the main thread, refuses a failed migration
33 failing -> 0 failing (unit)
Document the cause in the core manual's quarantine step, restore unrelated Known gaps wording, and cover the not-quarantined guard of the Cause fact.
…gnature; a non-stall hand-over is a delete-failed cause (#635)
Spec tests green, 14 failing -> 0 failing (unit and e2e waiting-requests).
…calls (#636) 0 failing -> 0 failing.
…e, in line order (#636)
…ILED; the twice-failed skip logic and provisioning-failed reason are gone (#636)
1 failing -> 1 failing
…ike the real one, so no agent-fallback notice reaches stderr (#632) 1 failing -> 0 failing
…is rounded in the CSV; one contract import in http/app (#632)
…der and the ledger in-flight key; docs name seven operator routes; reserved name stats in the optional-modules test (#632)
…the spec decides (#632)
… granted and three charts (#633)
…tats; a range picker 14 failing -> 0 failing (unit specs; console lane not yet run).
…cs follow three charts Console lane (chromium): 5 failing -> 0 failing.
…; Overview e2e runs past a completed minute and checks chart rows (#633)
…cked tiles and charts (#633)
Turns the Usage tests green: the view model, the screen, the route and icon, the Granted tile's link, docs. 13 failing -> 0 failing (unit)
…orward follows NAV's last two pages; counts keep a space between rows 0 failing (unit), 5 passing (usage e2e)
0 failing (unit)
…nd the held column header (#634)
…cs list Usage and the requester columns (#634)
V3RON
force-pushed
the
feature/623-adr
branch
from
October 19, 2026 12:29
b53ad76 to
d71eb83
Compare
V3RON
changed the title
V3RON
added a commit
that referenced
this pull request
Oct 20, 2026
…ations (#718) Proposes ADR 0035 for #707. - A new gateway-only module, `src/alerts`, built by `main.ts`; not an optional module. - Outbound HTTP through a new `WebhookPoster` port; redirects never followed. - Config `gateway.alerts.destinations`: named destinations, `slack` or `generic`, a fixed list of eleven events, https (http on loopback only). - Delivery: one send at a time per destination, 10 s per try, three tries, at most 100 waiting, memory only. - `generic` body is the event envelope, signed with `X-Simlock-Signature: sha256=…`. - `alerts.test` admin operation, gateway only. Numbered 0035: 0032 and two 0033s are taken by open ADR PRs (#626, #702, #704). Docs only. This PR stays open at the bottom of #707's stack and merges with its last task. ## Review Spec review: 0 blocking, 5 fixed, 0 notes. Code review: skipped. Claims review: skipped. Rounds: 3. Tokens: n/a. Assessment: complete. Fixed: R1 redaction names history.db; R2 secret rule moved to each format; R3 subscribe citation; R4 Slack escaping; R2b secret rule restored in section 5. *Written by an agent.* --------- Co-authored-by: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Delivers #623: the event history moves to
history.db, with usage projections,simlock stats,GET /v1/statsand the console's figures. It also includes ADR 0032.This PR carries the whole feature. The stack's PRs were reviewed one by one, and then a stack sync pushed every branch to one commit. GitHub then marked them as merged into each other, never into
main. Their reviews stay there:usage.getandsimlock statsfrom the projections #631 → feat(stats): usage.get and simlock stats from the projections #711GET /v1/statsand thesimlock stats --csvledger #632 → feat(http,cli): GET /v1/stats and the simlock stats --csv ledger #724After the sync onto
main, a fix-check reviewed the conflict resolutions. Its fix makeshistory.dband its WAL/SHM files owner-only (0600), as #685 did forevents.jsonl.Closes #629, closes #630, closes #631, closes #632, closes #633, closes #634, closes #635, closes #636, closes #637.
Status
Implement: done Review: per-task PRs passed; sync fix-check passed Hardware: n/a Gate: running
Review
Spec review: skipped. Code review: 4 blocking, 4 fixed, 1 notes. Claims review: 0 blocking, 0 fixed, 0 notes.
Rounds: 1. Tokens: 29.0M.
Written by an agent.