integrate: sync appendix sources to v0.5 appendix table (00-10)

Integration arbitration, not a PR commit: v0.3/v0.4/v0.5 synced body
changes into appendix chapters 00/02/04/06/07 while templates/roles/
sources stayed at v0.2, so check_appendix failed 6 chapters; and
09-ops/10-iteration chapters (v0.5) were invisible to the strict
chapter regex because of the ', v0.5 new' title suffix, breaking
the #214 matrix-vs-appendix test. Direction is sources follow the
appendix (appendix is the tenant-visible authoritative version;
never overwrite v0.5 text with v0.2). 09/10 headers normalized to
strict form (suffix only); 09/10 sources split mechanically from
the appendix; EXPECTED_IDS extended to 11 chapters in the checker
and both appendix tests.

cloud/tests/test_skill_appendix_sync.py

@@ -11,7 +11,8 @@ asserting two chapters (00-coordinator, 08-shared-core) exist in the
 seeded file -- a dropped middle chapter (01..07) would pass CI silently.
 The bidirectional assertion previously discussed on the #209 track is
 unmerged, so main does not have it; this file supplies it on the main
-base (skill text v0.2, 9 appendix chapters 00..08).
+base (skill text v0.2, 9 appendix chapters 00..08;
+  integrated text is v0.5, 11 appendix chapters 00..10).
 
 What "bidirectional" means here, concretely (all derived from SKILL.md
 itself, no new semantics invented):
@@ -25,8 +26,8 @@ itself, no new semantics invented):
   merge-gate / PR-number rules but no literal "GitHub" word, so the
   test must not demand that word there);
 - body role-matrix role names == appendix role-title names as sets
-  (order differs: matrix order vs numeric 00..08 order, so set, not
-  list, comparison), and appendix ids are exactly 00..08 in order.
+  (order differs: matrix order vs numeric 00..10 order, so set, not
+  list, comparison), and appendix ids are exactly 00..10 in order.
 
 CI: .github/workflows/host-verify.yml and release.yml both run
 `python3 -m unittest discover -s cloud/tests -v`, so this test_*.py
@@ -55,7 +56,8 @@ SKILL_PATH = (REPO_ROOT / "cloud" / "skills" / "software-engineering"
 
 EXPECTED_IDS = ["00-coordinator", "01-product-manager", "02-architect",
                 "03-designer", "04-client-developer", "05-backend",
-                "06-qa", "07-acceptance", "08-shared-core"]
+                "06-qa", "07-acceptance", "08-shared-core",
+                "09-ops", "10-iteration"]
 
 # Chapter -> keywords that chapter must carry for the GitHub guarantee
 # the body claims is "同样写进了附录的协调员、客户端、验收章节".