Name the New Pieces in the Release History (#662)

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>

Author: ptr727

HISTORY.md

@@ -5,6 +5,6 @@ Agent enablement for a fleet of repositories: autonomy and repeatable quality in
 ## Release History
 
 - Version 2.0:
-- Repurposed from a .NET sample-project template into a governance and workflow-audit catalog: the shared fleet rules (`AGENTS.md`, `CODESTYLE.md`, `WORKFLOW.md`), a machine-readable `spec/`, the fleet `registry/`, per-repo audit `reports/`, branch rulesets, and the `AUDIT.md`convergence procedure. Ships no application code, and the old sample project and its build pipeline are removed.
+- Repurposed from a .NET sample-project template into a governance and workflow-audit catalog: the shared fleet rules (`AGENTS.md`, `CODESTYLE.md`, `WORKFLOW.md`), a machine-readable `spec/`, the fleet `registry/`, per-repo audit `reports/`, branch rulesets, and three procedures an agent routes between by what a repository actually holds: `STANDUP.md` from nothing to operational, `AUDIT.md`to measure without changing anything, and `RESYNC.md` to bring a repository that has fallen behind back into line. Adds a host tool contract with version floors (`spec/host-tools.json` and a carried `host-tools.json` per repository), and a derived detector for files the hub hosts rather than carries, so a retired file is found rather than remembered. Ships no application code, and the old sample project and its build pipeline are removed.
 - Version 1.0:
 - .NET sample-project template with a build and publish pipeline.