shankar0123 f157c18368 docs: re-home ACME client walkthroughs under docs/migration/ ...

The three ACME client walkthroughs (Caddy, cert-manager, Traefik) are
conceptually "I have an existing X, here's how to point its ACME
client at certctl." They belong with the migration docs, not with the
acme-server protocol reference.

Renames:
  docs/acme-caddy-walkthrough.md       → docs/migration/acme-from-caddy.md
  docs/acme-cert-manager-walkthrough.md → docs/migration/acme-from-cert-manager.md
  docs/acme-traefik-walkthrough.md     → docs/migration/acme-from-traefik.md

Each walkthrough's lede gets a "Use this walkthrough when..." paragraph
that closes the WHY-weak gap flagged in the Phase 1 audit. The new
framing tells the reader when to pick this walkthrough versus the
alternatives:

  - Caddy: "you're running Caddy 2.7+ and want it to ACME-issue from
    certctl instead of Let's Encrypt"
  - cert-manager: explicit pointer to cert-manager-coexistence.md for
    the keep-cert-manager-running case (vs replacement)
  - Traefik: "you're running Traefik 3.0+ and want certctl as your
    ACME source of truth"

Cross-reference updates from other docs and README still pending in
Phase 11.

2026-05-05 02:51:10 +00:00

..

acme-from-caddy.md

docs: re-home ACME client walkthroughs under docs/migration/

2026-05-05 02:51:10 +00:00

acme-from-cert-manager.md

docs: re-home ACME client walkthroughs under docs/migration/

2026-05-05 02:51:10 +00:00

acme-from-traefik.md

docs: re-home ACME client walkthroughs under docs/migration/

2026-05-05 02:51:10 +00:00

cert-manager-coexistence.md

docs: Phase 2 mechanical file moves to subdirectory structure

2026-05-05 02:49:28 +00:00

from-acmesh.md

docs: Phase 2 mechanical file moves to subdirectory structure

2026-05-05 02:49:28 +00:00

from-certbot.md

docs: Phase 2 mechanical file moves to subdirectory structure

2026-05-05 02:49:28 +00:00