test(rivetkit): tag sleep routing workarounds

[NathanFlurry]

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How Has This Been Tested?

Please describe the tests that you ran to verify your changes.

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[NathanFlurry]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• test(rivetkit): tag sleep routing workarounds #4665 👈 (View in Graphite)
• fix(test): stabilize lifecycle, sleep, queue, and run edge cases #4660 : 1 other dependent PR (#4664 )
• test(rivetkit): re-enable gateway URL and direct-registry coverage #4659
• chore(engine): publish engine bases in ci #4649 : 2 other dependent PRs (#4650 , #4652 )
• chore: lockfile lefthook #4647
• fix(rivetkit): surface native sqlite kv errors to callers #4645
• fix(rivetkit): prevent sleep races during disconnect and db work #4644
• fix(rivetkit): isolate engine envoys and propagate startup failures #4643
• test(rivetkit): remove wasm sqlite-only fixtures and coverage #4642
• chore(sqlite-vfs): remove wasm sqlite packages and workspace wiring #4641
• chore(rivetkit): remove wasm sqlite runtime #4614
• fix(sqlite-native): restore native startup kv preload #4639
• fix(sqlite-native): delete metadata before chunk range #4638
• fix(sqlite-native): keep truncate cache coherent #4637
• fix(sqlite-vfs): use delete range for truncate cleanup #4636
• fix(sqlite-native): restore kv error hook #4635
• perf(sqlite-native): avoid cloning cached read chunks #4634
• perf(sqlite-native): gate kv operation labels #4633
• perf(sqlite-native): reuse read cache for partial writes #4632
• perf(sqlite-native): remove delete file existence probe #4631
• fix(sqlite-native): gate native read cache behind env var #4630
• fix(pegboard): isolate runner config dc lookup failures #4625 : 1 other dependent PR (#4626 )
• docs(pegboard): note runner config upsert split write risk #4624
• fix(pegboard): unpack global runner config keys correctly #4623
• fix(pegboard-gateway): enforce tunnel message state #4622
• fix(pegboard-runner): clear terminal tunnel routes #4621
• fix(pegboard): skip protocol version keys in runner pool backfill #4620
• fix(pegboard): create missing normal runner configs #4619
• fix(epoxy): reuse cached optimistic value #4618
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[claude]

Code Review

Overview

This PR tags all existing sleep/wake timing workarounds in the driver test suite with TODO(RVT-6193) comments, making them traceable to a single ticket. It also converts one HACK: comment into the standard TODO format. No functional code changes -- pure documentation cleanup.

What is Good

• Consistent tracking: All 9 workaround sites now reference RVT-6193, making it easy to find and remove them all once the underlying routing fix lands.
• Module-level context: Adding the TODO above function declarations is helpful -- a reader landing in the file gets the why before encountering the individual wait calls.
• Comment style matches conventions: Complete sentences, no em dashes, no fragmented structures. Follows CLAUDE.md comment guidelines correctly.
• HACK converted to TODO in actor-sleep.ts is a direct improvement -- the old label was opaque.

Minor Suggestions

• The module-level comments say "several tests below use fixed waitFor windows". Being specific about the count would make it easier to verify completeness when cleaning up, though "several" is fine given the count could change.
• Consider whether the module-level TODO should sit above the function it precedes vs. at the top of the file. For actor-sleep-db.ts and others where it sits above the exported test function, a top-of-file placement might be slightly more discoverable.

No Issues Found

No correctness, performance, or security concerns -- this is a comment-only change with no risk surface. Test behavior is unchanged.

This PR is straightforward and ready to merge once it comes out of draft. The TODO tagging is the right move before implementing the actual routing fix in RVT-6193.