Workspace deletion removes protected history before ordinary rows

Context

Database cleanup and external material retention are separate responsibilities.

Decision

Use resumable deletion participants to purge database records. Remove protected integration history before ordinary rows through privileged code; retain extension handler secrets under the current declared policy.

Alternatives Considered

Depend on deletion cascading from the workspace record. Restricted references and protected history require an observable, resumable cleanup sequence.

Consequences

Inventory reports expose records still awaiting cleanup.

Undeclared credential secrets and stored provider material survive database deletion and require a retention decision.

Provisioning seeds a default business calendar through the lifecycle seed ledger.