Write managed install artifacts

docs/architecture.md

@@ -124,6 +124,10 @@ supervisor, and health-check steps. It does not install packages, create directo
 start services. The output is a reviewable bridge between daemon ownership decisions and
 future live apply support.
 
+With `--write-artifacts`, install-plan writes managed config and supervisor files under
+the configured `plan_root`; those files are review artifacts, not installed service
+state.
+
 Tor and I2P HTTP publishing include the transport daemon and the loopback web-serving
 layer in the install plan, because the hidden service or tunnel must have a local HTTP
 target.

docs/daemon-management.md

@@ -40,6 +40,7 @@ config artifacts.
 python3 -m ampg --config gateway.toml status
 python3 -m ampg --config gateway.toml doctor
 python3 -m ampg --config gateway.toml install-plan --profile mobile-i2p
+python3 -m ampg --config gateway.toml install-plan --profile mobile-i2p --write-artifacts
 python3 -m ampg --config gateway.toml apply --dry-run
 python3 -m ampg --config gateway.toml apply --dry-run --profile mobile-i2p
 python3 -m ampg --config gateway.toml apply --dry-run --protocol i2p
@@ -59,6 +60,11 @@ health-check steps needed for AMPG-owned daemons. It is dry-run only. Adopted da
 external-policy targets are shown as skipped, while unsupported platform/daemon pairs are
 blocked.
 
+`install-plan --write-artifacts` writes managed daemon configs and platform supervisor
+files under the configured `plan_root`, grouped by site, protocol, and platform. For
+Tor/I2P HTTP publishing, AMPG writes both transport-daemon artifacts and loopback nginx
+artifacts.
+
 `apply --dry-run` prints the activation sequence for each enabled protocol: generated
 output readiness, config artifacts to review, daemon action, and post-apply health
 checks. It exits nonzero when any step is blocked. `--write-artifacts` writes reviewable