feat(spacecraft-steelbore-standard): §15.1 published, §18.4 at release — v2.07 - #73
Conversation
…e — v2.07 Skill-side sync of Standard PR #41. §15.1 read "each Spacecraft Software project has a dedicated subdomain", against a PROJECTS.md that tracks what is on disk. Reconciling them literally obliged sixty-seven entries covering vendored upstream forks, symlinks into other trees, and scratch directories — none published by us. The rule now says "published", defined as having a repository under a namespace we control (§6.4), and seventeen genuine rows are added. §18.4's remediation entry now falls due at a release tag or a declaration of usability rather than on adoption. Since v1.33 every pre-release experiment owed a dated assessment for existing at all, and at v2.06 exactly one project carried one while roughly fourteen owed one. Both changes remove obligations; neither can make a conforming project non-conformant. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 761eb97e1f
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| # The Steelbore Standard — Compliance Reference | ||
|
|
||
| **Version:** 2.06 | **Date:** 2026-09-15 | **Author:** Mohamed Hammad | ||
| **Version:** 2.07 | **Date:** 2026-09-15 | **Author:** Mohamed Hammad |
There was a problem hiding this comment.
Rebuild and commit spacecraft-steelbore-standard.zip and .skill with this source update. Both archive blobs are unchanged from the parent and still contain the v2.04 SKILL.md and changelog, so consumers installing either bundle receive none of the v2.07 rules added here even though the repository source advertises v2.07.
AGENTS.md reference: AGENTS.md:L98-L101
Useful? React with 👍 / 👎.
1 participant
Skill-side sync of Standard#41, at the same version and date.
§15.1 — now scoped to published projects
The clause read "Each Spacecraft Software project has a dedicated subdomain", against a
PROJECTS.mdthat tracks what is on disk. Reconciling the two literally obliged sixty-seven entries, covering vendored upstream forks under §4.2 (Redox, Ventoy-RS, Markitdown…), bare symlinks (Lattice,Result→ a/nix/storepath), and scratch directories (Rget-Temp,Majestic 5 (Copy)).The table was not sixty-seven rows behind — the rule was describing a set nobody intended. It now says published, defined as having a repository under a namespace we control (§6.4), and seventeen genuine rows are added — one per distinct controlled repo.
§18.4 — the entry falls due at release
Since v1.33 a project owed a dated accessibility remediation entry from the moment §18 was adopted — for existing at all, including every pre-release experiment. At v2.06 exactly one project carried one while roughly fourteen owed one: a clause being ignored rather than a standard being enforced.
The obligation now attaches at a release tag or a declaration of usability, and is strict from there.
Verification
All eight CI gates pass locally, including the two added at v2.06 (
check-token-names.py,generate-palette-css.py --check). Description cap re-measured at 994/1000.No project conforming at v2.06 becomes non-conformant at v2.07 — both changes remove obligations.
🤖 Generated with Claude Code