Publish with Wardlock

Publish a static directory as a private page under one root site on the user's own Wardlock server, and give the user a share link that opens only that page. Each page lives at its own path, /<slug>/, so many pages share one site and never overwrite each other.

This skill only publishes. Making the content (HTML, a built prototype, a report) is the user's job or another skill's; this skill takes a finished directory with an index.html at its top.

Use only the commands in references/cli.md, written exactly as there. Pass --json on every call and read stdout as one JSON object; on failure stdout is empty, the exit status is not 0 and stderr says why. Write --json first, straight after wardlock, as the reference does.

Rules

• Never public. A page must never be reachable without a link, not even briefly. Publish only to a root site whose default policy is protected; follow "Create a root site" for a new one.
• Never log in for the user. If the CLI is not logged in, ask the user to run wardlock login themselves.
• Never overwrite an existing page unless the user asked to update that page.
• Share URLs are secrets. Give the user each link's url once, in your reply. Never write it to a file, a commit, a log, a ticket or a command line you echo, and never repeat it later; if it is lost, rotate the link (wardlock --json share rotate ROOT LINK_ID).
• Stop and tell the user when a command fails; do not retry with different flags to work around a refusal.

1. Check the CLI