[NicolasDorier]

Summary

• Add LND and Core Lightning fork submodules pinned to published release source.
• Centralize shared conventions and project-specific bump procedures without relocating builds or publishing credentials.
• Incorporate the integration and artifact-validation corrections proposed in Correct and consolidate the LND release procedure lnd#19 and Require integration gates and streamline the CLN update workflow lightning#5.
• Add read-only upstream release lookup, patch, tag and image-platform checks with Bash fixture tests and ShellCheck CI.

Validation

• Pass all 31 Bash fixture checks, including temporary Git repositories, mocked image indexes, CLI invocation and local documentation links; shell syntax checks and ShellCheck also pass.
• Verify current release tag objects and peeled commits against GitHub, and inspect all three published platforms for both images.
• Run published amd64 LND, Loop and Core Lightning version smoke tests without network access.
• Confirm patch inventory; the existing LND overlay has trailing whitespace at docker-entrypoint.sh:9, docker-initunlocklnd.sh:19 and linuxarm32v7.Dockerfile:30; these are not changed by the migration.

No image was published, release tag moved, shared history rewritten or live deployment changed. Full builds, startup regressions, ARM execution and downstream integration are release gates documented here, not checks performed for this migration.

Rollout

Merge this setup before the fork documentation cleanup PRs so their links resolve on master. Existing historical release tags retain their original documentation. The empty initial master commit only establishes the PR base.

[NicolasDorier]

Fork cleanup PRs (draft until this setup is merged):

• LND: Move LND maintenance instructions to image-maintenance lnd#20
• Core Lightning: Move Core Lightning maintenance instructions to image-maintenance lightning#6

Fresh recursive-clone validation passed with both published source pins, all 14 tests, and a clean worktree. Local URL rewrites reused the existing fork objects; the committed submodule URLs remain the requested GitHub SSH URLs. Parent CI also passed.

The fork PRs trigger their existing CI independently; those runs are not evidence of startup coverage against the newly published release images.