You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@causeway.apache.org by da...@apache.org on 2026/08/29 06:08:17 UTC

(causeway) 14/22: docs(openspec): archive Vaadin Grid collection presentation

This is an automated email from the ASF dual-hosted git repository.

danhaywood pushed a commit to branch htmx
in repository https://gitbox.apache.org/repos/asf/causeway.git

commit 3142dab1700149121202d94a529ca3dae712e213
Author: Dan Haywood <da...@haywood-associates.co.uk>
AuthorDate: Fri Aug 28 15:27:25 2026 +0200

    docs(openspec): archive Vaadin Grid collection presentation
---
 .../.openspec.yaml                                 |  0
 .../design.md                                      |  0
 .../evidence.md                                    |  0
 .../proposal.md                                    |  0
 .../specs/domain-web-components/spec.md            |  0
 .../generic-htmx-web-component-viewer/spec.md      |  0
 .../spec.md                                        |  0
 .../specs/vaadin-collection-grid-adapter/spec.md   |  0
 .../tasks.md                                       |  0
 openspec/specs/domain-web-components/spec.md       | 53 +++++++++++++++
 .../generic-htmx-web-component-viewer/spec.md      | 58 +++++++++-------
 .../spec.md                                        | 77 ++++++++++++++++++++++
 .../specs/vaadin-collection-grid-adapter/spec.md   |  6 +-
 13 files changed, 169 insertions(+), 25 deletions(-)

diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/.openspec.yaml b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/.openspec.yaml
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/.openspec.yaml
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/.openspec.yaml
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/design.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/design.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/design.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/design.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/evidence.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/evidence.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/evidence.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/evidence.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/proposal.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/proposal.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/proposal.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/proposal.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/domain-web-components/spec.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/domain-web-components/spec.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/specs/domain-web-components/spec.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/domain-web-components/spec.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/generic-htmx-web-component-viewer/spec.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/generic-htmx-web-component-viewer/spec.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/specs/generic-htmx-web-component-viewer/spec.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/generic-htmx-web-component-viewer/spec.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/reference-application-viewer-regression-suite/spec.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/reference-application-viewer-regression-suite/spec.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/specs/reference-application-viewer-regression-suite/spec.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/reference-application-viewer-regression-suite/spec.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md
similarity index 100%
copy from openspec/changes/use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md
copy to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/tasks.md b/openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/tasks.md
similarity index 100%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/tasks.md
rename to openspec/changes/archive/2026-08-28-use-vaadin-grid-for-collection-presentation/tasks.md
diff --git a/openspec/specs/domain-web-components/spec.md b/openspec/specs/domain-web-components/spec.md
index aa155c9cece..05b81579011 100644
--- a/openspec/specs/domain-web-components/spec.md
+++ b/openspec/specs/domain-web-components/spec.md
@@ -1361,3 +1361,56 @@ A visible ordinary `<cw-action>` SHALL use the qualified internal action control
 - **WHEN** the control is a property edit, save, cancel, clear, action-prompt, shell, or another affordance outside ordinary `<cw-action>` qualification
 - **THEN** its established native control remains authoritative
 - **AND** the ordinary action adapter does not broaden its scope
