SandPackage 0.2.14

SandPackage 0.2.14

Fixes the installed-plugin minimum-version gate when a numeric core segment exceeds PHP integer range. Valid major/minor/patch digit strings are compared by length and lexicographic order, without integer or float conversion. Equal-core prereleases are below the stable bundled minimum; build metadata is ignored.

Bundled archive version, SHA, metadata, and waiting-candidate identity remain exact. Other version comparison sites and the current-provider read-only diagnostics are unchanged.

Install or update:

composer require 'supdger/sand-package:>=0.2.14'

Validation: the public 0.2.13 failure was reproduced against actual vendor classes. The fixed source passed 35 neutral ZIP/recording-database scenarios / 236 assertions, three PHP lint checks, independent complete-candidate review and Windows native-path CI. These checks do not prove original-host HTTP or business acceptance, and do not establish a past startup failure's cause. Existing upstream Composer constraints were not audited by this bounded change.

The system-update contract binds the exact release reference, host_min 0.2.0 with no upper host limit, and no schema or skeleton changes. Sand Core and dependency declarations are unchanged. An earlier isolated retry assertion failed without retained diagnostic evidence; its cause remains unknown.

SandPackage 0.2.13

SandPackage 0.2.13

• Installed plugin dependencies accept a valid installed version at or above the declared minimum. No dependency downgrade or reinstall is performed. Bundled ZIP version, SHA, metadata, and waiting-candidate identities remain exact. Invalid numeric prerelease leading zeros and lower versions are rejected before the target plugin SQL.
• Read-only dependency-start inspection adds safe current-worker provider identity hints from runtime metadata, lock and installed records, and the existing identity conditions. It does not refresh runtime metadata, write recovery records, or relax execution guards. These hints do not establish a past failure's cause, complete recovery eligibility, or successful startup.

Install or update through Composer:

composer require 'supdger/sand-package:>=0.2.13'

The system-update contract targets this exact release reference, with host_min 0.2.0 and no upper host limit. No database schema, host skeleton, dependency declaration, or Sand Core version change is included.

Validation: 28 dependency activation scenarios / 190 assertions, 49 diagnostic checks and 6 projection checks, independent source and integrated-candidate review, and Windows native-path CI passed. Original-host HTTP and business acceptance remain unverified. Existing upstream Composer constraints were not audited by this bounded change. An earlier isolated retry assertion failed without retained diagnostic evidence; its cause remains unknown.

SandPackage 0.2.12

SandPackage 0.2.12

Dependency startup failures now report a fixed stage and independent incident ID correlated with safe fields in the existing Webman logger. Logger failures preserve terminal callbacks and cleanup; diagnostics exclude raw exception messages, command arguments, environment, task nonce and trace arguments.

Authenticated superadmins can use POST /app/sandpackage/install/inspectDependencyStart with a fixed command key for read-only hints from the current HTTP worker. Lock acquisition, durable writes, child runtime support and actual launch remain unknown until execution.

An already-confirmed waiting dependency task spanning a further provider update can explicitly refresh the verified provider binding through the existing inspect-dependency / recover-dependency protocol, using a fresh full confirmation without --restart. It preserves original recovery and transaction bytes, creates no new command or nonce, and executes no SQL. Explicitly run the waiting task afterwards.

Validation: independent neutral diagnostics 50 checks, provider binding 89, existing provider recovery 128, and separate interruption checks passed; Windows native-path CI passed. These are source/native/recorded-PDO checks, not original-host HTTP or business acceptance. The earlier consumer startup failure cause remains unknown; this release adds diagnostic evidence and does not claim its root cause is fixed. The earlier isolated retry assertion without retained diagnostics also remains unexplained.

No schema, host skeleton or dependency declaration changes; Sand Core remains 0.2.4. System-update host_min 0.2.0 has no upper bound. This release does not operate existing consumer hosts. Install with normal Composer: supdger/sand-package:^0.2.12.

SandPackage 0.2.11

