Workspace closure is permanent. It requires an explicit owner decision and exact workspace confirmation. It is not a setup or testing step. Start with an owner session.
Read before changing
node "$BARUA_SKILL/scripts/owner.mjs" closure-status \
--workspace "$WORKSPACE_ID"
Success returns the current closure state. Confirm the workspace UUID and the owner's intent before preparing a close request. Read Close a workspace and keep its export in full; it defines the confirmation body and current version.
The close request uses a saved request_id. Retry only the same request and body after checking current status. Do not generate a new confirmation to recover from a timeout.
Keep the export
After closure, list retained artifacts:
node "$BARUA_SKILL/scripts/owner.mjs" closure-artifacts \
--workspace "$WORKSPACE_ID"
Follow the returned pagination with --after. Download a listed artifact using its exact revision and a new private destination:
node "$BARUA_SKILL/scripts/owner.mjs" closure-download \
--workspace "$WORKSPACE_ID" --id "$ARTIFACT_ID" \
--revision "$ARTIFACT_REVISION" --output-file "$PRIVATE_EXPORT_FILE"
Keep the revision as the exact decimal value returned. If it changes, read the artifact list again. A redaction hold can temporarily block downloads; do not bypass it with an earlier link or cached copy.
Retention and erasure
The archive window is 30 days from closure unless the owner explicitly extends it. Completion of an export does not restart that window. The owner reference explains extension and person-erasure requests, including the download hold until redaction is verified.
Check closure status for incomplete work before reporting completion. Export availability and workspace closure are separate outcomes.
Account deletion removes the sign-in account through a separate process. Finish workspace obligations and memberships before attempting it.