+
+### Requirement: Toolkit-backed qualified collection presentation
+The `<cw-collection>` component SHALL select an internal Grid only for semantically qualified active wide collections while preserving its public markup, state, events, renderers, navigation, and associated actions.
+Causeway SHALL remain the owner of collection loading, rows, columns, totals, ordering, paging, errors, focus, and lifecycle.
+
+#### Scenario: Qualified wide collection renders
+- **WHEN** a visible active collection has bounded windows, deterministic ordering, supported semantic columns, wide layout, and a healthy enabled Grid family
+- **THEN** `<cw-collection>` may render one internal Grid presentation
+- **AND** application-authored `<cw-collection-column>` and `<cw-action>` children remain the authoritative declarations
+
+#### Scenario: Stable total supports virtualization
+- **WHEN** a qualified collection reports a safely available stable total
+- **THEN** Causeway may serve bounded ranges to Grid virtualization
+- **AND** no Grid callback constructs GraphQL, domain identity, authorization, or navigation independently
+
+#### Scenario: Total is unavailable
+- **WHEN** a qualified deterministic window reports unavailable total count
+- **THEN** the collection renders only its current bounded window through Grid with Causeway-owned previous and next controls
+- **AND** it does not invent a total or silently traverse beyond normalized window metadata
+
+#### Scenario: Collection is narrow or unqualified
+- **WHEN** container width is at most 48rem or window, ordering, column, renderer, policy, or family qualification fails
+- **THEN** the established native collection presentation remains authoritative
+- **AND** no partial Grid or unsupported mixed presentation remains
+
+#### Scenario: Native toolkit is explicit
+- **WHEN** the common component toolkit resolves to native
+- **THEN** collections use established native presentation without a Grid request or style hash
+- **AND** GraphQL operations, routes, data, semantic events, and application markup are unchanged
+
+### Requirement: Toolkit-neutral collection range lifecycle
+Collection range work SHALL remain bounded by the current Causeway route, object generation, member identity, column selection, responsive mode, toolkit policy, renderer registry, and connection lifetime.
+Hydrated row contexts and focus restoration MUST follow domain identity rather than recycled presentation nodes.
+
+#### Scenario: Grid requests an additional range
+- **WHEN** a still-current virtual Grid requests a bounded range
+- **THEN** the collection host coordinates it through the existing object-context window operation
+- **AND** identical current work is deduplicated while accepted concurrent work remains independently cancellable
+
+#### Scenario: Collection lifetime supersedes range work
+- **WHEN** route replacement, refresh, column change, width change, policy revision, member change, or disconnect makes a request obsolete
+- **THEN** the request and its row contexts are aborted, disconnected, or ignored
+- **AND** stale rows, cells, errors, total, paging, focus, and controls cannot alter the current component
+
+#### Scenario: Cell is recycled
+- **WHEN** Grid reuses a presentation node for another row or column
+- **THEN** Causeway repopulates it from the current frozen semantic descriptor and cleans previous relationships
+- **AND** semantic events and focus identity refer to current domain row and member identity
+
+#### Scenario: Associated actions remain composed
+- **WHEN** a collection uses Grid and contains associated actions
+- **THEN** those actions remain Causeway siblings outside Grid in declaration order
+- **AND** their visibility, usability, prompting, execution, navigation, and focus lifecycles remain independent
diff --git a/openspec/specs/generic-htmx-web-component-viewer/spec.md b/openspec/specs/generic-htmx-web-component-viewer/spec.md
index 93f456efd18..28e5080cdb6 100644
--- a/openspec/specs/generic-htmx-web-component-viewer/spec.md
+++ b/openspec/specs/generic-htmx-web-component-viewer/spec.md
@@ -431,16 +431,16 @@ Qualification MUST preserve the public GraphQL data plane, semantic Causeway com
 
 ### Requirement: Common internal editor toolkit policy
 The existing `causeway.viewer.webcomponents.htmx.editor-toolkit` property SHALL remain readable with the bounded values `vaadin` and `native` as a deprecated compatibility input.
-When `component-toolkit` is absent and `editor-toolkit` is explicitly configured, its value SHALL resolve the complete component policy so existing explicit native rollback remains complete.
+When `component-toolkit` is absent and `editor-toolkit` is explicitly configured, its value SHALL resolve the complete component policy, including qualified Grid presentation, so existing explicit native rollback remains complete.
 
 #### Scenario: Deprecated editor policy selects Vaadin
 - **WHEN** `component-toolkit` is absent and `editor-toolkit=vaadin` is explicit
-- **THEN** the resolved compatibility policy enables every qualified reference, field, read-only presentation, and ordinary action adapter
+- **THEN** the resolved compatibility policy enables every qualified reference, field, read-only presentation, ordinary action, and Grid adapter
 - **AND** shell diagnostics identify `component-toolkit` as the replacement without changing application markup
 
 #### Scenario: Deprecated editor policy selects native
 - **WHEN** `component-toolkit` is absent and `editor-toolkit=native` is explicit
-- **THEN** every qualified Vaadin adapter and style hash is disabled
+- **THEN** every qualified Vaadin adapter and style hash, including Grid, is disabled
 - **AND** routes request no Vaadin closure
 
 #### Scenario: Component policy takes precedence
