feat(reliability): consolidate CI and storage safeguards#941
Conversation
3745ac0 to
32e9dfc
Compare
32e9dfc to
58c041d
Compare
|
All required checks are green (Typecheck/test, Linux, macOS, Windows). The next consolidated IPC/SSE reliability PR is intentionally waiting on this PR so it can target develop without duplicating the packaging/storage diff. Please merge #941 before the dependent branch is retargeted. |
|
Closing this split PR to reduce review fragmentation. The branch and commits are preserved; this work will be reintroduced in a smaller consolidated PR after the current reliability baseline is merged. |
|
Closed as part of PR consolidation; no branch data was deleted. |
|
Reopened for targeted CI repair and verification; this PR remains in the active fix set. |
|
感谢这组可靠性工作。关闭当前聚合 PR 的原因是它将 CI 诊断/flake 注册、打包 smoke 修复、存储统计和清理策略混在同一变更中;当前 其余工具多数尚未接入实际工作流,存储扫描还存在符号链接/检查时序问题,因此不适合整体合入。 请按独立可交付能力基于最新 |
Problem
Packaging failures were hard to classify and the repository had multiple split storage branches that were difficult to review. The packaged smoke job also waited indefinitely for an extension guest target even when the packaged page was already running normally.
Root cause
The smoke helper had no bounded fallback when Chromium did not expose the guest target in time. Storage lifecycle behavior was split across separate PRs without a single reviewable contract.
Scope
This PR consolidates two repository reliability concerns into one maintenance change: CI/package diagnostics and bounded storage lifecycle safeguards. It does not change product runtime behavior, automatically delete user data, or add UI.
Changes
Safety
lstatis used before opening roots and child entries.Tests
Local validation on the consolidated branch:
Results:
Review performed
PR size
developNon-goals
Automatic cleanup, retention UI, backup integration, database repair, and full release-channel orchestration remain separate follow-ups.
Supersedes