Souta 06297068c4 ci(release): main only ever merges from next — no release branch, clean sync ... The release/X.Y.Z → main promotion flow diverged next (beta.N) from main (stable) on every release, so the automatic main→next sync hit a version-file conflict each time and needed manual resolution (the 1.1.3 / 1.1.4 pain). New flow: bump next to the stable version via a PR INTO next, then promote next → main directly. main and next never diverge on the version files, so the post-release sync is a clean auto-merge. - version-check.yml: a plain X.Y.Z head on a `next` PR is now accepted as a promotion-staging shape (validated by the stable all-manifests-agree rule); the beta root-pinned rule applies only to `-beta.N` heads. Backward compatible — normal beta PRs are unaffected. - release-flow.md + CONTRIBUTING.md: rewrite the promotion + hotfix flow to "bump on next → promote next → main", drop the release/ branch, and route hotfixes through next too (main only merges from next). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-06-15 21:06:11 +09:00
..
development-setup.md	docs(en): round 1 — release-flow, dev-setup, upgrading, privacy, uninstalling	2026-05-10 19:54:08 +09:00
documentation.md	docs(ci): add wikilink + anchor checker as a docs-CI gate	2026-05-10 21:20:52 +09:00
index.md	docs(en): batch B — section landing pages for 10 sections	2026-05-10 21:39:14 +09:00
release-flow.md	ci(release): main only ever merges from next — no release branch, clean sync	2026-06-15 21:06:11 +09:00
testing-strategy.md	fix(docs): un-stale 600 KB / 330-test claims in migrated docs	2026-05-10 15:29:42 +09:00