feat(skills): add reply-router#196
Open
tttt28444 wants to merge 1 commit into
Open
Conversation
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.
Adds the reply-router runx skill for Frantic bounty #70.\n\nWhat changed:\n- Adds a public reply-router skill with typed route_reply inputs and outputs.\n- Covers unsubscribe suppression packet, interested routing packet, and ambiguous/unsealed needs_agent behavior in inline harness cases.\n- Includes evidence, verification, and report artifacts under skills/reply-router.\n\nVerification:\n- npx.cmd -y @runxhq/cli@0.6.14 --version -> runx-cli 0.6.14\n- npx.cmd -y @runxhq/cli@0.6.14 skill inspect ./skills/reply-router route_reply --json -> status ok\n- npx.cmd -y @runxhq/cli@0.6.14 harness ./skills/reply-router --json is blocked on this Windows host by sealed receipt store os error 87 during directory fsync.\n- registry publish is blocked by the same local Windows harness error before upload.\n\nFrantic claim: 3a9f6f23-1ebb-4dfa-97e8-be7d7f2f3d6f