Repository navigation
test: bind tailor fixture to verified skill snapshot - #76
Merged
Merged
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.
Why
Current
mainhas one deterministic backend baseline failure intest_tailor_resume_fixture_runs_ask_plan_receipts_and_workspace_on_one_run.The fixture creates a
tailor_resumeRun directly but does not persist theverified Skill snapshot / allowed tool scope. Production correctly rejects
Proposal preparation for such an unscoped Run.
Fix
Use the real
tailor_resumeregistry entry and persist:skill_idskill_versionskill_snapshot=skill.summary()This fixes the fixture rather than weakening the production authorization
boundary.
No product behavior change.