@@ -11,7 +11,7 @@ Metadata-protocol: none
 
 **BREAKING** for a host that imports any of these fifteen types from `@object-ui/types`. None had an importer anywhere in the workspace or in hotcrm, so the Console and every `@object-ui/*` package are unaffected.
 
-They are **gone from the package, not only from the entry**: the "Phase 3.6" driver interfaces and the "Phase 3.7" datasource interfaces at the end of `data-protocol.ts` were read only by each other. Nothing implemented the driver interface and nothing constructed the datasource manager; the client talks to data through the `DataSource` interface instead. Every other name of `data-protocol.ts` stays exported unchanged, among them `DriverQueryConfig`, `SqlQueryAST`, the query-AST node types, `AdvancedFilterSchema`, `FilterBuilderConfig` and `ObjectValidationRule` with its variants.
+They are **gone from the package, not only from the entry**: the "Phase 3.6" driver interfaces and the "Phase 3.7" datasource interfaces at the end of `data-protocol.ts` were read only by each other. Nothing implemented the driver interface and nothing constructed the datasource manager; the client talks to data through the `DataSource` interface instead. Every other name of `data-protocol.ts` stays exported unchanged, among them `DriverQueryConfig`, `SqlQueryAST`, the query-AST node types, `AdvancedFilterSchema` and `ObjectValidationRule` with its variants.
 
 What leaves, and what to write instead:
 
 
@@ -0,0 +1,20 @@
+---
+'@object-ui/types': patch
+---
+
+refactor(types)!: delete `SubqueryNode` and the filter builder configuration pair nothing reads
+
+Clause-②: no (narrowing)
+Metadata-protocol: none
+
+<!-- adr-0087: not-required (runtime-export-retired @object-ui/types#SubqueryNode, @object-ui/types#FilterBuilderConfig, @object-ui/types#FilterFieldConfig) the retired operands are TypeScript-only interfaces declared in `data-protocol.ts`: a query-AST subquery node and a filter builder configuration pair that no query builder, renderer, adapter or host constructs or reads; nothing in the workspace or in hotcrm imports any of them from the package entry, they have no zod twin, they are not arms of `AnySchema`, and no packages/spec schema, registered node type, conversion surface or stored shape names them, so there is nothing for `objectstack migrate meta` to rewrite -->
+
+**BREAKING** for a host that imports any of these three types from `@object-ui/types`. None had an importer anywhere in the workspace or in hotcrm, so the Console and every `@object-ui/*` package are unaffected.
+
+They are **gone from the package, not only from the entry**: `src/data-protocol.ts` no longer declares them. They were types only, so the built JavaScript is unchanged. The other query-AST node types (`SelectNode`, `OffsetNode`, `AggregateNode`, …), `DateRangeFilter` and `FilterBuilderDateRangePreset` stay exported unchanged.
+
+What leaves, and what to write instead:
+
+- FROM `SubqueryNode` TO no replacement in this package. Nothing built or read a subquery node; a host that kept one declares it locally on top of `QueryASTNode` and `SqlQueryAST`, which stay.
+- FROM `FilterBuilderConfig` TO no replacement. No filter builder read this configuration; a host that kept one declares it locally.
+- FROM `FilterFieldConfig` TO no replacement. It was only the `fields` item of `FilterBuilderConfig`; a host that kept one declares it locally (`AdvancedFilterOperator`, which typed its `operators`, stays).
@@ -158,7 +158,7 @@ describe('@object-ui/types — the Phase 3.5 validation types stay retired (obje
     // Firing controls on the same matcher: a truncated read or a matcher that
     // can never match would otherwise pass the absence assertion below.
     expect(declares(source, 'ObjectValidationRule'), 'the object-level rule union is missing').toBe(true);
-    expect(declares(source, 'FilterFieldConfig'), 'the neighbouring filter type is missing').toBe(true);
+    expect(declares(source, 'DateRangeFilter'), 'the neighbouring date range filter type is missing').toBe(true);
 
     expect(
       RETIRED.filter((name) => declares(source, name)),
 
@@ -157,14 +157,8 @@ export interface OffsetNode extends QueryASTNode {
   value: number;
 }
 
-/**
- * Subquery node (Phase 3.3.3)
- */
-export interface SubqueryNode extends QueryASTNode {
-  type: 'subquery';
-  query: SqlQueryAST;
-  alias?: string;
-}
+// `SubqueryNode` (Phase 3.3.3) is retired (objectstack#25921, batch 12): no
+// query builder, adapter or host constructed or read a subquery node.
 
 /**
  * Aggregate function node (Phase 3.3.5)
@@ -571,7 +565,7 @@ export interface DateRangeFilter {
  *    anything outside those thirteen by name;
  *  - this one adds eight FUTURE windows (`tomorrow`, `next_week`,
  *    `next_month`, `next_quarter`, `next_year`, `next_7_days`, `next_30_days`,
- *    `next_90_days`) for the `FilterBuilderConfig` surface below, where a
+ *    `next_90_days`) for {@link DateRangeFilter}'s `preset` above, where a
  *    forward-looking range ("due next week") is the point.
  *
  * So an author or agent who read the spec's thirteen off this name would have
@@ -608,60 +602,9 @@ export type FilterBuilderDateRangePreset =
   | 'next_30_days'
   | 'next_90_days';
 
-/**
- * Filter builder configuration (Phase 3.4.5)
- */
-export interface FilterBuilderConfig {
-  /**
-   * Available fields for filtering
-   */
-  fields: FilterFieldConfig[];
-  
-  /**
-   * Default operator
-   */
-  default_operator?: 'and' | 'or';
-  
-  /**
-   * Allow nested groups
-   */
-  allow_groups?: boolean;
-  
-  /**
-   * Maximum nesting depth
-   */
-  max_depth?: number;
-}
-
-/**
- * Filter field configuration
- */
-export interface FilterFieldConfig {
-  /**
-   * Field name
-   */
-  name: string;
-  
-  /**
-   * Display label
-   */
-  label: string;
-  
-  /**
-   * Field type
-   */
-  type: string;
-  
-  /**
-   * Available operators for this field
-   */
-  operators?: AdvancedFilterOperator[];
-  
-  /**
-   * Options for select fields
-   */
-  options?: Array<{ label: string; value: any }>;
-}
+// The filter builder configuration pair (Phase 3.4.5: `FilterBuilderConfig`,
+// `FilterFieldConfig`) is retired (objectstack#25921, batch 12): no filter
+// builder, adapter or host read either shape.
 
 // RETIRED (objectui#10719): the "Phase 3.5" field-validation family —
 // `AdvancedValidationSchema`, `AdvancedValidationRule`, `ValidationRuleType`,
 
@@ -660,7 +660,7 @@ export type {
   OrderByNode,
   LimitNode,
   OffsetNode,
-  SubqueryNode,
+  // `SubqueryNode` was retired here (objectstack#25921, batch 12).
   AggregateNode,
   WindowNode,
   WindowFunction,
@@ -687,8 +687,8 @@ export type {
   // Renamed from `DateRangePreset` in objectui#4167 — the spec owns that name
   // for the narrower dashboard filter-bar vocabulary (objectstack#4115).
   FilterBuilderDateRangePreset,
-  FilterBuilderConfig,
-  FilterFieldConfig,
+  // `FilterBuilderConfig` / `FilterFieldConfig` were retired here
+  // (objectstack#25921, batch 12) — see the notes in `data-protocol.ts`.
   // Object-level validation rules. The five spec-named variants are derived from
   // `@objectstack/spec/data`; the other three are @deprecated objectui-local
   // variants the spec's union rejects. See data-protocol.ts.