Ship NodeKit launch factory and freeze application contracts#4
Closed
HomenShum wants to merge 13 commits into
Closed
Ship NodeKit launch factory and freeze application contracts#4HomenShum wants to merge 13 commits into
HomenShum wants to merge 13 commits into
Conversation
This was referenced Jul 20, 2026
This was referenced Jul 20, 2026
This was referenced Jul 20, 2026
Owner
Author
|
Superseded by #5, which includes the hardened presets, exact vendored runtime, identity fixes, and executable two-preset empty-directory acceptance receipt. |
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.
Outcome
Ships the executable NodeKit launch/adoption factory and turns the GitHub portfolio into one contract-governed, evidence-bound ecosystem.
Factory and authored-agent standard
nodekit createbuilds a runnable filesystem-first research-loop app from an empty directory.nodekit adoptmaps brownfield repositories additively without replacing auth, routes, CSS, schemas, or user-owned coding-agent files.nodekit-launch,nodekit-qa, andnodekit-presentare projected into both Codex and Claude skill directories.local-readyremains distinct fromrelease-ready; live sponsor research, browser proof, and deployment cannot be inferred from local generation.Ecosystem and presentation seams
docs/GITHUB_ECOSYSTEM_AUDIT.md.Exact proof
Validated implementation head:
ec1d8bfe53fd205711d11cc7a1cf337f93381dd2Receipt-bearing PR head:
2ac7bad0fe1f3a1a34522b7278d85f1ed51da618npm test: 30/30npm run registry:check: passednpm audit --omit=dev: 0 vulnerabilitiesproof/p1-factory-rollout.jsonThe neighboring default-checkout audit is intentionally not treated as authoritative: several repositories are absent or on stale/default heads. The passing coordinated audit uses the exact reviewed PR heads. Audit timing varied from 14.59s to 69.8s and is not presented as an under-30 guarantee.
Cross-repository state
Merged foundations observed during this rollout:
Open review seams include NodeAgent #2, NodeSlide #10, NodeProof #22, NodeTrace #3, NodeMem #3, NodeRoom #219, NodeBenchAI #592, NodeVoice #4, NodeVideo #30, NodeTasks #1, BetterPRHandoff #4, and FeatureClipStudio #4. NodeBenchAI #592 has all 16 hosted checks green. NodeAgent, NodeTrace, NodeMem, and NodeRoom #219 have green repository-local checks but their hosted central-conformance job correctly waits for this registry change to reach
node-platform/main.Timing and release boundary
Observed local-ready runs ranged from 17.72s to 36.37s; the pnpm sample took 31.86s, with 29.5s in dependency installation. The under-30 goal is therefore not repeatably certified.
No npm package was published. No production deployment, paid-resource activation, destructive migration, remaining PR merge, public release, PPTX export/reopen certification, or fresh-judge live hackathon certification was performed.