docs(ci): remove the deleted publication benchmark from lane guidance (#184440)

docs(ci): remove the deleted publication benchmark from lane guidance

The Node test-lane guide still described release coverage from the keyed-publication benchmark, which #166939 deleted along with its release-inventory entry. The test file is absent on main. This removes the obsolete bullet; test inventories and CI selection are unchanged. Docs only.

Thanks @wyf027.

Co-authored-by: Ayaan Zaidi <hi@obviy.us>

docs/ci/scope-and-routing/node-test-lanes.md

@@ -62,7 +62,6 @@ The slowest Node test families are split or balanced so each job stays small wit
 - The planner's `RELEASE_ONLY_TOOLING_SHARDS` set and matching maintainer leaves in mixed fast configs defer the complete maintainer-tooling family on unrelated PRs. The tooling Vitest configs own the ordinary inventory and isolated/Docker catalogs. Maintainer leaves selected by fast configs retain their ordinary, isolated, or fake-timer owner and process pins; filtering mixed groups preserves product neighbors and gives the subsets separate timing identities. Dedicated product E2E and live tests, including the five `test/scripts/*.e2e.test.ts` gates, stay outside this tier. PRs touching a tooling test or owner select its owner files, transitive import consumers, and protected regressions, subject to the explicit release-proof exclusions below: `scripts/**`, `src/scripts/**`, `test/**`, `.github/**`, `config/**`, root package/pnpm inputs, tooling configs, and other inputs classified as tooling by the shared changed-path owner in `scripts/test-projects.test-support.mts`. That owner also covers Docker, agent/Crabbox tooling, app scripts/Fastlane, and extension scripts/package inputs. Directly changed tooling tests retain coverage on their own PRs except for the explicit process proofs. Hourly main and ordinary CI `workflow_dispatch` include the family, including Full Release Validation's `normal_ci` child against the frozen candidate. Its `Run Node test shard` step runs these unchanged tests before regular publication admission; an independent duplicate release test is not required. The existing approved preflight-only beta publication exception remains unchanged. Plugin Prerelease separately owns `agentic-plugins`; CI's plugin exclusion does not control the tooling tier. Fork repositories keep full tooling because they do not use upstream PR targeting. Product tests retain their existing tiers except for the explicit runtime proof inventory below.
 - The explicit `CI_PROOF_TEST_FILES` inventory keeps `test/scripts/frv.release.test.ts` and `test/scripts/install-ps1.release.test.ts` out of PR plans, including directly edited tests. Hourly main, manual CI, and Full Release Validation retain both complete process tours in the standard tooling config. FRV keeps its in-process continuation contracts in `frv.test.ts`; the installer keeps its source guards in `install-ps1.test.ts`. The full locale finalizer proof in `test/scripts/control-ui-locale-finalizer.test.ts` uses the same tier: it executes real generation, provider-request serialization, strict validation, and local Git publication. Direct local invocation and manual/release plans retain it; the fast `control-ui-locale-refresh.test.ts` contracts remain in PR selection. No cases or assertions are removed.
 - The explicit `RELEASE_ONLY_RUNTIME_TEST_FILES` inventory defers measured runtime integration tours from upstream automatic PR and push plans while faster owner tests retain their primary contracts. It covers Doctor configuration and migration compositions, CLI startup, Gateway model/plugin/session and worker-environment tours, and updater, packaging, and storage recovery proofs. The existing release inventory remains: `src/flows/doctor-health.test.ts`, `src/infra/update-managed-service-handoff-foreground.test.ts`, `src/node-host/node-worker-supervisor.recovery.test.ts`, `src/state/openclaw-database-preflight.lifecycle.test.ts`, and all eight `src/config/state-startup-corpus*.test.ts` wrappers. It also retains the real Git archive/deletion matrices in `src/gateway/server.sessions.archive-worktree-lifecycle.test.ts` and `src/gateway/server.sessions.delete-worktree-lifecycle.test.ts`, plus the native/broker child-process retirement matrix in `src/process/supervisor/adapters/child.service-lifecycle.test.ts`. Faster session-lifecycle, identity, worktree-owner, relay-state, and readiness tests remain in automatic CI. The startup-corpus paths owner supplies the complete family in its existing partition order. The files keep their assigned configs, process isolation, runtime prerequisites, worker limits, cases, and assertions. Whole-config CLI filtering uses the shared include and exclusion owner without introducing file stripes or changing its worker and serial-job policy. Parallel groups preserve the reduced coverage timing identity when applying worker policy, so automatic CI samples cannot overwrite full release estimates. Selected owner tests and direct test edits run in upstream PRs and exact-head release-gate substitutes; unrelated paths do not admit the remaining release matrix. Manual CI, Full Release Validation's `normal_ci` child, local full plans, and other repositories retain the complete inventory. The release tier also keeps the separate `published-upgrade-survivor` Docker cell with the published baseline, `legacy-operator-state` scenario, and `auto-auth` restart mode; the synthetic foreground-handoff cases do not substitute for that published-driver × candidate proof.
-- The keyed-publication scale benchmark (`src/gateway/session-row-projection.keyed-marks.benchmark.test.ts`) also uses the runtime release inventory. Full manual CI and Full Release Validation retain its 4,428-row SQLite fixture and 70,000 publications; ordinary PR and hourly main plans defer it. Direct edits still select it on their PRs. The smaller session-row projection tests keep exact-key invalidation, cross-agent isolation, row lookup, and refresh behavior in regular CI. The benchmark stays in the standard Gateway core config with every assertion intact.
 - Ten native maintainer-tooling and release matrices use `RELEASE_ONLY_RUNTIME_TEST_FILES`: `test/scripts/ci-linux-git.test.ts`, `test/scripts/pr-worktree-provision.test.ts`, `test/scripts/pr-worktree-interruption.test.ts`, `test/scripts/pr-merge-outcome.test.ts`, `test/scripts/pr-merge-admission.test.ts`, `test/scripts/pr-merge-rest.test.ts`, `test/scripts/pr-merge-receipt.test.ts`, `test/scripts/pr-merge-recovery.test.ts`, `test/scripts/full-release-validation-at-sha.test.ts`, and `test/scripts/package-acceptance-workflow.test.ts`. Tooling-owner PRs defer these matrices unless their test files change directly; ordinary main and product-only PRs already omit the tooling family. Faster Git-owner, import-closure, hosted merge, completion, state-isolation, and release-contract siblings remain in regular tooling coverage.
 - The same explicit runtime inventory also defers native runner state-cleanup, empty-discovery, and entrypoint matrices, correction-merge integration, and the bundled browser MCP package-manager matrix from tooling-owner PRs. Faster state-lifetime, home-isolation, runner admission, native argument parsing, correction preparation, and bundled MCP artifact tests retain their primary contracts. The complete compositions keep every case and assertion in their assigned configs. Direct test edits still select them; full manual CI, including hourly main and Full Release Validation, retains them.
 - The media-persistence large-corpus proof and SQLite reliability process tour use the same release inventory for heap, sparse-session, large-payload, and composed crash/restore bounds. Ordinary media-migration, local snapshot repository, SQLite snapshot, and Doctor compaction suites keep their primary contracts in regular coverage; the complete resource-scale and process compositions remain in manual and release validation.