Ros2 Contract Guard

👁️ Observability Guard (Logs & Status)

• Structured Logs: Prefer key=value format (e.g., event=detection class=laptop).
• Startup: Every node must log its name, version, and parameter source on boot.
• Heartbeat: Nodes must publish a <node_name>/status topic with ok, state, and last_error.
• Triage: When debugging, follow the Order of Operations:
  1. Process check -> 2. Topic check -> 3. Status check -> 4. Log progression.

⛓️ Development & Verification Guard

• Docs Lookup: Always consult docs.ros.org/en/kilted/p/ for package-specific APIs, parameters, and message definitions before implementation.
• Work Units: One small change + one criterion. Build & Verify after every unit.
• Git Hygiene: Commit format milestone(<id>): <summary> (verified: <method>). Always git pull --rebase origin main before pushing to avoid conflicts.
• Status Reporting: Update STATUS.md after every change using the mandatory template.
• Strict Verification: Every milestone requires an acceptance script in scripts/. Exit 0 required.
• Completion Rule: No milestone is done until a clean build passes acceptance.
• Check-In: Ping the user for hardware/sys-config changes or verification loops.