saubyk b790dc7abf Add a Core Lightning node to the regtest docker fixture ... The fixture had only bitcoind + three LND nodes, so RTL's Core Lightning screens had no backend to exercise. Add a `cln` node (official elementsproject/lightningd image, multi-arch) wired to RTL over clnrest with rune auth, and have the seed open a cln->alice channel so the CLN channel/peer screens have real data. - docker-compose.yml: cln service (clnrest on 0.0.0.0:3010, https), a healthcheck gated on the rune file so rtl waits for it, and rtl now mounts the cln volume read-only and depends on cln being healthy. The rtl image is parameterized via ${RTL_IMAGE:-...} so an unreleased build can be tested against the fixture. - cln/poststart.d/create-rune.sh: once the RPC is up, create a master rune and write it as LIGHTNING_RUNE="..." where RTL reads it (runePath). Polls for RPC readiness because the image entrypoint can invoke poststart before the socket exists. - RTL-Config.regtest.json: add node index 4 (CLN, rune auth, https://cln:3010). - seed.sh: fund cln, connect to alice, open a 4,000,000 sat channel, wait active. - README + release notes updated. Used to verify the CLN channel connection-status fix (#1606) end-to-end. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>		2026-07-19 22:01:23 -07:00
..
RTL-Config.regtest.json	Add a Core Lightning node to the regtest docker fixture	2026-07-19 22:01:23 -07:00