attmous

Commit-safe Rust-first dev-lane branch/SHA deploy to Raspberry Pi

Restart the active YoYoPod dev lane service on Raspberry Pi

Tail YoYoPod runtime/service logs from Raspberry Pi

Manual fallback for fetching CI Rust artifacts onto the Pi (prefer /yoyopod-deploy)

Capture a screenshot of the active YoYoPod display from Raspberry Pi

Health check for Raspberry Pi lanes, runtime, connectivity, processes, memory, recent logs

Sync a committed branch / SHA to the Raspberry Pi dev lane

Land one reviewed Sprints lane when workflow merge authority is present.

Create a focused commit for one Sprints lane after verification passes.

Sync the current lane branch with origin/main without losing local work.

Push a lane branch and create or update its pull request.

Review one Sprints pull request and return structured approval or required fixes.

Diagnose a blocked or failing Sprints lane using local state, logs, and runtime metadata.

Document lessons learned after each Sprints smoke test in playground, especially observed failures, manual recoveries, product gaps, and follow-up hardening work, by writing a concise Markdown note under docs/lessons_learned.

Run a fresh Sprints smoke test for playground by syncing main, reinstalling the Sprints plugin, selecting the workflow root, applying the active workflow contract, starting managed daemons, creating or selecting a smoke issue, and observing until completion or operator attention.

Clean the playground repository before a fresh Sprints smoke test by stopping active Sprints daemons, closing open playground PRs, and removing active workflow labels from open issues.