fix(spec): file-description skips doc blocks the lazify codemod detached from their symbols (#13336)

* fix(spec): file-description skips doc blocks the lazify codemod detached from their symbols

* chore(spec): regenerate reference pages and skill indexes for the tightened selection rule

---------

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

Author: claude[bot]

content/docs/references/api/discovery.mdx

@@ -5,16 +5,6 @@ description: Discovery protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Service Status Enum
-Describes the operational state of a service in the discovery response.
-
-- `available`   – Fully operational: service is registered AND HTTP handler is verified.
-- `registered`  – Route is declared in the dispatcher table but the HTTP handler has
-                  not been verified (may 501 at runtime).
-- `unavailable` – Service is not installed / not registered in the kernel.
-- `degraded`    – Partially working (e.g., in-memory fallback, missing persistence).
-- `stub`        – Placeholder handler that always returns 501 Not Implemented.
-
 <Callout type="info">
 **Source:** `packages/spec/src/api/discovery.zod.ts`
 </Callout>

content/docs/references/api/endpoint.mdx

@@ -5,9 +5,6 @@ description: Endpoint protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-API Mapping Schema
-Transform input/output data.
-
 <Callout type="info">
 **Source:** `packages/spec/src/api/endpoint.zod.ts`
 </Callout>

content/docs/references/api/events.mdx

@@ -5,16 +5,6 @@ description: Events protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Metadata Event Types
-
-Triggered when metadata items are created, updated, or deleted.
-Follows the pattern: `metadata.{type}.{action}`
-
-Examples:
-- `metadata.object.created` - A new object was created
-- `metadata.view.updated` - A view was updated
-- `metadata.agent.deleted` - An agent was deleted
-
 <Callout type="info">
 **Source:** `packages/spec/src/api/events.zod.ts`
 </Callout>

content/docs/references/automation/flow.mdx

@@ -5,18 +5,6 @@ description: Flow protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Flow Node Types — **built-in seed set** (ADR-0018).
-
-Historically this `z.enum` *gated* `FlowNodeSchema.type`, which made the
-closed protocol reject any plugin-registered node type — defeating the open
-runtime registry (`registerNodeExecutor(type: string)`). Per ADR-0018 the
-gate is removed: `FlowNodeSchema.type` is now a validated `string`, checked
-against the live action registry at `registerFlow()` time, not frozen here.
-
-`FlowNodeAction` is **retained** as the canonical list of built-in type ids
-(documentation + the seed descriptor set the engine registers at boot). It
-no longer constrains authored flows — plugins extend the vocabulary.
-
 <Callout type="info">
 **Source:** `packages/spec/src/automation/flow.zod.ts`
 </Callout>

content/docs/references/automation/webhook.mdx

@@ -5,37 +5,6 @@ description: Webhook protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Webhook Trigger Event
-When should this webhook fire?
-
-These mirror the record events the engine actually emits
-(`data.record.created` / `updated` / `deleted`), which the webhook
-auto-enqueuer maps to `create` / `update` / `delete`. Only events with a real
-producer are declared here — an author can't subscribe to something that
-never fires.
-
-**Bulk triggers (#4639).** `bulk_update` / `bulk_delete` map to the engine's
-aggregate `data.records.updated` / `data.records.deleted`, emitted when a
-predicate write (`multi: true` → `IDataDriver.updateMany`/`deleteMany`)
-affects a set of rows the driver reports only as a count. They are separate
-trigger values, not extra sources for `update` / `delete`, because their
-delivery has a different SHAPE: no `recordId`, no record body, just
-`object` + `matched`. Folding them into the per-record triggers would send
-every existing subscriber a body missing the fields it reads — the same
-class of breakage as the pre-#4626 `recordId: ''` fabrication, arriving from
-the other direction. A webhook that wants both subscribes to both.
-
-Deliberately NOT triggers (#3196):
-- `undelete` — there is no soft-delete / restore capability in the engine
-  (`delete` is a hard delete; no `deleted_at` convention, no restore
-  operation, no `data.record.undeleted` emit), so it had no event source.
-  Reintroduce it only alongside a real restore subsystem that emits an
-  undelete event.
-- `api` (manual/programmatic fire) — no manual fire path exists (the only
-  webhook HTTP surface re-queues already-failed deliveries). Reintroduce it
-  with a real "fire this webhook now" endpoint/service, not as a bare enum
-  value that silently never fires.
-
 <Callout type="info">
 **Source:** `packages/spec/src/automation/webhook.zod.ts`
 </Callout>

content/docs/references/data/document.mdx

@@ -5,24 +5,6 @@ description: Document protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Document Version Schema
-
-Represents a single version of a document in a version-controlled system.
-Each version is immutable and maintains its own metadata and download URL.
-
-@example
-```json
-{
-  "versionNumber": 2,
-  "createdAt": 1704067200000,
-  "createdBy": "user_123",
-  "size": 2048576,
-  "checksum": "a1b2c3d4e5f6",
-  "downloadUrl": "https://storage.example.com/docs/v2/file.pdf",
-  "isLatest": true
-}
-```
-
 <Callout type="info">
 **Source:** `packages/spec/src/data/document.zod.ts`
 </Callout>

content/docs/references/data/driver-nosql.mdx

@@ -5,9 +5,6 @@ description: Driver Nosql protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-NoSQL Database Type Enumeration
-Supported NoSQL database types
-
 <Callout type="info">
 **Source:** `packages/spec/src/data/driver-nosql.zod.ts`
 </Callout>

content/docs/references/data/driver-sql.mdx

@@ -5,9 +5,6 @@ description: Driver Sql protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-SQL Dialect Enumeration
-Supported SQL database dialects
-
 <Callout type="info">
 **Source:** `packages/spec/src/data/driver-sql.zod.ts`
 </Callout>

content/docs/references/data/driver.mdx

@@ -5,9 +5,6 @@ description: Driver protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Common Driver Options
-Passed to most driver methods to control behavior (transactions, timeouts, etc.)
-
 <Callout type="info">
 **Source:** `packages/spec/src/data/driver.zod.ts`
 </Callout>

content/docs/references/data/field.mdx

@@ -5,8 +5,6 @@ description: Field protocol schemas
 
 {/* ⚠️  AUTO-GENERATED — DO NOT EDIT. Run build-docs.ts to regenerate. Hand-written docs live in the module folders under content/docs/. */}
 
-Field Type Enum
-
 <Callout type="info">
 **Source:** `packages/spec/src/data/field.zod.ts`
 </Callout>