docs(design): rename Composed-1 docs *_proposed_* -> *_partial_* (M5a shipped)

Per CLAUDE.md design-doc lifecycle (rename after the first
milestone ships): both Composed-1 design docs move from
*_proposed_* to *_partial_* now that M5a has fully landed on main.

Parent doc:
  2026_05_29_proposed_composed1_cross_group_commit_guard.md
    -> 2026_05_29_partial_composed1_cross_group_commit_guard.md

  Status header updated to record:
    - M1-M4 shipped via PR #900
    - M5a shipped via PRs #911 / #916 / #924 / #925
    - M5b (route-shuffle nemesis) still open

M5 doc:
  2026_06_02_proposed_composed1_m5_jepsen_route_shuffle.md
    -> 2026_06_02_partial_composed1_m5_jepsen_route_shuffle.md

  Status header enumerates the M5a delivery PRs, the cross-PR
  PR #926 fix discovered during E2E, and a separate
  ResourceNotFoundException follow-up issue still under
  investigation.

Parent-doc cross-reference link updated to point at the renamed
partner so internal navigation stays correct after the rename.

Doc-only change.  All other content preserved verbatim per the
lifecycle convention (only the status block evolves; the design
body is the as-shipped record from each milestone).

Author: bootjp

…ed_composed1_cross_group_commit_guard.md …al_composed1_cross_group_commit_guard.mddocs/design/2026_05_29_proposed_composed1_cross_group_commit_guard.md renamed to docs/design/2026_05_29_partial_composed1_cross_group_commit_guard.md docs/design/2026_05_29_proposed_composed1_cross_group_commit_guard.md renamed to docs/design/2026_05_29_partial_composed1_cross_group_commit_guard.md

@@ -1,8 +1,12 @@
 # Composed-1 — cross-group commit-time ownership guard
 
-Status: Proposed
+Status: Partial — M1–M4 shipped via PR #900; M5a shipped via PRs
+#911 / #916 / #924 / #925; M5b (route-shuffle nemesis) still
+open.  See companion doc
+`2026_06_02_partial_composed1_m5_jepsen_route_shuffle.md` for the
+detailed M5 design and per-milestone state.
 Author: bootjp
-Date: 2026-05-29
+Date: 2026-05-29 (renamed *_proposed_* → *_partial_* on 2026-06-04)
 
 > **Forward-looking proposal.** Today's implementation is vacuously
 > safe with respect to Composed-1 because `SplitRange` is the only

…sed_composed1_m5_jepsen_route_shuffle.md …ial_composed1_m5_jepsen_route_shuffle.mddocs/design/2026_06_02_proposed_composed1_m5_jepsen_route_shuffle.md renamed to docs/design/2026_06_02_partial_composed1_m5_jepsen_route_shuffle.md docs/design/2026_06_02_proposed_composed1_m5_jepsen_route_shuffle.md renamed to docs/design/2026_06_02_partial_composed1_m5_jepsen_route_shuffle.md

@@ -1,10 +1,25 @@
 # Composed-1 M5 — Jepsen route-shuffle workload
 
-Status: Proposed
+Status: Partial.  M5a shipped:
+  - PR #911 — `cmd/elastickv-split` + `cmd/elastickv-route-key` CLI helpers
+  - PR #916 — `dynamodb-append-multi-table-workload` (Clojure)
+  - PR #925 — `cmd/elastickv-list-routes` + setup-hook
+    `verify-multi-group-routing!`
+  - PR #924 — `scripts/run-jepsen-m5-local.sh` single-process
+    two-group launcher (with cross-PR integration to #925)
+  - PR #926 (separate) — `--host 127.0.0.1` fix discovered during
+    M5a E2E
+
+M5b (route-shuffle nemesis) is still open.  Plus one known follow-up
+issue from M5a E2E: workers report `ResourceNotFoundException` for
+every txn despite `create-all-tables!` reporting success and ListRoutes
+showing the expected two-group catalog — likely a CreateTable
+race / sync issue under 5-parallel client setup; tracked separately.
+
 Author: bootjp
-Date: 2026-06-02
+Date: 2026-06-02 (renamed *_proposed_* → *_partial_* on 2026-06-04)
 Parent design:
-[`2026_05_29_proposed_composed1_cross_group_commit_guard.md`](2026_05_29_proposed_composed1_cross_group_commit_guard.md)
+[`2026_05_29_partial_composed1_cross_group_commit_guard.md`](2026_05_29_partial_composed1_cross_group_commit_guard.md)
 
 > **Forward-looking proposal, same posture as the parent doc.**
 > Today's `SplitRange` is same-group only (per CLAUDE.md and