@@ -451,7 +451,7 @@ When `component-toolkit` is absent and `editor-toolkit` is explicitly configured
 #### Scenario: Only deprecated pilot properties are configured
 - **WHEN** component and editor toolkit properties are absent and either reference-widget or field-family pilot property is explicitly configured
 - **THEN** the viewer preserves the former independent editor-only policy in which references default false and field families default empty unless their corresponding old value is supplied
-- **AND** read-only presentation and ordinary action buttons remain native during the compatibility period
+- **AND** read-only presentation, ordinary action buttons, and Grid remain native during the compatibility period
 
 #### Scenario: Editor toolkit value is invalid
 - **WHEN** configuration supplies an editor-toolkit value other than `vaadin` or `native`
@@ -459,13 +459,13 @@ When `component-toolkit` is absent and `editor-toolkit` is explicitly configured
 - **AND** the viewer does not silently select a broader policy
 
 ### Requirement: Default route-lazy toolkit delivery
-The generic HTMX viewer SHALL enable every qualified packaged adapter under the resolved component policy without eagerly importing any reference, field-family, or action-button closure.
+The generic HTMX viewer SHALL enable every qualified packaged adapter under the resolved component policy without eagerly importing any reference, field-family, action-button, or Grid closure.
 A closure MUST load only after an eligible connected Causeway presentation or editor selects its internal adapter.
 
 #### Scenario: Route contains one eligible read-only family
 - **WHEN** the first read-only property eligible for one default field family connects
 - **THEN** only that family's same-origin closure is requested and upgraded
-- **AND** route readiness, other families, references, and actions do not wait for it
+- **AND** route readiness, other families, references, actions, and Grid do not wait for it
 
 #### Scenario: Route contains one eligible editor family
 - **WHEN** the first editor eligible for one default field family connects before a read-only property from that family
@@ -475,15 +475,25 @@ A closure MUST load only after an eligible connected Causeway presentation or ed
 #### Scenario: Route contains an ordinary action
 - **WHEN** the first visible qualified ordinary action connects on a route without an eligible field
 - **THEN** only the independently packaged action-button closure is requested
-- **AND** no field-family closure is downloaded as a transitive convenience
+- **AND** no field-family or Grid closure is downloaded as a transitive convenience
+
+#### Scenario: Route contains a qualified wide collection
+- **WHEN** the first active wide collection satisfies Grid window, ordering, total or paging, column, renderer, and lifecycle qualification
+- **THEN** only the independently packaged Grid closure is requested for collection presentation
+- **AND** route readiness, fields, references, actions, and GraphQL loading do not wait for unrelated closures
+
+#### Scenario: Eligible collection is narrow
+- **WHEN** an otherwise eligible collection remains at or below the documented 48rem container boundary
+- **THEN** it uses native responsive presentation and does not request Grid solely for that collection
+- **AND** widening may request Grid later without changing route readiness
 
 #### Scenario: Route contains no eligible presentation or editor
-- **WHEN** a landing, menu-only, custom, or other unaffected route contains no eligible reference, field presentation, editor, or ordinary action
-- **THEN** it requests zero reference, basic, numeric, local-temporal, and action-button Vaadin assets
+- **WHEN** a landing, menu-only, custom, narrow-collection, or other unaffected route contains no eligible reference, field presentation, editor, ordinary action, or wide Grid collection
+- **THEN** it requests zero reference, basic, numeric, local-temporal, action-button, and Grid Vaadin assets
 - **AND** default CSP hash permission does not cause a network request
 
 #### Scenario: One family fails
-- **WHEN** a default field or action closure fails to load or define its controls
+- **WHEN** a default field, action, or Grid closure fails to load or define its controls
 - **THEN** its existing Causeway failure boundary activates the matching native implementation
 - **AND** other family closures remain independently eligible and lazy
 
@@ -493,56 +503,56 @@ It MUST retain `style-src-attr 'none'`, same-origin script and connection source
 
 #### Scenario: Default component policy renders CSP
 - **WHEN** the effective policy is the supported Vaadin default
