docs(service-datasource): re-anchor the dead tracker citations to the commits that decided them (#20693)

Part of #20596
Clause-②: no

## What changed

This is the fifth stage of the `domain:services` lane of the
dead-citation sweep. It covers
`packages/services/service-datasource/src/**` and nothing else. By the
seat's fresh census at the claim (`5894843429`), it is the largest
package in the lane that no in-flight work holds. Later stages cover the
other packages, so this PR says `Part of` and the card stays open.

Every comment or docblock site in scope that cited a tracker number
answering 404 has been rewritten in ruling C+D's form C (comment
5749154545 on #19123), by the method of stages 1 to 4 (PR #20609 as
`422db788a`, PR #20626 as `b80ab579d`, PR #20634 as `4d04b6be3`, PR
#20658 as `9a4b2bb38`). That is **75 sites on 74 lines in 23 files,
covering 16 numbers**:

- 44 census sites (every census site this package has);
- 31 sites in test comments, which the census defers.

Each rewritten line now cites the commit in `origin/main` history that
decided what the line describes, and says in its own words what was
decided: **17 distinct shas**. `#8696` was one card fixed in two halves,
so its lines cite the half they describe: the mysql DSN branch
(`72050cc47`) or the mongodb DSN branch (`90a12fb18`). `PR #8588` was
itself a pull request, and it now cites its squash commit `3dede582b`.
No number in this package has an ADR or ruling record of its own in the
repository (a grep of `docs/adr/` for all 16 finds none), so every
anchor is a commit, per ruling C's order. No number was dropped.

Only comments changed. Every touched source file keeps its line count
(78 lines out, 78 in, over 23 files), so no line citation into these
files moves. 4 of those 78 lines hold no dead citation; they are reflow,
listed under Wordings below. No code token moves (see the guard below).

**No citation number is added.** Every tracker number on an added line
was already on the line it replaces: the only one is `#12482`, which
resolves and stood on `datasource-connection-service.ts:101` before.
Over the whole diff, added minus removed is 0 or negative for every
number, and no number is new to the diff. No PR number stands on an
added line.

Thirteen dead sites are left on purpose, all of them test titles (see
the list below).

One more file: a `patch` changeset for
`@objectstack/service-datasource`, because the rewritten docblocks ship
(see Changeset below).

## Census: `service-datasource`, before and after

**Instrument (A1).** The gate's own `node
scripts/check-issue-citations.mjs --census --json`, read-only and
unchanged. The count below is its `allocated-but-absent` findings under
`packages/services/service-datasource/`. Each run counts as a reading
only because its board frontier equals the newest issue number, read by
a separate request just before and just after the run.

| reading | tree | board | whole-repo `allocated-but-absent` |
service-datasource sites | lines | files | numbers |
|---|---|---|---|---|---|---|---|
| before | base `6981abfd2`, run 2026-09-29T17:02:34Z to 17:06:27Z |
enumerated, 186 pages, frontier #20684 (newest #20684 before and after),
18,511 numbers | 1,318 | **44** | 43 | 9 | 14 |
| after | head `f5ec6bacd`, run 17:18:37Z to 17:22:33Z | enumerated, 186
pages, frontier #20686 (newest #20686 before and after), 18,513 numbers
| 1,274 | **0** | 0 | 0 | 0 |

The before count matches the seat's census at the claim (44 sites in 9
files, at `6bff748b`). The whole-repo drop is 44, exactly this diff's
census sites. The `resolves` tally is 32,909 in both runs, and
`resolves-as-pull-request` (1,984) and `cross-repo-unjudged` (994) did
not move either. The after run was taken on `f5ec6bacd`; the head
`265dc6861` adds only the changeset. No run was truncated or discarded:
all four enumerations in this stage (two census runs and the two
supplementary boards below) read 186 pages at the newest frontier.

**Supplementary instrument, the whole scope.** The census does not read
test files or strings, and this stage's scope includes test comments. So
a second reading runs the gate's own exported `extractCitations`
(whole-file and comment-prose projections) and `classifyCitation` over
every `.ts` file under `service-datasource/src` (61 files). It uses one
board for both trees, enumerated by the gate's own `enumerateBoard` at
17:22:42Z (186 pages, frontier #20686, equal to the newest).

| reading | citations | dead | src comment | test comment | src string |
test string |
|---|---|---|---|---|---|---|
| before, `6981abfd2` | 791 | **88** | 44 | 31 | 0 | 13 |
| after, `f5ec6bacd` | 716 | **13** | 0 | 0 | 0 | 13 |

Its src-comment column equals the census's 44, which is the control on
the second instrument. The 646 resolving and 57 pull-request citations
are the same in both readings, and the drop of 75 citations is exactly
the rewritten sites. An earlier board (17:07:08Z, frontier #20685) gave
the same base reading. A third, raw reading (every `#` followed by
digits, judged against the same board, whatever surrounds it) finds 88
dead occurrences before and 13 after, and its residue equals the gate's
residue site for site.

