Each rule now has one owning contract; others point to it: validation and multi-step rules live in forms-validation (modal-workflows references them), pagination metadata lives in go-api (table-management references it), the async task flow lives in go-background-tasks (go-api references it), backup git-safety checks live in backup-management (go-database references it). Remove the leftover Vapor/Aqua baseline mention and stale kit/patterns paths, compress the batch-file-upload ADR narrative, and drop content-free pattern READMEs. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Table Management Pattern (Shared Module)
Shared reusable module for high-density table screens across patterns.
This module is the canonical source for:
- unified table toolbar layout (single container, grouped actions, vertical separators)
- icon-first action buttons with deterministic semantics
- select/actions narrow edge columns
- toolbar+table visual seam behavior (single continuous block)
Use this module as the base interaction contract for controls-selection.
Pattern-specific contracts should only define additions or exceptions.
Visual styling (colors, typography, surfaces) comes from ../web-visual-baseline/.
The behavior/layout contract is contract.md.