T1 (audit-action rename in #93):
- Updated the user force-delete test to look up audit_logs by
action = ANY(['user.delete', 'user.force_delete']).
- Updated the app force-delete test to look up audit_logs by
action = ANY(['app.delete', 'app.force_delete']).
- Used array-of-actions matchers (forward-compatible with the old
name in case anything else still emits it).
- The service force-delete test was left untouched because
artifacts/api-server/src/routes/services.ts still emits
'service.force_delete' (only user/app/group were renamed in #93).
T2 (services per-run uniqueness + defensive sweep):
- Added module-level SVC_STAMP and SVC_PREFIX = `TestSvc_<stamp>_`.
- Renamed the three services-test name_en literals to
`${SVC_PREFIX}Clean`, `${SVC_PREFIX}Busy`, `${SVC_PREFIX}Force`
so re-running the file no longer collides on services_name_en_unique.
- Now pushes every created service id to createdServiceIds (clean +
busy + force), not just busy.
- Added a defensive sweep in after() that, after the tracked-id
cleanup, deletes any leftover services whose name_en starts with
SVC_PREFIX, plus their child rows in service_orders. This mirrors
the apps-side sweep added in Task #116.
Pre-existing pollution cleanup:
- Removed the orphan rows left over from the failed 2026-04-28
test runs (services ids 166/168 = 'Clean Svc'/'Force Svc',
user ids 4397/4889 = del_force_*) and their child rows. These
predate the fix; removing them now keeps the workspace clean.
Verification:
- pnpm --filter @workspace/api-server node --test
tests/delete-force-warnings.test.mjs: 9/9 PASS twice in a row.
- Post-run sweep query: 0 leftover apps, 0 leftover services with
the test prefixes, 0 leftover admin users.
Out of scope (not touched):
- Other test files in artifacts/api-server/tests/.
- The audit-action rename itself (already merged in #93).
- The wider failing `test` workflow — its other failures are
unrelated to this file.
Riyadh
f587e49dba