Repository navigation
SandPackage 0.2.10
SandPackage 0.2.10 fixes interrupted dependency command ownership (#31).
- Official
inspect-dependency/recover-dependencyCLI 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.