Keep autoresearch status checks read only - #74
Merged
Merged
Conversation
Keep the shared "Installed resources" block identical across skills and tighten the status-route wording to match Procedure steps 1-3. Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Member
|
Polished on top of your commit (3d57023): restored the shared "Installed resources" block so it stays byte-identical across all 16 skills (please drop that rewrite from the other PRs too, or do it once for all skills in its own PR), and tightened the status-route wording to match Procedure steps 1–3. |
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
2 participants
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.
An autoresearch status question could enter the executable campaign workflow and mutate or initialize state. This PR adds an explicit read-only route for status and explanation requests. Start, resume, and named-stage requests continue through the existing acceptance gates, sealed holdout, and attempt budget.
The boundary follows OpenAI's Rethinking skills and prompts for GPT-6 Astra: distinguish inspection from execution and define when work is complete. It is the autoresearch slice split from #62 after review feedback and is rebased on #63, retaining optional cycle-completion notifications.
Validation
python3 scripts/validate_skills.py: 16 skills passpython3 -m pytest -q: 268 passed, 5 skippedgit diff --check: clean