Repository navigation
Show equal practical v1 integrations across all five root demos - #13
Merged
Merged
Conversation
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
1 participant
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.
All five tools now expose practical v1 capabilities equally, alongside their full playful catalogs: measured build facts, bounded cause diagnostics, factual incident drafts, context redaction/runnable Node scopes and report-backed release policies. Supported report formats and JSON inputs/options are visible; matching commands/examples copy directly. Node-only boundaries and sample evidence are labeled.
Update actual vendored v1 pure APIs, browser bundle, versioned entry scripts and root install commands. Existing husky palette, Dallas/Benji story and candidate redirect remain. Local6 tests and jsdom interaction checks passed, including missing/failure/stale/commit/redaction paths. Merge only after npm1.0 registry verification and final site checks; then verify the root deployment in the real browser.