Skip to content

Commit b26de27

Browse files
docs: reconcile the smoke-campaign verifications
Flip the standalone repo's headline claim to verified: bootstrap + five-act walkthrough green on a fresh Fedora 44 host, 2026-07-04/05, twice (in-order and shuffled suite). Add verified rows for the full demo-script suite and for order independence via restore-baseline.sh, each with the campaign's caveats and fix range (5403d06..e22b318). Add one new unverified row for the gap the campaign exposed: the README prerequisites section doesn't list the legacy iptables kernel modules or the minimum minikube version a fresh host needs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 parent 158a276 commit b26de27

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

‎_plans/reconciliation.md‎

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -15,4 +15,7 @@ The historical reconciliation rows from the capstone era are preserved in
1515

1616
| Status | Claim | Where | Verification |
1717
|---|---|---|---|
18-
| **unverified** | This repo's `examples/lgtm-datamesh/` tree builds and runs the data-mesh reference end to end, producing the same five-act walkthrough verified in the parent repo as of r28 | `examples/lgtm-datamesh/` | Cluster-verifiable: from a fresh minikube profile, `./scripts/bootstrap-capstone.sh` followed by `./demos/walkthrough.sh` should produce 5/5 acts green. (Same verification procedure as the parent repo's r28.) |
18+
| **verified** | This repo's `examples/lgtm-datamesh/` tree builds and runs the data-mesh reference end to end, producing the same five-act walkthrough verified in the parent repo as of r28 | `examples/lgtm-datamesh/` | Verified 2026-07-04/05 on a fresh Fedora 44 host (rootless podman, minikube 1.38.1, fresh `capstone` profile): `./scripts/bootstrap-capstone.sh` then `./demos/walkthrough.sh` → 5/5 acts green, twice (once in-order, once in the shuffled suite). Caveats that verification surfaced and this repo fixed: six demo-script bugs (`5403d06`–`e22b318`), plus two host prerequisites the README didn't list — legacy `ip_tables`/`iptable_nat` kernel modules loaded on the host (Fedora is nftables-only; the rootless node can't modprobe), and minikube ≥ 1.36 (1.35's registry addon pins a dead `kube-registry-proxy` digest). |
19+
| **verified** | Every demo script passes against the bootstrapped stack: all 19 `demos/smoke-*.sh`, the `demo-canary.sh` cycle (up 90/10 → shift 50/50 → down), and the `demo-add-data-product.sh` cycle (up → down) | `examples/lgtm-datamesh/demos/` | Verified 2026-07-04/05, same host: two full-suite runs (24 scripted invocations each) green, with fixes landed and re-verified between them. Fix verification exercised the failure paths live (dead-tunnel port-forward re-attach, gateway wake from scale-to-zero, interceptor cold-start 502 retry). |
20+
| **verified** | The smokes are order-independent when `scripts/restore-baseline.sh` is run between groups (the smokes' pass-cleanup, CAP-008, otherwise couples them) | `examples/lgtm-datamesh/scripts/restore-baseline.sh` | Verified 2026-07-05: full suite re-run in a deliberately shuffled order (gateway-heavy first, `smoke-order` immediately after the cleanup-happy group — its prior failure position) with `restore-baseline.sh` between groups → all green. The shuffle also exposed one latent race (`smoke-kafka`, fixed in `e22b318`) that two in-order runs had passed on timing. |
21+
| **unverified** | `README.md`'s "Prerequisites (verified configuration)" section is sufficient for a fresh-host bring-up | `examples/lgtm-datamesh/README.md` | Known gap from the 2026-07 campaign: the section does not list the legacy iptables kernel modules or the minimum minikube version (see the caveats on the first row). Prose update pending; until then the bootstrap fails at tier 1 on a stock Fedora host and the fix commands live in the failure output and LESSONS-LEARNED. |

0 commit comments

Comments
 (0)