Covers <ns>.community.delete against real Postgres: - Owner soft-deletes; communities.deleted_at + every owned space's deleted_at flip together (verified by direct SQL on the test pool, so the cascade is observed at the source-of-truth layer). - <ns>.community.list filtering is real SQL — the deleted community drops out of the listing without any in-memory bookkeeping. - getCommunity's deleted_at filter blocks subsequent endpoints: community.space.create returns 404 community-not-found. - owner-required is enforced — an admin in $admin (strictly below owner) gets 403, and so does a stranger; the community stays alive. The router endpoint and softDeleteCommunity adapter method had no unit-test coverage for delete; these e2e tests fill that gap and add real-DB cascade verification on top.