-- **THEN** `style-src` and `style-src-elem` contain the deterministic deduplicated reference, field-family, and action-button hash union
+- **THEN** `style-src` and `style-src-elem` contain the deterministic deduplicated reference, field-family, action-button, and Grid hash union
 - **AND** every hash corresponds to pinned generated policy metadata
 
 #### Scenario: Deprecated editor compatibility renders CSP
 - **WHEN** the component property is absent and explicit `editor-toolkit=vaadin` resolves the complete Vaadin compatibility policy
-- **THEN** CSP contains the same reviewed union as the default component policy
+- **THEN** CSP contains the same reviewed union, including Grid, as the default component policy
 - **AND** shell diagnostics identify the deprecated source
 
 #### Scenario: Deprecated pilot subset renders CSP
 - **WHEN** compatibility mode enables only a subset of old editor adapters
 - **THEN** CSP contains exactly the reviewed union required by that old subset
-- **AND** read-only-presentation-only and action-button hashes are absent
+- **AND** read-only-presentation-only, action-button, and Grid hashes are absent
 
 #### Scenario: Native component policy renders CSP
 - **WHEN** the effective component policy is native
-- **THEN** CSP contains no Vaadin style hash
+- **THEN** CSP contains no Vaadin style hash, including no Grid hash
 - **AND** route, GraphQL, application stylesheet, and canonical identity policy remain unchanged
 
 ### Requirement: Supported default and native release qualification
 The viewer SHALL treat default-Vaadin and explicit-native component modes as supported release configurations rather than sample-scoped modes.
-Petclinic, the vanilla sample, the pinned Reference Application, deterministic packaging, strict CSP, accessibility, browser isolation, bundle budgets, licenses, vulnerabilities, and ordinary Maven packaging MUST remain passing gates.
+Petclinic, the vanilla sample, the pinned Reference Application, deterministic packaging, strict CSP, accessibility, browser isolation, bundle budgets, licenses, vulnerabilities, and ordinary Maven packaging MUST remain passing gates for qualified Grid and all previously accepted adapters.
 
 #### Scenario: Default release matrix runs
 - **WHEN** release qualification runs with no toolkit override
-- **THEN** eligible references, read-only fields, editors, and ordinary actions use internal Vaadin adapters and preserve authoritative outcomes
-- **AND** unexpected CSP, accessibility, console, page, external-request, stale-state, duplicate-control, focus, overlay, or overflow failures fail the gate
+- **THEN** eligible references, read-only fields, editors, ordinary actions, and wide collections use internal Vaadin adapters and preserve authoritative outcomes
+- **AND** unexpected CSP, accessibility, console, page, external-request, stale-state, duplicate-control, focus, overlay, clipping, or overflow failures fail the gate
 
 #### Scenario: Native release matrix runs
 - **WHEN** the same journeys run with `component-toolkit=native`
-- **THEN** native controls preserve the same GraphQL values, routes, interactions, semantic events, and classifications
-- **AND** all Vaadin closure requests and style hashes are absent
+- **THEN** native controls and collections preserve the same GraphQL values, windows, routes, interactions, semantic events, and classifications
+- **AND** all Vaadin closure requests and style hashes, including Grid, are absent
 
 #### Scenario: Deprecated editor compatibility matrix runs
 - **WHEN** compatibility qualification runs with explicit `editor-toolkit=vaadin` and no component property
-- **THEN** authoritative outcomes match default component mode
+- **THEN** authoritative outcomes and qualified Grid presentation match default component mode
 - **AND** bounded diagnostics identify the replacement property
 
 ### Requirement: Common internal component toolkit policy
 The HTMX viewer SHALL expose `causeway.viewer.webcomponents.htmx.component-toolkit` with the bounded values `vaadin` and `native` and SHALL default effectively to `vaadin`.
-The resolved component policy SHALL govern eligible references, editors, read-only field presentation, ordinary action buttons, and their CSP and asset delivery.
+The resolved component policy SHALL govern eligible references, editors, read-only field presentation, ordinary action buttons, qualified Grid collection presentation, and their CSP and asset delivery.
 
 #### Scenario: No toolkit property is configured
 - **WHEN** an application starts without the component, editor, or deprecated pilot toolkit properties
