lawnberry_pi

Use for LawnBerry Pi simulation vs real-hardware validation. Covers SIM_MODE selection, .env and config checks, simulation-safe test-first workflow, hardware preflight expectations, and avoiding false claims that local success proves on-device behavior.

Use for improving LawnBerry Pi AI result quality without breaking the existing backend contract. Covers ai_service review, model artifact or rule improvement, conservative evaluation, performance notes, and avoiding premature accelerator-specific churn.

Review regression-sensitive LawnBerry Pi manual control and camera paths: RoboHAT USB handoff, watchdog feeding, motor authorization, joystick responsiveness, MJPEG and snapshot fallback, camera ownership, and stream backpressure handling.

Keep LawnBerry Pi maintainer documentation synchronized with implementation. Use when runtime behavior, supported hardware scope, subsystem maturity, immediate focus, two-week plan, release notes, or callable interfaces have changed and docs must be updated in the same pass.

Use when returning to LawnBerry Pi after time away, starting substantial maintenance, or needing a fast project re-entry workflow. Covers docs to read first, runtime ports, hardware baseline, simulation vs hardware mode, important files by task, and validation planning.

Use when a LawnBerry Pi task spans re-entry, specialist routing, implementation, documentation sync, and validation. Covers choosing the right specialist workflow and sequencing investigation, changes, doc updates, and test planning.

Use for LawnBerry Pi mission persistence and recovery work. Covers what mission state should survive restart, safe restart semantics, paused vs running recovery behavior, lifecycle validation, and persistence-backed tests.

Use for LawnBerry Pi navigation hardening work: feedback audit, waypoint progress validation, stop and fault behavior, obstacle gating, interrupted traversal handling, and targeted regression coverage in navigation and mission flows.

Use for LawnBerry Pi runtime contract work that starts with drift audit and ends with aligned docs, config, scripts, service definitions, and targeted validation. Covers ports, startup behavior, proxies, systemd units, and maintainer-facing runtime guidance.

Audit LawnBerry Pi runtime contract drift across ports, startup behavior, systemd units, frontend proxies, docs, scripts, and config. Use for port mismatches, startup confusion, README vs runtime checks, and source-of-truth comparison work.

Use for delivering a LawnBerry Pi code change with re-entry, scoped investigation, safe implementation, maintainer doc sync, and targeted validation. Covers general backend/frontend work plus hardware-aware guardrails when the change is safety sensitive.

Use for coordinating a LawnBerry Pi hardening pass across high-risk subsystems such as navigation, mission recovery, manual control/camera, and AI quality. Covers routing to the right hardening skill, sequencing focused changes, and keeping validation and docs aligned.