feat: expand multi-harness support for 1.6 - #45
Draft
paladini wants to merge 1 commit into
Draft
Conversation
|
Hey @paladini, do you have an estimate for when this PR might be ready to merge? I'm planning to collaborate by adding a Codex plugin, and since this PR is expanding the multi-harness support, I would prefer to build on top of it, to avoid any conflicts. |
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
Compatibility and release scope
.agents/skillsas scoreable but vendor-neutral, avoiding inflated detected-tool countsAGENTS.override.mdbecause it is a local override rather than a portable repository signalValidation
npm run test:coverage: 21 files, 310 tests passed, 96.39% statement coveragenpm run check:types -w harness-scorenpm run plugins:sync-checknpm run docs:buildnpm run lint: 0 errors; 18 pre-existing CSS warnings in untouched filesnpm run scan: L4, 108/108, 100%git diff --checkCloses #44