# Verification Local only, base 1f01b9dab94fbd62a5cf7a3b188c894005c9aab0. No push, deployment, cron changes or Hermes restart. - RED: corporate-policy.spec.ts failed because corporate-policy module absent before implementation. Integration tests added after implementation; not claimed as strict TDD. - Prisma 5.22 schema validation PASS with explicit unused loopback URL; client generated privately (copied node_modules, not shared generated client). - Additive migration generated with `prisma migrate diff` from exact base schema; applied successfully with `prisma db execute` to disposable PostgreSQL database corporate_test, loopback port 55439 and scratch socket. Existing scratch PostgreSQL binaries used; Docker daemon unavailable. No production credentials used. - `npm run build` PASS (tsc -b). - `CORPORATE_TEST_DATABASE_URL=postgresql://hermes@127.0.0.1:55439/corporate_test node_modules/.bin/jest --runInBand --runTestsByPath src/admin/hermes/corporate.integration.spec.ts src/admin/hermes/corporate-policy.spec.ts src/common/guards/roles.guard.spec.ts src/admin/api-keys.service.spec.ts`: PASS 4 suites / 24 tests. - Five DB-backed HTTP scenarios verify actual Nest controller + service and existing guards: unauthenticated 401/admin scope 403; normalized list/search/meta; key replay and mismatch; actual concurrent duplicate create; exclusive concurrent claims; real held row lock skipped; lease expiration/reclaim and stale token rejection; independent reviewer; DONE receipt and logs; unavailable != zero; parent exclusion and QA rejection BLOCKED; research/source/roadmap/goal/report persistence. App listens on loopback TCP; DB fixture cleanup after suite. - Test API-key validator is a local test double; unauthenticated JWT rejection uses local test Passport strategy. This does NOT prove live production JWT/user lookup or live API-key validity. Existing roles/API-key unit suites passed. AdminModule wiring compiled; whole production AdminModule boot is not exercised because unrelated Redis/settings providers are not started. - No full backend regression suite, frontend/admin/storefront build, worker consumption, Stage runtime or production acceptance asserted. Spec baseline CLI 1.2.3 checked; scoped spec/plan/tasks authored explicitly without overwriting shared scaffolding.