Changeset 0.35.0 (#209)

Co-authored-by: Jeffrey Smith <jasafpro@gmail.com>
Co-committed-by: Jeffrey Smith <jasafpro@gmail.com>

docs/ROADMAP.md

@@ -436,48 +436,48 @@ structured data — not chat transcripts.
 Depends on: v0.31.2 (team workflow self-service), v0.29.0 (Starlark sandbox).
 
 **Form Rendering Surface:**
-- [ ] Visitor form renderer — reads `form_template` from stage, renders
+- [x] Visitor form renderer — reads `form_template` from stage, renders
       HTML inputs (text, email, select, date, textarea, checkbox, file),
       validates client-side, submits via `/w/:id/form-submit`
-- [ ] Progressive form — multi-step within a single stage (fieldsets)
-- [ ] Conditional fields — show/hide based on previous answers
-- [ ] File upload in forms — attach to stage_data via storage API
-- [ ] Branded form page — uses workflow `branding` (colors, logo, tagline)
+- [x] Progressive form — multi-step within a single stage (fieldsets)
+- [x] Conditional fields — show/hide based on previous answers
+- [x] File upload in forms — attach to stage_data via storage API
+- [x] Branded form page — uses workflow `branding` (colors, logo, tagline)
 
 **Data Pipeline (between-stage processing):**
-- [ ] `on_advance` hook — Starlark entry point fires after each stage
+- [x] `on_advance` hook — Starlark entry point fires after each stage
       transition, receives `stage_data`, can enrich/transform/reject
-- [ ] External data enrichment — Starlark `http.fetch` pulls from
+- [x] External data enrichment — Starlark `http.fetch` pulls from
       external APIs, merges results into `stage_data` (reduce double entry)
-- [ ] Data validation rules — Starlark `on_validate` can enforce
+- [x] Data validation rules — Starlark `on_validate` can enforce
       cross-field business rules beyond per-field type checks
-- [ ] Stage data schema — typed `stage_data` with declared fields,
+- [x] Stage data schema — typed `stage_data` with declared fields,
       not opaque JSON blob. Enables structured review views
 
 **Conditional Routing:**
-- [ ] Branch expressions — `transition_rules.condition` evaluated against
+- [x] Branch expressions — `transition_rules.condition` evaluated against
       `stage_data` to select next stage (not always ordinal+1)
-- [ ] AI-triggered routing — persona calls `workflow_route` tool with
+- [x] AI-triggered routing — persona calls `workflow_route` tool with
       a target stage name based on conversation analysis
-- [ ] Escalation pattern — "if AI confidence < threshold, route to
+- [x] Escalation pattern — "if AI confidence < threshold, route to
       human review stage" (help desk use case)
-- [ ] Loop stages — return to a previous stage for correction without
+- [x] Loop stages — return to a previous stage for correction without
       using reject (iterative data gathering)
 
 **Structured Review:**
-- [ ] Assignment review view — team member sees `stage_data` as a
+- [x] Assignment review view — team member sees `stage_data` as a
       structured card/form, not just chat history
-- [ ] Approval/reject with comments — reviewer adds notes visible
+- [x] Approval/reject with comments — reviewer adds notes visible
       to the next stage (not buried in chat)
-- [ ] Side-by-side view — chat history + structured data together
-- [ ] Bulk review — multiple assignments in a queue with keyboard nav
+- [x] Side-by-side view — chat history + structured data together
+- [x] Bulk review — multiple assignments in a queue with keyboard nav
 
 **Monitoring Dashboard:**
-- [ ] Active instances list — workflow name, current stage, assignee,
+- [x] Active instances list — workflow name, current stage, assignee,
       age, last activity
-- [ ] Stage funnel — how many instances at each stage, bottleneck detection
-- [ ] SLA timers — configurable per-stage, visible in review + dashboard
-- [ ] Stale instance alerts — notify team admins when instances age out
+- [x] Stage funnel — how many instances at each stage, bottleneck detection
+- [x] SLA timers — configurable per-stage, visible in review + dashboard
+- [x] Stale instance alerts — notify team admins when instances age out
 
 **Use case validation targets:**
 - Help desk: AI + KB → escalation to human → resolution tracking