@@ -17,7 +17,7 @@ The dispatcher is the central routing component that:
 4. Serves prefixes registered by the kernel services above. Plugins that need
    a code handler mount it imperatively on the `http.server` service (resolve
    it from the plugin context on `kernel:ready`) — the manifest's
-   `contributes.routes` key was removed in @objectstack/spec 17 (#10726):
+   `contributes.routes` key was removed in @objectstack/spec 17 (commit bc56e1881):
    nothing ever read it, and authoring it is now a tsc error and a parse
    error carrying that prescription.
 
 
@@ -109,7 +109,7 @@ absent here is a protocol gap, not a tier question.
 ONE shape, no second list: a `door: 'none'` code is a row like any other —
 the string under the package that stamps it, and a comment that states its
 `status` and the reachability reading ("no HTTP door on this tree; the
-thrown value is the boundary"). Until #16649 the dispatcher vocabulary
+thrown value is the boundary"). Until commit 44c917a47 the dispatcher vocabulary
 (`packages/runtime/src/dispatcher-error-vocabulary.ts`) carried a
 `boot-refusal` verdict that recorded that same reachability for the codes
 NOT yet registered; it is RETIRED, because the gate below now refuses it —
@@ -125,7 +125,7 @@ it, `error.code` carries the specific code instead of the status-derived
 member plus `declaredCode`. The `declaredCode` demotion (#9106) stays for
 genuinely unknown / third-party spellings only.
 
-EVERY published package's `src/**` is held to this mechanically — #16649
+EVERY published package's `src/**` is held to this mechanically — commit 44c917a47
 widened the rule from `packages/spec/src/**` alone, which is all #16449
 could afford to measure. `check:dispatcher-error-vocabulary` refuses to
 classify a stamp site under one as anything but `foreign-vocabulary` (a
@@ -172,7 +172,7 @@ host boot matching is not wire vocabulary.
 boot refusal that ships in `dist` is owed a row, so the codes left out or
 retired on the "not wire vocabulary" reasoning were registrations owed
 under the ruling, not re-argued per card — #16449 registered the nine
-measured on its tree, and #16649 the fourteen `boot-refusal` rows
+measured on its tree, and commit 613bfbd3d the fourteen `boot-refusal` rows
 `dispatcher-error-vocabulary.ts` still carried, among them
 `MONGODB_MULTI_TENANT_UNSUPPORTED` itself, back under
 `@objectstack/driver-mongodb` with the #8035 removal reversed on the
 
@@ -35,7 +35,7 @@ Architecture Alignment:
 // registered by plugin-hono-server; `examples/app-showcase`'s
 // recalc-endpoint is a real consumer of this exact shape). The worked
 // manifest example that used to sit here declared `contributes.routes`,
-// which was removed in @objectstack/spec 17 (#10726): nothing ever read
+// which was removed in @objectstack/spec 17 (commit bc56e1881): nothing ever read
 // it, so every route it showed parsed cleanly and served nothing.
 class RestApiPlugin {
   name = 'rest_api';