Skip to content

docs: put the version and fork PR rules on the card - #85

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

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

Conversation

@NSchatz

@NSchatz NSchatz commented Nov 8, 2026 •

Copy link
Copy Markdown
Contributor

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

Two rules the agent notes held that the removal (#83) did not place, one
line each on the CLAUDE.md card:

- Never move a published version backwards. npm refuses a version once
  used, consumers pin ranges, and no release step checks the order: the
  shared release workflow decides a release by the v<version> tag, and its
  publish-floor check compares tool versions, not package versions.
- CI on a fork PR is unproven: none has run here, and a first-time
  contributor's workflows wait for approval (the repository's policy is
  first_time_contributors). Tell no contributor a fork PR is fine until
  one has passed.

Claude-Session: https://claude.ai/code/session_01MXLcW95gf97vs9RBU1YsXf
@NSchatz
NSchatz merged commit 3ae4158 into main Nov 8, 2026
14 of 16 checks passed
@NSchatz
NSchatz deleted the docs/agent-notes-followup branch November 8, 2026 04:57
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