Skip to content

Promote the Release History Correction - #663

Merged
ptr727 merged 1 commit into
mainfrom
develop
Aug 11, 2026
Merged

Promote the Release History Correction#663
ptr727 merged 1 commit into
mainfrom
develop

Conversation

@ptr727

Copy link
Copy Markdown
Owner

One squash: #662 at 31880f0.

Merge with a merge commit, never a squash, and never with --delete-branch — this PR's head isdevelop.

Why it wants promoting before the release, not after

HISTORY.md's Version 2.0 entry enumerates what this repository contains and had stopped at the AUDIT.md convergence procedure, omitting three peers of the things it lists: RESYNC.md, the host tool contract and its version floors, and the derived detector for files the hub hosts rather than carries.

A release cut against the previous text publishes a changelog whose summary omits the work. The release reads main, so this promotion is the last step before a dispatch is worth making.

Verification

README.md and HISTORY.md must open as twins per spec/readme-structure.md, checked with the audit's own extraction rather than by eye: titles match, taglines match. cspell clean on both gated files, prose_lint, markdownlint-cli2 and editorconfig-checker clean, CRLF preserved byte-wise.

🤖 Generated with Claude Code

A pre-release check that found something, rather than a change anyone
asked for.
## Problem
`HISTORY.md`'s Version 2.0 entry enumerates what this repository became:
*"the shared fleet rules, a machine-readable `spec/`, the fleet
`registry/`, per-repo audit `reports/`, branch rulesets, and the
`AUDIT.md` convergence procedure."*
Three things shipped since are **peers of the items in that list** and
appear nowhere in it:
- **`RESYNC.md`**, now the third procedure an agent routes between, not
a detail of the second
- **The host tool contract** and its version floors,
`spec/host-tools.json` plus a carried `host-tools.json` per repository
- **The derived detector** for files the hub hosts rather than carries,
so a retired file is found rather than remembered
## Why it was worth catching first
A patch release cut against this entry would have published a changelog
whose summary omits the session's main deliverable. A reader asking how
a repository resyncs would find an enumeration naming only the procedure
that *measures*.
`HISTORY.md` is per minor version rather than per patch, so nothing is
owed for a routine `2.0.x`. What is owed is that the 2.0 summary stay
true about what 2.0 contains, and it had stopped being true.
## The pattern, third time today
This is the same shape as the `spec/` enumerations corrected in
[#653](#653) and the
`Repository Layout` bullet corrected downstream in Blog: **a list that
was accurate when written, going stale under a change that never
mentioned it, with no gate that reads it.**
The recurrence is worth noting on its own. Three instances in one
session suggests enumerations are a standing hazard rather than three
accidents, and the deletion sweep's new "read the files whose job is to
say what the repo holds"
([#660](#660)) covers
deletions only. Additions have no equivalent instruction. Not fixing
that here.
## Verification
The `README.md` and `HISTORY.md` openings must mirror per
`spec/readme-structure.md`, so that was checked rather than assumed:
titles match, taglines match, using the audit's own extraction.
`cspell` on both gated files clean, `prose_lint --diff HEAD` clean,
`markdownlint-cli2` clean, `editorconfig-checker` clean, CRLF preserved
byte-wise.
🤖 Generated with [Claude Code](https://claude.com/claude-code)
Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>
CopilotAI lite review requested due to automatic review settings August 11, 2026 00:16

CopilotAI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Updates the Version 2.0 release-history entry to accurately reflect the repository's current governance/audit scope before the next release cut from main.

Changes:

  • Expands the Version 2.0 bullet to include the three agent procedures (STANDUP.md, AUDIT.md, RESYNC.md).
  • Notes the host tool contract files (spec/host-tools.json, host-tools.json) and the derived “hub-hosted vs carried” detector.

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

@ptr727
ptr727 merged commit 1927e9a into mainAug 11, 2026
7 checks passed
Sign up for freeto 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.

2 participants

@ptr727