Piwork 0.0.12 Preview

Piwork 0.0.12 Preview fixes Core startup with committed SQLite data still in the WAL after shutdown or interruption.

• Validate a private snapshot of the database and WAL together before opening the live store. Recover committed state without a storage-format migration; unknown formats, versions and damaged databases still fail validation.
• Bound shutdown transaction draining and checkpoint waits by the remaining deadline. Report unconfirmed storage or final-log failures, keep installation ownership until actual cleanup, and exit nonzero when checkpoint completion cannot be confirmed.
• Preserve login sessions, installation identity and committed data on direct WAL reopen. Existing Work/Service shutdown and recovery behavior remains covered by the change's integration tests.

Linux amd64 delivery includes piwork-core and piwork-cli. All four matching production image roles are published and anonymously verified: Core, Agent, file helper and snapshot helper; package helper reuses Agent. The Docker archive contains deployment materials and pulls these images from the public registry. Browser UI remains on 17891; Core API remains on 17871.

Before upgrading, stop the previous Core and back up the entire data directory, including any remaining SQLite WAL/SHM files. Do not delete the WAL to work around this error.

Build source: 4f127751fc4805e504a1af0d7b48c02739f72489, modified=false. Input SHA256: 2fb10dd3192503035931250511779ccf87bec9f759eaabe07fc6d35558f4d8f8. The release tag also includes the later distribution-record commit; attached identities continue to identify the actual frozen build source.

Validation includes full make test, final native and Docker Core WAL/process regressions, production-container restart/login checks, static packaging guards, and anonymous registry digest/config verification. The change also passed scoped race checks and two real Work/Service shutdown scenarios with acceptance images. Final packaging did not rerun a real paid-provider model call or a complete GUI/Work matrix. Attached manifests, checksums and validation files state the exact scope. The website-sync archive is a generated handoff, not a website deployment.

---

Piwork 0.0.12 Preview 修复 Core 在 SQLite 已提交数据仍留于 WAL 时，重启误报“存储格式不支持”的问题。

• 在私有副本中联合检查主数据库与 WAL，再打开正式存储；恢复已提交状态，不迁移存储格式，继续拒绝未知格式、版本和损坏数据库。
• 按剩余预算排空事务和等待 checkpoint；存储或最终日志未确认时如实报错，实际清理完成前保留安装所有权，checkpoint 无法确认完成时以非零状态退出。
• 直接带 WAL 重开后保留登录会话、安装身份和已提交数据；既有 Work/Service 关闭与恢复行为已通过本变更的集成测试。

Linux amd64 安装包包含 piwork-core、piwork-cli。配套 Core、Agent、file helper、snapshot helper 四个生产镜像均已发布并完成匿名拉取核验；package helper 复用 Agent。Docker 下载包包含部署材料，镜像从公开仓库拉取。浏览器入口仍为 17891，Core API 仍为 17871。

升级前停止旧 Core，并备份完整数据目录，包含仍存在的 SQLite WAL/SHM；不要通过删除 WAL 绕过此错误。

附件记录真实构建来源、digest 和校验和。本次通过完整 make test、最终原生/Docker Core 的 WAL 进程回归、生产容器登录重启检查、静态打包检查和镜像匿名核验；变更验收另包含竞态专项及两个使用 acceptance 镜像的真实 Work/Service 停机场景。最终打包未重跑真实付费模型或完整 GUI/Work 矩阵。website-sync 附件仅为生成的官网同步材料，未部署官网。