Transaction-Science/open-standards
Watch
1
0
Fork
You've already forked open-standards
 0
Code Issues Pull requests Projects Releases 15 Packages Wiki Activity Actions

Public-text checks: the OER/2 documents and corpus are checked like any other file #545

Merged
dcharlot merged 1 commit from scripts/public-text-checks-cover-oer into main 2026-10-29 22:53:46 -04:00
Conversation 0 Commits 1 Files changed 2 +5 -10
dcharlot commented 2026-10-29 22:29:03 -04:00
Owner
Copy link

Both public-text checks (check-public-names.sh, check-comparative-prose.sh) skipped wai/extensions/oer-receipts.md, wai/wai-rs/src/oer.rs and wai/oer-conformance/ as settled text "which no change may edit". #542 adds OER/2 minor version 1 ("oer":"2.1", additive; a "2.0" receipt reads exactly as before) and edits all three, so its new text would have gone unchecked.

Every one of those files passes both checks, both on main and at #544's head (34 files). So nothing needed the exclusion. This PR removes it from both scripts, and a change to those files is now checked like a change to any other.

Checks

  • Both checks over the whole tree with the change: names clean (3,995 files), prose clean (3,981).
  • scripts/test-public-text-checks.sh: every case gave its stated status.
  • #542/#544's added lines in the OER/2 files (7 files), checked on their own: both clean.

Falsification. I appended a "best-in-class" line to wai/oer-conformance/README.md:

Check Files Result
With this change 3,981 caught: wai/oer-conformance/README.md:148
Main's check 3,949 (32 fewer, the excluded OER/2 files) clean

Then I restored the tree.

🤖 Generated with Claude Code

Both public-text checks (`check-public-names.sh`, `check-comparative-prose.sh`) skipped `wai/extensions/oer-receipts.md`, `wai/wai-rs/src/oer.rs` and `wai/oer-conformance/` as settled text "which no change may edit". #542 adds OER/2 minor version 1 (`"oer":"2.1"`, additive; a `"2.0"` receipt reads exactly as before) and edits all three, so its new text would have gone unchecked. **Every one of those files passes both checks**, both on main and at #544's head (34 files). So nothing needed the exclusion. This PR removes it from both scripts, and a change to those files is now checked like a change to any other. **Checks** - Both checks over the whole tree with the change: names clean (3,995 files), prose clean (3,981). - `scripts/test-public-text-checks.sh`: every case gave its stated status. - #542/#544's added lines in the OER/2 files (7 files), checked on their own: both clean. **Falsification.** I appended a "best-in-class" line to `wai/oer-conformance/README.md`: | Check | Files | Result | |---|---|---| | With this change | 3,981 | caught: `wai/oer-conformance/README.md:148` | | Main's check | 3,949 (32 fewer, the excluded OER/2 files) | clean | Then I restored the tree. 🤖 Generated with [Claude Code](https://claude.com/claude-code)
Public-text checks: the OER/2 documents and corpus are checked like any other file
All checks were successful
standards workspaces build + test / which workspaces this change touches (pull_request) Successful in 7s
Details
standards workspaces build + test / macOS energy backends (pull_request) Has been skipped
Details
repository checks / lockfiles, advisories, tests in CI, workflow hygiene, spec and section references, public text (pull_request) Successful in 2m30s
Details
6b297d9e54 
Both checks skipped wai/extensions/oer-receipts.md, wai/wai-rs/src/oer.rs and
wai/oer-conformance/ as settled text "which no change may edit". OER/2's minor
version 1 (#542) edits all three, and its new text would have gone unchecked.
Every one of those files passes both checks, at main and at #544's head, so
nothing needed the exclusion: it is gone, and a change to them is checked as a
change to any other file is.

Co-Authored-By: Claude Opus 5.5 <[email protected]>
Sign in to join this conversation.
Reviewers
No reviewers
Labels
Clear labels
No items
No labels
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
Transaction-Science/open-standards!545
No description provided.