nx_failover_compose_test.nx

nx_failover_compose_test.nx -- ransomware-judo failover end-to-end. Per [[feedback-cell-immune-system-ransomware-judo-ddos-by-bit]] scenario: "if website a got hit with ransomware we laugh and delete and shift to website b and load up c as the new backup defying ddos and all other systems of attack by judo by bit." The compose demo lifecycle: 1. Build cell A (primary) + cell B (chromatin backup) + cell C (newer chromatin backup waiting in the wings) 2. Build a dyad: A and B run side-by-side serving same input; observatory watches both outputs from outside 3. Provenance chain logs the input ingest + each cell's output production 4. Ransomware sig detected on cell A -- nx_promote swaps A to B using the latest chromatin 5. C's chromatin replaces the now-stale B-as-backup (C is fresher) 6. Provenance chain shows the failover as a transform link (NX_TX_NONE caller-defined kind for now) 7. Observatory now watches NEW dyad (B-as-primary + C-as-backup) This proves the judo: vendor's attack on A becomes our forensic record of attack + sub-second swap + audit-trail through provenance.