@cosyte/astm 0.0.21 → 0.0.22

package/CHANGELOG.md

@@ -11,6 +11,81 @@ this file is maintained by hand (Changesets handles the version bump and publish
 
 ### Added
 
+- **The PHI sweep now reads the bytes git carries, as a union with the working-tree walk.** All mode
+  reconciled the paths it walked against the paths git tracks, and a comparison of path _sets_ is
+  satisfied by a working tree that carries different content at those paths. Four states were
+  reproduced on the previous release, each printing `[phi-scan] OK: no hits` and exiting `0` over a
+  synthetic stream carrying a patient name, a mother's maiden name, a birthdate and a dashed SSN:
+  decoy content at a tracked path; a tracked path outside every walk root; a tracked symbolic link
+  or nested repository outside every walk root; and an empty index, against which every check passes
+  vacuously. All four now report or refuse. The mechanism is written down in exactly one place,
+  `buildTargetsForIndex` in `scripts/phi-scan.ts`, and every other surface states only what a green
+  means.
+  - **It is a union, never a replacement.** No scan root was narrowed and no clause dropped; a file
+    the walk reads is still read from disk with exactly the views it had, and a blob whose bytes the
+    walk has provably already scanned is skipped, so nothing is reported twice. The skip is a byte
+    comparison rather than a timestamp, a size or a hash, because those are exactly what a decoy
+    defeats.
+  - **The scan reported eighteen tracked files outside every walk root that no route had opened.**
+    One carried this package's own published contact address, which is already public in every
+    release's registry metadata and is not patient data; it is declared in
+    `scripts/phi-allow-list.txt` with the cost of that declaration written beside it, because an
+    allowed email domain is global and applies on every route.
+  - **A positive control proves the sweep opens the corpus it clears.** This package's own manifest
+    is placed at the same out-of-root path in a throwaway tree and the declaration is then struck:
+    the same corpus reports the address at exit `1`. A green over an unopened corpus is
+    indistinguishable from a green over a corpus that was read, so a case showing the scanner
+    passing proves nothing on its own.
+  - **What it deliberately does not do**, so a green is not read as wider than it is: it does not
+    credit a scan root (a root emptied on disk still refuses, though the index carries its files);
+    it does not reach `--staged`, whose scope decides what a _commit_ is blocked on; and markdown
+    stays excluded, which is the walk's own rule rather than a new one. Working-tree bytes at a path
+    outside every scan root are still read by neither route, unchanged from before and now stated.
+  - **Line endings are deliberately not normalized before the byte comparison.** Doing so would
+    compare a derived form of the two byte strings, and content differing only in what the
+    normalizer erases would then be skipped.
+
+- **The two-file contract between `CLAUDE.md` and `documentation/agent-notes.md` is now gated**
+  (`pnpm check:agent-notes`, `scripts/check-agent-notes.ts`), with the teeth in
+  `test/scripts/agent-notes.test.ts` so it rides the required `ci / verify` matrix rather than
+  adding a workflow that would have to be made a required context separately. It asserts that every
+  pointer resolves, that no section a pointer reaches is empty, that the record stays reachable from
+  the always-read file, and that the always-read file still links the record by path. It asserts
+  **no** ecosystem-wide contract: several cosyte repos carry no such record at all, and a gate
+  phrased as though every repo did would be an overclaim.
+  - **The matcher was re-derived against this tree rather than ported, and that was the whole job.**
+    Both sibling spellings score **zero** here: the path-qualified form used by `ccda` and `mllp`,
+    and the basename-qualified form used by `terminology`. Every pointer in this repository is a
+    third spelling neither sibling gate matches, a backtick-quoted anchor with no filename at all. A
+    verbatim port would have reported "all resolving" over a corpus it never opened. Both sibling
+    forms are matched anyway so a pasted pointer is never invisible, and the live form falling to
+    zero is a refusal rather than a pass.
+  - **The anchor space is this record's explicit `<a id>` tags, not GitHub heading slugs.** Not one
+    pointer here resolves to a heading slug, because the headings carry long titles with dates and
+    status in them. A gate checking only slugs, which is what the siblings check, would have
+    reported every pointer in the repository as dangling.
+  - **An early draft was vacuous rather than wrong, and only a positive control found it.** Treating
+    an explicit anchor and the heading it precedes as separate sections made the empty-section
+    assertion cover nothing: the anchor looked empty and the heading looked unreferenced, so both
+    were skipped and a deliberately emptied section still printed `OK`. Anchors are now bound to the
+    heading they name.
+  - **The one declared non-pointer is pinned to the single sentence it describes**, and refuses both
+    when it matches nothing (a phantom skip) and when it matches more than once. The second case
+    fired during this change's own build.
+  - The corpus is `git ls-files` reconciled as sets, with **no exclusion list, no binary skip and no
+    NUL skip**; this repository tracks NUL-bearing TypeScript sources, most of them tests, that a NUL
+    partition would drop in silence. A pointer is matched if and only if the file spells it in ASCII
+    bytes, pinned in both directions by test. Every tracked file is scanned, so a backticked anchor
+    is a live pointer wherever it is written, **including `README.md` and `docs-content/`, which
+    ships in an immutable release asset**: reference a section by title on any surface that ships.
+  - **CI caught a defect the local run structurally could not, and the gate was right.** Because the
+    corpus is the index, a new file is invisible until staged: `verify.sh` ran green while both new
+    files were untracked, and CI went red once they were tracked, because the gate's own test file
+    spelled pointers in its fixtures that were then scanned against the real record. Both the checker
+    and its test now **build** pointer strings at run time rather than spelling them, pinned by a
+    test; exempting those paths would have been the exclusion list the gate refuses to have. **Re-run
+    a corpus-scanning gate after staging, never only before.**
+
 - **The PHI commit-gate now reads a stream written as a source string literal, and refuses a sweep
   that did not observe its corpus.** Two separate holes, closed together because closing one alone
   buys only the cross-cutting SSN/email floor.

package/dist/index.cjs

@@ -2908,7 +2908,7 @@ function concatBytes3(chunks) {
 }
 
 // src/index.ts
-var VERSION = "0.0.21";
+var VERSION = "0.0.22";
 
 exports.ALL_ASTM_WARNING_CODES = ALL_ASTM_WARNING_CODES;
 exports.AMBIGUOUS_CODES = AMBIGUOUS_CODES;