openlogos deploy-done

After verify passes and a human has confirmed the deployment, deploy-done records the completion in a controlled way. It re-checks that verify passed, that the proposal actually requires deployment, and that the deployment plan and report exist — only then does it check off the deploy tasks, write the DEPLOY_DONE marker, and clear any stale smoke markers.

Synopsis

openlogos deploy-done [--env <name>] [--format json]

Must be run from the project root, with an active change proposal (guard file present).

Options

Option	Description
--env <name>	Target environment label recorded with the completion (for example staging).
--format json	Output a structured JSON envelope for tools such as RunLogos.

What it does

• Confirms verify passed — evaluated against the resolved verify node’s per-field predicate (marker VERIFY_PASS/VERIFY_FAIL, or a cmd:-gate), replacing a hard-coded marker check
• Requires an active proposal whose deployment decision resolves to “deployment required” (fails on a decision conflict or when deployment is not required)
• Requires a [deploy] task section in tasks.md and the deployment report at logos/resources/verify/deployment-report.md
• Checks off every task in the [deploy] section of tasks.md
• Writes the logos/changes/<slug>/DEPLOY_DONE marker
• Clears any stale SMOKE_PASS / SMOKE_FAIL markers from a previous run
• Reports next_step: ready-to-smoke (run openlogos smoke) or deploy-done (run openlogos archive)

This is a human-triggered, one-shot command — it fails loud on any missing precondition rather than partially recording completion.

Example

openlogos deploy-done --env staging

Deployment recorded

  Proposal: add-notify-webhook
  Environment: staging
  Marker: logos/changes/add-notify-webhook/DEPLOY_DONE
  Deploy tasks: 3/3 checked

Next: openlogos smoke --env staging

Related commands

• verify — Gate 3.6 acceptance (must pass first)
• smoke — Post-deployment health check (Gate 3.8)
• archive — Archive the completed proposal