Skip to content

docs: remove the agent notes and keep what still binds - #83

Merged
NSchatz merged 1 commit into
mainfrom
docs/remove-agent-notes
Nov 8, 2026
Merged

NSchatz merged 1 commit into
mainfrom
docs/remove-agent-notes

Conversation

@NSchatz

@NSchatz NSchatz commented Nov 8, 2026

Copy link
Copy Markdown
Contributor

Removes documentation/agent-notes.md (90 KB) at the operator's direction, keeping only what still binds, in the place it is used.

What moved where

Deleted

  • documentation/agent-notes.md: phase history, dated publish-state and ruleset readings, measurements, and refuted claims. Git history keeps them.
  • The pnpm check:agent-notes step in the standards job (the job keeps its README, card, and catalog checks) and the check:agent-notes script.
  • The pointers in CLAUDE.md, AGENTS.md, no-internal-refs.yml, and scripts/check-no-internal-refs.sh, whose error message now names the script's own header.

Left as dated records: documentation/hl7-refresh/record.md and test/_support/hl7-baseline-corpus.json name the old checker inside a capture of an earlier run.

No changeset: no published file changed.

Gate

Local: install, typecheck, lint, format:check, phi-scan, test (920 passed), build, attw, the examples job, check:readme, check:claude-card (50 of 60 lines, 2,842 of 5,120 bytes), check:catalog, check:no-emdash, check:no-internal-refs. test:coverage timed out in three conformance suites on a host at load 18 and passes the same suites without coverage; CI is the arbiter there.

The card's rules stand on their own, the #29 title rule is a test in test/sanity.test.ts, and the standards job drops its agent-notes step. Everything else that binds was already at the code it guards.
@NSchatz
NSchatz merged commit 602d82b into main Nov 8, 2026
13 checks passed
@NSchatz
NSchatz deleted the docs/remove-agent-notes branch November 8, 2026 04:18
NSchatz added a commit that referenced this pull request Nov 8, 2026
Places two rules the agent notes held that the removal (#83) left
without a home, one line each on the CLAUDE.md card (now 54 of 60 lines,
3,228 of 5,120 bytes):

- Never move a published version backwards: npm refuses a version once
used, even after an unpublish, and consumers pin ranges a lower version
falls outside. Nothing in the release workflow enforces it, which is why
it goes on the card: the shared `release.yml` this repo calls decides
that a release is pending by whether the `v<version>` tag exists, and
its `publish-floor.mjs` compares tool versions, not package versions.
- CI on a fork PR is unproven. No pull request from a fork has run here
(`gh pr list --state all` lists none), and the fork approval policy is
`first_time_contributors`, so a first-time contributor's workflows wait
for a maintainer's approval. Tell no contributor a fork PR is fine until
someone has watched one pass.

`CLAUDE.md` is not in `package.json` `files`, so there is no changeset.
The full gate from CLAUDE.md passed locally on Node 26, with one caveat:
on a machine at load 20 to 30, three conformance tests in
`test/conformance/` ran 10 to 22 s under `pnpm test:coverage` against
the 10 s test timeout, so that step passed (920 of 920, thresholds met)
only with `--testTimeout=60000`. `pnpm test` passed them at the standard
timeout, and CI runs the standard timeout.

https://claude.ai/code/session_01MXLcW95gf97vs9RBU1YsXf
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant