test: raise the 100k deep-cascade timeout to 60s (CI flake under load)

[andymai]

The recursion-free deep-cascade test (m8-relations.property.test.ts) builds a 100k-link chain before despawning — ~8s locally, but it overran the 30s timeout on a contended CI runner and spuriously failed a docs PR. Bump to 60s (7.5× the local time); the assertion and the decisive DEPTH=100000 are unchanged. Pure CI-robustness fix.

[greptile-apps]

Greptile Summary

Bumps the timeout on the a DEEP (100k) deleteSubject chain despawns without recursion test from 30 s to 60 s to address intermittent CI failures on contended runners. No logic, assertions, or test parameters are changed.

• The only change is timeout: 30_000 → timeout: 60_000 in a single it(...) call in m8-relations.property.test.ts.
• The test itself — including the DEPTH=100000 constant, the BFS-cascade assertion, and the aliveCount check — is untouched.

Confidence Score: 5/5

Safe to merge — this is a one-line timeout increase with no changes to test logic or application code.

The change is narrowly scoped: one timeout value in one test, with all assertions, constants, and cascade logic left intact. There is no risk of masking real slowness at 60 s given that the test runs in ~8 s locally.

No files require special attention.

Important Files Changed

Filename	Overview
packages/relations/test/m8-relations.property.test.ts	Single-line timeout bump for the 100k deep-cascade test from 30s to 60s to prevent spurious CI failures on slow runners.

_{Reviews (1): Last reviewed commit: "test: raise the 100k deep-cascade timeou..." | Re-trigger Greptile}