What The CLI Is
PostSnail CLI is the automation interface for local trusted workflows. The browser admin remains the main human interface; the CLI reuses the same workspace, exporter, verifier, and signing boundaries.
Open A Shell
Use workspace info or workspace migrate with a .postsnail Shell and the Shell passphrase. The Shell passphrase unlocks the encrypted workspace; it does not automatically unlock the signing key.
Content Commands
Use post list/new/import/status/delete, page list/import/status/delete/navigation, asset list/unused/delete-unused, and comment verify/approve/reject/list/block-key to manage encrypted Shell content locally.
Build And ZIP
Use build to write a public directory and zip to write a publishable Website ZIP. Both commands require the Shell passphrase and the identity passphrase so PostSnail can unlock the encrypted signing key and sign proof files.
Verify Output
Use verify on a public directory or ZIP. Verification recomputes hashes, checks signatures, and confirms the bundle fingerprint before publish or deploy steps.
Publish And Forest
Use publish surge for the local Surge bridge, forest announce for remote Forest refresh, shellname register/update/renew for aliases, and domain move/mirror for signed site moves. These commands send public records and generated files, not private keys or Shell vault data.
Boundaries
The CLI does not add backend accounts, browser token entry, guided menus, or a bundled local Forest server. Forest commands talk to remote Forest APIs and keep secrets local.