Data grid

# Implement Data grid in your agent

## Objective
Implement Data grid for this verified behavior: An interactive tabular composite that manages one keyboard entry point and directional focus among cells, often adding editing or selection.

## Prerequisites
- Inspect the repository, design system, and existing tests first.
- Preserve unrelated changes and keep the file scope bounded.
- Confirm that Data grid matches the need before writing code.

## Required behavior
- Arrow, Home, and End keys move one managed focus point through the two-dimensional grid.
- Activation or a documented edit command enters a cell control, then returns to grid navigation predictably.

## States to cover
- Grid ready
- Cell active
- Cell editing
- Row selected

## Accessibility
- ARIA role: grid > row > (columnheader | rowheader | gridcell)
- The primary control or named region for Data grid has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names.
- Use one consistent roving-tabindex or aria-activedescendant strategy, keep the active cell visible, and never put every cell in the page tab sequence.
- The grid is not dismissed; Escape exits cell interaction and restores grid navigation.
- The grid has a name; focus exposes row and column context, selection or editing state, and correct virtualized counts and indices.
- Tab enters at one managed cell and a later Tab exits
- Arrow keys move among cells; Home and End move within a row
- Control+Home and Control+End reach grid bounds
- Enter or F2 enters cell interaction and Escape returns
- Selection shortcuts exist only for the declared model

## When not to use
- The data is static and read-only
- The team cannot implement and test composite focus completely

## Acceptance criteria
- One cell or descendant is tabbable
- Every Arrow destination is focusable and labelled
- Edit mode has a clear entry and exit
- Focus and selection look different
- Virtualized indices and counts are exposed

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Web platform
• Requires · Access to the repository, design system, and tests

# Verify Data grid after implementation

## Objective
Audit the Data grid implementation against its behavior, states, and accessibility requirements without changing it automatically.

## Checks
- Replay the smallest representative journey.
- Check keyboard behavior, focus, accessible name, and announcements.
- Tie each gap to a specific acceptance criterion.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:a9623f01d42c632dad3cbf46bb98c1c895bb32bd07d5b905f049d4819e875cd9

# Debug Data grid in your agent

## Observed symptom
[DESCRIBE THE SYMPTOM HERE]

## Observable checks
- Reproduce the issue with the smallest relevant journey.
- Compare behavior with the documented states and transitions for Data grid.
- Verify keyboard behavior, focus, accessible name, and announcements.

## Possible causes
- The chosen primitive does not match the expected behavior.
- A state, transition, or focus return is missing.
- A neighboring component captures an event or hides an accessible signal.

## Bounded corrections
- Fix the reproduced cause without recreating neighboring components.
- Preserve the public contract and add a focused regression test.
- Do not install dependencies or change remote state without authorization.

## Final verification
- One cell or descendant is tabbable
- Every Arrow destination is focusable and labelled
- Edit mode has a clear entry and exit
- Focus and selection look different
- Virtualized indices and counts are exposed

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

• Web platform
• Requires · Access to the repository, design system, and tests

# Prevent the Data grid regression

## Objective
Turn the reproduced cause into a focused regression test and compare Data grid with neighboring concepts before widening the fix.

## Checks
- Prove that the test fails before the fix.
- Prove that it passes after the bounded fix.
- Verify that no neighboring component changed behavior.

## Guardrails
- Show the proposed changes before any external action.
- Do not publish, send, delete, pay for, or change remote state without explicit authorization.
- Preserve unrelated changes and stop if the scope becomes ambiguous.

## Output format
- Outcome or verdict.
- Files or actions involved.
- Checks run and observable evidence.
- Remaining blockers or limitations.

sha256:229ee6bf53e6bfb9ee7060434bee4a1e6630c44301158d5a9c7275ca00d2a25c