## Per-number table

Sites and files count every dead occurrence in scope at the base
(comments and strings, tests included). `rewritten / left` counts the
sites rewritten and the sites left. Each anchor was read in its message
and diff, not only its subject.

| number | sites / files | rewritten / left | anchor: what it decided |
|---|---|---|---|
| `#6268` | 6/4 | 6/0 | `68f5eccb1`: the libSQL/Turso host loader gets
one owner (`@objectstack/runtime`), and `MissingDriverPackageError`
becomes one class across both hosts, because `serve.ts` decides fatality
with `instanceof`. The cli and runtime stages' anchor |
| `#6345` | 9/5 | 9/0 | `e2798fab7`: one driver vocabulary; `mongo`
renamed to `mongodb`, `turso` made a full builtin with a contract, and
this factory's dispatch made exhaustive. The spec stages' anchor |
| `#8588` | 1/1 | 1/0 | `3dede582b`: `external.credentialsRef` (and only
it) allowed on `schemaMode: 'managed'`; `#8588` was that pull request,
and this is its squash commit |
| `#8696` | 13/4 | 10/3 | two halves: `72050cc47`, a bound
`credentialsRef` reaches the mysql client on the DSN branch as `{ uri,
password }` (5 sites); `90a12fb18`, the mongodb DSN branch carries it in
`options.auth` beside an unmodified url (5 sites). The spec stage's
anchor for the mongo half |
| `#8873` | 8/3 | 7/1 | `096106522`: a bound `credentialsRef` reaches
the postgres SERVER on the DSN branch; `connectionString` is dropped and
`pg` gets its own parse of the url with the credential attached. The
spec stage's anchor |
| `#8874` | 9/2 | 7/2 | `d70428ae7`: a declared `ssl` reaches the mysql
client on both branches, in the spelling `mysql2` accepts (`{}`, never
`true`). The spec stage's anchor |
| `#8876` | 1/1 | 1/0 | `d634e665b`: `urlUserinfoUsername` exported, the
username half of the shared URL userinfo grammar. The spec stage's
anchor |
| `#9040` | 4/3 | 2/2 | `24206416a`: a credential in the mongo options
passthrough (`config.options.auth.password`) is refused at publish. The
spec stage's anchor |
| `#9041` | 2/2 | 2/0 | `d491625c1`: a bound `credentialsRef` with a
user-less mongo `config.url` is refused at the one door that sees both
halves. The spec stage's anchor |
| `#10537` | 3/2 | 3/0 | `e634ecf6a`: `POST /external/validate` scoped
to the URL's datasource; it adds `validateDatasource`. The rest and
runtime stages' anchor |
| `#10962` | 5/2 | 4/1 | `29d067646`: one live introspection per
datasource per validation sweep, memoised per call and never per
instance (its message names `#10962`) |
| `#11166` | 5/1 | 4/1 | `735f5c709`: an unreachable remote is the new
`unreachable` diff kind, not `missing_table`. The runtime stage's anchor
|
| `#12010` | 9/5 | 8/1 | `77b91bdb4`: `ConnectionEngineLike` derived
from the engine contract, and `registerDriver` stops promising it
accepts any value. The runtime stage's anchor |
| `#12248` | 1/1 | 1/0 | `8425c17cc`: the ruled engine members adopted
onto `IDataEngine`, the datasource-lifecycle trio among them. The spec
stage's anchor |
| `#12943` | 3/2 | 3/0 | `090f2302e`: the guarded optional-driver loads
declared as optional peers of this package. The cli and runtime stages'
anchor |
| `#13279` | 9/4 | 7/2 | `6a180e42d`: a failed permission-store read
raises `AuthzStoreUnavailableError` (503) instead of reading as zero
grants; its message carries the 2026-08-30 ruling, and it moved
`driver-error-classification.ts` into `@objectstack/types`. The anchor
of stage 2 and of the rest, runtime and types stages |

