Skip to content

Ship NodeKit launch factory and freeze application contracts#4

Closed
HomenShum wants to merge 13 commits into
mainfrom
codex/nodekit-launch-factory
Closed

Ship NodeKit launch factory and freeze application contracts#4
HomenShum wants to merge 13 commits into
mainfrom
codex/nodekit-launch-factory

Conversation

@HomenShum

@HomenShum HomenShum commented Jul 20, 2026

Copy link
Copy Markdown
Owner

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 create builds a runnable filesystem-first research-loop app from an empty directory.
  • nodekit adopt maps brownfield repositories additively without replacing auth, routes, CSS, schemas, or user-owned coding-agent files.
  • generated apps include NodeAgent + a real Pi provider seam, deterministic fixtures/evals, proof scripts, deployment/container configuration, and build-friction events.
  • nodekit-launch, nodekit-qa, and nodekit-present are projected into both Codex and Claude skill directories.
  • local-ready remains distinct from release-ready; live sponsor research, browser proof, and deployment cannot be inferred from local generation.

Ecosystem and presentation seams

  • registers the 14-repository active nucleus and classifies pack/adapter, consolidation, and reference-only repositories in docs/GITHUB_ECOSYSTEM_AUDIT.md.
  • records the authenticated first-100 GitHub sample honestly as a lower bound: 78 owner-authored, 22 forks, 13 private, 36 recently pushed.
  • registers NodeTasks corpus receipts, BetterPRHandoff-to-Change-Story compilation, FeatureClipStudio media evidence, NodeRoom's existing Pi adapter, and NodeSlide deck/patch packages.
  • binds the P1 Change Story, claims, Evidence Index, slide plans, source-bound NodeSlide proposal, exact application receipt, and CLI/MCP transport proof.
  • optimizes source discovery while keeping nested temporary-looking source directories fail-closed.

Exact proof

Validated implementation head: ec1d8bfe53fd205711d11cc7a1cf337f93381dd2
Receipt-bearing PR head: 2ac7bad0fe1f3a1a34522b7278d85f1ed51da618

  • npm test: 30/30
  • final hosted quality: 29718538083 — passed
  • npm run registry:check: passed
  • npm audit --omit=dev: 0 vulnerabilities
  • package dry-run: 72 files, 50.7 kB
  • assembled coordinated workspace: 13/13 repositories passed, 14/14 signatures classified, zero architecture exceptions
  • evidence graph gate resolves every claim/slide evidence ID and local path and verifies NodeSlide proposal/application/transport digest parity
  • final receipt: proof/p1-factory-rollout.json

The 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:

  • NodeSlide #5 — injectable core
  • NodeSlide #7 — controlled React surfaces
  • NodeRoom #218 — package consumer proof

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.

@HomenShum HomenShum changed the title Freeze NodeKit application, pack, and event contracts Ship NodeKit launch factory and freeze application contracts Jul 20, 2026
@HomenShum

Copy link
Copy Markdown
Owner Author

Superseded by #5, which includes the hardened presets, exact vendored runtime, identity fixes, and executable two-preset empty-directory acceptance receipt.

@HomenShum HomenShum closed this Jul 21, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant