Prove isolated NodeSlide mount in NodeRoom#235
Merged
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Scaffold Handoff — For Your Coding Agent
Immutability CheckMode: advisory This is advisory because the check is not running in strict scaffold-repair mode. Immutable files guarded during scaffold repair:
Changed Files
Needs Adversarial Review — Do NOT Apply YetThese proposals passed the reject check but have not been approved by
Safety Boundary
Immutable files (never modify):
Scaffold files (safe to modify):
|
Changed areas: .github, artifacts, convex, docs, nodekit, scripts, src, tests, vendor. Bind the isolated component to NodeRoom authorization, prove the immutable release and mounted journey, fix the memory UI crashes, and publish camera plus CI receipts.
HomenShum
force-pushed
the
codex/nodeslide-v0.2.2-bind
branch
from
July 21, 2026 03:16
40e7430 to
20e83aa
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
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.
What changed
Why
NodeRoom previously proved the package/repository seam but did not mount the isolated Convex component under the host authorizer or carry an exact immutable install/upgrade receipt through CI. Camera dogfooding also exposed two real crashes in the memory journey: unconditional Convex hooks without a provider and a selection effect that always committed fresh state.
Trust boundary
The screenshots are deliberately classified as a local memory-room camera pass. The live deployment correctly rejected the disposable unauthenticated sample with
production_identity_required; no identity check was bypassed. ActorProof, membership, digest binding, exact-byte acceptance, replay rejection, durable proposal acceptance, reload, presenter/PPTX, and credential-free receipt claims come from the deterministic Convex/repository/component journeys.Validation
npm run nodeslide:mounted:release:proofagainst exact NodeSlidea88fb57f111db82e9334d68fa7611a51ed54c3c1— PASS; 11 assets, six runtime packages, fresh isolated component and full journey.v0.2.2— immutable; annotated tag objectec4870300e1ad7ddd74209aada3a47a26779b4bb; public proof run29787121559succeeded on the exact producer SHA.npm run prod:gate— PASS; zero production dependency vulnerabilities; 367 files / 2,548 tests; product-memory, build, and post-build security scan green.npm run nodeagent:frame:smoke— PASS.npm run omnigent:nodeagent:smoke— PASS (outer optional Omnigent CLI is not installed locally).