Every cited sha matches exactly one commit (`git rev-parse
--disambiguate`, count 1 for each of the 17), and every one is an
ancestor of the base (`merge-base --is-ancestor`, exit 0 for all 17; the
history is complete, `--is-shallow-repository` false, 15,110 commits).
Where an earlier stage already anchored a number, this stage reuses that
anchor after checking it against this package's lines. New to the sweep
here: `72050cc47` (the mysql half of `#8696`), `3dede582b` and
`29d067646`.

## Wordings to check

- **`#8696`'s two halves.** The mysql arm's lines
(`default-datasource-driver-factory.ts:718`, `:824`, and
`bound-secret-dsn-branches.test.ts:4`, `mysql-dsn-ssl.test.ts:189`,
`:263`) cite `72050cc47`; the mongo arm's lines
(`default-datasource-driver-factory.ts:926`, `:954`, `:1243`,
`datasource-credential-migration.ts:182`, and the heading
`bound-secret-dsn-branches.test.ts:72`, 「the mongodb half, added
second」) cite `90a12fb18`.
- **A referent, `datasource-connection-service.ts:95-96`.** 「the
inventory that filed that card」 lost its referent with the number, so it
now says 「the inventory that filed its card」, the card behind
`77b91bdb4` (1 reflow line).
- **`datasource-connection-service.ts:100-101`.** 「#12248 adjudicated
all three onto IDataEngine」 became 「Commit 8425c17 adopted all three
onto IDataEngine per the ruling」: the ruling decided and the commit
carried it out, as its changeset says (1 reflow line).
- **What the card described, `default-datasource-driver-factory.ts:412`
and `mysql-dsn-ssl.test.ts:40`.** 「the one #8874 describes as honouring」
became 「the one commit d70428a's card describes as honouring」, since
the words quote the card, not the commit.
- **A cross-reference, `default-datasource-driver-factory.ts:736`.**
「the falsy-value note under #8874 below」 points at the heading at
`:767`, which now carries `commit d70428a`, so the pointer names the
same anchor.
- **A future tense made past, `postgres-dsn-bound-secret.test.ts:223`.**
「the authoring door (#9041), which this card lands before」 became
「(commit d491625), which landed after this pin」. `096106522` (this
file's commit) is an ancestor of `d491625c1`, both on 2026-08-16.
- **`external-datasource-service.test.ts:444`.** 「The card's measured
defect」 became 「Its card's measured defect」, the card behind
`735f5c709`; `:588` 「the pre-#10537 route」 became 「the route … before
commit e634ecf」.
- **`datasource-admin-service.test.ts:674`.** 「Before PR #8588」 became
「Before commit 3dede58」, the squash commit of that pull request, which
answers 404.
- **Reflow, 4 lines with no dead site** (every file keeps its line
count): `datasource-connection-service.ts:96`, `:101`,
`default-datasource-driver-factory.ts:825`, `:826`.

## The 13 sites left

- **Test titles, 13 sites.** `describe` / `it` titles, which are string
tokens, left as stages 1 to 4 left theirs:
`admin-routes-authz-outage-envelope.test.ts:158` (`#13279`);
`admin-routes-tenancy-posture-admission.test.ts:557` (`#13279`);
`bound-secret-dsn-branches.test.ts:136`, `:244` (`#8696`);
`connection-engine-like-contract.test.ts:21` (`#12010`);
`datasource-config-redaction.test.ts:406` (`#9040`);
`datasource-credential-migration.test.ts:226` (`#9040`);
`external-datasource-service.test.ts:453` (`#11166`), `:690` (`#10962`);
`mysql-dsn-ssl.test.ts:165`, `:324` (`#8874`), `:260` (`#8696`);
`postgres-dsn-bound-secret.test.ts:160` (`#8873`).
- There is no operator string, assertion message, generated header or
quoted ruling carrying a dead number in this package. The verbatim
maintainer quotations in scope (「同意」 and 「同意所有」, on 8 lines) carry no
dead number and are untouched.

## Mechanical guard: no code token moves

The guard compares the TypeScript parser's leaf nodes, with comments as
trivia and JSDoc nodes never visited, base `6981abfd2` against head.
Template literals are therefore read in context. It ran over all 23
touched `.ts` files.

- Real run: 24,055 base leaf tokens, **0 files with a token change**
(exit 0).
- Comment control in `default-datasource-driver-factory.ts` (`Lazy +
caught exactly like` to `Lazy and caught exactly like`): 0 files
changed, as expected (exit 0).
- Positive control, a code token added in
`default-datasource-driver-factory.ts` (`const url =
resolveTursoUrl(spec);` given a trailing `?? undefined`): DIFFER (exit
1).
- Positive control, one digit changed inside a kept test title
(`mysql-dsn-ssl.test.ts:165`): DIFFER (exit 1).

Every mutation went through `scripts/ablation-replace.mjs`, and each
landed (anchor 1 to 0, blob changed). Each restore was proven
byte-identical to the HEAD blob (`8c164aa6178f`, `2feeaeb0411d`), with
`git diff HEAD` empty and a clean tree afterwards. A first draft of the
guard used the bare scanner, which loses template context and reported
token changes inside comments; it was replaced by the parser walk before
any reading was taken from it.

## Changeset

This change ships bytes, so a `patch` changeset for
`@objectstack/service-datasource`
(`.changeset/20596-service-datasource-provenance-anchors.md`) is
included. It says only that the provenance comments were re-anchored, in
stages 3 and 4's words.

Measured on the built package (A3): `files[]` is `dist`, `README.md` and
`CHANGELOG.md`. After the build, the rewritten comments reach `dist`:
`6a180e42d`, `e2798fab7` and `e634ecf6a` once, and `29d067646` three
times, in each of `dist/index.d.ts`, `index.d.cts`, `index.js` and
`index.cjs`; `68f5eccb1` 4 times, `090f2302e` twice, and `77b91bdb4` and
`8425c17cc` once each, in both declaration files. Positive control: the
unchanged line 「`registerDatasourceDef`, `markDatasourceUnavailable`,」
beside the shipped rewrite at `datasource-connection-service.ts:95` is
found once in `index.d.ts`. A never-written negative phrase appears
nowhere in `dist`. No dead number of the 16 is left anywhere in `dist`.

## Gates (head `265dc6861`)

- **Citation judging, as CI runs it:** `pnpm check:issue-citations`
(self-test) exits 0. `node scripts/check-issue-citations.mjs` exits 0:
the diff-scoped run judged 1 citation (`#12482`), and it resolves.
- **Doc authoring:** `pnpm check:doc-authoring` exits 0, with the
sibling-package prose ids at their baseline and no growth.
- **Derived gates:** `node scripts/pm/dispatch-gates.mjs --commands
--repo objectstack-ai/objectstack` at `265dc6861` derived 63 commands:
all 54 derived at dispatch, plus `check:duration-unit-keys`,
`check:dispatcher-error-vocabulary`, `check:engine-double-contract`,
`check:logger-receiver-detach`, `check:objectql-double-limit`,
`check:query-options-erasure`, `check:type-check-coverage`,
`check:type-check-debt` and `check:where-matcher`. Each ran with its
exit code captured before any pipe, and all 63 exit 0. `--ran`, fed each
command with its exit code, reports 63 run, 0 NOT MEASURED (a derived
zero), 0 unrun, and exits 0. A full `turbo run build` of `./packages/*`
and `./packages/*/*` ran first under the shared verify lock (71 of 71
tasks, exit 0), so no gate hit an unbuilt workspace.
- **Roster families the derivation lists outside its commands** (their
rosters sit in directories this diff touches): `node
scripts/check-changeset-fixed.mjs`, `pnpm check:authz-resolver`, `pnpm
check:error-code-casing` and `pnpm check:filter-alias-parity`, each exit
0.
- **Tests and typecheck, under the verify lock:**
- `pnpm --filter @objectstack/service-datasource test`: 34 files pass
and 693 tests pass. That is every test file in the package, the 14
touched ones included.
- `pnpm --filter @objectstack/service-datasource typecheck` exits 0. Its
`tsconfig.json` includes all of `src`, and `--listFiles` shows all 61
files under `src/`, the 34 test files included, and all 23 touched files
in the program.
- **Lint, as a proven narrowing:** `eslint --no-inline-config --format
json` over the 23 touched `.ts` files gives 23 files, 0 errors and 0
warnings. All 23 are in eslint's own population (`isPathIgnored` is
false for each). `eslint.config.mjs` never enables type-aware linting
(no `parserOptions.project`, as its own lines 327-328 state), so a
comment edit here cannot move the verdict on any untouched file. The
repo-wide `pnpm lint` is CI's run.
- **Control bytes:** `pnpm check:nul-bytes` exits 0, and a raw scan of
the 24 changed files for control bytes finds none.

## Acceptance notes

- **The gate-invisible spellings, grepped as the claim asked.**
`CITATION_RE` refuses a hyphen after the digits and a `/` before the `#`
(#20636). In this package there is no `#N-word` spelling at all. There
are 7 `#A/#B` lines (`admin-routes.ts:28`,
`datasource-route-ledger.ts:159`, `turso-driver-config.ts:132`,
`external-introspection-seam.test.ts:14`, `:102`, `:163`,
`turso-bound-secret-authoring.test.ts:8`), and every second number on
them is live: `#10998`, `#4251` and `#4249` are issues, and `#8078`,
`#4176` and `#4202` are pull requests. So nothing there needed
rewriting. The raw scan above, which sees both spellings, agrees.
- **The census instrument did not truncate in this stage.** Four
enumerations read 186 pages each at the newest frontier.
- **Anchors the next stages can reuse**, each checked here: `#13279` →
`6a180e42d`; `#12010` → `77b91bdb4`; `#6345` → `e2798fab7`; `#6268` →
`68f5eccb1`; `#12943` → `090f2302e`; `#8696` → `72050cc47` (mysql) or
`90a12fb18` (mongodb); `#8873` → `096106522`; `#8874` → `d70428ae7`;
`#10962` → `29d067646`.
- **Base.** The branch is 5 commits behind `origin/main` (`14f80e239`,
read at 17:27Z). None touches `service-datasource`, `scripts/` or
`.changeset/config.json`, so there was no merge.

---
_Generated by [Claude
Code](https://claude.ai/code/session_01XY5uCwTjZj7884yYtyur4H)_

---------

Co-authored-by: Claude <noreply@anthropic.com>

Author: objectstack-fleet[bot]

.changeset/20596-service-datasource-provenance-anchors.md

@@ -0,0 +1,10 @@
+---
+'@objectstack/service-datasource': patch
+---
+
+Provenance comments in `service-datasource` were re-anchored
+
+Comment and docblock lines under `src/` that cited tracker numbers which no
+longer resolve on GitHub now cite the commit in this repository's history that
+decided the matter, and say in their own words what was decided. Comments
+only: no type, schema, export, log or refusal text, or runtime behaviour changes.

packages/services/service-datasource/src/__tests__/admin-routes-authz-outage-envelope.test.ts

@@ -24,7 +24,7 @@
  *     turns exactly that into `AuthzStoreUnavailableError`: declared `status:
  *     503`, declared `code: SERVICE_UNAVAILABLE`.
  *  3. `requireDatasourceAdmin`'s own `catch` re-raises it rather than
- *     laundering an outage into a denial — the #13279 ruling, which this card
+ *     laundering an outage into a denial — commit 6a180e42d's ruling, which this card
  *     leaves completely untouched. Only the RENDERING moves.
  *  4. The throw escapes the handler. Before this card the adapter answered
  *     `500 { code: 'INTERNAL_ERROR', message: 'No response from handler' }` —
@@ -50,7 +50,7 @@
  * ⭐ The controls answering `401` rather than `200` is the SHARPER reading, and
  * it is the discriminator this card is actually about: a 401 is a VERDICT the
  * door reached, while the outage arm reaches no verdict at all — which is
- * exactly why #13279 refuses to answer it as a denial. Two different 4xx/5xx
+ * exactly why commit 6a180e42d refuses to answer it as a denial. Two different 4xx/5xx
  * answers separated by whether a decision was ever taken.
  */
 
@@ -159,7 +159,7 @@ describe('GET /api/v1/datasources — an authz-store outage reaches the caller a
     const { listDatasources } = await list({ kind: 'throws' });
 
     // The card moves the RENDERING only. If the outage started resolving to a
-    // verdict, this would be non-zero and #13279 would have been reversed as a
+    // verdict, this would be non-zero and commit 6a180e42d would have been reversed as a
     // rider.
     expect(listDatasources).not.toHaveBeenCalled();
   });

packages/services/service-datasource/src/__tests__/admin-routes-tenancy-posture-admission.test.ts

@@ -537,7 +537,7 @@ describe('[#15350] §5b — a `tenancy` service that was REGISTERED and FAILED i
     // handler"), not the `503 SERVICE_UNAVAILABLE` the brand carries. That is a
     // PRE-EXISTING relay gap, not one this card opened — `requireDatasourceAdmin`
     // has re-raised `AuthzStoreUnavailableError` for the identical `ql`
-    // permission-store outage since #13279, out of route handlers that have no
+    // permission-store outage since commit 6a180e42d, out of route handlers that have no
     // `catch`, and the Hono adapter renders any escaped throw as a bare 500. It
     // is filed separately. Asserting the class rather than the digits keeps this
     // pin measuring the SECURITY property — the outage is never answered as an

packages/services/service-datasource/src/__tests__/bound-secret-dsn-branches.test.ts

@@ -1,7 +1,7 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
 
 /**
- * #8696 — a bound `external.credentialsRef` reaches the client on the mysql
+ * Commit 72050cc47 — a bound `external.credentialsRef` reaches the client on the mysql
  * arm's DSN branch, not only on its discrete-fields branch.
  *
  * ## The defect
@@ -69,7 +69,7 @@
  * The first failure is the whole defect in one line: the arm answered with the
  * DSN *string*, which has no key for a credential to live in.
  *
- * ## The mongodb half, added second (#8696's remaining arm)
+ * ## The mongodb half, added second (commit 90a12fb18, the remaining arm)
  *
  * `buildMongoUrl`'s `if (explicit) return explicit;` dropped the bound secret
  * the same way, and is closed by `buildMongoAuth` — `options.auth` beside an

packages/services/service-datasource/src/__tests__/connection-engine-like-contract.test.ts

@@ -1,7 +1,7 @@
 // Copyright (c) 2026 ObjectStack. Licensed under the Apache-2.0 license.
 
 /**
- * [#12010] The seam pin for `ConnectionEngineLike`.
+ * [commit 77b91bdb4] The seam pin for `ConnectionEngineLike`.
  *
  * `ConnectionEngineLike` is the exported view `DatasourceConnectionService`
  * drives the ObjectQL `'data'` engine through. It used to re-declare seven
@@ -55,7 +55,7 @@ describe('ConnectionEngineLike is the contract, not a fork of it (#12010)', () =
   it('refuses a value that is not a driver, at the call site', () => {
     const engine = {} as ConnectionEngineLike;
     // @ts-expect-error - a bare `{ name }` is not an `IDataDriver`. This call
-    // compiled before #12010, which is precisely the hole: the seam promised
+    // compiled before commit 77b91bdb4, which is precisely the hole: the seam promised
     // the engine accepts any value as a driver, and it does not.
     engine.registerDriver?.({ name: 'com.example.not-a-driver' });
     expect(engine).toBeTruthy();

packages/services/service-datasource/src/__tests__/datasource-admin-service.test.ts

@@ -671,7 +671,7 @@ describe('migrateCredential (#8155)', () => {
 
 /**
  * The contract half the #8153 block was about: the row this migration WRITES
- * must be spec-valid. Before PR #8588 a managed row carrying
+ * must be spec-valid. Before commit 3dede582b a managed row carrying
  * `external.credentialsRef` failed re-parse, so the migration would have moved
  * rows from "invalid because it holds cleartext" to "invalid because it holds a
  * credentialsRef" while reporting success.

packages/services/service-datasource/src/__tests__/datasource-config-redaction.test.ts

@@ -404,7 +404,7 @@ describe('GREEN ON MAIN — #8078 is not weakened by anything above', () => {
 });
 
 describe('#9040 — the passthrough spelling, both halves at the service door', () => {
-  /** A legacy mongo row written before #9040: the password rides the MongoClient passthrough. */
+  /** A legacy mongo row written before commit 24206416a: the password rides the MongoClient passthrough. */
   const LEGACY_MONGO: StoredDatasource = {
     name: 'legacy_mongo',
     driver: 'mongodb',

packages/services/service-datasource/src/__tests__/datasource-connection-service.test.ts

@@ -45,7 +45,7 @@ function fakeEngine() {
     registerDatasourceDef: (def) => {
       defs.push(def);
     },
-    // [#12010] The double deliberately stores MINIMAL stand-ins (a bare
+    // [commit 77b91bdb4] The double deliberately stores MINIMAL stand-ins (a bare
     // `{ name }` is how these tests simulate an `onEnable`-registered
     // driver), while the derived seam member answers the contract's
     // `IDataDriver | undefined`. Narrowing on the way out keeps the double

packages/services/service-datasource/src/__tests__/datasource-pool-support.test.ts

@@ -162,7 +162,7 @@ describe('#5714 — which driver arms read a declared `pool`', () => {
   // literal as it stood on `origin/main` before this change, because "we only
   // added an arm" is a claim about bytes.
   // Byte-for-byte as #5714 wrote it, with ONE word changed: the closing clause
-  // names the pooled drivers, and #6345 renamed the canonical mongo id to
+  // names the pooled drivers, and commit e2798fab7 renamed the canonical mongo id to
   // `mongodb`. Naming the retired canon in an instruction the author is meant to
   // act on would send them to a spelling the catalog no longer publishes.
   it('leaves the sqlite arms\' message byte-for-byte as #5714 wrote it', () => {
@@ -305,7 +305,7 @@ function fakeEngine() {
     drivers,
     registerDriver: (driver: any) => { drivers.set(driver.name, driver); },
     registerDatasourceDef: () => {},
-    // [#12010] The double deliberately stores MINIMAL stand-ins (a bare
+    // [commit 77b91bdb4] The double deliberately stores MINIMAL stand-ins (a bare
     // `{ name }` is how these tests simulate an `onEnable`-registered
     // driver), while the derived seam member answers the contract's
     // `IDataDriver | undefined`. Narrowing on the way out keeps the double

packages/services/service-datasource/src/__tests__/default-datasource-driver-factory.test.ts

@@ -371,7 +371,7 @@ describe('createDefaultDatasourceDriverFactory — legacy config spellings are n
 // #7314 — the OPTIONAL libSQL driver is missing, and until now this arm said so
 // and stopped: `turso driver requested but @objectstack/driver-turso is not
 // installed (…)`. The HOST loader (`@objectstack/runtime`'s
-// `loadTursoDriverFactory`, single owner since #6268) has answered the same
+// `loadTursoDriverFactory`, single owner since commit 68f5eccb1) has answered the same
 // missing package with the install command, the consequence and the reason for
 // refusing since #5602 — so the SAME fault got two qualities of answer depending
 // on whether the datasource happened to be the host's `default` (told how to fix
@@ -437,7 +437,7 @@ describe('createDefaultDatasourceDriverFactory — the missing libSQL package is
   });
 
   it('is what the turso arm actually raises when the optional package is absent', async () => {
-    // ⭐ STAGED absence since #12943 — this case used to reach the arm with NO
+    // ⭐ STAGED absence since commit 090f2302e — this case used to reach the arm with NO
     // stub, and that is no longer possible. `@objectstack/driver-turso` is now
     // an OPTIONAL PEER of `@objectstack/service-datasource`
     // (`peerDependencies` + `peerDependenciesMeta.optional`): the honest