Idunn/tests/fixtures/idunn-control-legacy
Repository files (latest commit first)
Filename Latest commit message Latest commit date
Meta Vens 8212b9d15d B2 rework: rebuild the tests on the routed world and the target meters
The route-proof world's hand-built promotion is deleted: the world runs over
stub host programs, so Routing installs and proves the route for real and
every former promote_by_hand is a real step. The salvage fixtures of the old
B2 are not ported.

New tests pin each ruling under its own mutation: a full ledger still admits
and counts every survival actuation, first deployments are metered, a refused
preflight starts no private-mount unit and fails at once with the reopen time,
the actuation log slides, a clock step stalls nothing past one window, a
failed challenge ends the pass instead of losing a CAS, a proved challenge
clears the degradation, both storms are bounded, restarts are spaced,
counted in the mint and read from the target's own log (unreadable history no
longer stops crash recovery), and the v3 lift is pinned over golden bytes cut
with the 583b2a7 encoder, refusing a record that shows retired meters.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
2026-09-30 00:31:12 +02:00
..
generation-route-repair-started.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
generation-v3-odin.hex B2 rework: rebuild the tests on the routed world and the target meters 2026-09-30 00:31:12 +02:00
generation-v3-route-proof.hex B2 rework: rebuild the tests on the routed world and the target meters 2026-09-30 00:31:12 +02:00
generation-with-receipts.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
provider-anchor.hex Close the B1 transition: lift, precondition, boot reconciliation, closed history 2026-09-29 06:11:29 +02:00
README.md B2 rework: rebuild the tests on the routed world and the target meters 2026-09-30 00:31:12 +02:00
transaction-awaiting-ready.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-committing-v2.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-committing.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-failed-after-fencing.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-fencing.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-leasing.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00
transaction-post-fence-abort.hex Close the B1 transition: lift, precondition, boot reconciliation, closed history 2026-09-29 06:11:29 +02:00
transaction-pre-fence-abort-terminal.hex Close the B1 transition: lift, precondition, boot reconciliation, closed history 2026-09-29 06:11:29 +02:00
transaction-pre-fence-abort.hex Close the B1 transition: lift, precondition, boot reconciliation, closed history 2026-09-29 06:11:29 +02:00
transaction-routing.hex Bump admitted generation to v3 and transaction to v4 with typed readiness (F0) 2026-09-29 02:14:47 +02:00

Legacy control-record wire fixtures

Each *.hex file is two lines: the CultCache envelope schema_id, then the record's MessagePack payload in hex. They are the exact bytes the encoder at Idunn 9001b58 (the base of the F0 cut) wrote for records built through that revision's own constructors: DeploymentTransaction::new, AdmittedGeneration::from_transaction, SealedRelease::new, compile_deployment_plan, and rmp_serde::to_vec. A throwaway test on a scratch commit over 9001b58 printed them; it is not kept.

Everything in them is synthetic: identities were enrolled fresh in a temporary directory, the Odin receipts are placeholder bytes with correct digests, and the plan is the deployment_plan test recipe. No byte comes from a live store.

File Schema What it is
generation-with-receipts idunn.admitted_generation.v2 routed, stateless generation with Ready and latest Odin receipts
generation-route-repair-started idunn.admitted_generation.v2 the same with route_repair_started_at_unix_millis set
transaction-fencing .. transaction-committing idunn.deployment_transaction.v3 one continuity transaction in each post-fencing phase
transaction-committing-v2 idunn.deployment_transaction.v2 the Committing record in the v2 layout: the v3 tuple without key 34 (base code stops writing v2, so this one is the v3 encoding with its trailing nil slot dropped and the header count lowered)
transaction-failed-after-fencing idunn.deployment_transaction.v3 terminal post-fencing failure with complete abort evidence

control_plane.rs decodes these through LegacyDeploymentTransaction and LegacyAdmittedGeneration. The fixtures die with those structs.

Pre-B1 continuity aborts

The transaction-*-abort* files and provider-anchor were printed by a second throwaway test over 9001b58. It built a continuity transaction that issued an activation (the recipe and binding of the deployment_plan tests, a provider identity enrolled fresh, the trust-anchor path in the binding fixed at /tmp/idunn-b1-legacy/provider-anchor.cc) and gave it the aborts the base code writes: the pre-fence abort literal of begin_pre_fencing_abort, and the base post_fencing_abort_intent. In each, the transaction issued an activation and its abort records topology_reconciliation = Skipped, because the base rule owed a continuity no projection cleanup. The workload and Odin evidence are borrowed from transaction-fencing.

File What it is
transaction-pre-fence-abort Warming continuity, pre-fencing abort in flight
transaction-pre-fence-abort-terminal the same abort finished: Complete, FailedBeforeFencing
transaction-post-fence-abort Fencing continuity, post-fencing abort in flight
provider-anchor one line: the provider trust-anchor file bytes, hex. A test writes it to the fixed path so the Engine can read the plan's anchor

Generation v3 (the B2 lift)

generation-v3-odin and generation-v3-route-proof are the exact idunn.admitted_generation.v3 payloads the encoder at Idunn 583b2a7 wrote (admitted_envelope over rmp_serde::to_vec), printed by a throwaway test that is not kept. The first is the v2 generation-with-receipts record lifted by that revision's own LegacyAdmittedGeneration::into_current, the second is the generation route_proof::committed_generation admits through a real route-proof deployment. Both are synthetic.

File Schema What it is
generation-v3-odin idunn.admitted_generation.v3 routed, Odin-correlated generation
generation-v3-route-proof idunn.admitted_generation.v3 routed, route-proof generation, no Odin receipts

control_plane.rs decodes them through LegacyAdmittedGenerationV3; the fixtures die with that struct.