Breadcrumbs

# Implement Breadcrumbs in your agent

## Objective
Implement Breadcrumbs for this verified behavior: An ordered trail of links to ancestors of the current page that exposes its place in a site hierarchy.

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

## Required behavior
- Activating an ancestor link moves to that named level of the current hierarchy.
- Pointer, touch, or Enter follows the link; Space keeps its native page-scrolling behavior.

## States to cover
- Trail ready
- Ancestor focused
- Destination loaded

## Accessibility
- ARIA role: nav[aria-label] > ol > li > a[aria-current=page]
- The primary control or named region for Breadcrumbs has a stable accessible name from visible text or an explicit programmatic label; placeholder text and tooltips are not names.
- Visible focus remains on each ancestor link until navigation; a plain-text current page is not an extra tab stop.
- Breadcrumbs are persistent navigation and are not dismissible.
- Name the navigation landmark, expose the current linked page with aria-current=page, and hide decorative separators.
- Tab and Shift+Tab move among ancestor links
- Enter activates the focused link
- Decorative separators never receive focus

## When not to use
- The product is flat or only has peer pages
- The desired control is browser history or Back

## Acceptance criteria
- The landmark has a specific accessible name
- Ancestors are real links
- The current page is exposed once
- Separators are ignored by assistive technology

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

## Objective
Audit the Breadcrumbs 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:59589950f0a73cc3e59132a12cf3990cc53319d204b3245439238fcfdde75760

# Debug Breadcrumbs 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 Breadcrumbs.
- 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 landmark has a specific accessible name
- Ancestors are real links
- The current page is exposed once
- Separators are ignored by assistive technology

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

## Objective
Turn the reproduced cause into a focused regression test and compare Breadcrumbs 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:1a2138f7bcd8a4317e7c24c379dfdee9ef71146e03408b2aea3cffcbd048f361