docs(ui): state the view filter any-of group in the views guide; Skills-docs line in the changeset

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

Author: claude

.changeset/28370-view-filter-or-group-console.md

@@ -10,6 +10,7 @@ feat(console): a stored view filter's OR group filters the list, and the filter
 
 Clause-②: yes (widening: `@object-ui/core` adds the export `builderRulesOfSpecFilter` and its result type `BuilderFilterRules`; no schema, accept set or error code changes)
 Metadata-protocol: none
+Skills-docs: follow-up owed — skills/objectstack-ui/rules/list-views.md, skills/objectstack-ui/evals/views-apps-actions-pages.json (the any-of group is not taught there yet); `content/docs/ui/views.mdx` gains a Base filter section that states it
 
 A view filter list may hold an any-of group beside its rules, `{ or: [rule, ...] }` (`ViewFilterOrGroupSchema` in `@objectstack/spec/ui`): the list ANDs its elements and the group ORs its rules. Until now no console reader applied it. The list query passed the group through, the server refused the query as a malformed filter (400 `INVALID_FILTER`), and the view showed no rows.
 

content/docs/ui/views.mdx

@@ -98,7 +98,7 @@ A List View controls how a collection of records is presented. It supports multi
 | `label` | `string` | optional | Display label shown in the view switcher |
 | `type` | `enum` | optional | View type (see table above; default `'grid'`) |
 | `data` | `ViewData` | optional | Data source configuration (defaults to the `object` provider) |
-| `filter` | `array` | optional | Base filter criteria |
+| `filter` | `array` | optional | Base filter: rules that all must match, any of which may be an any-of group `{ or: [...] }` — see [Base filter](#base-filter-filter) below |
 | `sort` | `array` | optional | Sort configuration |
 | `searchableFields` | `string[]` | optional | Fields the toolbar search scans — **narrows** the set the object allows, never widens it (ADR-0061). Every entry must be in that allowed set, or every toolbar search on the list returns `400 INVALID_FIELD` (#4254) — see [Toolbar search](#toolbar-search-searchablefields) below |
 | `grouping` | `object` | optional | Row grouping configuration |
@@ -115,6 +115,30 @@ The view's machine name is its **key** in the container (`listViews.urgent` on
 object `task` becomes `task.urgent`); the default `list` claims `task.default`.
 List and form views share that one namespace — don't reuse a key.
 
+### Base filter (`filter`)
+
+A list view's `filter` is a list of conditions that **all** must match. Each
+element is a rule `{ field, operator, value }`, or an **any-of group**
+`{ or: [rule, ...] }` that matches a record when **any** of its rules does. A
+group holds flat rules only (no group inside a group), and the list still ANDs
+the group with the elements beside it:
+
+```typescript
+// open, or completed in the last 7 days — and owned by me
+filter: [
+  { or: [
+    { field: 'status', operator: 'equals', value: 'open' },
+    { field: 'completed_at', operator: 'after', value: '{7_days_ago}' },
+  ] },
+  { field: 'owner', operator: 'equals', value: '{current_user_id}' },
+],
+```
+
+The Console's filter builder saves its **OR** toggle as one such group, and
+opens a filter that is exactly one group as an OR group. A filter whose group
+sits beside other conditions is applied to the list as written, but the
+builder shows it read-only, because it edits one AND or OR over flat rows.
+
 ### Toolbar search (`searchableFields`)
 
 The toolbar's search box scans a set the **object** owns. A list view's