Start by reading current state. A timeout or interrupted terminal session does not tell you whether a write reached Barua.
Read the operation
With the original BARUA_MANAGEMENT_KEY and installed skill:
node "$BARUA_SKILL/scripts/manage.mjs" operations
node "$BARUA_SKILL/scripts/manage.mjs" status --id "$OPERATION_ID"
Success returns the stored operation and its next allowed step. Follow Errors and recovery for the returned status. Use the original idempotency key and identical input when retrying a write.
status is a read. wait can resume a ready operation, so use it only when continuing that operation is authorized. Do not use it as a harmless polling substitute.
Match the blocker
- Missing permission: read
capabilities, then ask the owner for the required grant. Do not bypass it with another credential or dashboard clicks. - Pending review: have the owner read the current review context. Approval does not automatically resume the operation.
- Stale terms: the owner must review and explicitly accept the current version. Do not accept terms on their behalf.
- Missing email: inspect Play runs and email history before attempting another send.
For a lost management key, follow Recover a lost management key. Recovery saves the same key again privately; it does not create a second connection or alter pending operations.
Report partial results
Distinguish unavailable data from an empty result. Follow pagination when completeness matters. For event imports, wait for the stored receipt outcome; for email, distinguish provider acceptance from observed delivery.
After a resumed setup operation or the last setup change, follow Finish and hand off, including the review package. Report the remaining owner decision when one still blocks progress.
Closure and deletion have separate recovery rules. Use workspace closure or account deletion rather than repeating a destructive command.