chore(deps): bump @cosyte/ncpdp from 0.0.8 to 0.0.13

[dependabot]

Bumps @cosyte/ncpdp from 0.0.8 to 0.0.13.

Release notes

Sourced from @​cosyte/ncpdp's releases.

v0.0.13

What changed

• Strengthen this repository's PHI commit-gate so a full sweep reads the bytes git carries as well as the files on disk.
• Add a repository check that keeps this project's two-file contributor guidance in step, so a rule can no longer point at reasoning that has quietly stopped existing.

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/ncpdp@0.0.13

npm: https://www.npmjs.com/package/@​cosyte/ncpdp/v/0.0.13

v0.0.12

What changed

• An all-mode PHI sweep now reconciles the files it actually opened against git ls-files and refuses when a tracked in-scope file went unread, so an emptied scan root can no longer read as clean on that route.
• CHANGELOG.md is now written by the release rather than by hand, so the copy inside every published tarball stops describing already-shipped code as something still to come.
• The README lockup now links to cosyte.com (ASSETS).

Full detail for each change is in CHANGELOG.md.

Install

npm install @cosyte/ncpdp@0.0.12

npm: https://www.npmjs.com/package/@​cosyte/ncpdp/v/0.0.12

v0.0.11

What changed

Internal tooling and CI only. No change to the published package surface.

Install

npm install @cosyte/ncpdp@0.0.11

npm: https://www.npmjs.com/package/@​cosyte/ncpdp/v/0.0.11

v0.0.10

What changed

• Internal CI and repo tooling only.

... (truncated)

Changelog

Sourced from @​cosyte/ncpdp's changelog.

0.0.13

Patch Changes

• b0999b2: Strengthen this repository's PHI commit-gate so a full sweep reads the bytes git carries as well as the files on disk. No runtime behaviour, public API, parsed output, or emitted diagnostic changes.

  The sweep previously proved that every tracked, in-scope path had been opened, and then read each one from the working tree. A working tree is not the committed corpus, so a payload held in the index at a path the sweep had opened was reported clean, with a file count that was entirely correct. The sweep now reads both, as a union.

  Duplicate reads are skipped on the pair of a path and git's own object name for its content, so an unmodified checkout matches every index entry without fetching anything, and where a path's two copies differ both are scanned. A conflicted path is read at every stage it holds, each reported with its stage, so the merge base is never mistaken for what git carries.

  Every report line now carries both the number of files scanned and the number of additional blobs read, so neither number can be read without the other. Content found in a carried blob exits 1, the same as content found on disk; a git command that cannot answer exits 2 rather than reporting a pass.

• 2cade73: Add a repository check that keeps this project's two-file contributor guidance in step, so a rule can no longer point at reasoning that has quietly stopped existing. It verifies that the narrative document is tracked, that no section has been emptied down to its heading, and that every anchor pointing into it resolves.

  No runtime behaviour, public API, parsed output, or emitted diagnostic changes.

0.0.12

Patch Changes

• b041427: An all-mode PHI sweep now reconciles the files it actually opened against git ls-files and refuses when a tracked in-scope file went unread, so an emptied scan root can no longer read as clean on that route. Internal repo tooling only: no published API, type, warning code or parse-result change.

  The root check shipped previously certifies that each declared scan root EXISTS and is ENUMERABLE. It never certified that anything was OBSERVED under one, and no version of it could: an empty directory enumerates perfectly. Measured in a clone at 16c2fea with that check in place, emptying src/ (51 tracked files, the directory left in place) printed OK: no hits (71 file(s) scanned) and exited 0; deleting src/telecom/ alone printed OK: no hits (105 file(s) scanned) exit 0 with 17 unopened; the healthy control printed 122.

  A denominator cannot detect either shape, which is the second time that has had to be recorded here: 71 next to a healthy 122 is not a number anything about the report makes look wrong, because a count counts the files that WERE found. The sweep now refuses (exit 2) naming every tracked in-scope file it did not open. The expected set comes from the index, never from the walk, because anything re-derived from the walk would agree with the walk forever.

  Fails closed when git cannot say what is tracked (pre-fix that case printed OK: no hits and

... (truncated)

Commits

• c3ba287 Version Packages (#71)
• b0999b2 fix(phi-scan): read the bytes git carries as a union with the walk (PHI-SCAN)...
• 2cade73 feat(gate): assert the two-file agent-notes contract in the test suite (AGENT...
• 2d1b295 Version Packages (#67)
• 2978d94 docs(readme): link the Cosyte lockup to cosyte.com (ASSETS) (#66)
• 3e140ff fix(changeset): reword the pending summary so the release renders, and re-der...
• df05854 fix(changelog): turn the Changesets changelog generator on, so the tarball st...
• b041427 fix(phi-scan): reconcile the sweep against the index, so an emptied scan root...
• 16c2fea Version Packages (#62)
• bf276ff fix(phi-scan): refuse a declared scan root the walk cannot enumerate (PHI-SCA...
• Additional commits viewable in compare view