docs: sync superpowers specs/plans to hold decision

- iterations 18/25/26 marked hold in their spec + plan headers
- 25's story file removal committed; plan doc stays for resumption
- web-framework spec's relates-to flags 25 held

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/stories/language-runtime-database/25-http-service.md

@@ -1,53 +0,0 @@
-# Iteration 25 — HTTP service layer
-
-> Format: fiberloom `product/story-iteration-template`. Part of
-> [Story — one language, one runtime, one database, one binary](00-story.md).
-
-## Goals
-
-- The single binary serves: `service rest` blocks compile to routes and the
-  runtime answers HTTP from its shards — hand-rolled HTTP and JSON, zero
-  libraries, per the dependency doctrine.
-- The new stack reaches feature parity with the Rust runtime's Stage 2
-  REST surface — the concrete bar the retirement decision measures
-  against.
-
-## Acceptance Criteria
-
-- What to achieve?
-    - **Given** the blog sample's `service` declarations,
-    - **when** the compiled binary boots and `reference/rest/blog.rest`
-      runs against it,
-    - **then** every request in the smoke file answers as documented —
-      including the intentional 501/405/404 responses.
-- What to achieve?
-    - **Given** a method call arriving over REST that traps (borrow
-      violation, abort, unique violation),
-    - **when** the response returns,
-    - **then** exactly one trap-to-HTTP table governs the mapping (e.g.
-      conflict-shaped 409s) and the structured error body carries the trap
-      record — the same trap surface everywhere, now over the wire.
-- What to achieve?
-    - **Given** transports declared at boot,
-    - **when** the runtime starts under systemd socket activation or with
-      zero listeners,
-    - **then** both boot correctly — a runtime is not tied to a port.
-
-## Out Of Scope
-
-- WebSocket/live subscriptions and UI (the parked `##ui` story).
-- The management plane endpoints (iteration 11 builds them on this
-  machinery).
-
-## Info
-
-- Route declarations ride the `.wob` format as a versioned section — a
-  coordinated format bump, the pattern later sections follow.
-- The C reference's phase-C HTTP machine is the porting source.
-
-## Proposed Solution
-
-- Execute the existing plan: `docs/superpowers/plans/2026-08-01-http-service-layer.md`
-  (per-shard http module, hand-rolled JSON codec, service-block route
-  section, Stage-2-parity CRUD, method RPC with the trap table, blog.rest
-  smoke).

docs/superpowers/plans/2026-08-01-http-service-layer.md

@@ -1,6 +1,6 @@
 # HTTP Service Layer Implementation Plan
 
-> **Status: ⬜ pending** (story iteration 25) — `service` blocks route to VM methods; REST parity with the shipped Rust Stage 2 runtime. Board: [00-status.md](../../00-status.md)
+> **Status: ⏸ hold (2026-08-21, developer decision)** (story iteration 25) — `service` blocks route to VM methods; REST parity with the shipped Rust Stage 2 runtime. Board: [00-status.md](../../00-status.md)
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 >

docs/superpowers/plans/2026-08-20-framework-v2-memory-features.md

@@ -1,6 +1,8 @@
 # Iteration 18 — framework v2 (transaction{} + cache/flags/jobs): implementation plan
 
-> **Status: ready to execute (2026-08-20).** Board:
+> **Status: ⏸ hold (2026-08-21, developer decision)** — story iteration 18
+> sits in `stories/language-runtime-database/hold/`; plan was ready to
+> execute (2026-08-20) and stays intact for resumption. Board:
 > [docs/00-status.md](../../00-status.md).
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use

docs/superpowers/specs/2026-08-03-blue-green-vm-design.md

@@ -1,7 +1,7 @@
 # Blue/Green VM deployment — design spec
 
 **Date:** 2026-08-03
-**Status:** approved (2026-08-03); implementation plan deferred until plans 5 + 6 ship
+**Status:** approved (2026-08-03); ⏸ on hold (2026-08-21, developer decision — story iteration 26 moved to `stories/language-runtime-database/hold/`); implementation plan deferred until plans 5 + 6 ship
 **Scope:** the writeonce runtime's in-process deployment subsystem
 **Supersedes:** §5–§6 of [`docs/plan/exploration/blue-green-vm/00-vision.md`](../../plan/exploration/blue-green-vm/00-vision.md)
 

docs/superpowers/specs/2026-08-18-web-framework-design.md

@@ -7,9 +7,10 @@
 library, HTTP/1.1 behind a TLS-terminating reverse proxy, and (C) the parked
 HTTP/2 path. Three sub-projects; A and B are the fundable ones, C is a
 recorded successor.
-**Relates to:** iteration 25 (`service` blocks — this framework becomes their
-lowering target, not a rival), iterations 8/23/11 (the concurrency work h2c
-waits for), `docs/plan/discarded.md` (FFI reject row — load-bearing here).
+**Relates to:** iteration 25 (⏸ on hold since 2026-08-21; `service` blocks —
+this framework becomes their lowering target, not a rival), iterations
+8/23/11 (the concurrency work h2c waits for), `docs/plan/discarded.md` (FFI
+reject row — load-bearing here).
 
 ## Decisions locked during brainstorming
 

docs/superpowers/specs/2026-08-20-memory-db-features-design.md

@@ -4,10 +4,13 @@
 > the framework README's status ledger; this spec is what the embedded
 > store adds on top of it.
 >
-> **Status: APPROVED 2026-08-20** (developer review). Plan next.
-> Decisions were settled in
+> **Status: APPROVED 2026-08-20** (developer review); ⏸ on hold
+> (2026-08-21, developer decision — story iteration 18 sits in
+> `stories/language-runtime-database/hold/`). Decisions were settled in
 > [the iteration](../../stories/language-runtime-database/hold/18-memory-db-features.md);
-> this spec makes them buildable. The plan follows after review.
+> this spec makes them buildable. The plan is authored
+> ([framework v2 plan](../plans/2026-08-20-framework-v2-memory-features.md))
+> and held with it.
 > Board: [docs/00-status.md](../../00-status.md).
 >
 > Per repo convention: concept, reason, and required behavior in words