repos.json withholds the changelog block from five repositories that now have the file

[sehkone]

Every repository in the organization keeps a CHANGELOG.md, and the five that did not have one are getting the skeleton: aicers/bootler#221, aicers/multifold#96, aicers/roxyd#52, aicers/aice-web-next#923, aicers/aimer-web#921.

repos.json has not caught up. It gives the changelog block to seven repositories and withholds it from those same five, which would leave them holding the file with no shared rules for maintaining it — exactly the split STYLE.md warns about, in the direction it does not cover. STYLE.md says the block follows the file rather than leading it; the file is arriving, so the block should follow.

Scope

• repos.json: bootler, multifold, roxyd, aice-web-next, and aimer-web gain changelog. All twelve then carry it.
• CHANGELOG.md: an entry for 0.1.2.

Why this is safe to land before those five pull requests merge

None of the five consumes anything yet — no drift-check job, no pin file, no marker pairs. repos.json is intent, and intent has no effect on a repository until it is onboarded. What this must not do is get ahead of the file: onboarding one of them while it still has no CHANGELOG.md would hand it rules for a file that is not there, which is what deploy-core hit. #22 orders that work, and each repository's CHANGELOG.md has to be merged before its onboarding pull request opens.

Grade

PATCH. A rule newly applying to a repository is MINOR, and below 1.0.0 the grades shift down one. Nothing in blocks/ changes.

This also exercises the guard fixed in #20 for real: blocks/ is byte-identical to 0.1.1 and only repos.json moves, which is the release the old guard refused.

Acceptance criteria

• All twelve entries in repos.json include changelog
• CHANGELOG.md has a 0.1.2 entry
• CI passes
• 0.1.2 tags and releases, with the guard comparing both paths