fix(ci): 补 ADR-0087 disposition 标记,并把两处指向已退役 ETL 页的死链修在源头

- 三份 changeset 各补 `adr-0087: registered <id>`(#6148 门禁要求书面处置)
- `integration/connector.zod.ts` 的三处 TSDoc 指向 automation/etl.zod.ts:
  L2 已退役,指针改指真正执行的面(data/mapping.zod.ts 的 transform),
  而不是转到另一个不执行的层——这正是该文件 header 自己写的"signpost 必须
  落在被执行的地方"
- quick-reference.mdx 删掉 ETL 行并把 Automation 计数 5 → 4

Author: claude

.changeset/etl-pipeline-layer-retired.md

@@ -47,3 +47,5 @@ a rename on a shape that does not survive the major has no observable effect, an
 The retirement kit — route 3: no tombstone, no D2 conversion.
 `RETIRED_DEFS_BY_MAJOR[17]` (9 defs) plus the D3 `SemanticMigration`
 `etl-pipeline-layer-retired` are the declaration.
+
+<!-- adr-0087: registered etl-pipeline-layer-retired -->

.changeset/http-server-runtime-vocabulary-retired.md

@@ -48,3 +48,5 @@ baselines (`json-schema.manifest/system.json`, `authorable-surface/system.json`,
 
 If host-implementer conformance becomes a real requirement it returns through the
 ENFORCE route: an adapter contract with a checker behind it, vocabulary second.
+
+<!-- adr-0087: registered http-server-runtime-vocabulary-retired -->

.changeset/view-management-protocol-retired.md

@@ -51,3 +51,5 @@ generated baselines and reference docs lose their entries in the same change.
 
 If "read and write ONE view by id" becomes a real requirement, it returns
 implementation-first.
+
+<!-- adr-0087: registered view-management-protocol-retired -->

content/docs/getting-started/quick-reference.mdx

@@ -145,7 +145,7 @@ REST/GraphQL endpoints, real-time subscriptions, and discovery.
 | **[Metadata](/docs/references/api/metadata)** | `metadata.zod.ts` | Metadata | API metadata endpoints |
 | **[Storage](/docs/references/api/storage)** | `storage.zod.ts` | Storage | API storage operations |
 
-## Automation Protocol (5 schemas)
+## Automation Protocol (4 schemas)
 
 Flows, state machines, approvals, and integrations.
 
@@ -155,7 +155,6 @@ Flows, state machines, approvals, and integrations.
 | **[Approval](/docs/references/automation/approval)** | `approval.zod.ts` | ApprovalNodeConfig | Flow approval-node config |
 | **[State Machine](/docs/references/automation/state-machine)** | `state-machine.zod.ts` | StateMachine | State machine definitions |
 | **[Webhook](/docs/references/automation/webhook)** | `webhook.zod.ts` | Webhook | Outbound webhooks |
-| **[ETL](/docs/references/automation/etl)** | `etl.zod.ts` | ETLPipeline | Data transformation pipelines |
 
 ## Security Protocol (3 schemas)
 

packages/spec/src/integration/connector.zod.ts

@@ -14,10 +14,12 @@ import { retiredKey } from '../shared/retired-key';
  * Connectors enable ObjectStack to sync data with SaaS apps, databases, file storage,
  * and message queues through a unified protocol.
  * 
- * **Positioning in the sync/integration layering** (L1 "Simple Sync" was
- * retired in #4738 — narrative-only, zero consumers; see
- * `packages/spec/docs/SYNC_ARCHITECTURE.md`):
- * - **ETL Pipeline** (automation/etl.zod.ts) - Data engineers - Aggregate 10 sources to warehouse
+ * **Positioning in the sync/integration layering** — this file is now the ONLY
+ * layer. Both layers above it were retired under ADR-0049 for the same measured
+ * reason, that no engine ever executed them: L1 "Simple Sync"
+ * (`automation/sync.zod.ts`) in #4738, and L2 "ETL Pipeline"
+ * (`automation/etl.zod.ts`) in #6414. See
+ * `packages/spec/docs/SYNC_ARCHITECTURE.md`:
  * - **Enterprise Connector** (THIS FILE) - System integrators - Full SAP integration; connector-attached sync via `syncConfig`
  * 
  * **SCOPE: Most comprehensive integration layer.**
@@ -98,9 +100,11 @@ import { retiredKey } from '../shared/retired-key';
  * - Microsoft Dynamics 365 connector
  * 
  * **When to downgrade:**
- * - Data transformation only → Use {@link file://../automation/etl.zod.ts | ETL Pipeline}
- *
- * @see {@link file://../automation/etl.zod.ts} for the ETL Pipeline layer (data engineering)
+ * - Per-field value conversion on import only → the import mapping's own
+ *   `transform` (`data/mapping.zod.ts`), which the REST import path executes
+ *   row by row. (This used to point at `automation/etl.zod.ts`; L2 was retired
+ *   at #6414 for having no executor, so the pointer would have been a signpost
+ *   landing nowhere — the same defect class this header names below.)
  * 
  * ## There is no "Trigger Registry" alternative
  *
@@ -113,9 +117,11 @@ import { retiredKey } from '../shared/retired-key';
  * per-provider template cluster). The same defect class as the
  * `capabilities.readOnly` prescription #4487 corrected: a signpost must land
  * somewhere enforced. Lightweight cases are served HERE — a connector instance
- * with simple `auth` — or by `automation/etl.zod.ts` for transformation
- * pipelines. (The automation-side L1 "Simple Sync" file was itself retired as
- * a dead end of the same class in #4738.)
+ * with simple `auth`. (Both automation-side layers were themselves retired as
+ * dead ends of the same class: L1 "Simple Sync" in #4738, L2 `etl.zod.ts` in
+ * #6414. This paragraph named L2 as the transformation destination until the
+ * second retirement; a signpost that must land somewhere enforced cannot make
+ * an exception for itself.)
  */
 
 // ============================================================================