Phase 2: execute discovered workflow proposals on /discover

[enricopiovesan]

Goal

Deliver Phase 2 of the medium-term /discover discovered path: after a visitor
reviews a browser-local BrowserWorkflowProposal from Phase 1
(website#68), hand the
reviewed proposal to local Spec-109 validation + the composed-execution adapter and
execute offline over exact prepared registry_ref components — real per-node WASM
with per-invocation redacted traces.

The runtime stays the sole authority; the browser remains an untrusted proposer
(Spec 1277 FR-005). Authored-bundle Real mode stays; this extends the discovered
path from review-only to execute.

Depends on

• website#68 (Phase 1) — discover + plan + review UI, snapshot/prep, truthfulness
  labels, committed goals, fail-closed planning path.
• traverse-embedder-web@>=0.9.0 on npm — composed-execution web binding
  (traverse#1313 code Done via PR #1315; as of 2026-09-09 npm still only publishes
  0.7.0, so consumable 0.9.0 is still required).

Decisions (from 2026-09-09 brainstorm on #68)

Full log: #68 (comment)

• Phase 1 ships publicly first; this issue owns execute only
• Keep the third labelled path; Phase 2 copy upgrades from “reviewed, not executed”
  to “…and executed”
• Do not demote authored Real until this path is proven

Definition of done

• A reviewed BrowserWorkflowProposal + prepared RegistryCacheStore is handed
  to the local Spec-109 / Spec 1277 FR-006 composed-execution path
  (traverse-embedder-web@>=0.9.0).
• Offline execution over exact prepared registry_ref components; real per-node
  WASM; per-invocation redacted traces rendered on the page.
• A proposal for an undeclared capability / prohibited mapping / connector /
  placement / side effect is rejected by the local runtime even though the browser
  produced it (FR-005).
• Fail-closed and redacted for: prepared-component drift, authorization/policy
  denial, a node that errors (replan or halt per the runtime), resource-bound
  breach, unverified/stale snapshot binding. No fabricated success.
• No network activity after preparation; no remote planning/execution endpoint
  (FR-008).
• Checked-in browser E2E: one discovered-and-executed success + one fail-closed
  rejection, against a deterministic pinned snapshot fixture.
• discover-truthfulness updated: real-discovered claims include execution only
  where it actually happened; no claim exceeds Spec 1277.
• PR references traverse-embedder-web@0.9.0 (or later) and Spec 1277 / ADR-0062;
  documented local reproduction.

Non-goals

NL/LLM planning; auto-submit without review; multi-plan auto-selection; retiring
authored-bundle Real; re-doing Phase 1 planner/UI work (belongs on #68).

Related

• website#68 (Phase 1 — plan + review)
• traverse#1313 / PR #1315 (web composed-exec binding)
• traverse#1308 (parent web SDK release umbrella)
• Spec 1277 FR-006, Spec 109 / 1258, ADR-0062

[enricopiovesan]

Filed from the 2026-09-09 brainstorm split of #68.

• Phase 1 (plan + review): Phase 1: discover + plan + review on /discover (no execute) #68
• Decision log: Phase 1: discover + plan + review on /discover (no execute) #68 (comment)