docs(tooling): T-1253 — sweep the live references to retired tool paths

A script scanned every tracked doc, rule, skill, agent, hook and source file
for tooling/ paths that no longer exist, skipping historical records (sprints,
discussions, workshops, governance, generated wiki pages). It found 62. The
ones that tell a reader what to RUN now name the reach verb:

- The atlas skill still sent agents to tooling/atlas, atlas-verify,
  atlas-update-field and atlas-commit-and-sync — about forty lines, all
  retired in T-1285. They now name the `reach atlas` verbs, and the skill
  records that commit-and-sync STAGES by default (--commit to commit) and
  takes --corridor as an option.
- The clerk agent named tooling/clerk-review (now `reach dev clerk`). The Si
  and clerk briefings sent those agents to the retired tooling/db/decision
  and sqlite-query CLIs and to decisions/*.md paths that moved to
  governance/ in the pql migration. They now name pql.
- The ticket-cli rule documented `pql decisions read`, which does not exist;
  `show` already includes the body.
- The culture authoring guide and the RON sources name
  `reach validate ron`, with the same arguments as before.
- The 41 Blender payloads' usage lines ran the retired tooling/blender
  wrapper, and the docstrings still cited pre-carve-out paths. They now read
  `reach blender run <payload>`.
- Doc comments in server/, client/, wiki TOMLs and the domain modules.

What is left is deliberate: "Formerly …" provenance, dated plans and findings
docs, the retired-pipeline doc, and a build-artefact path.

project.yaml 0.4.14 (mirrored to the client). Comment-only, but four touched
files are in the canvas-version registry (trait_catalog_reader.rs, since
T-1289, canvas_sources.py itself, and two client files). The gate is
path-based and has no override. The previous push was rejected on exactly
this.

Three of the edits are stamped ledger sources, so systems.db is regenerated
and the stamp is fresh.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

server/src/atlas/atlas_data_proxy.rs

@@ -3,7 +3,7 @@
 //!
 //! - **Star map** ([`StarMapRequest`]/[`StarMapResponse`]): a session-scoped,
 //!   non-per-body proxy over the static `client/data/star_map_data.json`
-//!   dataset (produced by `tooling/generate-star-map-data.py`). Reads the file
+//!   dataset (produced by `reach atlas map data`). Reads the file
 //!   fresh on every request — no caching, no staleness handling — because the
 //!   client only asks once per session when the Atlas star-map view opens.
 //!   The parsed JSON is passed through as an opaque `serde_json::Value` rather
@@ -79,7 +79,7 @@ pub enum StarMapStatus {
 pub struct StarMapResponse {
     pub status: StarMapStatus,
     /// Verbatim parsed JSON (`_meta`, `nodes`, `edges` — see
-    /// `tooling/generate-star-map-data.py`), re-serialized as MessagePack.
+    /// `reach atlas map data`), re-serialized as MessagePack.
     /// `None` unless `status == Ready`.
     pub data: Option<serde_json::Value>,
 }