[UPDATE] Split Badge composed behavior

[egdev6]

Task: Split Badge composed behavior

Category

component

Team

Squad 1

Milestone

V1

Reference

• Parent tracker: refactor(v1): recatalog MVP primitives and atoms #224
• Accepted inventory: chore(v1): inventory MVP components and assign target taxonomy #223
• Validated child handoff: refactor(v1): recatalog MVP primitives and atoms #224 (comment)
• Cataloging guide: docs/COMPONENT-CATALOGING.md
• Cataloging guide English mirror: docs/COMPONENT-CATALOGING.en.md

Scope

Keep core Badge as an atom and extract/re-scope positioned wrapper behavior only when it is independently reviewable.

Out of scope:

• Moving unrelated primitives or changing Badge visual tokens.

Current workflow

• Issue triaged with Team and Category fields set on the Project board, and GitHub milestone assigned.
• Specification or plan recorded in this issue when behavior, API, accessibility, or tokens are affected.
• Validated spec reviewed and linked issue labeled status:approved before implementation starts.
• Assignee ownership checked before START WORK; if assigned to someone else, explicit reassignment permission documented.
• START WORK completed after label status:approved and assignee gate: assignee set, Project status moved to In progress, branch/worktree recorded.
• Implementation completed inside the approved scope.
• Validation evidence recorded in the PR or issue.
• PR opened and linked with Closes #NNN.
• PR merged or maintainer explicitly approved closure.
• END WORK completed: completion evidence added and Project status moved to Done.

Specification or plan

• Identify core Badge atom behavior.
• Identify positioned wrapper/composed behavior.
• Extract or defer composed wrapper with clear API boundaries.
• Preserve existing Badge consumers.

Accessibility impact

• Pattern or standard: native / Radix / WAI-ARIA APG / WCAG / not applicable, depending on the component.
• Keyboard impact: preserve current behavior for interactive components.
• Screen reader impact: preserve roles, names, states, and descriptions.
• Focus impact: preserve focus behavior where applicable.
• Contrast or reduced-motion impact: no visual token changes unless explicitly approved.
• Required accessibility validation: run component-specific accessibility checks when interaction or semantics are touched.

Validation plan

• targeted Badge tests
• Storybook story check
• TypeScript

Work start state

Filled during START WORK:

• Approval marker: issue label status:approved
• Assignee gate: unassigned / assigned to contributor / explicit reassignment permission
• Assignee:
• Branch: refactor/308-split-badge-composed-behavior
• Worktree:
• Project item ID:
• Project status: In progress

PR and completion evidence

Filled during PR review or END WORK:

• PR:
• Validation evidence:
• Component audit:
• Visual review:
• Follow-up issues:
• Closure basis: merged PR / explicit maintainer approval

Notes

Created from #224's validated child-issue handoff. Do not implement before START WORK verifies status:approved, assignee ownership, Project state, and branch/worktree.

Resources

• chore(mvp): define V1 component recatalogation handoff #222
• chore(v1): inventory MVP components and assign target taxonomy #223
• refactor(v1): recatalog MVP primitives and atoms #224