diff --git a/AGENTS.md b/AGENTS.md index df1b546..4836588 100644 --- a/AGENTS.md +++ b/AGENTS.md @@ -44,7 +44,7 @@ gh project item-list 2 --owner traverse-framework --format json --limit 300 \ | `two-app-reuse-execute-ci` | **Done** (#287) | Fixture-only evidence (no Traverse core examples) | | `pin-ci-traverse-0-10` | **Done** (#292) | CI / embedder / runtime.wasm → Traverse v0.10.0 | | `llm-mcp-0-10-live-cutover` | **Done** (absorbed) | Mode A → `llm-mcp-traverse-starter-catalog`; Mode B → `llm-mcp-embedded-host` Future; pin already #292 | -| `two-app-reuse-host-execute` | **Blocked** | Traverse Project 1 ticket `bundle-embedder-wasi-proc-exit-success` (issue #1240) — BundleEmbedder still fails WASI `proc_exit(0)` on 1.3.2 | +| `two-app-reuse-host-execute` | **Blocked** | #1240/#1255 fixed on Traverse **main** (`ff50bbc`); App-Refs pin **v0.10.0** still fails (`registered artifact execution failed`). Need a Traverse release tag containing #1255, then pin bump | | `two-app-reuse-lifecycle` | **Done** (#283) | Fixture pin-flip + documented deprecation for meeting-notes + loop (not BundleEmbedder; not production release-train) | Full gap table + wave notes: [`docs/production-reference-plan.md`](docs/production-reference-plan.md). diff --git a/docs/decision-log.md b/docs/decision-log.md index 9a0380a..9b2a65b 100644 --- a/docs/decision-log.md +++ b/docs/decision-log.md @@ -708,3 +708,25 @@ Append-only record of design decisions for App-References. Newest sessions at th **Decision:** Move ticket Ready → claim → wire `mode-a/prepare.sh` + `serve.sh` to `TRAVERSE_MCP_REGISTRY_CACHE`; capture evidence for `core.normalize-participants` (App-Refs Loop WF1 kit). **Why:** Spec 119 host is merged; App-Refs DoD is consumer evidence + docs, not waiting on the next Traverse tag. Expedition without the cache env remains non-happy-path. + + +--- + +## 2026-09-07 — `two-app-reuse-host-execute` premature Ready → re-Blocked + +**Context:** Board hygiene moved `two-app-reuse-host-execute` Ready because Traverse #1240 closed. Ops claimed it; App-Refs still pins `traverse-embedder` / CI at tag **v0.10.0**. + +### Is #1240 closed enough to implement? + +**Question:** Can host-execute DoD be satisfied on the current App-Refs pin? + +**Options considered:** +- Implement against v0.10.0 — pros: no pin churn; cons: empirically still `registered artifact execution failed` on `meeting-notes-cli` +- Pin App-Refs to Traverse main / `ff50bbc` (#1255) now — pros: unblocks host proof today; cons: breaks single-tag pin discipline from `pin-ci-traverse-0-10` +- Re-Block until a Traverse release tag contains #1255, then pin bump — pros: honest pin + ticket DoD ("if v0.10.0 still fails, stay Blocked"); cons: Ready empty until release + +**Recommendation:** Re-Block until a tagged Traverse release includes #1255 (or Enrico explicitly authorizes a commit/main pin). + +**Decision:** Re-Block on Project 2; do not ship host-execute evidence against v0.10.0; ask Enrico release-vs-commit-pin. + +**Why:** Ticket Blocked-by text forbids wrapping WASM; fix is on main only (`ff50bbc` / PR #1255), not in tagged v0.10.0. diff --git a/docs/two-app-reuse-contract.md b/docs/two-app-reuse-contract.md index 81cd227..9a48d9f 100644 --- a/docs/two-app-reuse-contract.md +++ b/docs/two-app-reuse-contract.md @@ -91,7 +91,7 @@ bash scripts/ci/two_app_reuse_execute.sh `two_app_reuse_execute.sh` prepares both dest trees from the published 1.3.2 fixture only (no `$TRAVERSE_REPO` example trees — CI pins Traverse v0.10.0; evidence stays fixture-only). It then executes those bytes with wasmtime. -Host CLI execute via public `BundleEmbedder` (`meeting-notes-cli` / `loop-cli`) is ticket `two-app-reuse-host-execute`. Verified against Traverse **v0.10.0**: wasmtime succeeds on the same 1.3.2 bytes, but BundleEmbedder still returns `registered artifact execution failed` for this WASI `proc_exit(0)` agent — tracked upstream as Traverse Project 1 ticket-id `bundle-embedder-wasi-proc-exit-success` (issue [#1240](https://github.com/traverse-framework/traverse/issues/1240) on [Project 1](https://github.com/orgs/traverse-framework/projects/1)). Do not wrap the agent or invent substitute WASM in App-Refs. +Host CLI execute via public `BundleEmbedder` (`meeting-notes-cli` / `loop-cli`) is ticket `two-app-reuse-host-execute` (**Blocked** on Project 2). Upstream Traverse [#1240](https://github.com/traverse-framework/traverse/issues/1240) / [#1255](https://github.com/traverse-framework/Traverse/pull/1255) fixed WASI `proc_exit(0)` on **main** (`ff50bbc`), but App-Refs still pins **v0.10.0**. Re-verified on that pin: wasmtime succeeds on published 1.3.2 bytes; `meeting-notes-cli` BundleEmbedder still returns `registered artifact execution failed`. Unblock path: Traverse release tag containing #1255 → App-Refs pin bump → claim host-execute. Do not wrap the agent or invent substitute WASM in App-Refs. ## Downstream @@ -99,7 +99,7 @@ Host CLI execute via public `BundleEmbedder` (`meeting-notes-cli` / `loop-cli`) |---|---| | `#286` `two-app-reuse-execute` | Align meeting-notes pin; execute both apps; publish digest-equal evidence (Done) | | `#287` `two-app-reuse-execute-ci` | Fixture-only CI evidence (Done) | -| `two-app-reuse-host-execute` | Public BundleEmbedder CLI execute — Blocked on Traverse Project 1 ticket-id `bundle-embedder-wasi-proc-exit-success` | +| `two-app-reuse-host-execute` | Public BundleEmbedder CLI execute — **Blocked** until App-Refs pin includes Traverse #1255 (not in tagged v0.10.0) | | `#283` `two-app-reuse-lifecycle` | Fixture pin-flip + documented deprecation for the same pair (Done — fixture-only; **not** production release-train; **not** BundleEmbedder). See below and `docs/decision-log.md` 2026-09-05 | ## Lifecycle (fixture-only) — `two-app-reuse-lifecycle`