ci: bump node-platform reusable-workflow pin (red conformance run was registry lag) - #3
Merged
Merged
Conversation
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>
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>
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.
Root cause of the red 2026-07-20 conformance run
The failing "Node Platform conformance" run on PR #2 was registry lag, not a NodeAgent defect. The run predated node-platform registering
nodeagent.event-protocolandnodeagent.provider-piinownership.yaml, so the checker reported them as unknown concepts and flagged the two contract declarations as stale. Those concepts are on node-platformmainnow.Proof: re-running the exact same failed run against today's registry passes — https://github.com/HomenShum/NodeAgent/actions/runs/29712393345 (now green, 4/4 contract declarations classified). Also reproduced locally with node-platform@ab7c9e69 as the registry root.
What this PR changes
Bumps the pinned reusable-workflow SHA from
ef4ac8a(20 days stale) toab7c9e69(current node-platform main), picking up the CI gate fixes from node-platform #22/#23. Workflow interface (platform_ref,node_version) is unchanged; the registry checkout still floats atmainby design.Test count check
npm test(vitest) on main: 41 passing. On the PR #2 branch: 47 passing (that PR adds 6 tests). The "41 passing tests" claim is accurate for main.🤖 Generated with Claude Code