@dcrackel/hematournamentui 1.0.698 → 1.0.701

package/AGENTS.md

@@ -22,6 +22,7 @@ This project is `@dcrackel/hematournamentui`, the shared Vue 3 Storybook/UI pack
 - Keep local component state only for UI-only behavior, such as folding/unfolding menus, open/closed modal state when locally controlled, transient hover/focus state, input draft display, and similar presentation concerns.
 - Do not add API clients, socket code, localStorage workflow state, or route-level orchestration to this package unless the explicit goal is to create a reusable UI API around those concerns.
 - Clone incoming objects before building emitted payloads when the component may add or reshape UI-specific fields.
+- Do not mutate incoming props or nested prop data. Clone arrays/objects into local UI state before adding UI-only fields such as `Promoted`, `customStatus`, local order, temporary scores, or modal draft state. Emit changed intent upward for the parent to persist.
 - Keep emitted payload shapes stable. If an event contract changes, update the related Storybook examples and consuming documentation.
 
 ## Atomic Design
@@ -48,6 +49,7 @@ This project is `@dcrackel/hematournamentui`, the shared Vue 3 Storybook/UI pack
 - Keep logic out of templates/JSX where practical. Move meaningful conditions, transformations, and class decisions into named computed values or helpers.
 - Keep Vue methods focused. Fetching, transforming, emitting, and local UI state updates should be separable when practical.
 - Prefer explicit `emits` declarations and prop definitions that document component contracts.
+- Keep emitted event names and payload fields aligned through wrapper components. When forwarding child events, use the same semantic event name, such as `penalty:add` for adding and `penalty:update` for updating, instead of compensating with swapped handlers.
 - Use watchers sparingly. Prefer computed values and direct event handlers unless side effects are truly needed.
 - Keep Storybook stories aligned with the public component API and use them to demonstrate meaningful states, variants, empty states, disabled states, and responsive behavior.
 
@@ -82,4 +84,5 @@ This project is `@dcrackel/hematournamentui`, the shared Vue 3 Storybook/UI pack
 - Useful commands include `npm run lint`, `npm run build-storybook`, `npm run build:tailwind`, and `npm run test`.
 - For component behavior changes, verify emitted events, optimistic display updates, prop reconciliation, empty states, disabled states, and responsive layout.
 - For public API changes, update Storybook stories and check the consuming app contract.
+- Keep Storybook args aligned with component props. Stories should use `{ args: { ... } }`, include required props in every variant, and use correct control types for arrays, objects, booleans, and text.
 - Avoid running package version/publish flows unless explicitly requested. `npm run build` currently patches the package version as part of the script.