From a851e47eca020d11dc2d2dc9408ee9dfceb40b8f Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?=E9=98=BF=E7=99=BD=E5=8F=94?= <11794527+absfan@user.noreply.gitee.com> Date: Tue, 27 Oct 2026 18:15:00 +0800 Subject: [PATCH] docs: record verified iCDB recovery trial and delivery scope --- ...-27-icdb-failure-lifecycle-and-recovery.md | 15 ++++++++ .../plans/2026-10-27-icdb-failure-recovery.md | 38 ++++++++++--------- 2 files changed, 36 insertions(+), 17 deletions(-) diff --git a/docs/releases/2026-10-27-icdb-failure-lifecycle-and-recovery.md b/docs/releases/2026-10-27-icdb-failure-lifecycle-and-recovery.md index 50647d0..2dc3acc 100644 --- a/docs/releases/2026-10-27-icdb-failure-lifecycle-and-recovery.md +++ b/docs/releases/2026-10-27-icdb-failure-lifecycle-and-recovery.md @@ -75,6 +75,13 @@ ZIP、原生进程正常退出及地址释放。满足后只重试一次完整 - 原生 Repair 模块真实执行:完整备份、Repair 确认、本 PID 的 dbcheck/ 数据库关闭日志、Project Repair ZIP 校验齐全,最终 `REPAIRED`、退出码 0。 这验证了原生恢复链,不代表复现并恢复了现场同一个 dirty session。 +- 完整自动恢复链:向隔离副本的首次校验注入合成失联错误,之后实际执行 + 正常关闭、完整备份和原生 Repair,再启动第二次真实校验,最终 + PASS/GREEN、`safe_to_continue=True`。只启动两次校验 worker、一次 Repair; + 原错误及 evidence 保留。没有故意破坏数据库,也没有恢复现场损坏库。 +- PyInstaller 目录包构建和冻结 GUI 生命周期冒烟通过;直接使用生成的 EXE + 在另一个独立工程副本上运行 Repair worker,最终 `REPAIRED`、退出码 0。 + 因此原生修复入口也已验证能在冻结包内工作。 - 原样本 21,011 个文件在上述试验前后 SHA-256 内容指纹一致。 - 最终 Python 全量回归 **448 项通过**(含前次 417 项基线);仍有基线已有的 一条 pywinauto STA COM 模式提示。两组 PowerShell 测试、编译和 Git 空白检查通过。 @@ -82,3 +89,11 @@ ZIP、原生进程正常退出及地址释放。满足后只重试一次完整 父进程丢失、共享 COM 应用退出等边界均已修正,并补充对应回归。 本地原始证据位于 `diagnostics/icdb-auto-recovery-20261027`,不随包发布。 + +## 分支试用包 + +本地 `CbbRefreshVerify-icdb-recovery-20261027.zip` 包含完整目录程序、试用说明、 +本报告和逐文件 SHA-256 构建清单;压缩包旁另有 SHA-256 文件。源码构建提交为 +`9cd4968`,版本号仍为 `0.2.2b1`,这是分支修复试用包,不是新正式版本。 +解压整个目录后启动 `CbbRefreshVerify.exe`,必须保留 `_internal`。尚未部署到 +200091-CBB,也未推送远端;现场已有共享库损坏仍受上述原生入口限制。 diff --git a/docs/superpowers/plans/2026-10-27-icdb-failure-recovery.md b/docs/superpowers/plans/2026-10-27-icdb-failure-recovery.md index a17d9ce..424b00a 100644 --- a/docs/superpowers/plans/2026-10-27-icdb-failure-recovery.md +++ b/docs/superpowers/plans/2026-10-27-icdb-failure-recovery.md @@ -10,29 +10,33 @@ ## Task 1 — Retain native owners on content timeout -- [ ] Add a regression that starts a harmless importer with a harmless child, times out, and checks both survive until normal exit or test cleanup. -- [ ] Add a content-timeout batch regression proving the second item does not start. -- [ ] Remove tree/client termination from `_run_process` timeout; retain/drain the process in a background observer, record PID/command/release in evidence, and return TIMEOUT with `safe_to_continue=False`. -- [ ] Verify targeted tests and the existing content-check tests. +- [x] Add a regression that starts a harmless importer with a harmless child, times out, and checks both survive until normal exit or test cleanup. +- [x] Add a content-timeout batch regression proving the second item does not start. +- [x] Remove tree/client termination from `_run_process` timeout; retain/drain the process in a background observer, record PID/command/release in evidence, and return TIMEOUT with `safe_to_continue=False`. +- [x] Verify targeted tests and the existing content-check tests. ## Task 2 — Normal close of failed owned sessions -- [ ] Add x86 cscript harness tests for failed Save and close-only operation, checking `Close(False)`, reference release and Quit, with failure status preserved and mismatched identity untouched. -- [ ] Implement an identity-checked close helper and call it only after the worker has returned from its native call and released Python references. Retain busy helpers instead of terminating them. -- [ ] Add cooperative cancellation at Python/VBS native-operation boundaries; a supervisor timeout/crash must not terminate a pending native Save. -- [ ] Add targeted tests for cancel before Save, cancel after a pending call returns, supervisor loss and blocked native-call retention. -- [ ] Check shared `SymbolLibs/__ReusableBlocksSymb` ownership as well as Work/PCB database ownership before writing and before declaring release. -- [ ] Give the status reader an EOF shutdown grace period before any fallback termination. +- [x] Add x86 cscript harness tests for failed Save and close-only operation, checking `Close(False)`, reference release and Quit, with failure status preserved and mismatched identity untouched. +- [x] Implement an identity-checked close helper and call it only after the worker has returned from its native call and released Python references. Retain busy helpers instead of terminating them. +- [x] Add cooperative cancellation at Python/VBS native-operation boundaries; a supervisor timeout/crash must not terminate a pending native Save. +- [x] Add targeted tests for cancel before Save, cancel after a pending call returns, supervisor loss and blocked native-call retention. +- [x] Check shared `SymbolLibs/__ReusableBlocksSymb` ownership as well as Work/PCB database ownership before writing and before declaring release. +- [x] Give the status reader an EOF shutdown grace period before any fallback termination. ## Task 3 — Attempt official native recovery -- [ ] Probe native UI on new isolated copies only; record accepted project/database identity, exact command, backup creation and completion signals. Do not invent CLI Repair flags or manipulate native ownership metadata. -- [ ] Add recovery-policy tests: reject foreign/unresolved targets, active clients, inconsistent backups and repeat repair; preserve the original error; at most one recovery attempt. -- [ ] Implement the supported native repair route with a complete backup and exact target checks. If the installed native tool cannot accept a shared symbol database, retain that explicit blocked result instead of repairing an unrelated Work project. -- [ ] Retry opening/verifying only after native success and confirmed release; authoritative READY remains the success criterion. +- [x] Probe native UI on new isolated copies only; record accepted project/database identity, exact command, backup creation and completion signals. Do not invent CLI Repair flags or manipulate native ownership metadata. +- [x] Add recovery-policy tests: reject foreign/unresolved targets, active clients, inconsistent backups and repeat repair; preserve the original error; at most one recovery attempt. +- [x] Implement the supported native repair route with a complete backup and exact target checks. If the installed native tool cannot accept a shared symbol database, retain that explicit blocked result instead of repairing an unrelated Work project. +- [x] Retry opening/verifying only after native success and confirmed release; authoritative READY remains the success criterion. ## Validation and delivery -- [ ] Run full Python and PowerShell regressions, compilation and whitespace checks, plus independent code review. -- [ ] Verify a successful native run and a controlled failed integration/close on an isolated library, and source fingerprints afterward. -- [ ] Record precisely which recovery target types were actually exercised and any remaining field-only limitations; commit changes on the current branch. +- [x] Run full Python and PowerShell regressions, compilation and whitespace checks, plus independent code review. +- [x] Verify a successful native run and a controlled failed integration/close on an isolated library, and source fingerprints afterward. +- [x] Record precisely which recovery target types were actually exercised and any remaining field-only limitations; commit changes on the current branch. + +## Execution evidence + +Completed on 2026-10-27. See `docs/releases/2026-10-27-icdb-failure-lifecycle-and-recovery.md` for 448 passing Python regressions, PowerShell and x86 harness checks, real failed-session close, real native Repair, the synthetic-error/real-repair/real-retry chain, frozen EXE Repair validation, and trial-package scope. Shared symbol databases without a supported PRJ entry remain explicitly unsupported; no field database was repaired.