远程日志系统基本运行成功

AGENTS.md

@@ -105,24 +105,24 @@ Additional enforcement rules:
 ## Build, Flash, and Validation
 
 - Use the ESP-IDF/toolchain version declared by the project documentation or lockfiles.
-- Activate ESP-IDF v5.5.3 before building.
+- Activate ESP-IDF v5.5.4 before building.
 - Before running any `idf.py` command, first determine which activation style exists in the current environment:
   - Prefer path expressions that are portable across developer machines. Avoid hardcoded user-specific absolute paths such as `/home/<user>/...` or `/Users/<user>/...` in docs, scripts, and shell snippets when a variable-based form is sufficient.
   - For POSIX shells, prefer parameterized paths such as:
     ```bash
     export ESPRESSIF_ROOT="${ESPRESSIF_ROOT:-$HOME/.espressif}"
-    export IDF_VERSION_TAG="v5.5.3"
+    export IDF_VERSION_TAG="v5.5.4"
     ```
   - If `eim` exists on the current machine, prefer running ESP-IDF commands through `eim run`, for example:
     ```bash
     eim run <COMMAND> [IDF_VERSION]
-    eim run "idf.py build" v5.5.3
+    eim run "idf.py build" v5.5.4
     eim run "idf.py --version"
     ```
   - In sandboxed or other write-restricted environments, `eim` logging initialization may fail if the default user state/log directories are not writable. In that case, pass `--log-file` with a writable path, for example:
     ```bash
-    eim --log-file ./eim-build.log run "idf.py build" v5.5.3
-    eim --log-file /tmp/eim.log run "idf.py --version" v5.5.3
+    eim --log-file ./eim-build.log run "idf.py build" v5.5.4
+    eim --log-file /tmp/eim.log run "idf.py --version" v5.5.4
     ```
   - If `eim` does not exist, prefer the newer EIM-managed activation script when available:
     ```bash