Add a verified Vite and WebLLM consumer starter - #6
Merged
Conversation
aantenore
force-pushed
the
codex/verified-consumer-starter
branch
from
July 19, 2026 10:23
096770a to
2790222
Compare
aantenore
force-pushed
the
codex/verified-consumer-starter
branch
from
July 19, 2026 10:28
2790222 to
187c4c6
Compare
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.
What changed
Why
A reusable local-inference control plane needs a consumer that proves the public package surface, runtime identity, artifact integrity, and owner handoff work together outside the source tree.
Impact
Developers get a runnable starter that keeps prompts in the selected browser owner, fails closed when pinned artifacts drift, and demonstrates TabLoom topology selection with a real model.
Validation
pnpm check: 125/125 tests; 88.02% statement coverageResidual development risk
A low-severity advisory remains in the transitive Windows development server path of
tsup/esbuild; it is outside production dependencies and the compatible range currently declared bytsup, so this PR does not force an incompatible override.