fix(resource-deleter): await integration teardown and self-heal setup

[ajimae]

The bug

packages/resource-deleter/test/integration/cli.spec.ts discarded the promise in its teardown:

afterAll(async () => {
  await Promise.each(Object.keys(resources), (name: MethodNames) => {
    clearData(apiConfig, name);      // no `return`
  });
}, 45000);

Promise.each therefore had nothing to await. Teardown resolved immediately while the deletes were still in flight, and Jest tore the process down mid-request, leaving fixtures behind in the shared test project.

The beforeAll directly above it returns correctly (return createData(...), line 64), as does the other teardown at line 278 — this one was the outlier.

Why it was not self-correcting

beforeAll seeded without clearing first, so once residue existed it was permanent. Every subsequent run died at fixture setup with:

BadRequest: A duplicate value '"fooCatKey"' exists for field 'key'.

Because the failure is in a before* hook, it cascades to every test in the suite — including should print the module version given the version flag, which never calls the API. That is why recent runs showed 23 failures across 3 suites with a single underlying cause.

The fix

1. return the promise in afterAll so teardown actually completes.
2. Clear before seeding in beforeAll, so an interrupted run heals itself on the next attempt. This mirrors what personal-data-erasure already does (await Promise.all([clearData(...)]) before creating).
3. Setup timeout 30s → 60s to cover the added clear step.

Verification

• yarn typecheck → exit 0
• yarn lint → exit 0

The integration tests themselves need project credentials, which are only injected in CI, so they could not be exercised locally — CI on this PR is the real check.

Note

This fixes the leak going forward. Any fooCatKey category (and the published product behind Product cannot be deleted as long as it is published in a catalog) already stranded in the shared test project still needs a one-time manual purge, or the new clear-before-seed step will handle it on the first run — whichever lands first.

🤖 Generated with Claude Code

[changeset-bot]

⚠️ No Changeset found

Latest commit: d752dbd

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR