Expose installable NodeAgent runtime contracts and Pi AI adapter - #2
Draft
HomenShum wants to merge 1 commit into
Draft
Expose installable NodeAgent runtime contracts and Pi AI adapter#2HomenShum wants to merge 1 commit into
HomenShum wants to merge 1 commit into
Conversation
HomenShum
added a commit
that referenced
this pull request
Jul 29, 2026
… registry lag) (#3) * ci: bump node-platform reusable-workflow pin to current main The 2026-07-20 red conformance run on PR #2 was registry lag, not a NodeAgent defect: the run predated node-platform registering the nodeagent.event-protocol and nodeagent.provider-pi concepts in ownership.yaml. Re-running the same run against today's registry passes 4/4 contract declarations (verified locally and on Actions). This bump moves the pinned reusable-workflow SHA from ef4ac8a (20 days stale) to ab7c9e69, picking up node-platform's CI gate fixes (#22/#23). The workflow interface (platform_ref, node_version) is unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> * fix(conformance): sync canonicalFor with registry-owned concepts node-platform main now registers nodeagent.event-protocol and nodeagent.provider-pi with NodeAgent as owner, so the conformance check requires them in canonicalFor. Verified locally against node-platform@ab7c9e69: PASS, 2/2 declarations classified. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> --------- Co-authored-by: Claude Fable 5 <noreply@anthropic.com>
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.
Outcome
Creates a collision-safe package boundary for NodeAgent and a real optional Pi AI provider adapter while keeping orchestration, tools, policy, durability, and receipts inside NodeAgent.
@homenshum/nodeagentnodeagent.event/v1validation aligned with NodeKitProof
npm audit --omit=dev: 0 vulnerabilitiesDependency status
The branch's own
verifyand security checks pass. The hostednode-platform / conformancecheck is expected to remain red until the canonical provider/event ownership additions in node-platform #4 land onmain; the same assembled registry passes locally.Boundaries
This does not publish npm, deploy an app, or replace the existing NodeAgent orchestration loop.