chore(deps-dev): @types/node 22.20.4 and vitest 5.0.2

[MongLong0214]

No-Issue: two Dependabot dev-dependency bumps, carried together so one canonical rebuild covers both

• @types/node 22.20.1 → 22.20.4 (chore(deps-dev): bump @types/node from 22.20.1 to 22.20.4 in the dev-dependencies group #1160) — inside the pinned major, which is
  what the ignore rule added this morning deliberately still allows.
• vitest 4.1.11 → 5.0.2 (chore(deps-dev): bump vitest from 4.1.11 to 5.0.2 #1161) — a major, so it was run rather than assumed.

Both branches are merged, not cherry-picked, so both pull requests close by
reachability when this lands.

typescript 7.0.2 (#1162) is not here. It is the native compiler and does
not typecheck against this tsconfig.json as Dependabot proposed it — 636
Cannot find name 'process' errors, with @types/node 22 and 26 alike, fixable
by adding "types": ["node"]. That makes it a compiler swap affecting the bytes
in dist/, not a dev-dependency bump; the reasoning is on #1162.

Verification

• npm ci clean on this lockfile; installed versions read back 22.20.4, 5.0.2
  and typescript 5.9.3.
• tsc -p tsconfig.json --noEmit clean.
• Full suite under vitest 5: 212 files, 4614 passed, 4 skipped, 0 failed.
• The lockfile is Dependabot's own, not regenerated. Regenerating it here drops
  the ten libc hints from the optional platform packages — the hazard
  r-honoadvisory records on this path ("the diff looks like ordinary churn"),
  and the defect fa9909a repaired. grep -c '"libc"' is 10, as on main.

dist/ is absent on purpose: canonical-merge.yml rebuilds it and regenerates
the manifest.

[github-actions]

CommitLore — record lint

Trailers: clean — 3 commits in origin/main..e12cbe42af416fbe364b942776c9c35a8666c4a3
Active constraints: 111 limits · 178 ruled-out · 61 warnings — from 111 records over 2 changed paths

Active constraints for the paths this PR touches

Limits (111)

• r-2fb1c649b3ad 922f95f — 새 ip-address advisory가 기존 production audit gate를 실패시켜 이번 릴리즈에 compatible transitive patch가 필요하다.
• r-3081e462f9b8 3b2fd09 — canonical-merge publication의 force push가 승인 조건과 충돌하여 공식 pinned builder로 artifacts를 만들고 일반 PR로 제출한다.
• r-ef0defcd69a8 11ef133 — the previous version occurs 62 times across twelve files on main; 59 are install pins and manifest versions and moved, and the three that stay are CHANGELOG.md's 1.6.0 heading and the lockfile's sourcemap-codec version and tarball URL
• r-276fed4dac2b d71a55c — after the bump the only occurrence of the previous version is CHANGELOG.md's own 1.5.1 heading, which is that release's section and must not move; the other 59 across eleven files are install pins and manifest versions
• r-release151 94e85f9 — two occurrences must not move and were read rather than filtered -- CHANGELOG.md carries 1.5.0 as its previous heading, and docs/adr/ADR-0009 carries gitlore@1.5.0, which is a different package's version and a coincidence of numbers
• r-release150 df9fe0d — enforcement exists only where a Bash PreToolUse hook does; a person at a terminal, CI, a script and every host without that hook get a simpler command and no gate
• r-release150 df9fe0d — the trivial thresholds are chosen rather than measured, and are not configurable in this release -- a trivial block in the policy would move policy_identity_hash and invalidate every binding and pending transaction in flight
• r-release142 208b821 — the version pins moved across 11 files; installer/canonical-artifact.json is regenerated by the canonical build and is deliberately not among them
• r-treebind1030 ad4c4ef — the argument is optional, so a caller that does not pass it binds to the server's checkout exactly as before -- this closes the silent case only for callers that say what they meant
• r-treebind1030 ad4c4ef — the assertion compares working trees, so a server and caller in the same tree at different times are indistinguishable; HEAD moving under a prepared transaction is still the receipt's job (r-requirereceipt1005)
• r-treebind1030 ad4c4ef — commitlore capture on the CLI is unchanged and needs no assertion, because it binds to its own working directory -- only the MCP surface can disagree with its caller
• r-measurewrites988 4edfd9f — dbstat is a SQLite compile option, and the harness prints an empty table rather than failing where it is absent -- an empty table there means the measurement did not run, not that the cost is zero
• r-measurewrites988 4edfd9f — a bare npx vitest run still reads whatever dist/ is on disk; only the two documented commands build first, and nothing but a paragraph in CONTRIBUTING guards the third
• r-buildbeforetest960 346006a — npm test and a bare vitest run are untouched, so the same trap is still open for anyone who reaches past the documented command -- CI builds explicitly, which is why that is tolerable rather than fixed
• r-believablesuite960 3ee700c — the harness reverses one hunk at a time, so a fix spread over two hunks that only fails together reads as two unguarded changes
• r-believablesuite960 3ee700c — 120s is a measurement from one machine; a slower one needs its own number rather than this one inherited
• r-pinnedmirror957 a06b984 — a note's own block still costs a process each, because %(trailers) parses the annotated commit's message and there is no atom for a note body
• r-pinnedmirror957 a06b984 — the reachability filter still reads HEAD at listing time, so a HEAD that moves mid-pass can still change which notes are in scope; only the mirror is pinned here
• r-probeconsumers975 adcbd50 — the block cache lives on CollectCache and therefore for one invocation only -- hoisting it to module scope would serve a rewritten message from memory, which is the staleness r-staleonepass names
• r-probeconsumers975 adcbd50 — doctor still spends 71 parses against a complete index, through its own short per-branch ranges; batching within a range trades N parses for one batch and a short range has few, so the batch has to span ranges to help there
• r-monotonic968 8f5ee12 — two unbudgeted rebuilds racing still overwrite each other, and repeated replacement can still keep a drain from converging -- neither is closed by this
• r-monotonic968 8f5ee12 — the comparison is inside the write transaction and the scan is not, so a rebuild can still do the whole scan and then discard it; what it cannot do is publish it over something better
• r-probebatch951 8d78b62 — the equivalence is proven over this repository's 114 candidate paragraphs and sixteen constructed shapes, not over every paragraph git can parse -- the two shapes that broke the first design were both outside the first corpus
• r-probebatch951 8d78b62 — one temp directory per call, removed in a guarded finally; a process killed with SIGKILL leaves it for the operating system
• r-probebatch951 8d78b62 — the batch shares an answer between identical paragraph texts within one call, which holds only while git's configuration is fixed for that call
• r-atomreuse951 eb2869d — the saving is one process per message that reaches the recovery pass, so a history with no multi-block messages sees no change at all -- 20,000 generated commits spent zero interpret-trailers before this and spend zero after
• r-atomreuse951 eb2869d — atomIsAmbiguous still sends a message to the process, so the count is bounded by the framing of real messages rather than by a rule
• r-resume951 83f5629 — the drain reads one batch before its deadline may cancel anything, so a call can overshoot its slice by one batch -- without that floor a batch costing more than the slice is cancelled every time and the queue never drains at all
• r-resume951 83f5629 — a note's body is still read through the live ref after the mirror was listed from it, so a single invocation can cross a notes update; the queue now carries its originating ref, which closes the resumed case and not that one
• r-resume951 83f5629 — the equivalence is proven on this repository and on synthetic histories of 400 commits, not over every repository shape
• r-release1219 6fd1ed5 — the pin count is a property of this tree and grows with each README section, so the next release measures it rather than reusing 59
• r-release1218 3ba5d09 — the pin count is a property of this tree and grows with each README section, so the next release measures it rather than reusing 59
• r-release1217 4836a95 — the pin count is a property of this tree and grows with each README section, so the next release measures it rather than reusing 59
• r-release1216 573d14c — the pin count is a property of this tree and grows with each README section, so the next release measures it again rather than reusing 59
• r-release1215 b6d2cfe — the pin count is a property of this tree; the surface grows with each README section, so the next release must measure it again rather than reuse 44
• r-release1214 6e91b8e — dist/ is not rebuilt here -- the canonical bundle is rebuilt on linux/amd64 by canonical-merge.yml, and a macOS esbuild output would not match CI
• r-release1213 86f6dab — dist/ is not rebuilt here -- the canonical bundle is rebuilt on linux/amd64 by canonical-merge.yml, and a macOS esbuild output would not match CI
• r-release1212 0e93f7c — dist/ is not rebuilt here -- the canonical bundle is rebuilt on linux/amd64 by canonical-merge.yml, and a macOS esbuild output would not match CI
• r-release1211 24dbdcf — dist/ is not rebuilt here -- the canonical bundle is rebuilt on linux/amd64 by canonical-merge.yml, and a macOS esbuild output would not match CI
• r-release1210 da1cc9f — dist/ is not rebuilt here -- the canonical bundle is rebuilt on linux/amd64 by canonical-merge.yml, and a macOS esbuild output would not match CI
• r-release129 276feed — dist/ and installer/canonical-artifact.json are absent by design, so artifact:verify fails on this tree -- canonical-merge.yml rebuilds them on linux/amd64
• r-release128 795791c — dist/ and installer/canonical-artifact.json are absent by design, so artifact:verify fails on this tree -- canonical-merge.yml rebuilds them on linux/amd64
• r-release127 ba88444 — dist/ and installer/canonical-artifact.json are absent by design, so artifact:verify fails on this tree -- canonical-merge.yml rebuilds them on linux/amd64
• r-honoadvisory d339291 — this repairs one resolution rather than the class -- the next advisory in a transitive production dependency will block a release the same way, and nothing here notices earlier
• r-release126 55e8d79 — dist/ and installer/canonical-artifact.json are absent by design, so artifact:verify fails on this tree -- canonical-merge.yml rebuilds them on linux/amd64, where a macOS esbuild output would not match
• r-release125 9d03977 — dist/ and installer/canonical-artifact.json are not in this commit, so artifact:verify fails on this tree by design -- canonical-merge.yml rebuilds them on linux/amd64, where a macOS esbuild output would not match
• r-release121 9845d44 — npm audit is a claim about advisories published now, not about the code; and the canonical build was reproduced on one machine against the pinned image digest, which CI repeats twice but no one has repeated on another date
• r-depsbatchbump 42013a6 — says nothing about behaviour changes inside SDK 1.30.0 itself; the suite covers this repository's use of the SDK, not the SDK
• r-fasturiqsaudit 1752273 — an audit is a claim about advisories published at this moment, not about the code; a clean run says nothing about tomorrow's disclosures
• r-cdebremoval 36ae3ab — four documents still mention CDEB and are deliberately kept -- ADR-0033, the archived readiness SSOT, an archived handoff, and two CHANGELOG lines. They are the record of decisions that were made, and rewriting them would be deleting evidence rather than code
• r-cdebremoval 36ae3ab — one full-suite run in the middle of this work reported a single failure that the next two runs did not reproduce, with no relevant change between them. Its name was not captured before the output was discarded, so it is recorded as an unidentified flake rather than as something this commit fixed
• r-v5stage1r1reviewfixes 87cacec — the pilot-gate custody gap is open and needs role separation -- execution, custody of arm-coded outcomes, and continuation held by different parties. That is an owner decision and it has to be settled before the pilot, not after
• r-v5stage1r1reviewfixes 87cacec — the firewall now names who produced the maintenance need and refuses a producer not declared record-blind, but a declaration is not evidence. Making it evidence needs an attestable isolated authoring environment this layer does not have
• r-v5stage1r1reviewfixes 87cacec — tau_squared_bound = 0.06 is a frozen assumption, not a measurement. It is conservative in the direction that matters -- lower true heterogeneity means the study detects more than promised -- but nothing here establishes the true value
• r-v5stage1r1designlayer 28699d8 — the task-author firewall has still never run. Whoever built this corpus has read all 241 records, so the record-blind half cannot be satisfied from here -- it needs an author whose only inputs are the base tree and the maintenance need, with the manifest proving it
• r-v5stage1r1designlayer 28699d8 — no oracle exists for any of the 62. Stage 0 recorded that reviewers thought one could be written; between that and a validated discriminating oracle sits the whole of G2, and nothing has crossed it
• r-v5stage1r1designlayer 28699d8 — the between-candidate variance in the power table is a range I chose to bracket, not a measurement. The pilot supplies the real value, and only then does the detectable effect stop being a family of curves
• r-v4qualification b8ff1b9 — G3 and G4 were judged from the commit message, the changed paths and the ruling. Neither reviewer read the current code or ran a test, so both are informed judgements about a maintenance task rather than measurements of one. G5 classifies whether an oracle could be written; none was built
• r-v4qualification b8ff1b9 — this says nothing about whether recording decisions helps an agent. It says the four surveyed repositories cannot supply gold that is independent of the records being tested, which is a fact about these repositories and this gate
• r-v3terminalseal 7754f1a — the placeholder row remains in the ledger and always will. This makes it legible, not absent, and a reader who takes digests on faith rather than reading the deviation is still misled
• r-v3terminalseal 7754f1a — the canonical digest binds the artifact list it is given. A transition that names too few artifacts is bound to a partial set, and nothing here decides what the right set is for a future study
• r-v3terminalseal 7754f1a — guard coverage is unchanged -- thirteen exclusion kinds remain uncovered and one scan inert, recorded in the mutation baseline
• r-release120 b073960 — the passive notice only speaks once a check has landed, so the first invocation after this install says nothing however out of date the next release finds it. That is the trade the zero-latency design buys, and the answer arrives on the following command
• r-rel114 9692b6d — the README restructure and the mobile hero redesign are not in this release, so the four READMEs remain long and the hero's labels remain small at 375px
• r-builderpin cb1515f — nothing checks that the pinned digest still exists upstream, so a digest deleted from the registry surfaces as a build failure rather than as a clear message
• r-rel113 17a1301 — #749 question 1 stays open -- a fix that lives in the hook reaches a repository only on its next visit, and nothing on this machine knows which repositories exist
• r-rel112 ad6fee3 — the readback confirms the link, not that the interpreter behind it runs -- doctor remains the check for that
• r-rel112 ad6fee3 — this repairs the installer; a machine already upgraded to 1.1.0 or 1.1.1 keeps its stale current until the installer is re-run, which is why the note names the command to check
• r-rel111 8c29f5d — Hermes still fails on that machine for a cause that is not this one and is not yet named (Windows: every detected host fails to wire — the temp filename carries the whole path, and hasCommand cannot see a .cmd #716)
• r-rel111 8c29f5d — a zero-byte .cursor/mcp.json on the tester's machine is a user file; the installer read the file it says it reads and reported the true reason
• r-rel111why 8c29f5d — this changes the note, not the behaviour -- the behaviour shipped in the merged branch and is already covered by artifact:verify
• r-rel110 d9a041f — this release does not make host wiring work on Windows -- detection still cannot see a .cmd and spawn still cannot run one (Windows: every detected host fails to wire — the temp filename carries the whole path, and hasCommand cannot see a .cmd #716)
• r-rel110 d9a041f — 1.0.0 through 1.0.2 have no CHANGELOG entries; a pointer to the releases page stands in rather than reconstructing them
• r-rellock110 d9a041f — nineteen version surfaces was already wrong before this -- the lockfile makes it twenty-one, and the count is only ever known after the gate says so
• r-relmanifest110 d9a041f — this is the release commit's own repair, not a fix -- the next release will need the same regeneration for the same reason
• r-rel102 25c11ed — an installer-boundary fix reaches nobody until it is released
• r-rel101 b65e34f — a distribution-boundary fix reaches nobody until it is released
• r-680ver 47359a1 — an assertion that reads the source it checks proves nothing
• r-rel100 47359a1 — a published install URL must resolve the moment it is published
• r-canon605 f474cf4 — esbuild resolves a platform-specific binary
• r-rel0820 59c6730 — release versions must agree across manifests, lockfile roots, installer pins, and the runtime CLI
• r-pretag01 86e0153 — registers_commitlore reads the key, so a config that registers under a different key -- a host with its own naming -- still reads as unregistered and is wired again
• r-engfloor01 fe83524 — the parser covers the range shapes npm packages actually publish -- comparators like >=22 <23, and pre-release identifiers, are read by their first version and not by their bounds
• r-nodefloor1 f4c924f — this bounds the version, not the feature -- a Node that ships node:sqlite behind a flag, or removes it, is not detected here
• r-release081 ffe702a — the capture half reaches a host that surfaces MCP instructions; one that ignores that field still needs --agents-md, and nothing detects which kind a host is
• r-cdeb10reg 48bd5a8 — wrong-path viability, deterministic oracle feasibility, code disclosure, bounded implementation, and unproven ordinary or benchmark authorship cannot be decided from history and remain undecided for human review
• r-cdeb08an 60db89f — the paired bootstrap describes resampling stability within these five frozen repositories and thirty frozen tasks, and says nothing about any other repository, task or agent population
• r-rel071 af8e0ab — 0.7.0 stays published with its notes amended to name the defect at the top; retracting a tag people may already have installed trades a known-bad version for an unknown one
• r-rel070 d4a4d8b — the README's behaviour claim now rests on M5 while the generated numbers block beneath it still publishes M4, which is The README's generated numbers block still publishes M4; M5 measured the thing the README leads with #480 rather than a release-time edit
• r-cdebver01 ce7b278 — the schemas freeze protocol 1.2.0 constants -- thresholds, matrix size, category names -- so a protocol change is a schema change and CI notices
• r-m5analysis 3450656 — the script enforces the row count, not the identity of the rows; a run that produced 1,160 rows under a changed harness would satisfy it, which is what harness_commit and dist_digest on each row are for
• r-benchscope 67f4375 — nothing checks the shape of the eight metric-row files. This gate names them and steps over them, and bench/deterministic/types.ts is the only definition that family has -- there is no JSON schema for it, so drift on that side is still invisible
• r-benchscope 67f4375 — the pre-provenance exemption reads started_at, which is data on the row rather than a fact about the file. A row that misreported it would be held to the shorter list of requirements; that is a deliberate falsification rather than the omission this fixes, and nothing here detects it
• r-3c9d52 dc9e769 — the sweep is two git log calls per path and the delivery phase runs git log --follow on every tracked path, so a full run over the four externals is hours rather than minutes on one machine
• r-rel060 e999b9d — the install one-liner in all four READMEs now points at a tag that does not exist until this is tagged, so the window between merging to main and pushing v0.6.0 is one where the documented install is broken
• r-release051 19810d2 — the hook is written at install time, so no release repairs a repository that already has one; every release touching hook behaviour has to restate what does
• r-convertreadme e12c816 — a README claim about the default workflow is only true if the shipped skill performs it, and the skill currently requires the user to name CommitLore first
• r-release050 ad402c7 — the hook is written at install time, so a corrected release never reaches a repository that already has one; every release fixing hook behaviour has to say what repairs an existing install
• r-rel041notes 71efe1f — 0.4.1 makes the installer honest about a verification it cannot complete rather than fixing the kill, so an upgrading user may still see the unverified message instead of a version
• r-rel040notes 5d57a72 — the 26.3-point density gap quoted in the notes is measured at this head and will drift with merge volume; it is illustrative of the denominator problem rather than a stable figure
• r-rel021a a79e350 — v0.2.0 remains on the remote with no release attached
• r-fix93pkg 9c4a396 — package.json remains a development artifact (build, typecheck, dependency floor) -- it is not read as a distribution manifest by anything in this repository
• r-relinstall c6e1d04 — never tested against the real GitHub release infrastructure (no release exists yet — that is the owner's action) — verified against a locally built SEA binary, a hand-made SHA256SUMS, and a local HTTP server standing in for GitHub's release-asset redirects, which is everything this repository lets a change verify before a tag exists.
• r-adr0012 e263059 — node:sqlite is experimental and version-gated -- it does not exist before Node 22.5, which satisfies but predates the >=22 floor in package.json; loadDatabaseCtor stays lazy so that gap degrades to --no-index instead of breaking validate/guard/parse
• r-det058 695cdf6 — the suite must need no model, agent, network or uncommitted benchmark input
• r-7a3e91 cf859e4 — better-sqlite3 stays external because it is native — the bundle degrades to --no-index without it, which only works because r-6f2a08 made that load lazy first
• r-4a8e15 49e12c7 — git's grammar requires a subject before a trailer block, so a serialized block is not by itself a parseable message
• r-7e5f02 e5f5e00 — npm installs through an engine mismatch, so the ecosystem's own signal cannot be relied on to stop anything
• r-5a8c04 c46a577 — git owns the definition of a trailer block, so any behavior we cannot get from interpret-trailers is behavior we must not invent
• r-c0f4e2 3d249cd — npm gitlore is held by an active same-domain CLI, so the owner's first-choice name was not available
• r-b2e7f1 00d348d — Parsing must delegate to git interpret-trailers -- reimplementing the block rules would drift from the rest of the git ecosystem

Ruled out (178)

• r-ef0defcd69a8 11ef133 — publishing this release as 1.6.1 rather than 1.7.0 | COMMITLORE_DOCTOR_REMOTE_TIMEOUT_MS is a new setting and hooks install has a new way to exit 2, and 1.6.0 set the rule that a new configuration key makes a minor
• r-276fed4dac2b d71a55c — publishing this release as a patch rather than a minor | commitlore.syncRemote is a new configuration key and a dry run's --json outcomes changed names
• r-release151 94e85f9 — keeping the regenerated manifest in the release commit | canonical-merge refuses that path outright, and the canonical build is what writes it
• r-release151 94e85f9 — publishing this version bump as a minor release rather than a patch | the only user-facing change is the folded-block withholding defect, and a defect fix that adds no command, flag or trailer key is a patch
• r-release151 94e85f9 — bumping the CHANGELOG's 1.5.0 heading or the ADR's gitlore@1.5.0 | the first is the previous release's own heading and the second is another package
• r-release151 94e85f9 — text-replacing the version in the lockfile | it also matches dependencies genuinely at that version, and no test reads those fields, so the corruption is silent
• r-treebind1030 ad4c4ef — resolving the repository from the caller's argument | r-emptystageddiff911 refused it and the refusal stands -- a caller that names the tree would turn a wrong-tree answer into a wrong-tree write, where an assertion can only produce a refusal
• r-treebind1030 ad4c4ef — inferring the caller's working directory from the process tree | MCP carries no such field and the inference is wrong in exactly the multi-worktree case this exists for, which would make the check fail where it is needed
• r-treebind1030 ad4c4ef — refusing every prepare whose staged diff is empty | it is the report's preferred shape and r-emptystageddiff911 already measured it out: it removes recording a decision with no code change and contradicts harvest --prompt-only emits nothing without a staged diff, though the contract it prints is static #310
• r-treebind1030 ad4c4ef — naming the repository in the harvest prompt's no-diff branch | text present only in that branch inflates the pricing scaffold above a real prompt, which test/token-ledger.test.ts refuses -- the same rejection r-emptystageddiff911 recorded
• r-treebind1030 ad4c4ef — git rev-parse --path-format=absolute for the common dir | it is git 2.31 and later, and this package states no git floor beyond "and Git", so it would turn a correct assertion into a refusal on the oldest runtime
• r-measurewrites988 4edfd9f — PRAGMA page_count deltas for write amplification | it measures growth, and freelist reuse is invisible to it -- which is how the zero was produced
• r-measurewrites988 4edfd9f — whole-database bytes divided by a row count | it prices a proposed table with the average of every existing structure
• r-buildbeforetest960 346006a — a vitest globalSetup that builds | it would build for every invocation including a single-file run during a debugging loop, where the developer is already rebuilding deliberately
• r-buildbeforetest960 346006a — a test asserting dist matches src | a local esbuild bundle is not byte-identical to the canonical Docker build that is committed, so the comparison is red in a clean checkout
• r-believablesuite960 3ee700c — making the mutation check a CI gate | a gate would be answered by tests that fail for any mutation, which is not the same as tests that check the property
• r-believablesuite960 3ee700c — splitting the suite into a fast tier and a history tier | the split runs along a line nobody can maintain -- most files build a temporary repository and a handful read the real one, and the boundary moves every time a test is added; bounding the parallelism needs no boundary
• r-believablesuite960 3ee700c — lowering the global testTimeout and giving every slow test its own | it moves the same contention limit rather than removing it, which the vitest 4 upgrade already measured
• r-pinnedmirror957 a06b984 — a rev-parse after the pass to detect that the ref moved | it is detection rather than closure, costs a process, and still leaves the caller holding rows it has to throw away
• r-pinnedmirror957 a06b984 — accepting the window because it self-corrects | it corrects on the next call only while the ref keeps moving; a ref that returns to the stamped value leaves the mixture in place indefinitely
• r-pinnedmirror957 a06b984 — cat-file --batch-command to fetch bodies and commit fields together | its format atoms carry no committer date and no %G?, and an embedded signature is not git's verification verdict
• r-pinnedmirror957 a06b984 — re-scoping a resumed queue against the current mirror | the rows already written came from the earlier scope, so re-scoping would mix two of them under one stamp -- the defect this closes, arriving by another route
• r-probeconsumers975 adcbd50 — batching inside collectRange | it is squash-preserve's reader and doctor's, not validate's, and batching there changed neither command -- the stack attribution is what found the reader that mattered
• r-probeconsumers975 adcbd50 — memoising the note blocks by sha alone | the reference pass sees sources with no sha yet, which is the case the commit-msg hook takes, so the cache is keyed on the message text
• r-probeconsumers975 adcbd50 — pairing noteMessages with readRecordBlocks | both call showNote, so the batch would have read every note twice and spent more processes than it saved
• r-probeconsumers975 adcbd50 — writing the measurement rule down without a harness | I had noticed this failure three times before making it a fourth, so noticing is demonstrably not the mechanism
• r-monotonic968 8f5ee12 — holding the writer lock across the scan | it closes the unbudgeted case too, and serialises cold rebuilds on exactly the path the budget exists to keep bounded
• r-monotonic968 8f5ee12 — recording an indexed-commit count to compare against | scan_pending already carries it, and a second number for the same fact is a second thing that can disagree with the rows
• r-monotonic968 8f5ee12 — comparing without pinning HEAD | two rebuilds against different heads owe different things, so the comparison would refuse a rebuild that is not worse, only different
• r-monotonic968 8f5ee12 — accepting the regression because it is recoverable | it is recoverable over later calls, and the answers given in between come from an index that was complete a moment earlier
• r-probebatch951 8d78b62 — appending the marker to the paragraph | git accepts a group holding a recognised trailer once a quarter of its lines are trailers, so one appended line can carry a paragraph over the threshold and manufacture a block; and a scissors line swallows an appended marker while still emitting the trailers above it, which moves those records into the next paragraph's answer
• r-probebatch951 8d78b62 — counting markers against the answers written | that detects a duplicate index and not a missing one, so the scissors case passed it -- the count has to be against the inputs, in order, or it is checking its own output
• r-probebatch951 8d78b62 — a trailer atom for a note's body | %N is the note text and %(trailers) parses the annotated commit's message; adding both to one format does not compose them, so a note's own block stays a process
• r-probebatch951 8d78b62 — deciding a paragraph's shape without git | SPEC 2.1 B3 is unreproducible by line matching, and the 25% rule found here is a second reason the rule is not the one a regex would encode
• r-atomreuse951 eb2869d — tightening the candidate prefilter in the same change | the necessary condition a tighter filter would test is "a line beginning with the exact key", and trailer.<token>.key lets a repository configure an alias git would emit that key from, so a pure regex cannot be a sound filter without first reading that configuration
• r-atomreuse951 eb2869d — batching the candidate parses into one process here | git processes several files in one invocation but emits nothing between them, so attribution needs a sentinel trailer appended to each paragraph; that is a real design with a real proof obligation and does not belong in a change whose whole claim is that it altered no row
• r-atomreuse951 eb2869d — passing the stripped trailers as the last block | stripConventional can empty a block that git parsed as non-empty, which changes blocks.length <= 1 and so which messages are treated as multi-block; the raw atom field is what the existing entry point takes
• r-resume951 83f5629 — a positional watermark into rev-list <head> | grafts, git replace and a deepened shallow clone all change that list without changing the commit it starts from, so the saved offset silently addresses different work
• r-resume951 83f5629 — deriving the unread set from rows already stored | a commit with no trailers leaves no row, so a processed recordless commit and an unread one are indistinguishable in trailers and commit_paths
• r-resume951 83f5629 — making the budgeted incremental resumable with its own watermark | its range overlaps scan_pending, and two watermarks over overlapping ranges can disagree about which commits are owed
• r-resume951 83f5629 — leaving the drain the whole remaining budget | it converged in four calls and made every budgeted call cost the full ceiling, which is the edit hook's latency on every fire until the backlog cleared
• r-release1219 6fd1ed5 — holding the mode-only fix for its own release | it is a wrong verdict that prescribes writing records onto a commit, and it has shipped in every version measured
• r-release1219 6fd1ed5 — a minor version | nothing gained a command or changed a contract; one verdict got narrower and three paths stopped repeating themselves
• r-release1218 3ba5d09 — folding this into 1.2.17 | that release is tagged and published, and the guard's whole claim is that it would have failed on it
• r-release1218 3ba5d09 — a minor version | nothing gained a command or changed a contract; a test artifact moved and a test was added
• r-release1218 3ba5d09 — shipping the baseline in spec | package.json ships that directory, and 80 KB of one implementation's regression record is not the protocol
• r-release1217 4836a95 — holding the two fixes for separate releases | they are one report from two directions, the second was found while fixing the first, and their fixtures share a directory and a test
• r-release1217 4836a95 — a minor version for the new capture refusal | it refuses a draft that would have been withheld anyway, so no record that reaches a reader today stops reaching one
• r-release1217 4836a95 — text-replacing the version in the JSON files | the lockfile holds dependency versions that resemble ours
• r-release1216 573d14c — calling this a minor release | nothing gained a command or changed a contract; vantage is a field added to an envelope, and the rest are fixes to what existing surfaces report
• r-release1216 573d14c — holding the parser change for its own release | it shares a file and a test harness with the notes fix, and separating them would leave a commit whose source and tests disagree
• r-release1216 573d14c — text-replacing the version in the JSON files | package-lock.json holds dependency versions that resemble ours closely enough for a careless pattern to reach one
• r-release1215 b6d2cfe — text-replacing the version in the JSON files too | package-lock.json holds dependency versions that resemble ours, and one of them is close enough that a careless pattern reaches it
• r-release1215 b6d2cfe — releasing as 1.3.0 rather than a patch version | every change here is a fix to how a diagnostic reports, and no command's contract or output schema moved
• r-release1215 b6d2cfe — holding README's squash-inheritance workflow omits the required cli-path input, so the recipe as published cannot run #926 for its own release | the broken recipe is published and reachable now, and the row that hid it shipped in the same version
• r-release1214 6e91b8e — replace 1.2.13 globally across tracked files | it would rewrite the changelog heading and the rolldown dependency, which are not pins on this project
• r-release1213 86f6dab — replace 1.2.12 globally across tracked files | it would rewrite the changelog heading and the rolldown dependency, which are not pins on this project
• r-release1213 86f6dab — leave the README action pin unbumped | a reader copying the workflow would wire an older action than the CLI they just installed, and nothing else in the suite reads that line
• r-release1212 0e93f7c — fold the version bump into the fix commit | the pins move as one surface and two tests assert them together, so a partial bump fails CI in a way that reads as a test problem
• r-release1212 0e93f7c — replace 1.2.11 globally across tracked files | it would rewrite the changelog heading and the rolldown dependency, which are not pins on this project
• r-release1211 24dbdcf — fold the version bump into the fix commits | the pins move as one surface and two tests assert them together, so a partial bump fails CI in a way that reads as a test problem
• r-release1211 24dbdcf — replace 1.2.10 globally across tracked files | it would rewrite the changelog heading and the rolldown dependency, which are not pins on this project
• r-release1210 da1cc9f — fold the version bump into the fix commits | the pins move as one surface and two tests assert them together, so a partial bump fails CI in a way that reads as a test problem
• r-release1210 da1cc9f — replace 1.2.9 globally across tracked files | it would rewrite the changelog heading and the rolldown dependency, which are not pins on this project
• r-release129 276feed — text-replacing the version across the manifests | it has matched a real dependency in two of the last four releases, at a different name each time
• r-release128 795791c — text-replacing the version across the manifests | it has matched a real dependency in two of the last three releases, at a different name each time
• r-release127 ba88444 — text-replacing the version across the manifests | rolldown and its fifteen bindings are at 1.2.6, so this release would have corrupted over fifty lockfile lines that no test reads
• r-release127 ba88444 — bumping every v1.2.6 in the READMEs | only the three install shapes are pins, and README.md's release-boundary prose is a historical statement
• r-honoadvisory d339291 — npm audit fix as written | it also strips all ten libc hints from the optional platform packages, which is how npm chooses glibc against musl binaries, and this project installs on musl in CI
• r-honoadvisory d339291 — an npm overrides entry pinning hono | the SDK's own ^4.11.4 already admits the fixed version, so an override would add a permanent constraint to work around nothing
• r-honoadvisory d339291 — waiting for a new @modelcontextprotocol/sdk | it is already the newest published version, and the advisory blocks the release now
• r-release126 55e8d79 — text-replacing the version across the manifests | it also matches dependencies genuinely at that version, and which dependency that is changes from release to release
• r-release126 55e8d79 — bumping every v1.2.5 in the READMEs | the install shapes are the only pins; README.md's release-boundary prose is a historical statement no test guards
• r-release125 9d03977 — text-replacing the version across all manifests | it also matches four dependencies genuinely at that version, and no test reads them
• r-release125 9d03977 — bumping every v1.2.4 found in the READMEs | README.md's release-boundary prose is a historical statement, and moving it makes the document say something false that no test checks
• r-release121 9845d44 — releasing the security fix alone and holding the rest | it was already merged and the remaining advisories are only reachable through the vitest upgrade, so a fix-only release would have left five of the seven, one critical, in a tree that says it is production ready
• r-release121 9845d44 — one branch per remaining pull request | main requires its checks against the current base, so each merge invalidates the others and costs a full 45-minute cycle; five sequential merges buy no evidence that one branch carrying five recorded commits does not
• r-depsbatchbump 42013a6 — repairing chore(deps-dev): bump js-yaml from 5.2.3 to 5.4.1 in the dev-dependencies group #862 and chore(deps): bump @modelcontextprotocol/sdk from 1.29.0 to 1.30.0 #863 on their own branches | each regenerates the same manifest file, so the first to merge invalidates the second; the cost is a rebuild and a full CI cycle per bump for no additional evidence
• r-depsbatchbump 42013a6 — npm audit fix --force alongside these | the remaining advisories are dev-only and its breaking upgrades are the vitest major question, which is a separate decision with a measured cost
• r-fasturiqsaudit 1752273 — fixing this on each dependency pull request instead | the advisories are on main, so each branch would carry an identical lockfile and dist change and the three would conflict with each other on merge
• r-fasturiqsaudit 1752273 — npm audit fix --force | it also rewrites the dev tree through breaking upgrades, which is the vitest major question and not a security fix; the five remaining advisories are dev-only and outside what CI's --omit=dev gate asserts
• r-cdebremoval 36ae3ab — archiving bench/cdeb to a tag or an orphan branch instead of deleting | the instruction was to discard it, and the history already holds every version; a tag would be a second place to keep something nobody is to consult
• r-cdebremoval 36ae3ab — keeping guard-mutations and pointing its registry at product tests | it had never guarded a product test, so re-aiming it would be new work introduced under a removal, and it belongs in its own change if it is wanted
• r-cdebremoval 36ae3ab — leaving the two jobs in ci.yml as no-ops so the workflow digest and REQUIRED_CHECKS could stay | a required check that cannot fail is the shape this repository's release gate exists to reject
• r-v5stage1r1reviewfixes 87cacec — treating the reviewer's findings as claims to weigh | six of them were statements about what the code does, and running the code settled each one in under a minute
• r-v5stage1r1reviewfixes 87cacec — keeping 8 repeats and reporting the detectable effect as a range | the range was over a parameter the design had no way to obtain, which is how an operator ends up choosing the favourable end of it
• r-v5stage1r1reviewfixes 87cacec — lowering the minimum important effect to what 8 repeats reaches | that is the move the HOLD rule exists to refuse, and writing it into the rule that refuses it would have been circular
• r-v5stage1r1reviewfixes 87cacec — claiming the pilot custody finding was closed by the schema | the record now cannot carry an arm contrast and the operator can still have watched the runs; a control over bytes is not a control over people
• r-v5stage1r1designlayer 28699d8 — filling the runtime lock with plausible placeholder values | an unpinned runtime that reads as pinned is worse than an empty lock, because the next reader stops asking
• r-v5stage1r1designlayer 28699d8 — marking the 62 screen-surviving candidates BUILDABLE | the screens can only refute, and calling a candidate buildable without an oracle is the claim the census exists to check
• r-v5stage1r1designlayer 28699d8 — patching the six defects into the failed Stage 1 draft | its own section 7 says anything but the deferred N makes a change a new preregistration, so amending the document that defines amendment is the failure it guards
• r-v5stage1r1designlayer 28699d8 — reporting PASS on the eleven satisfied criteria | four unresolved P0/P1 is a HOLD under section 19, and a partial pass reads as readiness to whoever approves execution
• r-v4qualification b8ff1b9 — adjudicating the 92 split gates myself | the study operator reading their own corpus, already knowing how the pair voted, is the least blind reader available; a third blind vote costs one more session and is a vote rather than an override
• r-v4qualification b8ff1b9 — averaging or passing an unresolved disagreement | it would put a candidate in the corpus that no two reviewers agreed on, and the disagreement would stop being visible
• r-v4qualification b8ff1b9 — relaxing the quote-correspondence floor after seeing 8% | the floor was fixed in code and in the deviation record before any overlap was computed, and moving it now would let the count choose the method
• r-v4qualification b8ff1b9 — accepting any rejection found in the same commit | it qualifies candidate X on evidence about decision Y, which is how a corpus fills up without meaning anything
• r-v3terminalseal 7754f1a — correcting the placeholder digests in place | the correction is indistinguishable from the mistake it repairs, and the row is historical evidence rather than a working value
• r-v3terminalseal 7754f1a — recomputing digests for the historical rows from today's artifacts | the artifacts have changed since, so the result would be a number that never bound anything, wearing the authority of one that did
• r-v3terminalseal 7754f1a — hand-maintaining evidence-matrix.md beside the JSON | two copies of the same claims disagree eventually and the disagreement is silent
• r-v3terminalseal 7754f1a — leaving cdeb-fresh-v3r1 as the default study root | a terminated study as a fallback is how a measured run gets attempted against a study that ended
• r-rel111 8c29f5d — claim Windows host wiring works | two of the four detected hosts wire, and a release note that rounds that up is the false green this release exists to remove
• r-rel110 d9a041f — fold the second Windows cause into this release | it arrived as Fix Windows host resolution and batch spawning (#716) #720 with real Windows evidence and needs its own judgement, and holding this back would make the note about what is still broken false in both directions
• r-rellock110 d9a041f — replace the version string throughout the lockfile | it matches four dependencies that are really at 1.0.2, and nothing in the suite would have caught it
• r-oneinstall001 31cf0d1 — filename equality | two shipped entrypoints of one install are one runtime
• r-runtime001 31cf0d1 — version-only comparison | equal version strings still allow different entrypoints and package roots
• r-runtime001 31cf0d1 — filename equality | two shipped entrypoints of one install are one runtime
• r-canon605 f474cf4 — remove the legacy dist sidecars now | that changes test harnesses and needs a separate reviewed reduction
• r-rel0820 59c6730 — rebuild dist | the CLI reads package.json at runtime and a rebuild changes the bundle digest without changing behaviour
• r-engfloor01 fe83524 — adding semver as a dependency to parse this | one regex over a handful of published shapes does not justify a runtime dependency in a check that runs before install
• r-relfix01 96102b4 — keeping "floor, measured" and footnoting it | the sentence is the claim a reader takes away, and a footnote that contradicts it is worse than either alone
• r-cdeb08an 60db89f — discovering row files under the result directory | an unregistered file contaminates the matrix while leaving every stopping rule looking satisfied
• r-cdeb08an 60db89f — filling or dropping unavailable usage | both change a token aggregate without evidence, one by inventing a number and one by redefining the population
• r-rel071 af8e0ab — deleting the v0.7.0 tag and re-cutting it | rewriting a published ref breaks every clone that already fetched it, and the release notes can carry the truth without that
• r-rel071 af8e0ab — reading the flag with a nullish check and documenting the commander default | the documentation would sit in this file while the defect sits in every install, which is the arrangement that produced this
• r-rel070 d4a4d8b — bumping the manifests first and the README pins after | the readme suite pins them to package.json, so the intermediate commit is one where CI is red and the documented install is wrong
• r-rel070 d4a4d8b — rebuilding dist for the version change | the version is read at runtime, and a rebuild would move the digest every M5 row records without changing a byte of behaviour
• r-cdebver01 ce7b278 — default-in discovery over the CDEB tree like the legacy gate | that gate's enemy was the unregistered file, CDEB's is the unregistered input, and bench:m5 reads every jsonl in bench/results, so the registered analysis would run over M1, M4 and files marked non-citable #441 showed a glob passing a stopping rule on contamination
• r-cdebver01 ce7b278 — validating with the draft-07 Ajv entry and downgrading the schemas | the 2020-12 entry ships in the same package, and weakening six schemas to fit a meta-schema is backwards
• r-m5analysis 3450656 — Computing the table now and not looking | the file would exist, and a number that exists is a number someone reads
• r-m5analysis 3450656 — Leaving the analysis to be written after the run | that is the freedom this document was written to give up, and writing it afterwards is indistinguishable from writing it to fit
• r-m5analysis 3450656 — Asserting the M1 control in a vitest suite instead of --validate | it belongs to the analyser, and a reader checking the verdict should be able to re-derive the control with the same command that produced the verdict
• r-benchscope 67f4375 — A declared list of result files, in the gate or in a manifest | opt-in under another name, and a file left off it is silently ungated -- which is precisely the failure bench/verify.mjs is not run by anything, so the result schema drifted unnoticed #392 reports
• r-benchscope 67f4375 — Validating only the three files that pass today | a description of the present rather than a rule, and it goes stale the first time a matrix is added or the schema moves
• r-benchscope 67f4375 — A naming convention on results filenames | the runner's default output is an ISO stamp plus hex and the metric writers' is a family name plus an ISO stamp, but every run-record file in the tree was named by hand through --out (t702-m2, m5-off-design-20-tasks), so the convention is enforced nowhere and cannot carry a gate
• r-benchscope 67f4375 — A marker file dropped beside each gated result | still a step somebody has to remember, and a forgotten step is the defect being fixed
• r-benchscope 67f4375 — Widening result.schema.json to describe both row families | they share no required field, so the union would accept a run record with no task and a metric row with no metric, which is a schema that rejects nothing
• r-benchscope 67f4375 — Making harness_commit and dist_digest optional in the schema | weakens the gate for every future row in order to admit six historical files, and Make per-turn token usage observable, and say what it still cannot price #390's drift was an additionalProperties failure that a laxer schema catches later rather than sooner
• r-benchscope 67f4375 — Skipping the six pre-provenance files whole | cheaper to write, but it stops checking types, patterns and the closed property set on 380 rows in order to excuse two absent fields
• r-3c9d52 dc9e769 — reimplementing the scorer for the external corpus | two scorers that drift by a line produce two numbers that look comparable and are not, which is the failure No-index query at 100k regressed from 7.7s to 90s — cause not yet identified #163 already recorded here
• r-3c9d52 dc9e769 — replacing the per-path --follow chain with one forward pass over a rename graph | it is much faster and it is a different attachment predicate from the one DECISION-DELIVERY.md §3 registered, so the two corpora would stop being comparable
• r-3c9d52 dc9e769 — turning the census notes option on by default | every measurement registered before it existed read commit messages only, and a denominator that silently grew would invalidate them without saying so
• r-rel060 e999b9d — 0.5.2 | three observable behaviour changes and one narrowed acceptance rule are not a patch, and an upgrader reading the number would not go looking
• r-rel060 e999b9d — Publishing the delivery figure in the README | the measurement is one corpus and one repository, and the README already carries more numbers than a first-time reader can weigh; docs/evidence.md and bench/ hold it
• r-release051 19810d2 — Waiting for 0.5.2 to carry index ingests any key: value line as a trailer; doctor reports 106 records where git has 0, and context serves commit subjects to the agent #335 | false decision context reaching an agent is the inversion of the product claim, and a stable release should not hold it
• r-release051 19810d2 — 0.6.0 | no command is added and nothing breaks; calling it minor would hide a correctness fix behind a feature number
• r-release051 19810d2 — Filtering Verified: because a report listed it as noise | it is vocabulary, and separating a release-note use from a record use needs a guess that can discard real records
• r-convertreadme e12c816 — Adding "Keep coding normally" now | the commit skill still triggers on explicit requests and teaches harvest; shipping the sentence first repeats the doc-ahead-of-code failure this session fixed twice
• r-convertreadme e12c816 — Writing testimonials to fill the social-proof section | one real field report exists, and fabricated or padded quotes would cost the claim honesty that is this project's strongest asset
• r-convertreadme e12c816 — Moving the benchmark block and protocol detail out of the README now | the generated block is byte-compared by check-readme-numbers and the guard figures are asserted inside the limitations slice; the move is worth doing and is worth its own change
• r-convertreadme e12c816 — Dropping "decision authority" everywhere | it is the right term in the architecture sections; it is only the wrong term for a first screen
• r-release050 ad402c7 — 0.4.2 | a new command and a platform support claim are not a patch, and calling them one hides both from anyone reading version numbers to decide whether to upgrade
• r-release050 ad402c7 — 1.0.0 | nothing here breaks an existing install, and the milestone that closed is Gate B rather than a stability commitment
• r-release050 ad402c7 — Describing Windows as supported without the caveat | the word is the one most likely to be read as more than it is, and the release that earns it is the right place to bound it
• r-nobin284 ab2f08f — Keeping the binary classification arm for the installer's wrapper | the wrapper is a shell script that execs node, so trusting it by name would re-admit any extensionless executable called commitlore while the bundle it runs is the thing with an interpreter to check
• r-nobin284 ab2f08f — Relaxing the dogfood Evidence check to allow a missing path | it exists to catch a citation nobody can follow, and dropping the check to accommodate a deletion would retire the guarantee instead of correcting the question it asked
• r-nobin284 ab2f08f — Leaving src/core/paths.ts alone because ADR-0026's inventory did not name it | it was the only remaining code that read files out of a compiled artifact, so leaving it would have left the invariant false while the test asserting it passed
• r-nobin284 ab2f08f — Keeping /dist/commitlore in gitignore in case a binary returns | an ignore rule for an artifact nothing produces is a claim that something might, and the ADR says otherwise
• r-rel041notes 71efe1f — folding this into the next feature release | the documented install is broken for upgraders now, and every day it stays tagged is a day the one-liner in the README fails for them
• r-rel041notes 71efe1f — moving the v0.4.0 tag to the fixed commit | a tag users may already have fetched must not change under them; the fix gets its own version
• r-rel040notes 5d57a72 — describing 0.4.0 as making agents safer | no study here measures agent behaviour, and the recovery protocol is registered and unrun; the release delivers a loop, not an outcome
• r-rel040notes 5d57a72 — omitting guard's figures from the release notes because they are unflattering | the notes are read by people deciding whether to trust the tool, and a quality limit hidden at release time is discovered in use
• r-rel021a a79e350 — retagging v0.2.0 | the tag is already on the remote and moving a published tag breaks anyone who fetched it
• r-rel0200a a074754 — bumping ci.yml's "v0.1.0 was published with zero attached assets" comments | those describe a historical fact about the actual v0.1.0 release, not a version this project declares; the check they document (releases/latest/download/SHA256SUMS returning 200) is written to start exercising the real path automatically the day any release ships assets, v0.2.0 included, with no workflow edit
• r-rel0200a a074754 — touching docs/adr/ADR-0001-scope-v010.md, docs/tickets/release.md, bench/VERDICT-M1.md, HANDOFF.md, bench/ROUTE-GAP.md | planning and historical-record prose that names v0.1.0 as a past decision or measurement subject, not a live version carrier
• r-rel0200a a074754 — changing test/mcp.test.ts's CommitLore-Version: 0.1.0 fixture trailer | that's protocol-version content inside a synthetic seed commit (what an old commit's trailer looked like), unrelated to and never asserted against package.json's version
• r-fix93pkg 9c4a396 — repointing bin at dist/commitlore.mjs instead of removing it | that entry exists only to serve a package-manager install ADR-0011 already replaced with a git clone; repointing it keeps maintaining a path to an install mode that will never happen
• r-fix93pkg 9c4a396 — also removing files now | the issue's own "After B-09 · Single static binary — remove the Node runtime dependency #39" note groups bin/files/dependencies as one cleanup once the static binary lands; files alone is inert without a registry rather than actively broken, so doing it now means doing it twice
• r-relinstall c6e1d04 — guessing the current version to build the asset URL directly | would need either the GitHub API (rate-limited, needs no-auth headers handled correctly) or trusting a redirect's final Location header parsing. Downloading the fixed-URL SHA256SUMS first and reading the real asset name back out of it needs neither and is what the checksum step has to fetch anyway.
• r-relinstall c6e1d04 — local for scoping — not POSIX per se, but supported by dash, bash, and every shell this script is realistically piped into (verified directly, see Verified) | not used in the end; the script has few enough variables that scoping was not needed, only noted here because it was considered.
• r-adr0012 e263059 — db.isTransaction to detect nesting depth | it needs Node 22.16, and this migration only needs the 22.5 floor node:sqlite itself sets
• r-adr0012 e263059 — --external:node:sqlite in the bundle script | esbuild's --platform=node already treats it as external like any other builtin; the built bundle has zero occurrences of "better-sqlite3" and runs with no node_modules
• r-adr0012 e263059 — a static top-level import of node:sqlite | it breaks ADR-0003's guarantee that importing this file never throws before --no-index is chosen, and it also fails vitest's Vite-based transform outright ("Failed to load url sqlite"), so createRequire stayed in both src and test
• r-adr0012 e263059 — flattening nested db.transaction() calls into one BEGIN/COMMIT | the call-graph check found real nesting, and flattening it would turn a partial failure into a partial write
• r-det058 695cdf6 — add the 100k history suite to CI | CI budget and deterministic local measurement are separate decisions
• r-7a3e91 cf859e4 — inlining spec/SPEC.md and the schema into the bundle | SPEC.md would need a codegen step that itself needs a drift guard, and the package-root walk removes the reason to want it
• r-7a3e91 cf859e4 — replacing the tsc output with the bundle | test/cli.test.ts, test/hooks.test.ts and test/mcp.test.ts import dist internals by path
• r-0d4b81 8005227 — a longer quickstart that demonstrates context, limits, ruled-out, warnings and stale | an agent calls those itself once the MCP server is registered, so listing them teaches the human a workflow that is not theirs
• r-4a8e15 49e12c7 — make the parser accept a bare block | it would disagree with git, and delegating to git is the one thing SPEC section 2 requires
• r-7e5f02 e5f5e00 — hold Node 20 and downgrade both dependencies | paying maintenance cost to keep supporting an unpatched runtime
• r-7e5f02 e5f5e00 — floor at 24 | excludes Node 22 users today for no benefit, and 22 outlives v0.1.0
• r-7e5f02 e5f5e00 — drop engines entirely | the failure moves from install time to runtime, where it is someone else's confusing bug
• r-5a8c04 c46a577 — regex trailer parsing | B3 prose false-positives are the failure mode this protocol exists to prevent
• r-5a8c04 c46a577 — a custom GitError subclass | the convention here is new Error with structured context, and callers read GitResult
• r-c0f4e2 3d249cd — GitLore published as git-lore | the binary and search results still collide with the existing gitlore tool
• r-c0f4e2 3d249cd — keep Annals | the sound problem does not decay, and with code near zero this is the cheapest moment the project will ever have
• r-c0f4e2 3d249cd — rename code and spec first, documents later | the drift window makes every artifact written in it wrong
• r-b2e7f1 00d348d — line-matching Key: prefixes | prose containing a colon line parses as a record and feeds agents false context (verified B3)
• r-b2e7f1 00d348d — content-hash Record-Id | must survive rebase and squash, which a hash of the commit does not

Warnings (61)

• r-release151 94e85f9 (claim) — the note to run artifact:manifest in the release commit is out of date -- canonical-merge.yml runs it itself and commits the result, and refuses any pull request whose diff touches installer/canonical-artifact.json
• r-release151 94e85f9 (claim) — a Ruled-out: whose alternative is a bare version number matches unrelated prose -- "calling this 1.6.0" scored 0.55 against the guard corpus's retry-with-jitter webhook entry, which is the same clean entry a single-token number hit at 0.5417 during A Record-Id declared in both the commit message and the note blocks the whole record, over a trailer the note itself dropped #1020; the alternative has to name what is being rejected in words
• r-release151 94e85f9 (claim) — git grep -c reported 44 pins and that was wrong -- it counts lines containing the string, and several pins put two occurrences on one line, so the real surface is 54 across eleven files
• r-release151 94e85f9 (claim) — the rule to measure the surface every release applies to the measuring method too -- the first number came from a command whose semantics I had not checked
• r-release150 df9fe0d (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release150 df9fe0d (claim) — an agent working through the Claude Code plugin with mode: auto will have git commit refused on a non-trivial unconsidered tree from the moment the plugin is updated; the refusal names the command that clears it, and records: [] is a complete answer
• r-release150 df9fe0d (claim) — capture and the MCP capture tools now write a consideration under the git directory on the paths that stage a record or accept an empty draft -- a new file in .git/commitlore/, per worktree, never committed
• r-release142 208b821 (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release142 208b821 (claim) — init run in a terminal now asks a second question before it installs anything; a wrapper that drove it interactively and answered only the unattended prompt will hang on this one until it sends a newline, and --mcp-scope skips it
• r-release142 208b821 (claim) — init with no flag no longer writes .mcp.json by default -- it registers at user scope instead; automation that expected the committed file must pass --mcp-scope project
• r-treebind1030 ad4c4ef (claim) — paths are compared after realpath on both sides; a future change that compares the strings git returns will refuse macOS callers who reached the same tree through /tmp instead of /private/tmp
• r-treebind1030 ad4c4ef (claim) — assertRepositoryBinding runs before prepareCaptureContext on purpose, and moving it after would leave a pending file for every refusal
• r-release140 c204468 (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release140 c204468 (claim) — a host that reads phase: "verified" from pending ls as "a capture is ready" now sees fewer such rows, which is the repair; one that counted them as coverage was counting wrong before and will see the number drop
• r-release140 c204468 (claim) — verify_capture no longer requires diff, gains source_mismatch and no_transaction; prepare_capture gains diff_window; stale --json gains coverage; a host validating any of those shapes strictly sees them arrive
• r-release1317 a2ff8e9 (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release1317 a2ff8e9 (claim) — totalRecords rises on any repository with both a flattened commit block and an intact mirror; a consumer that pinned that number sees it move, and the new value is the correct one
• r-release1316 2049bcf (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release1316 2049bcf (claim) — --json gains an unfoldedDeclarations field; a consumer that validates the shape strictly will see it arrive
• r-release1315 2415e44 (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200
• r-release1315 2415e44 (claim) — the declared set is now a superset of what it was, so a reference that was reported dangling on a real defect also stops being reported; the control is the case asserting an undeclared id is still caught
• r-release1314 8d525f0 (claim) — between this merge and the tag push every README install one-liner and the action pin point at a tag that does not exist; tag promptly and confirm both URLs return 200

Truncated: 43 lines omitted — the comment hit GitHub's 65000 character limit.

_{Trailer violations fail this check. Active constraints are informational — they are what the repository already decided, not a verdict on this PR.}