SandPackage 0.2.11 preserves official dependency recovery across a normal update of its own provider requirement (follow-up to #31).

• Allow only the single raw version-value token in require.supdger/sand-package to differ from the exact completed dependency transaction. Verify original backup/candidate, current requirement, lock and installed package identity, canonical executing source and code hashes. Other manifest bytes, origins, payload drift and stale confirmation remain refused. other_lock_history_verified=false does not invent historical lock evidence.
• Confirmed recovery only retires the dead original occupation and preserves dependency waiting. It does not rewrite Composer outputs or replay dependency commands or lifecycle SQL. Explicitly retry the waiting dependency task afterwards.
• Preserve a transition bound to original closed recovery/journal/candidate, new owned nonce/type and durable successful completion against all current dependency inputs. Ordinary later lifecycle retirement archives the original journal byte-for-byte and resumes interruption windows. Ordinary apply/restore stays strict without the confirmed completion proof; old 0.2.10 ordinary checkpoints retain their compatible shape.

Validation: independent fixed-source and final metadata review passed provider128, ordinary checkpoint36, existing recovery123, canonical projection6, foreign-source2 and the strict dependency suite. Windows native-path CI passed32s for the merged source tree; this is path/package compatibility, not POSIX recovery on Windows. Fixtures record SQL rather than operate a real PostgreSQL business host. Actual same-scene public Composer upgrade and dependency retry are separately verified after publication.

No schema, host skeleton or dependency version declarations changed; Sand Core remains 0.2.4. System-update host_min0.2.0 has no upper bound. This release does not operate an existing consumer host. Install through the normal documented Composer flow using supdger/sand-package:^0.2.11.

Validation limitation retained from #31: an earlier isolated retry assertion had no retained diagnostic evidence and its cause remains unknown; later fixed-source checks do not establish that cause.

SandPackage 0.2.10

SandPackage 0.2.10 fixes interrupted dependency command ownership (#31).

• Official inspect-dependency / recover-dependency CLI and administrator POST entries bind the original task, candidate, process evidence and fresh confirmation. Recovery requires proof that the original process group and recorded descendants have exited. It preserves dependency waiting without declaring command success or replaying dependency commands or lifecycle SQL.
• Durable reaped/completion proof lets the same entry finish interrupted cleanup. Deferred reload intent is handled only after the last dependency is successfully registered; an explicit restart-only request is separate from worker rotation acceptance.
• Missing or uncertain process proof, active/reused process identities, changed candidate/checkpoint evidence and stale confirmation are rejected. POSIX process inspection is required; this release does not upgrade or operate an existing host.

Validation: 123 neutral formal CLI/API and native-process checks, disabled-POSIX rejection boundary, related regressions and independent source/asset review. SQL is recorded by isolated fixtures; no real PostgreSQL business host was restored. Windows native-path CI passed for the merged source tree (its scope is path and package compatibility).

No database schema, host skeleton or dependency version changes. Sand Core remains 0.2.4. System-update contract: host_min 0.2.0, no host_max.

Install/update through the normal documented Composer flow using supdger/sand-package:^0.2.10.

Validation limitation: An earlier isolated retry assertion failed without retained diagnostic evidence; its cause remains unknown. The fixed-source fault-injection and native-process checks passed.

SandPackage 0.2.9

SandPackage 0.2.9

修复新驱动仅上传升级包、尚未开始当前插件生命周期时，待安装候选不能经正式入口撤回并重新上传的问题（#29）。在宿主 server/ 先运行 php webman sandpackage:recover inspect-candidate <插件标识>，有动作时用本次 fingerprint 执行 README 中的 discard-candidate --confirmation="DISCARD ..."。超级管理员 API 为 inspectCandidate 与现有 discardCandidate。

仅支持已有安装的未开始升级候选。确认绑定原始候选、精确备份、归属、运行目录、当前数据库身份/结构和撤回检查点；现场变化后重新检查。原候选与旧备份保留，成功恢复升级前 version/state=1。恢复目录完成但日志保存中断时仅补完已有日志，不重写已恢复候选。已有生命周期、未完成操作/依赖任务、篡改或旧确认继续拒绝，首次安装候选不适用。

不执行生命周期 SQL、不改宿主载荷或重载服务；不撤销其他插件依赖，当前数据库检查不证明上传前数据库未变。

• 正常公开消费：composer require supdger/sand-package:^0.2.9，配套 Sand Core 0.2.4。
• Source ref: b26e782e19847816e90d3a556111dd209b818c35
• system-update.json SHA-256: 6280308b0b5d3cd8e9b360596c2ec325611dec6d5d811f4626a5f167e2364b69
• 最低宿主 0.2.0，无新增上限；数据库结构及宿主骨架均不变。
• 119 项正式 CLI/API 中立录制回归、96 项既有恢复回归及独立验收通过；Windows native-path CI 34 秒通过。未操作既有业务宿主或真实 PostgreSQL，发行不会自动撤回候选、升级或重载现有部署。

SandPackage 0.2.8

SandPackage 0.2.8

修复宿主应用载荷升级在 SQL 和新文件事务开始前因文件冲突失败后，上一轮已完成文件事务记录阻止正式恢复检查与旧候选回滚的问题（#27）。

sql_not_started 只开放恢复旧候选，不开放继续升级，不重放升级 SQL。恢复前核对当前候选、旧 owned 与数据库身份/结构证明；缺失或矛盾证明、现场变化、外部修改和错误确认继续拒绝。先运行 php webman sandpackage:recover inspect-host-upgrade <插件标识>，再使用本次 fingerprint 执行 README 中的 restore-host-upgrade --confirmation。恢复保留失败候选和冲突文件；处理冲突后才能按调用方权限重试。

• 正常安装/升级：composer require supdger/sand-package:^0.2.8，配套 Sand Core 0.2.4。
• Source ref: c97266d8a6312117d132b7cf74682614c729c8b1
• system-update.json SHA-256: 529f8d09bb37649116a3cc1ea654e2e86c62a3483b41b44ad6b744193e4dd934
• 最低宿主 0.2.0，无新增上限；数据库结构与宿主骨架均不变。
• 96 项正式恢复 CLI 录制回归与独立验收通过；Windows native-path CI 35 秒通过。未操作既有宿主或真实业务 PostgreSQL，发行不会自动升级、恢复或重载现有部署。

SandPackage 0.2.7

• 统一上传、仓库下载与安装包处理的压缩 ZIP 容量规则，默认及硬上限为 16MiB；宿主 plugin.sandpackage.upload.size 只可下调，非法或超上限配置明确拒绝。构包工具沿用相同硬上限，无新增参数。对应 issue #25。
• 超限诊断显示实际接收的 actual 与生效的 max bytes，测量失败、下载中断和摘要不符分别处理；保留 64MiB 解压上限、2048 条目及路径、声明载荷防护，补齐 ZIP 条目实际读取与 CRC 校验。
• HTTP 请求包络独立于压缩 ZIP 容量，需容纳 multipart 开销（例如 20MiB）；发行不修改宿主 HTTP 配置。无数据库、宿主骨架或依赖变更，继续配套 Sand Core 0.2.4，已有部署需升级本包才能获得修复。

源码：3482b8c9c8a1908901dbd063e0670d1095ce58d9。

发行契约：system-update.json，SHA-256：62c2d78ed48d27eb949830e718a2a2c7e2e9cc63854c809ac344b2034ef5f866。宿主最低版本 0.2.0，无数据库和宿主骨架变更。

Composer 安装：composer require supdger/sand-package:^0.2.7（宿主 server 目录）。发行不升级既有部署；HTTP 请求包络仍需按宿主配置容纳 multipart 开销。

Sand Package 0.2.6

0.2.6（2026-10-10）

• 修复自动安装依赖后，当前 worker 尚未加载依赖的正式 autoload 文件，导致原安装请求无法查询服务目录的问题；按 Webman 配置加载协议激活已安装依赖，保留版本、摘要、路径与目标 SQL 前的目录预检。对应 issue #22。
• 修复恢复 CLI --restart 将重载信号发给调用者父进程的问题；核对当前宿主 Workerman master 及 HTTP worker 身份后才重载，并等待 worker 轮换。无法定位、信号失败或轮换超时返回明确失败，保留已提交 SQL 的恢复检查点。对应 issue #23。
• 无数据库、宿主骨架或依赖变更；继续配套 Sand Core 0.2.4。已有宿主需升级本包才能获得修复；发行不自动升级或重载已有部署。恢复 CLI 重载在缺少 POSIX 的平台会拒绝执行，应使用宿主正式服务控制入口。

本次仅发布修复版本，不自动升级或重载用户宿主。

固定源码：2795e1b12b046058c1f3f3bdf26486751b23783e。system-update.json SHA-256：0adcd96e1f9a48a74518caadd3bd7c4b9cb77d9b2f4508264544d5600da0d877。

Sand Package 0.2.5

0.2.5（2026-10-09）

• 修复依赖命令两层子进程丢失宿主 HOME、Composer 配置、缓存及代理环境的问题；仅继承宿主进程环境，不接受请求提供的环境值。
• 修复 Composer / npm / pnpm / yarn 参数重复包含可执行文件名的问题，保持固定命令、进程隔离、完成回调和失败恢复守卫。对应 issue #11。
• 无数据库、宿主骨架或依赖变更；继续配套 Sand Core 0.2.4。已有宿主需升级 SandPackage 才能获得修复，发行不会自动升级部署。

本次仅发布修复版本与系统更新契约，不自动部署或升级已有宿主。

固定发行源码：72eea126802d44e815f23b01b12796fbd0448330。
system-update.json SHA-256：2c6d1ccbd16c63cadf697963736dcea6a78411af2ea5035cc828b13e4d9cfdcf。