Update to PIO Agent

{
  "description": "Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.",
  "included_files": [],
  "name": "firmware-bringup",
  "skill_md_contents": "---\nname: firmware-bringup\ndescription: Bring up a new embedded board or create a minimal working firmware project with PlatformIO. Use when setting up a new project, identifying a connected board, creating a blink or serial smoke test, verifying build/flash/boot, or confirming the board is alive.\n---\n\n# Firmware Bringup\n\n## Purpose\n\nUse this skill when the user wants to bring up a new embedded board or create a minimal working firmware project.\n\n## Safety Rules\n\n- Do not flash firmware without explicit user approval.\n- Do not erase flash unless the user explicitly asks.\n- Do not assume the serial port. Discover connected devices first.\n- Preserve logs and task IDs for debugging.\n\n## Workflow\n\n1. Inspect the exact project with `pio-agent project context --project-dir <dir>` and `pio-agent policy-status --project-dir <dir>`.\n2. Use `pio-agent devices` and `pio-agent boards` only for discovery, then run `pio-agent target-resolve` with one environment and optional explicit port.\n3. Stop if target resolution is ambiguous, unavailable, or lower-confidence than the user accepts.\n4. Initialize the project only when requested (`pio-agent init --board <id> --project-dir <dir>`), then add a minimal serial boot marker such as `BOOT_OK`.\n5. Run `pio-agent agent-validate --project-dir <dir>`, then `pio-agent agent-build-diagnose --project-dir <dir> --environment <env>` for the resolved environment.\n6. If the build succeeds, request explicit approval for `pio-agent agent-flash-monitor-verify` using the resolved binding's port and environment.\n7. After approval, flash and verify bounded runtime markers. Keep the returned task ID, log paths, and binding digest.\n8. Report build, flash, monitor, and assertion outcomes separately with one next action.\n\n## Preferred Commands\n\nUse the `pio-agent` CLI for all build, upload, monitor, and port-claim\noperations. Pass `--json` when you intend to parse the output. Do not\nsubstitute raw `pio` or `platformio` shell commands: they bypass port claims,\ntask tracking, and log spooling. See the `pio-manager` skill for full syntax.\n\nA non-zero exit means read BOTH streams. An operation that ran but failed (a\nbuild with errors) puts `success: false` on **stdout**; one that could not run\n(bad arguments, policy, a busy port) puts `errorType` on **stderr** with stdout\nempty. Capture stdout and stderr separately with `--json`.\n"
}