RELEASE QUALITY GATE

Evidence before Ready

Release status reflects review evidence, not an automatically calculated score.

Release gate steps

Quality v1.0

CURRENT REVIEW

Accessibility Review

Evidence is reviewed manually for this stage. A release can be marked Ready only when the required checks are complete.

Production Core v1.0 gate matrix

Quality v1.0

Gate 1TypeScriptnpx tsc --noEmitPass

Gate 2Design System ESLintcomponents/design-system: 0 errors / 0 warningsPass

Gate 3Studio ESLintapp/studio: 0 errors / 0 warningsPass

Gate 4Production BuildNext.js production route generationPass

Gate 5Public API contractTyped entry point and internal helper boundary reviewedPass

Gate 6Accessibility contractEdge keyboard and accessibility-tree checks passed; screen-reader listening session remains environment-requiredManual Required

Gate 7320px and large textEdge 320px execution passed across all required Studio routes; 200% effective reflow passedPass

Gate 8Reduced Motion / Forced ColorsEdge emulation matched both media queries; animation removal and visible control boundaries passedPass

Gate 9Regression75 static pages and required Studio routes generatedPass

Manual verification procedure

Quality v1.0

TabsFocus Overview, run Right/Left/Home/End, confirm disabled Archive is skipped and the matching panel is labelled.

Modal lifecycleOpen Dialog, Drawer, and Sheet from each trigger; cycle Tab/Shift+Tab, press Escape, then confirm focus returns to that trigger.

DismissalConfirm the standard backdrop closes; confirm Protected confirmation ignores the backdrop while Close, Cancel, Delete, and Escape remain available.

Toast queueCreate four notifications, confirm only three display, focus does not move, action/dismiss work, and the fourth appears after dismissal or timeout.

320px / 200%Review Form, Tabs, Feedback, and Overlay boards at 320px and 200% zoom for clipping, action collision, and page-level horizontal overflow.

User preferencesEmulate reduced motion and Windows forced colors; verify animations stop and control, focus, dialog, and toast boundaries remain visible.

Repository ESLint policy

Quality v1.0

Production Core PassStudio PassExisting Application debt Needs ReviewBackup debt Needs Review

A Design System release requires Core and Studio to remain at zero errors and warnings. Unrelated application debt is reported and tracked separately; it is never hidden, added to ignore rules, or treated as resolved.

Known issues and evidence

Quality v1.0

Existing project lint debt47 errors / 31 warnings remain in legacy areas including management modules and backups.New Design System and Studio changes must not increase this baseline.