docs: record D1 deployment verification

这个提交存在于:
YokiiroBW 2026-07-27 13:23:53 +08:00
父节点 6f1a80cafd
当前提交 54b4aa297a

查看文件

@ -177,4 +177,4 @@
- Root cause: new-install defaults, the flat persisted value, and the nested `schedule_detail_config` persisted value are separate paths; startup migration can copy the nested value back over the flat one; the script also assumed a Unix developer environment.
- Fix or workaround: set all three defaults to `true`; after stopping AstrBot, deploy writes the VM JSON config before startup; Bash accepts `VM`, `SSH_KEY`, `SSH_PORT`, `PYTHON_BIN`, `SKIP_LOCAL_TESTS`, and `DETAIL_ENHANCEMENT_ENABLED`; add `ops/deploy-plugin.ps1`.
- Prevention rule: configuration switches must be checked at schema, runtime fallback, and production persistence layers; cross-machine deploy commands must make SSH and test-runtime dependencies explicit.
- Validation evidence: `tests/test_d1_default_enabled.py` and `tests/test_deploy_script_windows.py`; deployment verifies service state, logs, and persisted config.
- Validation evidence: `python -m unittest discover -s tests -q` passed 250 tests; commits `d8a5c18`, `c3d7151`, and `6f1a80c` were pushed; final VM verification found `FLAT=True`, `NESTED=True`, matching `main.py` and schema hashes, `active`, and `NRestarts=0`.