docs(spec): regenerate the build-progress and sharing reference pages from their docblocks, and add the patch changeset (stage 31)

gen:docs output only: the two pages follow the module docblocks that now name
their decisions in words. The changeset records the shipped comment text.

Claude-Session: https://claude.ai/code/session_01DhTqaEHqPVSVnAkjG3jywn
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/20749-reader-needles-in-words.md

@@ -0,0 +1,16 @@
+---
+'@objectstack/spec': patch
+---
+
+Source comments that cited a tracker number now say in words which decision they mean, and the pin tests that read those comments match the new words
+
+Clause-②: no
+
+The package ships its `src/**/*.zod.ts` sources, and `dist` carries the member docblocks. Four of those texts named a decision only by its tracker number. Each now names the decision in words. The pin test that reads each text matches the new words, at the places the old number stood:
+
+- `ai/build-progress.zod.ts`: the cloud card that ruled the build-progress phase vocabulary in, and that owns where the emitter sits, is now "the cloud build-progress card" in all seven places. The consumer's strict-parse carrier is "block 2 of the objectui build-panel card". The `ai/build-progress` reference page is regenerated from the module docblock, so its description now ends with "(the cloud build-progress card, ruling A)".
+- `contracts/approval-service.ts`: the `IApprovalService.continueRestoredRun` docblock says the verb is declared "exactly as the automation-service contract declared" `IAutomationService.cancelRun` / `restoreConsumedSuspension`.
+- `ui/notification.zod.ts`: the tombstone note for the removed `./ui` `Notification` / `NotificationConfig` wrappers is labelled `[dual-source removal]`. The `NotificationAction` removal is called "the no-door retirement".
+- `ui/sharing.zod.ts`: `EmbedConfigSchema` is recorded as removed "at the no-door retirement (ADR-0049 enforce-or-remove)". The `ui/sharing` reference page is regenerated from the module docblock.
+
+Comments and docblocks only. No key, type, default, accepted value, `.describe()` string or export changes.

content/docs/references/ai/build-progress.mdx

@@ -1,13 +1,13 @@
 ---
 title: Build Progress schema — AI Protocol reference
 navTitle: Build Progress
-description: "Build-progress PHASE vocabulary for the data-build-progress stream frame."
+description: "Build-progress PHASE vocabulary for the data-build-progress stream frame (the cloud build-progress card, ruling A)."
 ---
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
 Build-progress PHASE vocabulary for the `data-build-progress` stream frame
-(cloud#2172 ruling A).
+(the cloud build-progress card, ruling A).
 
 ## How to read the claims in this module
 
@@ -26,7 +26,7 @@ therefore carries exactly one of three labels, and none is left bare:
 ## Producer
 
 The cloud AI-studio **agent loop** — deliberately not the tool it just ran.
-**Declared by ruling**: cloud#2172 ruling A owns WHERE in the loop a frame is
+**Declared by ruling**: the cloud build-progress card's ruling A owns WHERE in the loop a frame is
 emitted; this module declares only what such a frame may SAY.
 
 A build turn applies its change through `apply_blueprint` / `apply_edit` and
@@ -76,15 +76,15 @@ repository reachable from here they have zero emitters and zero readers
 (**measured on named reachable sources** — each reading is recorded in the
 source beside its surface: on `BUILD_PROGRESS_PHASES` for the phase, and on
 the `hop` / `tool` field declarations). They stand on a ruling instead
-(**declared by ruling**): cloud#2172 ruled the vocabulary in, and
+(**declared by ruling**): the cloud build-progress card ruled the vocabulary in, and
 objectui#7388 asked the panel to be able to name the phase. That is a good
 reason, and it is not a measurement.
 
 ⛔ No gate watches this. The ADR-0049 liveness ledger is rooted in the
 metadata-type registry, and `BuildProgressFrame` is not a registered
 metadata type, so the liveness job stays green however long these three go
-unused. Two named carriers are meant to close it — cloud#2172 for the
-emitter, objectui#7388 block 2 for the consumer's strict parse. If neither
+unused. Two named carriers are meant to close it — the cloud build-progress card for the
+emitter, block 2 of the objectui build-panel card for the consumer's strict parse. If neither
 lands, the three become enforce-or-remove candidates with nothing watching
 them, and the only thing that notices is a person reading this paragraph.
 

content/docs/references/ui/sharing.mdx

@@ -24,7 +24,7 @@ asymmetry survives as the reason this file reads the way it does:
   `@objectstack/metadata-core` re-exports to the server's doors). Both
   example apps author it (`app-showcase` `inquiry.view.ts`, `app-crm`
   `lead.view.ts`). It is `strictObject` as of #4001 批 14.
-- `EmbedConfigSchema` was **REMOVED** at #5015 (ADR-0049 enforce-or-remove) —
+- `EmbedConfigSchema` was **REMOVED** at the no-door retirement (ADR-0049 enforce-or-remove) —
   see the block below where it stood.
 
 The ledger's classification question is *"who writes this schema's input?"*,