@cosyte/mllp 0.0.10 → 0.0.11
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/CHANGELOG.md +71 -0
- package/README.md +6 -4
- package/dist/index.cjs +1 -1
- package/dist/index.cjs.map +1 -1
- package/dist/index.mjs +1 -1
- package/dist/index.mjs.map +1 -1
- package/package.json +2 -1
package/CHANGELOG.md
CHANGED
|
@@ -1,5 +1,76 @@
|
|
|
1
1
|
# Changelog
|
|
2
2
|
|
|
3
|
+
## 0.0.11
|
|
4
|
+
### Patch Changes
|
|
5
|
+
|
|
6
|
+
- aa8ea34: Gate this repository's two-file guidance contract, so a dangling pointer or an emptied section cannot land unnoticed.
|
|
7
|
+
|
|
8
|
+
`scripts/check-agent-notes.ts` (`pnpm check:agent-notes`) checks three things: that
|
|
9
|
+
`documentation/agent-notes.md` is tracked, that every section under a heading has a body, and that
|
|
10
|
+
every pointer at it, in a file the check opened, resolves to an anchor GitHub would actually mint.
|
|
11
|
+
A heading immediately followed by a deeper one is a container whose body is its subsections, so it
|
|
12
|
+
is not reported; the obligation moves down to the deeper heading, which means an emptied leaf is
|
|
13
|
+
still a finding and a trailing heading is never a container.
|
|
14
|
+
Splitting the guidance in two moved the reasoning behind a link, which made the link load-bearing,
|
|
15
|
+
and nothing
|
|
16
|
+
checked it. A rename, an emptied section, or an anchor edited on one side of the pair and not the
|
|
17
|
+
other would all have been silent.
|
|
18
|
+
|
|
19
|
+
The check is named for what it checks and asserts no universal. Measured across the sibling
|
|
20
|
+
repositories on 2026-08-06, three carry no such file at all, so a check written as though every
|
|
21
|
+
repository kept the same contract would assert something those three disprove. This one asserts this
|
|
22
|
+
repository's promise only, and it runs in this repository's own tests.
|
|
23
|
+
|
|
24
|
+
It refuses rather than reporting clean over a corpus it never opened. There is no declared root to
|
|
25
|
+
be wrong about: the file list comes from `git ls-files`, every path in it is opened or refused, and
|
|
26
|
+
the only silent skip is a file containing a NUL byte, which is counted and named on the success
|
|
27
|
+
line as a disclosed miss rather than a pass. It exits 2 when nothing is tracked, when a tracked
|
|
28
|
+
path is missing, unreadable, a symlink or not a regular file, when a path is unmerged, and when it
|
|
29
|
+
finds no pointers at all. A finding exits 1 and a refusal exits 2, so a broken checker can never be
|
|
30
|
+
read as a list of real findings.
|
|
31
|
+
|
|
32
|
+
Each tracked path is resolved exactly once, by a single open, and the symlink and regular-file
|
|
33
|
+
questions are asked of the resulting descriptor rather than of the path a second time. Checking a
|
|
34
|
+
path and then reading it again is a time-of-check/time-of-use race, and the refusal it threatens is
|
|
35
|
+
the symlink one, which is what stops bytes from outside the tree being scanned under a tracked
|
|
36
|
+
path's name. Opening with the no-follow flag makes that refusal part of the open itself, and the
|
|
37
|
+
non-blocking flag is what keeps a tracked path replaced by a FIFO from hanging the check instead of
|
|
38
|
+
refusing it.
|
|
39
|
+
|
|
40
|
+
Both heading shapes that defeat a naive leading-hash rule are handled and reproduced end to end: a
|
|
41
|
+
heading indented by a space, and one underlined rather than hashed. Both are false-red bypasses,
|
|
42
|
+
because a missed heading is a missing anchor. So is the opposite direction, where a hash line inside
|
|
43
|
+
a code fence, or a YAML front-matter key, must not mint an anchor or a dangling pointer would pass.
|
|
44
|
+
The slug transformation is measured against github-slugger rather than assumed, including four
|
|
45
|
+
shapes that diverge from the obvious implementation: a dropped leading character leaves a leading
|
|
46
|
+
hyphen behind, a repeated heading is re-suffixed until its slug is free, a space separator other
|
|
47
|
+
than the plain one is deleted, and a heading wrapped across two lines has the break deleted rather
|
|
48
|
+
than turned into a hyphen.
|
|
49
|
+
|
|
50
|
+
Measured against the parent commit by running it there: zero violations. This changes no content and
|
|
51
|
+
exists to stop a regression. `test/scripts/agent-notes.test.ts` runs it against this tree, seeds each
|
|
52
|
+
violation class into throwaway repositories, pins each disclosed miss that has anything to execute in
|
|
53
|
+
the direction it actually fails, and includes the control that a check pointed at nothing must refuse
|
|
54
|
+
rather than report clean. Two of the disclosed misses are statements of scope rather than behaviour,
|
|
55
|
+
so there is nothing to run for them and none is claimed.
|
|
56
|
+
|
|
57
|
+
Repository tooling and guidance only. No runtime code, no public API, no warning code, and no
|
|
58
|
+
framing or transport behaviour changed.
|
|
59
|
+
- 4cc0776: The README lockup now links to cosyte.com (`ASSETS`).
|
|
60
|
+
|
|
61
|
+
The `<picture>` block above the H1 is wrapped in an anchor to https://cosyte.com, per the founder
|
|
62
|
+
requirement of 2026-08-06. Nothing inside the block moved: the `<source>`, the `<img>`, the alt text
|
|
63
|
+
and both tile URLs are byte-identical.
|
|
64
|
+
|
|
65
|
+
What the anchor does was measured on both surfaces by `fhir`, not assumed, because fourteen READMEs
|
|
66
|
+
carry this shape. On GitHub the anchor works and the colour-scheme switch keeps working, because the
|
|
67
|
+
`<img>` stays a direct child of `<picture>`, which is the condition the HTML spec puts on `<source>`
|
|
68
|
+
applying at all. On an npm package page the anchor is lost: npm wraps a README image in its own
|
|
69
|
+
anchor to the image file, a nested anchor is not representable, so the parser closes ours early and
|
|
70
|
+
the image ends up linked to the image file rather than to cosyte.com. Shipped anyway by founder
|
|
71
|
+
decision of 2026-08-07: on npm that is no worse than the unlinked lockup it replaces, and GitHub is
|
|
72
|
+
where these READMEs are read.
|
|
73
|
+
|
|
3
74
|
## 0.0.10
|
|
4
75
|
### Patch Changes
|
|
5
76
|
|
package/README.md
CHANGED
|
@@ -1,7 +1,9 @@
|
|
|
1
|
-
<
|
|
2
|
-
<
|
|
3
|
-
|
|
4
|
-
|
|
1
|
+
<a href="https://cosyte.com">
|
|
2
|
+
<picture>
|
|
3
|
+
<source media="(prefers-color-scheme: dark)" srcset="https://cosyte.com/tile/cosyte-lockup-tile-on-dark-1200x300.png">
|
|
4
|
+
<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">
|
|
5
|
+
</picture>
|
|
6
|
+
</a>
|
|
5
7
|
|
|
6
8
|
# @cosyte/mllp
|
|
7
9
|
|
package/dist/index.cjs
CHANGED