docs: fix stale and inaccurate README claims

Five corrections found in an audit against the live schema and tree:

* dolt_history_users example used WHERE rowid_val = 42, but the
  vtable's columns are the user table's PK and columns (no
  rowid_val); fix to WHERE id = 42.
* dolt_conflicts shows column "table" (not "table_name") and
  dolt_conflicts_users columns are
  (from_root_ish, base_<col>..., our_<col>..., our_diff_type,
   their_<col>..., their_diff_type, dolt_conflict_id),
  not the generic base_rowid/our_rowid/their_value triple the
  README invented. Update the example and the resolution DELETE
  to use dolt_conflict_id.
* Sysbench: 31 workloads, not 23 (test/sysbench_compare.sh has
  31 make_test() entries).
* Doltlite shell tests: 60+ suites, not 40 (the test/doltlite_*.sh
  file count is 68).
* doltlite_parity.sh: 119 tests, not 110.

Doc-only; no code change.

Author: Tim

README.md

@@ -343,7 +343,7 @@ Two per-table virtual tables for time travel:
 
 ```sql
 -- Every version of every row across all commits
-SELECT * FROM dolt_history_users WHERE rowid_val = 42;
+SELECT * FROM dolt_history_users WHERE id = 42;
 
 -- The table as it existed at a specific commit / branch / tag
 SELECT * FROM dolt_at_users('abc123...');
@@ -494,15 +494,18 @@ View and resolve merge conflicts:
 ```sql
 -- View which tables have conflicts (summary)
 SELECT * FROM dolt_conflicts;
--- table_name | num_conflicts
--- users      | 2
-
--- View individual conflict rows for a table
+-- table | num_conflicts
+-- users | 2
+
+-- View individual conflict rows for a table. Columns are
+-- (from_root_ish, base_<col>..., our_<col>..., our_diff_type,
+--  their_<col>..., their_diff_type, dolt_conflict_id) — one base/our/their
+-- triple per user column, plus per-side diff_type and a stable
+-- dolt_conflict_id for resolution.
 SELECT * FROM dolt_conflicts_users;
--- base_rowid | base_value | our_rowid | our_value | their_rowid | their_value
 
 -- Resolve individual conflicts by deleting them (keeps current working value)
-DELETE FROM dolt_conflicts_users WHERE base_rowid = 5;
+DELETE FROM dolt_conflicts_users WHERE dolt_conflict_id = 5;
 
 -- Or resolve all conflicts for a table at once
 SELECT dolt_conflicts_resolve('--ours', 'users');   -- keep our values
@@ -819,7 +822,7 @@ Doltlite is a drop-in replacement for SQLite, so the natural question is: what
 does version control cost?
 
 Every PR runs a [sysbench-style benchmark](test/sysbench_compare.sh) comparing
-doltlite against stock SQLite on 23 OLTP workloads, with a 2× ceiling enforced
+doltlite against stock SQLite on 31 OLTP workloads, with a 2× ceiling enforced
 by CI. The per-release numbers (reads + writes table) are published with each
 release on the [GitHub releases page](https://github.com/dolthub/doltlite/releases).
 Run `test/sysbench_compare.sh` to reproduce locally.
@@ -845,15 +848,15 @@ invocation).
 
 ### Doltlite Shell Tests
 
-40 test suites covering all features:
+60+ test suites covering all features:
 
 ```bash
 # Run all suites
 cd build
 bash ../test/run_doltlite_tests.sh
 
 # Run individual suites
-bash ../test/doltlite_parity.sh          # SQLite compatibility (110 tests)
+bash ../test/doltlite_parity.sh          # SQLite compatibility (119 tests)
 bash ../test/doltlite_commit.sh          # Commits and log
 bash ../test/doltlite_staging.sh         # Add, status, staging
 bash ../test/doltlite_branch.sh          # Branching and checkout