feat(discover): migrate the generate panel to traverse-embedder-web 0.14 registerPackage (#139) - #140
Open
enricopiovesan wants to merge 1 commit into
Open
enricopiovesan wants to merge 1 commit into
enricopiovesan wants to merge 1 commit into
Conversation
….14 registerPackage (#139) - pin traverse-embedder-web ^0.14.0 (npm 0.14.0) - discover-generate admits fixture.responder@1.0.0 through registerPackage with its real signed manifest bytes and detached Ed25519 signature, trusting only Traverse's labelled test-only fixture key; the pin digest is now the SHA-256 of the signed manifest (wasm digest unchanged) - tests assert both digests against the traverse fixture and that insertVerified is gone - embedder-pin Q&A and llms.txt updated: the ^0.13.0 sentence is no longer true Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
This migrates the public website from
traverse-embedder-web@^0.13.0to^0.14.0(npm0.14.0, lockstep with Traverse v0.14.0). It moves the/discovergenerate panel onto the 0.14 signed admission path. Closes #139.src/scripts/discover-generate.jsadmits thefixture.responder@1.0.0conformance fixture throughregisterPackage(manifestBytes, wasm, signatureBytes). It embeds the real signed package files fromtraverse-framework/traversefixtures/models/fixture-responder-1.0.0/: the exactmodel.manifest.jsonbytes and the detached Ed25519model.sig.json, next to the same 491-bytemodel.wasmit already embedded."hi there", otherwise"hmm"), still described as not a trained language model.tests/discover-generate.test.mjs): the WASM digest still equals the Traverse fixture'swasm_digest(bf04760b…), and the pin digest equals the SHA-256 of its signed manifest (50b74bd3…). A new test asserts admission viaregisterPackagewith noinsertVerifiedleft.^0.13.0" and that/discover"still usesinsertVerified". Both are false after this change, so the page and itsllms.txtentry now describe the 0.14 pin and signed admission, and keep the "the site can lag future releases; pin published packages" guidance. Dated blog posts are historical snapshots and are unchanged.Honesty locks
Test plan
npm ls traverse-embedder-webreports0.14.0npm test: 11/11 pass, including real signed admission and execution in Nodenpx playwright test tests/e2e: 6/6 pass against the built site. Run locally on a static server on port 4399, because another session's Astro preview held port 4321; the repo's Playwright config is unchanged.npm run buildsucceeds/discovergenerate panel runs on 0.14 after deploy🤖 Generated with Claude Code