Use disposable sandbox proof for destructive fuzz mutations

[chubes4]

Summary

• Replace rollback-required REST/CRUD/DB destructive fuzz execution with explicit disposable sandbox boundary validation.
• Record destructive permission, mutation boundary, teardown intent, and sandbox isolation proof on mutation/delete boundary artifacts.
• Update CRUD/DB command guards, descriptors, docs, and tests to use options.destructivePermission instead of rollback/reset write proof.

Tests

• npx tsx tests/playground-public-runtime-primitives.test.ts
• npm run test:wordpress-runtime-actions
• npm run test:wordpress-db-contracts
• npm run test:fuzz-suite-runner
• npx tsx tests/wordpress-crud-contracts.test.ts
• npm run build
• npm run check (fails in unrelated tests/browser-callback-materialization-contracts.test.ts artifact-bundle ref assertion)

AI assistance

• AI assistance: Yes
• Tool(s): openai/gpt-5.5 via OpenCode
• Used for: Implementing the destructive fuzz sandbox boundary contract changes, tests, docs, and PR preparation.