docs: sequence pending iterations in implementation order

- new "Implementation order (sequenced 2026-08-20)" section in 00-status.md
  pending bucket: 7-finish, 17, 9g, 14, 9c/9d, 9e, 8, 9f, 11, 10, 12,
  13 + parked drain
- forcing rules recorded: 9f after 8+9e; 9c precedes 10; 9d folds into 9c;
  12 after 9+10; 11 rides 8's scheduler; h2c behind 8/9f/11; post-12 park
  directive unchanged
- 9e placed before 8 so restructure/perf work has a signed baseline
- 14 early as next driving workload (stdlib-shaped, shard-independent)
- story 00-story.md notes point at the sequenced list

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

docs/00-status.md

@@ -305,6 +305,41 @@ The C proving-ground work (`exploration/c-runtime/`, phases A–F: 859k reads/s,
 
 ## Pending
 
+### Implementation order (sequenced 2026-08-20)
+
+Dependency-derived order for everything not yet landed. Rules that force it:
+9f explicitly after 8 + 9e; 9c "precedes iteration 10"; 9d's plan folds into
+9c's; 12 only after 9 + 10 (catalog to diff, HTTP to build on); 11 rides 8's
+shard scheduler; h2c parked behind 8/9f/11; the post-12 parked list stays
+parked by the 2026-08-08 scope directive.
+
+1. **7 finish** — in progress (executable plan: leaks, stop signal, fd
+   lifetime, soak); the locked critical path ends here.
+2. **17** — forks settled, compiler-driver-only, no runtime deps; kills the
+   framework's `--emit` wart while iteration 16 is fresh. (Merge the
+   `web-framework` branch first.)
+3. **9g** — likely collapses to "confirm `len(query)` + add `exists`"; the
+   skillhost corpus already showed no new grammar; do before 14 consumes it.
+4. **14** — skillhost port, the next driving workload (log-watcher's role for
+   host capabilities); stdlib-shaped, independent of shards;
+   bounded-subprocess gap first.
+5. **9c then 9d** — finish the half-done branches (ipc-attach: manifest +
+   binding; keypair-auth: manifest) while DB context is warm; 9d folds into
+   9c's plan; both must precede 10.
+6. **9e** — the measurement backbone; baseline single-shard BEFORE the
+   runtime restructure so 8/9f have numbers to sign against.
+7. **8** — shard-actor; the big structural move; precondition (collector
+   settled, 7b) already met; unblocks 9f, 11, h2c.
+8. **9f** — io_uring group-commit; explicitly after 8 + 9e.
+9. **11** — fibers on the shard scheduler; keeps VM-core work contiguous
+   with 8/9f (same dispatch/io seams).
+10. **10** — HTTP service layer; after 9c by its own precedence note;
+    lowers `service` blocks onto the iteration-16 framework.
+11. **12** — blue-green; prerequisites 9 + 10 now exist.
+12. **13 + parked drain** — metaprogramming (spec first), then h2c,
+    group-by, `pub(read)`/`using`/`#if`, ADT roster, WO-E225 — all held
+    behind 12 by the scope directive.
+
 ### Language track — sequenced, on the critical path
 
 | #   | Item                                                                                                                                                                           | Plan                                                                                               |

docs/stories/language-runtime-database/00-story.md

@@ -89,6 +89,10 @@ list, and a pointer to the plan document that already sequences its tasks.
 - **Critical path (locked 2026-08-08): compile and run log-watcher.**
   Iterations 3 → 4 → 5 → 6 → 7 are the committed line; nothing off that
   line lands before iteration 7's acceptance. Then 7b, then 8–12 (with 9b after the database engine).
+- **Implementation order re-sequenced 2026-08-20** for everything still
+  pending: 7-finish → 17 → 9g → 14 → 9c/9d → 9e → 8 → 9f → 11 → 10 → 12 →
+  13 + parked drain. Rationale and forcing dependencies live in
+  [`docs/00-status.md`](../../00-status.md) under "Implementation order".
 - **Iteration 7b (inserted 2026-08-11)** sits after the critical path
   deliberately: it delays nothing on the log-watcher line, and it must precede
   iteration 8 because the collector should be settled before shards multiply.