create-runner-adapter

Topics in the source

• Add a native Runner adapter
• Work sequence
• Rules that must survive implementation pressure

Use this skill to add a harness to the new, native Paperclip Runner execution system. Here, adapter means the provider translation and launch integration behind a Runner harness driver. Preserve existing direct adapters and historical records as compatibility constraints; do not route this work through their package-authoring recipe or migrate agents as a side effect. The complete procedure is the Runner integration playbook. Use its working templates for the release contract, capability inventory, acceptance ledger, and failure record. These repository files contain the decision rules and test criteria themselves. No private chat, task, prior campaign, or separate private repository is required. Source links identify code to inspect, not evidence that a new integration passed. If this skill was installed separately, locate the target checkout from the current workspace or git rev-parse --show-toplevel. Verify it contains packages/paperclip-runner and tests/runner-e2e; resolve doc/ paths there. Follow that checkout's AGENTS.md and scoped rules before editing. 1. Define a finite release. Read playbook sections 1–3. Record the user outcome, first environment, supported platforms, set

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