Skip to content

test: use a local signed manifest for parachain routing - #1

Merged
firegrass merged 1 commit into
mainfrom
agent/BKLG-20261019-tzlx-proof-cli-baran-s-parachain-routing
Oct 19, 2026
Merged

firegrass merged 1 commit into
mainfrom
agent/BKLG-20261019-tzlx-proof-cli-baran-s-parachain-routing

Conversation

@firegrass

Copy link
Copy Markdown
Contributor

The parachain routing tests now serve a signed discovery manifest from loopback, so discovery can complete before each command reaches its routing assertion. Every case verifies that it fetched the fixture, preserving the existing backend and Hub-target rejection checks.

The suite uses a throwaway signer, isolates its configuration home, and cleans up the server and temporary files.

Packet: BKLG-20261019-tzlx

Validation: the workflow's proof-cli-baran.sh gate passed on commit c37a992ecf372190c1d7f4ac0c9bc8dbff36f063, tree 47b6f6546f65484a1594f5236429421a956cb84b. The published branch matches that approved commit; the worktree was clean before publication.

Packet: BKLG-20261019-tzlx

Serve a throwaway signed discovery manifest on loopback and assert each command fetches it before the existing routing rejection. Isolate SWITCHBOARD_HOME and clean up the fixture and proof file after the suite.
@firegrass
firegrass merged commit e47e6c6 into main Oct 19, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant