CLI or Agent skill is missing
If the CLI is absent, install it before changing document content. If the skill doctor fails, repair the reported target instead of assuming publishing is configured.
command -v ow
ow agent doctor --target autoHosted credentials are missing
Run setup when Hosted publishing reports a credential problem or when you intentionally need to log in again. Local draft construction does not require Hosted login.
ow setup --target autoThe package does not validate
Fix the draft command that produced the invalid content. Do not edit generated JSON or the .mdw binary to bypass validation, and do not delete the workspace merely because an idempotent draft command reports a conflict.
ow a2ui draft status ./artifact
ow a2ui draft check ./artifact
ow a2ui draft build ./artifact
ow a2ui digest ./artifact/document.mdwThe input is unsupported
Hosted publishing does not accept raw Markdown, raw HTML, directories, stdin, legacy Bundle JSON, or JSON-LD. Build a typed .mdw package first. If the goal is simply to host an existing HTML file unchanged, use a static host or an HTML artifact host instead.
Review timed out
A timeout means no final decision was received. It does not mean approved. Keep the current formal version, report the timeout, and resume waiting or publish a revised candidate only when the workflow calls for it.
FAQ
Frequently asked questions
What should I run before retrying a failed publish?
Start with ow agent doctor, then run draft status, check, build, and digest. Retry only the smallest failing boundary.
Should I delete the draft workspace after a conflict?
No. A conflict can be an idempotency signal. Inspect draft status and preserve the workspace unless a command explicitly says recovery requires removal.
Use the real workflow
Publish what your agent creates.
Give every report, document, or plan its own reader-ready page. Comments, review decisions, and formal revisions can flow back from there.