-- **THEN** the resolved component policy enables every qualified Vaadin reference, field, read-only presentation, and ordinary action adapter
-- **AND** unsupported or excluded shapes and controls retain native or explicit unsupported presentation
+- **THEN** the resolved component policy enables every qualified Vaadin reference, field, read-only presentation, ordinary action, and Grid adapter
+- **AND** unsupported or excluded shapes, collections, and controls retain native or explicit unsupported presentation
 
 #### Scenario: Native component policy is explicit
 - **WHEN** `component-toolkit=native` is configured
 - **THEN** the shell explicitly disables every Vaadin component adapter and emits no Vaadin CSP hash
-- **AND** routes request no reference, field-family, or action-button closure
+- **AND** routes request no reference, field-family, action-button, or Grid closure
 
 #### Scenario: Component policy overrides compatibility inputs
 - **WHEN** `component-toolkit` and `editor-toolkit` or a deprecated pilot property are configured with conflicting values
diff --git a/openspec/specs/reference-application-viewer-regression-suite/spec.md b/openspec/specs/reference-application-viewer-regression-suite/spec.md
index 3d9206246e5..bec579185e8 100644
--- a/openspec/specs/reference-application-viewer-regression-suite/spec.md
+++ b/openspec/specs/reference-application-viewer-regression-suite/spec.md
@@ -330,3 +330,80 @@ The Reference Application browser suite SHALL exercise read-only field and actio
 - **WHEN** default and native controls are exercised by keyboard at wide and narrow viewports with theme switching, reduced motion, forced colors, disabled reasons, validation, route replacement, and representative errors
 - **THEN** there are no unexpected accessibility, console, page, external-request, duplicate-control, overlay, focus, clipping, or overflow failures
 - **AND** accessible names, descriptions, state, order, and authoritative outcomes remain equivalent
