`resolveTenantId` accepted any truthy tenant value, including the
`SYSTEM_TENANT_ID` sentinel that `runAsSystem()` installs for background
work. The expired-file sweep runs entirely under `runAsSystem()`, so on
deployments without multi-tenant onboarding (`file.tenantId` undefined)
it minted Code API tokens claiming `tenant_id: '__SYSTEM__'`.
The Code API derives its storage namespace from that claim, so the
re-derived session key never matches the one cached at upload time and
the delete is rejected with 403. `deleteCodeEnvFile` only treats 404/405
as already-gone, so `expiredAt` is never cleared and the same files are
retried on every sweep cycle and every process boot.
Treat the sentinel as absent tenant context, consistent with every other
identity-bearing `getTenantId()` consumer, so resolution falls through to
`CODEAPI_JWT_SINGLE_TENANT_ID` (both sides default to `legacy`) or fails
fast under `TENANT_ISOLATION_STRICT`.