Button

# Implement Button in your agent

## Objective
Implement Button for this verified behavior: A named control that performs an action in the current interface when activated.

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

## Required behavior
- Pointer, Enter, or Space activation runs one named action exactly once.
- The content region exposes its busy state while a separate visual indicator remains redundant.

## States to cover
- Save idle
- Save pending
- Save error
- Save successful

## Accessibility
- ARIA role: button
- The primary control or named region for Button has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names.
- A high-contrast focus indicator remains visible in every enabled visual variant and pending state.
- Not applicable: an action button does not open a surface unless that separate relationship is defined.
- Accessible name, disabled or pressed state when applicable, and pending result are exposed without changing the label ambiguously.
- Tab focuses the button
- Enter and Space activate it
- Form submit behavior follows its explicit type

## When not to use
- Activation primarily navigates to another URL
- The control has no clear action name

## Acceptance criteria
- The button performs an action rather than navigation
- Its visible label states that action
- Enter, Space, focus, disabled, and pending states work
- Text contrast and target size meet the quality bar

## 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 Button after implementation

## Objective
Audit the Button 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:e3ad88b2402fc89e324f39a708a5869e251812c4a777801dede95ecdf0634bb9

# Debug Button 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 Button.
- 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
- The button performs an action rather than navigation
- Its visible label states that action
- Enter, Space, focus, disabled, and pending states work
- Text contrast and target size meet the quality bar

## 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 Button regression

## Objective
Turn the reproduced cause into a focused regression test and compare Button 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:8aa43a1346558e33de34377af0d3377a092473973ba96d52a8af74b722130b33