fix-failed-paperclip-run

Topics in the source

• Fix Failed Paperclip Run
• 1. Establish the incident and the finish line
• 2. Find the first causal failure
• 3. Prove the bug before changing production code
• 4. Repair the cause and prove the safety assumptions
• 5. Verify the real workflow at the fixed revision
• 6. Deliver the PR and close the incident to the authorized endpoint

Own the failure from evidence through a tested repair and a green PR. A diagnosis, a proposed plan, a successful provider turn, and a passing unit test are intermediate results. The finish line is a verified user workflow and a PR whose current commit passes the required checks and review. Honor an explicit diagnosis-only request or a calling workflow's approval boundary. Otherwise proceed through implementation without a separate plan-approval pause. Carry forward existing authorization for merge, rollout, and recovery; do not ask again. When the assignment ends at a PR, distinguish local verification from deployment and recovery of the original task. This skill does not itself authorize merging or deploying. Start from the supplied task/run URL or failure report. Resolve these facts from available tools and records before asking the user for missing information: Instance, company, task, affected run(s), time window, and intended useful result. Current state versus state at failure; parent/child tasks and pending interactions only where they control progress. Multiple failed runs can have different causes. The code actually served, runner/provider pack versions, operating system a

This is an excerpt. Refer to the complete source and its current requirements.