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.