Repository navigation
feat(skills): add staging-io skill for WPC staging folder I/O - #229
Merged
Merged
Conversation
…ubfolders, seq+retry fixes
- seq regex now rejects 00, matching the stated 01-99 range and README.txt - note that a retryNN reply carries no out/err marker, so its content is read to judge the re-run outcome
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
staging-ioskill: prose instructions for the plain-text hand-carry lanes atagent-staging\between the personal device (where Conditional Access blocks Azure DevOps) and the work PC. It mirrors theREADME.txt/INBOUND-SAFETY.txtcontract at the staging root and adds no wrapper script, CLI, or daemon.Covers writing to
agent-outputs\, reading replies fromagent-inputs\, the initiative-subfolder layout, naming and header conventions, redaction guardrails, and the close-out archive triage.Reviewed with quick-review (folded reviewer plus Codex as a cross-model second opinion); all findings were LOW/CLEANUP. Two were applied on top of the original three commits:
00, matching the stated01-99range and the staging README.retryNNreply has noout/errmarker, so its content is read to judge the re-run outcome.Refs #227.