v1.0.0 release notes: nothing in the repository says what the release covers or lists its known limits #472

Lane: openreposhape-3 (openRepoShape-3)

(lane openRepoShape-3, 2026-10-12T21:40Z) Filed by lane 3's v1.0.0 triage. Proposed holder: lane openRepoShape-4, on Brett Heap's word at 21:21Z, "try to assign to lane 4 some tasks". Lane 4 claims it under Rule 1 as usual. Not claimed by lane 3.

What v1.0.0 needs. Brett Heap's release gate (2026-10-12) is: every in-scope issue closed, a full run green on Linux, macOS and Windows on the release commit, README and AGENTS.md accurate, and release notes listing the known limits. Nothing in the repository holds release notes yet: there is no CHANGELOG, no notes file, and no draft release.

The task. Draft the v1.0.0 release notes, so Brett can read them and amend them before he tags.

1. What v1.0.0 is. Core flows on all OSes: scaffold (setup.sh, setup-project.py, openRepoShape), adopt, update-shape, bump-leg, family and doctor. Say which platform runs which entry point, as README does.
2. What changed since the shape was first published. Group it by area, following the five parents: Tracking: adopt-project.py, converting an existing repository in place #457 adopt, Tracking: update-shape.py and bump-leg.py, keeping a project's shape copies and leg pins current #458 update-shape and bump-leg, Tracking: setup, scaffold, family and the shared helpers, creating projects and families #459 setup, scaffold, family and the shared helpers, Tracking: shape-doctor.py, reporting a repository's compliance #460 doctor, Tracking: the test suite, CI and the docs #461 tests, CI and docs. Keep it to the user-visible behaviour and the refusal and finding codes a reader will meet. Use git log on main for the material, and never paste commit messages wholesale.
3. Known limits. Every open issue that is NOT in the v1.0.0 milestone, plus every unfiled item on the five parents' checklists. Give each one line: what input triggers it and what the person sees. Group them by area. The parents' bodies say which issues are known limits. Re-read them just before the PR, because lanes add items all day.
4. Placement. Propose the notes as a pull request. A new file under docs/ is the obvious home, but check tests/test_repo_hygiene.py first for any rule about files in docs/. Copy the text into the GitHub release body at tag time; that is Brett's act. Leave the README and AGENTS.md caps alone.

The in-scope list keeps moving until the tag, so the PR should land late. A draft that names the known limits early is still worth having, because Brett may move items in or out of scope once he reads them listed together.

Parent: #461 (tests, CI and docs).