chore(changeset): name KanbanConditionalFormattingRuleSchema's real locus, a module export of src/zod/objectql.zod.ts that is not on the @object-ui/types/zod barrel (objectui#11522)

The new changeset's @object-ui/types bullet and the dated note on the 7664
entry both placed the schema on `@object-ui/types/zod`. At this head that
barrel does not re-export it and no `exports` entry carries it; the note now
says so, and records that the 7664 bullet's own locus claim does not hold in
this release either. Text only; no export added.

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

Author: claude

.changeset/11522-kanban-rule-dialect-retired.md

@@ -21,7 +21,7 @@ Each refusal message names the key, objectui#11522 and the `{ condition, style }
 
 - `KanbanConditionalFormattingRule` is now an interface that extends `SpecConditionalFormattingRule`, with `field`, `operator`, `value`, `backgroundColor`, `borderColor` and `textColor` declared `?: never`. It used to be the union of `SpecConditionalFormattingRule` and `KanbanNativeConditionalFormattingRule`.
 - `KanbanNativeConditionalFormattingRule` is removed. Importing it is a compile error (TS2305).
-- `KanbanConditionalFormattingRuleSchema` (`@object-ui/types/zod`) is the spec `ListViewSchema.conditionalFormatting` rule taken by reference and extended, not a union. It keeps the spec rule's strictness and its `style` map. Its `condition` is the same schema the list view's and the grid's `{ condition, style }` arm reads, so a string condition is still not canonicalized into an envelope and `''` is still accepted. The six retired keys are retirement tombstones.
+- `KanbanConditionalFormattingRuleSchema`, the rule schema `ObjectKanbanSchema` applies, is a module export of this package's `src/zod/objectql.zod.ts`. It is not on the `@object-ui/types/zod` barrel or on any other entry of the package's `exports` map, so it is not an import a consumer can name. It is the spec `ListViewSchema.conditionalFormatting` rule taken by reference and extended, not a union. It keeps the spec rule's strictness and its `style` map. Its `condition` is the same schema the list view's and the grid's `{ condition, style }` arm reads, so a string condition is still not canonicalized into an envelope and `''` is still accepted. The six retired keys are retirement tombstones.
 
 **`@object-ui/plugin-kanban`.** The `object-kanban` registration's `conditionalFormatting` input description now describes the one rule. `KanbanRendererProps.schema.conditionalFormatting` and the board's `ConditionalFormattingRule` follow the narrowed type.
 

.changeset/7664-kanban-arm-plugin-dialect.md

@@ -96,5 +96,12 @@ comparison or `{ condition, style }`. Now it is one object, the spec list view's
 `{ condition, style }` rule by reference, and the native rule and a top-level
 colour key (`backgroundColor`, `borderColor`, `textColor`) are refused by name;
 the `'kanban'` arm it was shared with has itself retired in this release
-(objectui#8802). It is still exported from `@object-ui/types/zod` under the same
-name. The rest of this entry is kept as the reading of this change.
+(objectui#8802). It keeps its name, and it is a module export of
+`src/zod/objectql.zod.ts` inside `@object-ui/types`, NOT an export of the
+`@object-ui/types/zod` barrel. Measured at objectui#11522's change: that barrel
+re-exports `KanbanCardSchema`, `KanbanColumnSchema` and `ObjectKanbanSchema` from
+the kanban family and not this schema, and no entry of the package's `exports`
+map carries it. So the bullet above that calls it "newly exported from
+`@object-ui/types/zod`" does not hold in this release either; whether it held at
+objectui#7664's own commit was not measured. The rest of this entry is kept as
+the reading of this change.