Cleanup used resource-specific trash and block-removal operations
Notion's resource model uses page updates to trash pages and database entries and block removal for child blocks and database blocks. It does not expose permanent page deletion. Opus made a second enumeration pass to remove two verification paragraphs and an orphaned database created by earlier work; Sonnet cleaned its resources in one pass. Both agents verified that the shared test page was clean. The extra Opus pass was caused by artifacts from earlier tasks, not a failed cleanup response. Resource-specific lifecycle operations require orientation, but the audit measured autonomous completion and no permanent-delete requirement.
How can I reproduce this?
Requires: Notion internal connection token with access to a test page
- Create a test page, then add a child block (e.g. a paragraph).
- Archive the page: PATCH /v1/pages/{id} with { "archived": true }.
- Try deleting the page directly: DELETE /v1/pages/{id}.
- Delete a block: DELETE /v1/blocks/{id}.
Expected: Trash/archive via PATCH returns 200; DELETE /v1/pages/{id} returns 400 "invalid_request_url"; DELETE /v1/blocks/{id} returns 200 for removable block resources. No permanent page-delete endpoint is exposed.
Evidence · transcript moments