Plan managed supervisor actions

This commit is contained in:
jwinterm
2026-07-06 12:17:05 -04:00
parent 3063e61676
commit a921f158c3
8 changed files with 167 additions and 6 deletions
+2 -2
View File
@@ -113,8 +113,8 @@ render-only environment while making daemon ownership decisions explicit.
activation sequence. Each enabled protocol gets output, artifact, daemon, and health
steps, plus an address step when AMPG must capture or confirm a generated transport
identity. With `--write-artifacts`, it also prints planned copies from reviewed artifacts
into managed state. Blocked steps stop the command before any live apply path can touch
services.
into managed state and planned supervisor start/reload actions. Blocked steps stop the
command before any live apply path can touch services.
The dry-run command is intentionally stricter than `doctor`: missing generated output is
blocked during activation, because AMPG must not point a transport at an unbuilt output
+2 -2
View File
@@ -86,8 +86,8 @@ Missing output blocks the plan, while placeholder transport addresses are review
output readiness, config artifacts to review, daemon action, address capture or reuse,
and post-apply health checks. It exits nonzero when any step is blocked. `--write-artifacts`
writes reviewable config snippets to the configured plan root, then prints the planned
copies from those reviewed artifacts into `gateway.state_dir`. It still does not install
or reload services.
copies from those reviewed artifacts into `gateway.state_dir` and the supervisor services
that would be registered or started. It still does not install or reload services.
`--protocol` scopes operational commands to selected enabled protocols. A clearnet
`adopt` failure will block a full activation run, but it will not block
+2 -1
View File
@@ -39,6 +39,7 @@ Current managed defaults:
AMPG must never delete sensitive contract paths without an explicit destructive command.
`apply --dry-run --write-artifacts` prints `AMPG_APPLY_STATE_COPY` rows that show which
reviewed artifacts would be copied into managed state. Live apply should perform those
reviewed artifacts would be copied into managed state and `AMPG_APPLY_SUPERVISOR` rows
for the services that would be registered or started. Live apply should perform those
reviewed copies, start daemons, capture public addresses, and then run published health
checks.