Align NodeBench with frozen NodeKit v1 contracts#591
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
PR size advisoryThis PR adds 10272 lines of substantive change. CONTRIBUTING.md defines a soft limit of ~400 LOC. If the PR is genuinely cohesive (e.g. an architecture map, a generated migration, a deletion of a dead module), no action is needed. Otherwise consider:
This is advisory — it does not block the merge. |
Vercel preflight failed:
|
|
Superseded by #592. The replacement preserves this brownfield contract alignment, uses the repository-required |
Outcome
Aligns NodeBenchAI's current post-Phase-2 tree with the frozen NodeKit v1 contracts without moving runtime code or changing production behavior.
What changed
apiVersion/kind/specmanifests with canonical flatnodekit.repo/v1,nodeagent.application/v1, andnodeagent.pack/v1repo-local-nodebenchexplicitly authoritative while recordingnodeagent-nativeas the migration target.nodeagent/definition and config hash over the current 1,908-file authored surfacePolicyContextas a domain specialization, not a fork of the runtime policy contractValidation
Against the latest NodeKit v1 compiler:
ce762d645646cb409ea3e20e58517608ce921dc9262eae8aa3377847bfc4594fgit diff --check: passHonest boundary
This is contract alignment, not a runtime replacement. It does not edit the live Convex/agent loop, deploy anything, add Pi AI to production, claim a no-key application demo, or promote NodeBenchAI from the registry's
untrackedcommand profile. The clean worktree intentionally had no installed application dependencies, so the existing full app typecheck/build were not rerun for this manifest/docs/generated-metadata-only delta.