docs(spec): 重生成 connector 参考页,并更新一处指向已删文件的注释

- content/docs/references/integration/connector.mdx 随 connector.zod.ts 的
  TSDoc 修正重生成(三条死链消失)
- alias-integrity.test.ts 的十点测量里 etl.zod.ts 已不在:保留原计数并注明
  退役,论点是 AST 盲区,不因少一个文件而变弱

Author: claude

content/docs/references/integration/connector.mdx

@@ -11,10 +11,12 @@ Defines the standard connector specification for external system integration.
 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](/docs/references/automation/etl)) - 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.**
@@ -95,9 +97,11 @@ Authentication is now imported from the canonical `auth/config.zod.ts`.
 - Microsoft Dynamics 365 connector
 
 **When to downgrade:**
-- Data transformation only → Use [ETL Pipeline](/docs/references/automation/etl)
-
-See also: [../automation/etl.zod.ts](/docs/references/automation/etl) 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
 
@@ -110,9 +114,11 @@ platform's authority, at a dead end (#4499; removed alongside the #4480
 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.)
 
 <Callout type="info">
 **Source:** `packages/spec/src/integration/connector.zod.ts`

packages/spec/src/shared/alias-integrity.test.ts

@@ -31,9 +31,12 @@
  *    no source-literal reader can see, so the target check has to be suppressed
  *    for most of the interesting schemas. `.shape` sees them.
  * 2. **Assembled tables.** Ten call sites build `aliases` (or `surface`) from
- *    something other than a literal — `data/field.zod.ts`, `ui/theme.zod.ts`,
- *    `automation/etl.zod.ts` and others. The AST reads those as empty and
- *    reports them clean.
+ *    something other than a literal — `data/field.zod.ts`, `ui/theme.zod.ts`
+ *    and others. The AST reads those as empty and reports them clean.
+ *    (`automation/etl.zod.ts` was one of the ten when this was measured; the
+ *    whole L2 layer was retired at #6414, which is why the count above is kept
+ *    as the measurement it was rather than silently decremented — the argument
+ *    is about the AST's blind spot, and it does not get weaker by one file.)
  * 3. **Colliding surfaces.** `'this field group'` names two different schemas
  *    (`data/object.zod.ts`, `studio/object-designer.zod.ts`), so the surface
  *    string is not a key and the hand-map silently judges one against the