docs: reconcile roadmap with shipped v1.2 Workflows track

The blueprint, CLAUDE.md, and the groups design doc still described the
Workflows track as "not-yet-started" and listed a per-app `materialized`
column as deferred — both stale. Workflows shipped M1–M6 (DAG execution +
conditional `when`, nested sub-workflows, durable orchestrator,
`workflow::start` SDK + admin API + `pic workflows`, dashboard DAG +
run-history; migrations 0071/0072), and D1's `materialized` column shipped.

Update the status lines to mark Workflows shipped (leaving §9.4 service
interceptors as the one remaining Workflows-track item and cluster mode as
next), bump the "migrations through 0070" note to 0072, and drop the stale
`materialized`-deferred line. Docs-only.

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

serverless_cloud_blueprint.md

@@ -1,6 +1,6 @@
 # Project Blueprint: Lightweight Event-Based Serverless Cloud
 
-**Status**: v1.1 shipped (SDK + services) · v1.2 *Hierarchies* track **complete**; v1.2 *Workflows* track + v1.3 cluster mode are next  
+**Status**: v1.1 shipped (SDK + services) · v1.2 *Hierarchies* track **complete** · v1.2 *Workflows* track **shipped** (M1–M6: DAG execution, conditional branching, nested sub-workflows, `workflow::start` SDK, dashboard DAG + run-history); §9.4 service interceptors + v1.3 cluster mode are next  
 **Last Updated**: 2026-07-12 (reconciled to shipped code — CLAUDE.md is the live source of truth)  
 **Audience**: Solo developer (DIY self-hosted)
 
@@ -171,7 +171,8 @@ rhai_executor --script $SCRIPT_PATH --request "$REQUEST_JSON"
 
 ### 3.4 PostgreSQL Database
 **Schema (MVP sketch — NOT authoritative):** the block below is the original MVP shape. The **authoritative
-schema is the migration set** in `crates/manager-core/migrations/` (through `0070` as of v1.2), which has
+schema is the migration set** in `crates/manager-core/migrations/` (through `0072` as of v1.2, incl. the
+Workflows tables), which has
 since added apps/domains, RBAC (`admin_users`/`app_members`/`api_keys`), the v1.1 data-plane services
 (KV/docs/files/queues/…), and the v1.2 groups/collections/templates/projects tables. Treat this as
 illustration only.
@@ -1271,9 +1272,9 @@ Released in patch steps (v1.1.0 → v1.1.8), each landing one focused capability
 ### Phase 5: v1.2 (Advanced Workflows & Hierarchies)
 
 Two tracks under the same minor line. The **Hierarchies** track is **complete** (all §11 Phases 1–6
-shipped, plus the Track A closeout + the 2026-07-11 audit remediation); the **Workflows** track is the
-remaining, not-yet-started half (sequencing was an open call — see the design doc's §11 re-sequencing
-note).
+shipped, plus the Track A closeout + the 2026-07-11 audit remediation); the **Workflows** track is now
+**shipped** too (M1–M6 — see the list below), leaving only §9.4 service interceptors as the remaining
+Workflows-adjacent work.
 
 **Hierarchies — groups + the declarative project tool** (the detailed design and 6-phase breakdown
 live in [docs/design/groups-and-project-tool.md](../docs/design/groups-and-project-tool.md) §11; this
@@ -1299,12 +1300,12 @@ absorbs the original one-line "Hierarchies" bullet into a full initiative):
 - **Only remaining in this track:** multi-node cluster propagation (route-table + broadcast snapshot),
   which lives in the Phase 6 / v1.3+ scaling work below.
 
-**Workflows:**
-- Function workflows (DAG execution, conditional branching, error handling)
-- Nested workflows
-- Call graph visualization + execution tracing
-- Advanced query support for document store (`docs.query()` with filters: `$gt`, `$or`, etc.)
-- Service interceptors (see section 9.4)
+**Workflows** (shipped M1–M6 unless noted; migrations `0071_workflows.sql`, `0072_execution_source_workflow.sql`):
+- Function workflows (DAG execution, conditional `when` branching, error handling) — **shipped**
+- Nested workflows (`start_child`, parent-park, depth ceiling) — **shipped**
+- Call graph visualization + execution tracing — dashboard DAG view + run-history **shipped**
+- Advanced query support for document store (`docs.query()` with filters: `$gt`, `$or`, etc.) — **shipped** (`docs_filter` DSL)
+- Service interceptors (see section 9.4) — **remaining** (the only unshipped Workflows-track item)
 
 ---