Repository navigation
Conversation
The spike's live-server evidence — the generated snapshot query is accepted and returns exact seed counts, a like/unlike round trip lands and restores state, and an unauthenticated refusal matches the generated whitelist — was a manual run: `e2e.mjs` was invoked by no test, CI job, or `just` target, so nothing re-checked it. The harness is now the suite's fifteenth test. It boots the canonical Instagram authority in-process through `StandaloneRun` (in-memory database, rebuilt from seed, so the asserted counts are the contract's own), serves it on an ephemeral loopback port, and runs the unchanged `e2e.mjs` against it. The server is shut down through a oneshot and its task joined, so a server failure surfaces instead of being masked by a passing harness. `run_node` gains a raw variant because this harness takes `<base> <module>` rather than a trailing runtime path. Verified: `provider_gen` 15 passed, 0 ignored; fmt, clippy -D warnings, `cargo test --locked --workspace`, and the doc snippets all exit 0.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Organization UI Review profile: CHILL Plan: Pro Plus Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
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. Comment |
|
Closing without merging as part of the October 2026 Spock renewal tracked in epic #38. The work is preserved on |
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.mjssat intests/provider_runtime/invoked by no test, CI job, orjusttarget; 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:uhura/examples/instagram/backend/app.spock) in-process viaStandaloneRun— in-memory database rebuilt from seed, so the counts the harness asserts are the contract's own, never leftover state;spock_runtime::http::serveon an ephemeral loopback port — no fixed port, no collision with a dev server;e2e.mjsagainst it: seed counts, like/unlike round trip and restore, refusal-whitelist admission;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_nodegains a raw variant because this harness takes<base> <module>rather than the trailing runtime path every other harness uses.Type
test
Checklist
e2e.mjsitself unchanged — the wiring proves the recorded evidence, not a new claimTest 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_authorityin 0.44s)cargo fmt --all --check— exit 0cargo clippy --locked --workspace --all-targets -- -D warnings— exit 0cargo test --locked --workspace— exit 0node scripts/check-doc-snippets.mjs— exit 0