Repository navigation
packages devx: lyracore publish defaults to ALL provisioned databases #91
Description
Spec: the packages-devx design, §4 (public proposal: #1; the full design doc lives in the private working origin).
Change lyracore publish (lyracore-cli repo + pin bump) so no args = every provisioned database, replacing today's "no args = the fixture database". Partial-shard publish is the most documented trap in docs/danger-zones.md (presents as an unrelated mid-session hang), and the fixture is already four databases — the safe thing must be the zero-thought default. Naming databases stays supported as the explicit expert case. Update docs/development-cli.md §publish accordingly.
Done when: lyracore publish with no arguments publishes all databases dev status knows about (verified against the 4-DB fixture), and lyracore publish <one-db> still targets only that one.
Migrated 2026-08-11 from the private tracker (spacetime-core#499).
Activity
Mathih13 commentedon Aug 24, 2026
Agent Brief
Category: enhancement
Summary: Make bare
lyracore publishtarget the persisted fixture topology.Current behavior:
The pinned CLI publishes only
lyracorewhen no destination is named, although its topology model knows the four sharded fixture destinations. Existing tests preserve this unsafe default.Desired behavior:
With explicit destination names, publish only those destinations. With no names, read the persisted active fixture topology. An active single fixture publishes its one destination. An active sharded fixture publishes its four ordered destinations. If no fixture is active, use the configured default sharded fixture topology. Keep the existing fail-fast behavior and report the destination that failed.
Key interfaces:
lyracore publishAcceptance criteria:
lyracoreas the universal bare default.Out of scope: