test(provider-gen): wire the live-authority evidence into the suite

[k08200]

Summary

Stacked on #34 → #33 → #29. Closes the last unwired evidence claim in gridaco/uhura#29.

That issue's live-server evidence — snapshot query accepted with exact seed counts, like/unlike round trip restoring state, unauthenticated refusal matching the generated whitelist — was a manual run. e2e.mjs sat in tests/provider_runtime/ invoked by no test, CI job, or just target; the issue body has carried a "not reproducible from the repository as it stands" qualifier since 2026-07-26.

Now it is the suite's fifteenth test, generated_tables_drive_a_live_authority:

• boots the canonical Instagram authority (uhura/examples/instagram/backend/app.spock) in-process via StandaloneRun — in-memory database rebuilt from seed, so the counts the harness asserts are the contract's own, never leftover state;
• serves it with spock_runtime::http::serve on an ephemeral loopback port — no fixed port, no collision with a dev server;
• runs the unchanged e2e.mjs against it: seed counts, like/unlike round trip and restore, refusal-whitelist admission;
• shuts the server down through a oneshot and joins its task, so a server-side failure fails the test instead of hiding behind a passing harness.

No #[ignore]: CI's test job already builds the Uhura provider bundle and has node, so this runs on every push (0.4s locally).

run_node gains a raw variant because this harness takes <base> <module> rather than the trailing runtime path every other harness uses.

Type

test

Checklist

• e2e.mjs itself unchanged — the wiring proves the recorded evidence, not a new claim
• Ephemeral port + in-memory DB — parallel-safe, no shared state
• Server failure surfaces (task joined, result asserted)
• Draft: stacked on refactor(provider-gen): name the declaration after what it declares #34/fix(provider-gen): make the shared runtime app-independent #33/spike: spock gen provider — assembly-layer tables from the contract #29; scope direction for the track is pending in RFD: the assembly layer between the Spock contract and an app uhura#29

Test plan

On the pinned toolchain (1.92.0) and node 24.18.0, after pnpm -C uhura/web build:provider:

• cargo test --locked -p spock-cli --test provider_gen — 15 passed, 0 failed, 0 ignored (generated_tables_drive_a_live_authority in 0.44s)
• cargo fmt --all --check — exit 0
• cargo clippy --locked --workspace --all-targets -- -D warnings — exit 0
• cargo test --locked --workspace — exit 0
• node scripts/check-doc-snippets.mjs — exit 0

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spock	Ready	Preview	Aug 1, 2026 12:05am

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 2656b686-d7b7-4353-87e8-bd0280530ab1

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}