docs(driver-tests): repair progress tracker

[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 👈 (View in Graphite)
• docs(driver-tests): drop vitest name filter #4892
• 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: docs(driver-tests): repair progress tracker

Overview

This PR resolves a raw git merge conflict that was left unresolved in .agent/notes/driver-test-progress.md (the conflict markers <<<<<<< HEAD / ======= / >>>>>>> were still present in the file) and expands the tracker to cover both native (NAPI) and wasm runtimes with a cleaner, more structured format.

What Changed

• Merge conflict resolved: Removes the unresolved conflict markers from the old DB-only tracking session.
• Dual-runtime coverage: Each row now shows [native] [wasm] status, giving a cleaner cross-runtime picture.
• Fast/Slow/Excluded split: Useful categorization that aligns with how the driver-test-runner skill instructs tests to be run.
• Final summary section: Good addition — provides a quick snapshot of overall pass rates and maps failing groups to their root cause (remote-SQLite exec stubs vs. actual bugs).
• Notes section: Documents the three fixes applied during the run and links to .agent/notes/driver-test-complaints.md for the prioritized issue list.

Observations

Minor inconsistency in hibernatable-websocket-protocol row:

- [-] [ ] hibernatable-websocket-protocol | ...

The second column is [ ] (not run) while the Final Summary reports 1/2 fail for native. The wasm column being blank is fine if wasm was never attempted, but it would be clearer to annotate it like other wasm-skipped rows (e.g. [-] with a parenthetical reason) so future runs don't misread [ ] as "pending."

Log section is truncated: Only 6 entries appear after the reformat. The old log had granular per-test timestamps useful for tracing regressions across sessions. If the intent is to keep the log lightweight going forward that is fine, but worth being intentional since .agent/notes/driver-test-progress.md is referenced by the driver-test-runner skill to track state across agent runs.

actor-sleep-db placement: It appears only under Slow Tests now (removed from Fast Tests), which is the correct categorization. Worth confirming the skill's ## Fast Tests section parsing (per CLAUDE.md: "pass only the files listed under ## Fast Tests") is not affected by the removal.

Summary

Clean, well-motivated doc fix. The main nit is the hibernatable-websocket-protocol wasm column inconsistency — [ ] vs [-] is ambiguous when the test was intentionally not run. Everything else looks good.