docs(driver-tests): drop vitest name filter

[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

• docs(driver-tests): repair progress tracker #4893
• docs(driver-tests): drop vitest name filter #4892 👈 (View in Graphite)
• chore(driver-test-runner): add native/wasm runtime matrix to skill #4884 : 3 other dependent PRs (#4894 , #4896 , #4901 )
• chroe: rename rivetkit-sqlite to depot-client #4883
• fix(rivetkit-wasm): fix mem leaks #4880
• chore(rivetkit): wasm support #4860
• feat(sqlite): add cold read benchmarks and simplify optimizations #4857
• feat(sqlite): benchmark cold reads #4848 : 1 other dependent PR (#4864 )
• docs(actors): document manual lifecycle controls #4847
• test(sqlite): expand db stress coverage #4846 : 1 other dependent PR (#4849 )
• test(raw-websocket): add serverless smoke coverage #4845
• feat(serverless): configure drain grace period #4844
• fix(publish): enable frontend build for engine target and use turbo build instead of turbo build:engine #4843
• feat(rivetkit): expose conn handle in onWebSocket context #4842
• fix(rivetkit): normalize waitUntil/keepAwake promises to null to avoid serde undefined error #4841
• fix(rivetkit): remove requirement for token #4839 : 1 other dependent PR (#4840 )
• fix(pegboard-envoy): allow sqlite requests across lifecycle states #4838
• fix(pegboard): route scoped actor key reads by runner dc #4837
• fix(sqlite-storage): let sqlite open take over stale owners #4834
• fix(engine-tests): parallelize multi-DC startup + enable 6 multi-DC tests #4833
• fix(api): honor cursor in actor_ids list path #4832
• fix(api): silently filter invalid IDs from actor_ids query instead of 400 #4831
• fix(api-peer): make actors_delete idempotent for already-destroyed actors #4830
• fix(pegboard): use Iterator streaming mode in list_names so limit param is honored #4829
• chore(engine-tests): convert envoy tests to Sleep crash policy + triage ignored #4828
• feat(engine-tests): wire envoy actor names through prepopulate_actor_names #4827
• chore(depot): fault injection tests #4868
• feat(sqlite): pitr & forking #4859 : 1 other dependent PR (#4863 )
• chore(sqlite): stateless storage refactor #4856
• main

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

[claude]

Code Review

Overview

This PR updates the driver-test-runner skill documentation to remove Vitest -t name filtering from the driver test commands. The change recognizes that environment variables already constrain the test matrix to a single runtime/backend/encoding cell, making the regex-based -t filter redundant — and potentially harmful to describe.sequential ordering.

---

Analysis

Correctness

The change is sound. Since RIVETKIT_DRIVER_TEST_RUNTIME, RIVETKIT_DRIVER_TEST_SQLITE, and RIVETKIT_DRIVER_TEST_ENCODING already gate which describe block runs, adding a -t regex is pure noise. More importantly, the project's testing conventions confirm that describe.sequential ordering can be disrupted by Vitest name filtering, so removing -t is the correct fix for any flakes caused by out-of-order execution.

Documentation quality

• The new note ("Do not use Vitest -t for driver matrix cells") is placed immediately before the base command — exactly where a reader executing the steps would see it. Good placement.
• The substitution guide now correctly drops the <SUITE_DESCRIPTION> placeholder from commands while retaining it in the progress-file description, which avoids confusion between the two contexts.
• The debugging section adds a concrete alternative (describe.only) and an explicit prohibition against using -t as a flake workaround. This aligns with the project's rule against papering over flakes (see CLAUDE.md: "Never paper over flakes with retry loops or bumped waits").

Style

All prose follows project comment conventions: lowercase, complete sentences, no em dashes, no unnecessary parentheticals.

---

Minor Suggestions

• The file-to-suite-description mapping table is still present even though <SUITE_DESCRIPTION> is no longer used in commands. Consider adding a short note in the table header clarifying it is retained for human-readable progress tracking only (e.g., "Suite descriptions below are for the progress file only; they are not passed to pnpm test"). This prevents a future reader from wondering whether the table is still actionable.
• The describe.only workaround guidance already mentions removing .only before committing — this is handled well.

---

Summary

Small, targeted documentation fix with clear motivation and no code risk. The change improves clarity, prevents a class of flakes, and is consistent with the project's testing conventions. No blocking issues.