{
  "schema": "liskov.changelog.v1",
  "record": {
    "id": "2026-11-21-docs-set-secrets-before-first-run",
    "url": "https://changelog.liskov.proof.computer/r/2026-11-21-docs-set-secrets-before-first-run/",
    "md_url": "https://changelog.liskov.proof.computer/records/2026-11-21-docs-set-secrets-before-first-run.md",
    "json_url": "https://changelog.liskov.proof.computer/records/2026-11-21-docs-set-secrets-before-first-run.json",
    "title": "How to set a required secret before your first run",
    "summary": "An Application's Secrets page lists nothing until a policy that declares the secret is published, so a required secret could not be set in advance. The GitHub guide now shows the way through: publish paused, set the secret, then resume.",
    "type": "improved",
    "breaking": false,
    "components": [
      "docs",
      "secrets"
    ],
    "status": "live",
    "live_at": "2026-11-21T16:57:27Z",
    "versions": {},
    "credits": [
      {
        "anonymous": "a design partner"
      }
    ],
    "docs": [
      "https://docs.proof.computer/liskov/get-started/github"
    ],
    "agent": {
      "surface": "Application Secrets page; proof liskov application publish / resume",
      "before": "Undocumented: a secret value can be set only after a policy declaring it is published, and an unpaused first publication runs before the secret exists.",
      "after": "Documented route: add `--paused --reason \"set secrets before first run\"` to the publish command, set the value on the Application's Secrets page, then run `proof liskov application resume <app> --reason \"secrets set\" --yes`.",
      "action": "Use the paused-publish route for any Application whose manifest declares a required secret.",
      "unaffected": [
        "Secret storage and delivery behaviour (unchanged)"
      ],
      "errors": []
    },
    "supersedes": null,
    "body": ""
  }
}
