fix(frontend): ignore stale blueprint loads after route changes

[ai-yang]

Fixes #146

Summary

• Ignore getBlueprint() callbacks after their route ID or RPC stub has been superseded.
• Tie rendered blueprint data to the (id, rpcStub) that loaded it, so the old blueprint cannot flash during the first render of a new route.
• Clear loaded/error state at the start of each load.

Without these guards, an older request could settle after the current request and overwrite the page. The URL and action handlers would then target the new blueprint ID while the UI displayed metadata from the old blueprint.

Regression coverage

The new component tests use controlled promises to verify that:

• an A response resolving after B cannot replace B;
• the first render after changing A to B shows loading rather than A;
• a not-found B response does not leave A visible; and
• a rejected B request shows B's error without leaving A visible.

Test plan

• pnpm --filter @gadgets/workshop-frontend test — 28 test files / 140 tests passed
• pnpm --filter @gadgets/workshop-frontend types:check
• pnpm exec oxlint packages/workshop-frontend/src/BlueprintLandingPage.tsx packages/workshop-frontend/src/BlueprintLandingPage.test.tsx
• git diff --check

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[ai-yang]

I have read the CLA Document and I hereby sign the CLA

[ai-yang]

Hi maintainers — this PR was opened before the new contribution-policy workflow was added.

The production change is 23 changed lines; the deterministic regression test accounts for the remaining 238 lines. I rechecked current main, and the stale blueprint request race is still present.

Would you prefer to keep the regression test under a policy/override label, or should I revise this into a production-only patch below the 30-line automatic limit? Once you confirm the preferred scope, I can rebase onto current main, update the PR description to the current template, and rerun validation.

If the current scope is acceptable, could you also approve the pending CI and Bonk PR Review workflows when convenient?

Thank you.