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.