@cosyte/cli 0.0.4 → 0.0.6

package/CHANGELOG.md

@@ -17,6 +17,130 @@ still do. Each entry was assigned to the release whose tag first contains it, re
 
 ### Fixed
 
+- **`pnpm phi-scan`'s all-mode walk was rooted at `test/__fixtures__` and `src` only, so 89 of this
+  repository's 123 tracked files were scanned by NEITHER of its two routes
+  (PHI-SCAN-WALK-ROOT-SCOPE).** The walk now roots at **`src`, `test` and `scripts`**, which opens 72
+  tracked files instead of 34.
+  - **Measured back to back on the base commit, and re-derived for this repository rather than ported
+    from a sibling.** A dashed SSN and an off-domain address written into `test/planted.test.ts`, in
+    this repository's own inline-message shape (a whole HL7 message as one `.ts` string literal with
+    `\r` escapes between its segments), exited **0** with `OK, no hits` in all mode, while naming the
+    same file in paths mode reported both at **exit 1** over the same bytes. A file written under
+    `scripts/` behaved identically. Both routes now report both.
+  - **All 38 newly opened files were hand-read.** Every message literal is a placeholder and the only
+    SSN/email shapes anywhere are the scanner's own declared synthetic payload, so the gap was one of
+    **enumeration**, not a live exposure: the defect was that the gate could not see those files, so
+    nothing would have caught a real value if one appeared.
+  - **`test` REPLACES `test/__fixtures__` rather than joining it.** Roots must stay disjoint: each is
+    walked independently and the results concatenated, so a nested root would enumerate every file
+    beneath it twice and report each hit twice. The fixture directory is still watched, through the
+    observation rule's other condition, **wherever git tracks files under it** (here, seven); only the
+    root a refusal is filed under changed.
+  - **One cover was LOST, and it is stated rather than implied away:** where git tracks NOTHING under
+    `test/__fixtures__`, an empty one no longer refuses. As a declared root it refused by the
+    opened-nothing floor whatever git carried; as an ordinary directory it contributes no entry and the
+    reconciliation has no expected path to miss. A test pins it.
+  - **`scripts/` is a root because the scanner, its allow-list and its override log live there**, so
+    the one directory guaranteed to hold PHI-shaped text was the one nothing enumerated. All nine
+    files there were measured against the detector before the root was declared: no hits.
+  - **The cost of that root nobody would guess: the allow-list's own bytes.** The allow-list documents
+    `ID <value>` as a synthetic id "matching an SSN / MRN / member-id shape", and the dashed-SSN check
+    consults no allow-list, so an `ID` entry written in that dashed shape now reds the gate on the
+    allow-list itself. Latent today (the shipped file declares its only id in the `MRN-` form, and a
+    test pins that). **The remedy is to spell the id in a shape the check does not match**, never to
+    make that check consult the allow-list (which would delete a detection) and never to exempt the
+    file (which would leave the likeliest place for a real value unswept).
+  - **A narrowing that came with it:** `test/__fixtures__` is no longer a declared root, so a live or
+    dangling symbolic link at that path is now an enumerated entry and is refused outright, whatever
+    it points at. Only the three top-level roots can still be followed.
+  - **`test/scripts/phi-scan.test.ts` is exempt from the sweep, and is the only exempt path.** It
+    carries violator literals on purpose, as the positive half of the scanner's own tests. The
+    exemption is applied **after the read**, so the file still counts as observed and an unreadable
+    one still refuses; it is **scoped to the sweep**, so naming the file explicitly still reports
+    every hit; and it is **per path, never a pattern**.
+  - **What this does NOT buy, stated because a wider reading would be false:** the detector is still
+    the cross-cutting SSN + email floor, over 38 more files. Structured, field-level detection remains
+    unimplemented, and a test now pins that limit rather than leaving it as prose.
+  - **`--staged` is deliberately unchanged**, because widening it changes what a commit is blocked on.
+    The two routes therefore differ widely, and the scanner's own documentation says by how much.
+  - **Four claims about which directories are deliberately NOT scan roots are now checks rather than
+    prose**, after two of them were measured false: `docs-content/` and `.changeset/` each carry one
+    tracked non-markdown file, and the repository root is not clean under the detector (the `author`
+    field carries a real off-domain contact address). `documentation/` and `.github/` were correct.
+
+- **`pnpm phi-scan` printed `OK, no hits` and exited 0 over a corpus it never opened
+  (PHI-SCAN-OBSERVED-NOTHING-IS-GLOBAL).** A declared scan root that the walk never observed is now
+  a refusal at **exit 2**, in the all-mode sweep CI runs. Each root's walk is reconciled against
+  `git ls-files`, and two independent conditions refuse: the root contributed **nothing**, or git
+  tracks an in-scope file under the root that the walk did not open.
+  - **Six states measured on this repository, every one of them previously exiting 0 with
+    `OK, no hits`:** the root missing; the root emptied; the root a **dangling** symbolic link; the
+    root a **live** symbolic link to a directory outside the repository; a single tracked fixture
+    removed from the working tree with the rest of the root still opened; and `src` moved away.
+  - **The dangling case is why a kind check cannot stand in for this rule.** `existsSync` follows
+    the link and answers false, so `walk()` returns before `readdirSync` and the existing
+    not-a-regular-file refusal never fires. Nothing about the entry is ever inspected, so no check
+    on its kind can reach it. Refusing on what was **observed** needs no opinion about the entry.
+  - **A denominator is deliberately not what this is.** A count counts the roots and the files that
+    did exist, so a healthy-looking total is exactly what a starved root produces. This scanner
+    prints no file count and one was not added.
+  - **Existence is not observation, which is why both conditions ship.** Refusing only a missing
+    root leaves the emptied one open; refusing only an empty result leaves the swapped one open,
+    because a root pointed at another directory opens plenty. Neither subsumes the other.
+  - **Exit 2 was derived from this scanner's own contract, not ported from a sibling.** `1` means
+    "hits found" here; `walk()` already raises an unreadable root as an invocation failure, and a
+    root replaced by a regular file already exits 2 through `readdirSync`. Sibling scanners disagree
+    on this code, and carrying one across would have been the defect.
+  - **`git ls-files` failing refuses rather than answering the empty set**, because an empty answer
+    is indistinguishable from "this root tracks nothing" and would switch the rule off in silence.
+  - **The rule is one-directional on purpose.** A tracked in-scope file the walk missed refuses; an
+    untracked working-tree file the walk found does not, because scanning more than git carries is
+    the safe direction.
+  - **Scope, stated rather than left to be inferred:** all-mode only. `--staged` is a diff and not a
+    corpus, and widening it would change what a **commit** is blocked on, which is a separate
+    decision. Naming paths explicitly is unchanged.
+  - **Narrowed, not closed, and still disclosed in the module header:** a scan root that is itself a
+    live link is still followed. It is now refused whenever git tracks an in-scope file under the
+    root that the link's target does not also carry **at the same relative path**, so a link to an
+    unrelated directory refuses; the reconciliation compares path **sets** rather than the bytes git
+    carries at those paths, so a target mirroring the tracked names still passes at exit 0, and a
+    root git tracks nothing under is the degenerate case of that rather than the whole of it. An
+    **ancestor** of a scan root remains out of the staged route's scope, and paths mode still follows
+    a link a caller names.
+- **A present-but-unreadable `phi-scan-overrides.md` exited 1, the code reserved for "hits found".**
+  `loadOverrideLog` threw a raw filesystem error past every handler while its sibling reader,
+  `loadAllowList`, had already been wrapped. It now exits 2 with a diagnostic. A caller branching on
+  the exit code read a broken invocation as a PHI finding.
+- **A red pre-publish gate showed a red X and merged anyway, because `ci / prepublish` was a
+  required check nowhere (CI-REQUIRED-CHECKS).** The shared pipeline this repo calls grew a
+  `prepublish` job on 2026-08-05 (`cosyte/.github#35`, `6142ac4`; its second layer defaulted on in
+  `#36`, `90936ea`), so `ci.yml` began emitting a `ci / prepublish` context on every pull request
+  here **with no commit landing in this repo**. Repository ruleset `19907924` did not name it, so
+  the job could fail and the merge still landed on `main`, which is the branch that publishes.
+  `ci / prepublish` is now a required context, `integration_id`-pinned like the other six.
+  - **What it gates is this package's own worst shipped defect.** The job is an offline manifest
+    lint that refuses a dependency specifier no registry can resolve, plus a probe that packs this
+    tree and installs the tarball into a clean directory. `@cosyte/cli@0.0.1` and `0.0.2` reached
+    the registry carrying `file:vendor/*.tgz` specifiers and are permanently uninstallable; the
+    manifest lint would have refused both. A gate that catches that and then cannot block the merge
+    reintroducing it is documentation.
+  - **The order was load-bearing and is recorded because it is easy to get backwards.** The context
+    name was read off a real `pull_request` check run before the ruleset was written, never off the
+    workflow's `name:` field. Requiring a context nothing emits does not fail a pull request, it
+    leaves it pending and unmergeable forever. A census of the eight most recent head shas here
+    (`#27` through `#34`) finds `ci / prepublish` **zero** times, because the newest of them merged
+    before the upstream job existed, so it could not have been required any earlier.
+  - **`ci.yml`'s banner now covers the hazard that actually bit.** Every previous wording of it was
+    scoped to splitting a step out of `verify` locally. The `uses:` reference is unpinned, so a job
+    added upstream emits a new `ci / <job>` context here with no commit in this repo, and it always
+    arrives unrequired.
+  - **Deliberately NOT in this change: `release.yml`'s version-PR trap note.** It carries a stale
+    required-context count and a claim about the "Version Packages" PR arriving with zero check runs
+    whose truth depends on whether `RELEASE_PR_TOKEN` is authoring that PR. Two attempts to correct
+    it inside this change each produced a fresh false claim: the first a false operational premise,
+    the second a false claim about the note's own history. So it is cut out to its own change rather
+    than rewritten a third time. Nothing about it is made worse here; it is left exactly as it was.
+
 - **The shipped documentation sidebar was off the canonical IA spine, and it was holding up the
   docs site's deploy (CLI-SIDEBAR-IA-NONCANONICAL).** `docs-content/sidebars.json` declared two
   top-level categories that are not on the spine, **"MCP server"** and **"Reference"**. The docs

package/README.md

@@ -1,7 +1,9 @@
-<picture>
-  <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
-  <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
-</picture>
+<a href="https://cosyte.com">
+  <picture>
+    <source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
+    <img alt="Cosyte: a plus mark set in two overlapping rounded squares, one solid and one outlined, beside the Cosyte wordmark" src="https://cosyte.com/tile/cosyte-lockup-tile-on-light-1200x300.png">
+  </picture>
+</a>
 
 # @cosyte/cli
 

package/dist/bin/cosyte-mcp.cjs

@@ -7,7 +7,7 @@ var types_js = require('@modelcontextprotocol/sdk/types.js');
 var util = require('util');
 
 // src/core/version.ts
-var VERSION = "0.0.4";
+var VERSION = "0.0.6";
 
 // src/core/exit-codes.ts
 var EXIT = {