Arseniy Klempner e738135924 live-registry: skip the chain-clock test on local; record the gap ...

The standalone sequencer leaves CLOCK_50 at zero — chain time never tracks
wall time on a local devnet, so membership lifecycle timing is only
faithfully exercised against testnet. First local run surfaced it: 6/7
green, the clock test correctly red. docs/contract.md gains a
local-vs-testnet gaps section (clock + the 1MiB-vs-459KB block cap).

2026-08-10 20:19:08 -06:00

..

contract.md

live-registry: skip the chain-clock test on local; record the gap

2026-08-10 20:19:08 -06:00

naming.md

drop journey docs; add the live-registry scenario

2026-08-10 20:06:53 -06:00