+
+### Requirement: Vaadin Grid collection regression coverage
+The pinned Reference Application browser suite SHALL compare default Grid and explicit-native collection journeys against authoritative GraphQL windows, rows, values, routes, and interactions.
+The retained target catalogue MUST cover every important Grid qualification and exclusion class deterministically.
+
+#### Scenario: Stable-total scalar collection is exercised
+- **WHEN** a wide deterministic collection with safe total and scalar columns is visited in default and native modes
+- **THEN** Grid and native presentations expose equivalent labels, descriptions, row identities, column order, values, totals, and navigation outcomes
+- **AND** default mode issues only bounded deduplicated window requests
+
+#### Scenario: Reference and polymorphic cells are exercised
+- **WHEN** retained collections contain object references, runtime-polymorphic rows, nullable values, resources, hidden cells, disabled reasons, or application renderers
+- **THEN** qualified cells preserve established semantic rendering and exact navigation
+- **AND** any unqualified collection remains wholly native with a bounded reason
+
+#### Scenario: Unavailable total is exercised
+- **WHEN** a deterministic retained target reports unavailable total count with previous or next windows
+- **THEN** default mode uses bounded Grid plus Causeway paging without an invented size
+- **AND** native mode reaches the same windows and row outcomes
+
+#### Scenario: Unstable ordering is exercised
+- **WHEN** a retained collection reports encounter or unstable ordering
+- **THEN** default and native profiles both retain native presentation
+- **AND** no speculative Grid range request is emitted
+
+#### Scenario: Narrow collection is exercised
+- **WHEN** the same eligible collection is rendered at or below the accepted container breakpoint
+- **THEN** default and native profiles use the established native responsive presentation
+- **AND** there is no Grid request, clipped focus, inaccessible cell, or page overflow attributable to that collection
+
+#### Scenario: Collection actions are exercised
+- **WHEN** a retained collection displays enabled, disabled, hidden, parameterless, and parameterized associated actions
+- **THEN** Grid and native modes preserve order, preparation, validation, invocation, results, routing, request counts, and focus restoration
+- **AND** Grid never owns an action callback or GraphQL mutation
+
+### Requirement: Grid range lifecycle and delivery regression coverage
+The Reference Application suite SHALL exercise Grid loading, caching, paging, refresh, replacement, failure, responsiveness, policy precedence, CSP, packaging, and native rollback against real HTMX lifecycles.
+
+#### Scenario: Overlapping virtual ranges are requested
+- **WHEN** browser scrolling causes overlapping and repeated Grid range callbacks
+- **THEN** GraphQL requests remain bounded and identical current ranges are deduplicated
+- **AND** visible rows, total, order, errors, and focus correspond only to the latest current generation
+
+#### Scenario: Membership changes between ranges
+- **WHEN** authoritative action or fixture mutation changes collection membership or ordering before refresh
+- **THEN** the old range generation is retired and the collection requalifies from the refreshed first window
+- **AND** stale cached rows and totals cannot mix with current data
+
+#### Scenario: Route changes during Grid upgrade or range load
+- **WHEN** module import, custom-element definition, renderer work, or range request is pending while HTMX replaces the route
+- **THEN** disconnected work cannot restore old Grid, cells, controls, focus, errors, or route state
+- **AND** the new route remains authoritative
+
+#### Scenario: Grid family failure is injected
+- **WHEN** Grid fails before connection, after connection, during rendering, or during a data-provider callback
+- **THEN** connected collections recover to current native presentation without duplicate controls or requests
+- **AND** reference, field, action, other routes, values, errors, and recoverable focus remain correct
+
+#### Scenario: Responsive mode changes repeatedly
+- **WHEN** an eligible collection crosses the 48rem boundary repeatedly while requests and focus are active
+- **THEN** only the current wide mode contains Grid and every narrow mode remains native
+- **AND** stale callbacks, duplicate controls, clipped focus, and page overflow remain absent
+
+#### Scenario: Policy precedence profiles run
+- **WHEN** browser profiles cover default, explicit component Vaadin, explicit native, deprecated editor Vaadin and native, former pilot subsets, and conflicting properties
+- **THEN** Grid eligibility, shell diagnostics, closure requests, CSP hashes, and complete rollback match documented precedence
+- **AND** former pilot subsets do not enable Grid
+
+#### Scenario: Clean and incremental inventory runs
+- **WHEN** capability inventory and retained target generation run from clean and incremental builds
+- **THEN** output remains byte-identical unless reviewed Grid evidence intentionally changes the baseline
+- **AND** every qualified and excluded target remains discoverable
+
+#### Scenario: Grid accessibility matrix runs
+- **WHEN** default and native journeys run with keyboard, pointer, zoom, wide and narrow containers, theme switching, reduced motion, forced colors, disabled reasons, partial errors, paging, and refresh
+- **THEN** accessible names, descriptions, busy state, row and cell order, object links, visible focus, authoritative outcomes, and native parity remain accepted
+- **AND** unexpected axe, CSP, console, page, external-request, duplicate-control, stale-cell, clipping, or overflow failures fail the suite
diff --git a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md b/openspec/specs/vaadin-collection-grid-adapter/spec.md
similarity index 98%
rename from openspec/changes/use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md
rename to openspec/specs/vaadin-collection-grid-adapter/spec.md
index 8487f8fd764..27655835924 100644
--- a/openspec/changes/use-vaadin-grid-for-collection-presentation/specs/vaadin-collection-grid-adapter/spec.md
+++ b/openspec/specs/vaadin-collection-grid-adapter/spec.md
@@ -1,5 +1,8 @@
-## ADDED Requirements
+# vaadin-collection-grid-adapter Specification
 
+## Purpose
+TBD - created by archiving change use-vaadin-grid-for-collection-presentation. Update Purpose after archive.
+## Requirements
 ### Requirement: Internal Grid adapter boundary
 Qualified collection presentation SHALL remain behind `<cw-collection>` and `<cw-collection-column>` public contracts.
 Raw Vaadin elements, item objects, data providers, renderer callbacks, events, methods, properties, and Shadow DOM MUST remain unsupported application integration points.
@@ -237,3 +240,4 @@ Default and native collection journeys SHALL remain release-qualified across key
 - **WHEN** module, definition, renderer, data-provider, route, or CSP failure is recorded
 - **THEN** events and diagnostics contain only family, phase, bounded classification, and revision metadata
 - **AND** row values, protected values, GraphQL variables, serialized snapshots, and full server errors remain absent
+