Repository navigation
Package Deltas: orchestrate replay across every targeted Shard #310
Description
This was generated by AI during triage.
Agent Brief
Category: enhancement
Summary: Apply and replay Package Deltas across a Realm without hiding partial completion.
Current behavior:
The importer accepts one destination at a time. There is no Package inventory-driven plan or Realm-wide recovery record.
Desired behavior:
The Operator command resolves the enabled Package inventory and every targeted Shard. It preflights the complete Realm plan before writing, then applies Shards sequentially through the idempotent single-Shard contract. A failure stops further work and reports completed, failed, and untouched Shards plus an exact resume command. A retry verifies already-complete provenance and continues safely.
Non-spatial catalogues reach every World Shard and Instance Pool that owns a copy. Spatial claims follow World Import Scope and Import Family ownership.
Key interfaces:
- Realm Package Delta plan
- Shard target resolver
- Persisted per-Shard Package provenance
- Resume and status output
Acceptance criteria:
- Preflight validates every target and artifact before the first write.
- A mid-run failure never reports Realm-wide success.
- Output identifies completed, failed, and untouched Shards.
- Retrying is idempotent and resumes without duplicating rows.
- Removing one Package replays every affected target with the remaining Package set.
- Integration coverage includes a forced failure between two Shards.
Out of scope:
- Distributed atomic transactions across Shards
- Automatic rollback of already-complete Shards
Activity
Mathih13 commentedon Aug 27, 2026
Closing as implemented; the maintainer opted to fold live verification into a single test pass rather than hold this open.
Shipped as lyracore-cli #44 (merged):
lyracore packages replay [DATABASE ...] [--check] [--yes] [--force-all] [--client-data PATH]. All six acceptance criteria have test coverage (33 new tests), including the forced failure between two Shards: the FakeStack suite scripts Shard 2 to fail and asserts Shard 1 completed, Shard 2 errored, Shard 3 was never touched, and the report names all three states plus the literal resume command. Retry is resume-by-default: a Shard is skipped only when every enabled Package's recordedgame_package_importdigest matches the local artifact's BLAKE3, no disabled Package has a leftover row, andbase_source_shamatches the Shard's current spell stamp.What the eventual live pass should exercise (deferred, not forgotten):
game_package_importtable +apply_package_deltasreducer) to the target Shards first — the verb's preflight names this if missing.The single at-risk assumption only a live run settles: the CLI's restated canonical digest matching the module's. Drift fails safe (needless reapply, never a false skip).