feat: 接入 D601 F103 v2 device-pod

skills/device-pod-cli/SKILL.md

@@ -68,6 +68,15 @@ node /app/skills/device-pod-cli/scripts/device-pod-cli.mjs profile show --pod-id
 node /app/skills/device-pod-cli/scripts/device-pod-cli.mjs health --pod-id device-pod-71-freq --api-base-url <url> --session-token <token>
 ```
 
+Start every Device Pod task or resumed context with `bootsharp` so the agent sees the current workspace tree and `AGENTS.md` through the formal REST path:
+
+```sh
+node /app/skills/device-pod-cli/scripts/device-pod-cli.mjs bootsharp --pod-id <devicePodId> --api-base-url <url> --session-token <token>
+node /app/skills/device-pod-cli/scripts/device-pod-cli.mjs <devicePodId>:workspace:/ bootsharp --api-base-url <url> --session-token <token>
+```
+
+For the D601 F103 v2 board, the registered `devicePodId` is `D601-F103-V2`; its server-side profile points to `F:\Work\D601-HWLAB`, Keil project `projects/01_baseline/Projects/MDK-ARM/atk_f103.uvprojx`, target `USART`, `C:\Keil_v5\UV4\UV4.exe`, and UART `COM9` at `115200`.
+
 Diagnose auth, grant, lease, and gateway blockers without touching local profiles:
 
 ```sh
@@ -165,6 +174,7 @@ Do not treat local files such as `.device-pod/device-pod-71-freq.json` or `DEVIC
 ## Operation Rules
 
 - Use `device-pod-cli` first for workspace, build, download, reset, UART, and debug-probe tasks.
+- After selecting a pod or resuming context, run `bootsharp --pod-id <devicePodId>` before edits, build, or download.
 - Prefer `workspace apply-patch` for source edits. Use `workspace put` only for intentional whole-file writes or new files, because it bypasses hunk-level conflict detection.
 - If apply-patch fails, read the returned `patchHint`, re-read the current file with `workspace cat` or `workspace rg`, and retry a smaller exact-context hunk before using whole-file write.
 - Do not start by calling `/app/tools/hwlab-gateway-tran.mjs`, Windows-side Keil skills, serial-monitor skills, `keil-cli.py`, or generic shell when the Device Pod REST path is available.