docs: display ccc-node harness names - #255
Merged
Merged
Conversation
seoseo-ai
approved these changes
Jul 1, 2026
seoseo-ai
left a comment
Collaborator
There was a problem hiding this comment.
Approved after local adapter/round validation, round plan display check, live-runner fixture, npm test, and green GitHub Validate check. Display-only; no live operations.
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.
Summary
Use the named ccc-node roster in Agent Olympics operator-facing displays instead of showing the generic
ccc-node-harnesslabel alone.docs/ccc-node-named-harnesses.mdccc-node-harnessas the schema/runtime adapter id for compatibilityVerification
node scripts/validate.js adapter-capabilitiesnode scripts/validate.js roundsnode scripts/round.js plan rounds/season-002-round-001.yamlccc-node named harness fleet (노숙/nosuk, 순욱/soonwook, 등애/dungae, 공융/gongyung, 대교/daegyo)node scripts/live-runner.js run fixtures/live-runner/round-live-runner-fixture.yaml --config fixtures/live-runner/runner-config-ccc-node-harness.yamlnpm testBoundary
Display/documentation-only change. No live node contact, Gateway/broker/bridge restart, provider send, DB action, credential movement, release, or publication.