docs(standard): extract changelog into CHANGELOG.md — v1.37 - #16
Conversation
The version history is moved out of §1 — Preamble into CHANGELOG.md at the repo root, newest-first; the Preamble now carries a pointer to it plus the current version/date. All 37 entries (v1.0 through v1.36) are preserved verbatim, converted through the same texi2any --docbook | pandoc route the .md companion uses. No normative change — every rule in force is unchanged. The history had grown to roughly a fifth of the document, pushing §2 and everything after it far down the page for a reader who wants the rules rather than their provenance. This also mirrors the skill encoding, which has kept its history in references/CHANGELOG.md since v1.24. CHANGELOG.md is hand-maintained, not generated: it carries its own SPDX two-tag header (CC-BY-SA-4.0, document class per §4.1.1) rather than riding the REUSE.toml override used for the .texi/.md pair. Verified: makeinfo --no-split → zero errors/warnings; reuse lint → compliant, 8/8 files; .md companion regenerated (2166 → 1800 lines). Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
…#17) Back-sync of Spacecraft-Software/Standard#16: the Standard's version history moved out of §1 — Preamble into standard/CHANGELOG.md at the repo root. No normative change — the rules this skill encodes are unchanged; only the masthead, frontmatter version, and changelog entry move. references/CHANGELOG.md: the header no longer claims the published Standard "keeps its own inline changelog as the canonical record" — the canonical record is now standard/CHANGELOG.md, which this file mirrors. Also rebuilds spacecraft-standard-constitution.{zip,skill}, which the v1.36 sync (#15) left stale at v1.35 content — the bundles are the install surface, so they ship with every skill-directory edit. Frontmatter description: 924 chars (under the 1000-char limit). reuse lint: compliant, 604/604 files. Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 3263280067
ℹ️ 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".
| for upstream skill changes, registry updates (§2.1, §15.1), factual corrections | ||
| to normative content, and brand/identity changes. | ||
|
|
||
| - **v1.37 (2026-07-26):** **Changelog extracted from the document.** The full |
There was a problem hiding this comment.
Record the v1.37 release date in UTC
The canonical history says its dates are UTC, but this release commit was authored and committed at 2026-07-25 23:42:58 UTC while the new entry records 2026-07-26. This makes the audit record inaccurate for v1.37; use the UTC calendar date rather than the maintainer's +03:00 local date.
Useful? React with 👍 / 👎.
| @file{spacecraft-standard-constitution/references/CHANGELOG.md} in the | ||
| @uref{https://github.com/Spacecraft-Software/Construct,Construct | ||
| repository}; both are synced to the same version and date. |
There was a problem hiding this comment.
Avoid claiming the deferred changelog sync is complete
As submitted, the Construct back-sync is explicitly deferred to a separate follow-up, so its parallel changelog does not yet contain this v1.37 entry even though the published standard now states that both histories are synced. If this commit lands first, consumers are given a false synchronization guarantee; either land the Construct update first or phrase this as a synchronization requirement rather than current state.
Useful? React with 👍 / 👎.
What
The version history moves out of §1 — Preamble into
CHANGELOG.mdat the repo root, newest-first. §1 now carries a short pointer plus the current version/date.All 37 entries (v1.0 → v1.36) are preserved verbatim, converted through the same
texi2any --docbook | pandoc -t gfmroute the.mdcompanion uses, so wording and markup match what the document rendered before.Why
No normative change — every rule in force is unchanged. The history had grown to roughly a fifth of the document, pushing §2 and everything after it far down the page for a reader who wants the rules rather than their provenance. It also mirrors the skill encoding, which has kept its history in
references/CHANGELOG.mdsince v1.24.Notes
CHANGELOG.mdis hand-maintained, not generated — it carries its own SPDX two-tag header (CC-BY-SA-4.0, document class per §4.1.1) rather than riding theREUSE.tomloverride used for the.texi/.mdpair. Future version bumps prepend an entry here instead of adding an@itemto the.texi.The_Steelbore_Standard.md2166 → 1800 lines.Verification
makeinfo --no-split→ zero errors, zero warningsreuse lint→ compliant, 8/8 files carry copyright + license info.mdcompanion regenerated@settitle/@set VERSION(@set UPDATEDalready 2026-07-26)Follow-up
Construct back-sync at v1.37 lands as its own PR — it also fixes a line in
references/CHANGELOG.mdthat still claims "the published Standard document keeps its own inline changelog as the canonical record."🤖 Generated with Claude Code