archetech / archon / 28877135156

92%

main: 92%

push

github

fix(deploy/noderunner): drop drawbridge from stage 0 (compose profile coupling)

Investigation: docker/compose/lightning.yml declares Lightning services with
profiles: ['lightning', 'drawbridge'] — because docker compose ORs profile
membership, enabling the drawbridge profile also boots CLN, LNbits, rtl, and
lightning-mediator. That would drag the full 21-container Lightning stack into
stage 0 and break the "no funding, no external RPC keys" promise (CLN needs a
bitcoind source that stage 0 doesn't have).

Reworked stage 0 to talk Caddy → gatekeeper directly, deferring the entire
drawbridge/Lightning/Herald/Tor bundle to add-lightning.

- templates/env.stage0.template: drop drawbridge from COMPOSE_PROFILES;
  comment explains the coupling.
- templates/Caddyfile.stage0.template: reverse_proxy targets flip to
  localhost:4224 (gatekeeper) instead of localhost:4222 (drawbridge). Comments
  note that add-lightning will flip them to :4222 for L402 handling.
- SKILL.md: list the ~9 stage-0 containers explicitly. Replace the earlier
  "stage 0 already includes Tor SOCKS" section with a "Profile coupling to be
  aware of" section that documents the drawbridge/lightning marriage, notes
  that Tor SOCKS + onion arrive with add-lightning, and preserves the 127.0.0.1
  security posture guidance for when they do.
- README.md: stage-0 description reflects the smaller container set;
  add-lightning row calls out the drawbridge/Herald/Tor ride-along; closing
  note reframes the "stage 0 already includes tor" claim.
- stages/add-lightning.md: preface calls out the profile coupling and lists
  what else comes online besides Lightning proper.
- stages/add-didcomm.md: the /didcomm/* Caddy target now depends on whether
  add-lightning has run — reverse_proxy localhost:4236 (didcomm direct) if
  pre-lightning, localhost:4222 (via drawbridge) if post. Note that
  add-lightning must flip the didcomm route as part of its transition.

Follow-up (out of scope for this scaffold)... (continued)

2816 of 3323 branches covered (84.74%)

Branch coverage included in aggregate %.

5851 of 6142 relevant lines covered (95.26%)

882.15 hits per line