fix(spec): correct false CoreServiceName JSDoc claims in contracts/*.ts

[os-elon]

Fixes#9752

What

packages/spec/src/contracts/email-service.ts:11 claimed "Aligned with CoreServiceName 'email' in core-services.zod.ts" — CoreServiceName has no email member (email is subsumed under notification). The runtime slot 'email' is real (@objectstack/plugin-email calls ctx.registerService('email', ...)); only the claim about where the name comes from was false. Corrected to name the real registry slot and its registrant, and to note the relationship to 'notification' — per the card's suggested resolution. No enum member was added (the #9630-class forbidden fix).

Template sweep (triage-instructed)

The "Aligned with CoreServiceName 'X' in core-services.zod.ts" sentence is copied across 16 files in packages/spec/src/contracts/*.ts. Checked every instance against the actual CoreServiceName enum (packages/spec/src/system/core-services.zod.ts): metadata, data, auth, file-storage, search, cache, queue, automation, analytics, realtime, job, notification, ai, i18n, ui.

File	Claimed member	In enum?	Action
auth-service.ts	auth	yes	unchanged (byte-identical)
notification-service.ts	notification	yes	unchanged
automation-service.ts	automation	yes	unchanged
analytics-service.ts	analytics	yes	unchanged
storage-service.ts	file-storage	yes	unchanged
export-service.ts	export	no	fixed — no CoreServiceName slot, no evidenced provider binding at all (no registerService('export', ...) anywhere in the tree, no implementer)
ai-service.ts	ai	yes	unchanged
realtime-service.ts	realtime	yes	unchanged
job-service.ts	job	yes	unchanged
i18n-service.ts	i18n	yes	unchanged
metadata-service.ts	metadata	yes	unchanged
cache-service.ts	cache	yes	unchanged
queue-service.ts	queue	yes	unchanged
email-service.ts	email	no	fixed — primary target; runtime slot 'email' is real, registered by @objectstack/plugin-email, subsumed under notification in the enum
search-service.ts	search	yes	unchanged
seed-loader-service.ts	seed-loader+ "SeedLoaderProtocol in data/seed-loader.zod.ts"	no (both halves)	fixed — no CoreServiceName slot, no registration binding, and SeedLoaderProtocol does not exist anywhere in the repo (not even in data/seed-loader.zod.ts, whose exports are SeedLoaderRequestSchema/SeedLoaderResultSchema/SeedLoaderConfigSchema). metadata-protocol's SeedLoaderService implements the contract by direct construction, not ctx.registerService.

Totals: 16 checked, 13 true (left byte-identical), 3 false (fixed).

data-engine.ts ("Aligned with 'src/data/data-engine.zod.ts'") and llm-adapter.ts ("Aligned with IAIService in ai-service.ts") also contain "Aligned with" sentences but are a different claim shape (pointing at a schema file / sibling contract, not asserting CoreServiceName membership) — out of this sweep's scope, not evaluated for truth here.

Scope

JSDoc prose only — no interface shape, no runtime, no schema changes. No member was added to CoreServiceName. Verified contracts/*.ts JSDoc feeds no generator on this diff: no reference doc under content/docs/references/ embeds these sentences (grepped), and no other source file quotes the "Aligned with CoreServiceName" sentence outside packages/spec/src/contracts/*.ts itself.

Tests

• pnpm --filter '@objectstack/spec' build — clean.
• pnpm --filter '@objectstack/spec' test — full package suite ran (the name filter did not narrow it): 413 test files / 10,987 tests passed.
• pnpm --filter '@objectstack/spec' typecheck — pass.
• Gate list below (all 17 gates the dispatch-time derivation names, re-derived post-diff with node scripts/pm/dispatch-gates.mjs), all green at fee9e2a: check:changeset-gate-self-tests, check:cross-package-test-inputs, check:doc-formula-expressions, check:empty-state, check:liveness, check:merge-driver, check:objectui-changeset, check:spec-parsed-alias, check:strictness-ledger, check:type-source-resolution, check:variant-docs, check-adr-0087-registration.mjs, check-changeset-no-major.mjs, check-cross-package-test-inputs.mjs, check-dev-prereqs.mjs --self-test (matches CI's invocation — the full-workspace-build scan mode is not what CI runs here), check-empty-changeset.mjs, check-affected-docs.mjs (self-test). Plus check:generated (13/13 artifacts up to date — confirms contracts/*.ts JSDoc feeds no generator on this diff) and check:docs (229 generated files in sync), and node scripts/check-nul-bytes.mjs (clean).

Changeset

patch on @objectstack/spec — comment-only, but the JSDoc text is emitted into the published package's .d.ts output, so it is a (very small) user-visible change.

---

Generated by Claude Code

[github-actions]

📓 Docs Drift Check

Nothing in this diff resolved to a documentable surface (no symbol, route or SDK anchor derived from 1 changed package(s)), so this run has no opinion about the docs.

What this run could not see

• 3 changed file(s) yielded no anchor (packages/spec/src/contracts/email-service.ts, packages/spec/src/contracts/export-service.ts, packages/spec/src/contracts/seed-loader-service.ts) — pages documenting those are invisible to this run

Coarse fallback — 115 page(s) merely mention a changed package (the pre-#9192 predicate, kept for the deliberately-wide backstop): node scripts/docs-audit/affected-docs.mjs --json e2899f6bee8214e31a9481854ff0bf6cc97177ce → packageMentionDocs.