aiox-core 5.0.4 → 5.0.5

package/pro/squads/design/checklists/ds-component-quality-checklist.md

@@ -1,150 +0,0 @@
-# Component Quality Checklist
-
-**Purpose:** Validate component before marking complete
-**Agent:** Merovingian (Design System Builder)
-**Standard:** Production-ready React/TypeScript components
-
----
-
-## CODE QUALITY
-
-- [ ] TypeScript compiles with zero errors
-  → Fix: Run `tsc --noEmit` and resolve each error by type. Most common: missing prop types, incorrect event handler signatures
-- [ ] No `any` types used
-  → Fix: Replace `any` with specific types. Use `unknown` + type guard for truly dynamic data. Search: `grep -rn ': any' src/`
-- [ ] Props fully typed with interface
-  → Fix: Create `interface {Component}Props` with each prop explicitly typed. Avoid `Record<string, unknown>` for known shapes
-- [ ] All props documented with TSDoc comments
-  → Fix: Add `/** description */` TSDoc comment above each prop in the interface. Include `@default` for optional props
-- [ ] Component exported correctly
-  → Fix: Ensure `export const {Component}` or named export in index.ts. Verify barrel file re-exports: `export { Component } from './Component'`
-
----
-
-## STYLING
-
-- [ ] All styling uses tokens (zero hardcoded values)
-  → Fix: `grep -rn '#[0-9a-f]' *.module.css` to find hardcoded values, replace with `var(--token-name)`
-- [ ] CSS Modules or chosen approach used consistently
-  → Fix: Rename .css to .module.css, update imports to `import styles from './X.module.css'`
-- [ ] No inline styles
-  → Fix: `grep -rn 'style={{' *.tsx` — move all inline styles to CSS Module classes
-- [ ] Responsive design implemented (if needed)
-  → Fix: Add `@media` queries for sm/md/lg breakpoints using token breakpoint values
-- [ ] All variants styled correctly
-  → Fix: Create CSS class per variant (`.primary`, `.secondary`), verify each renders differently in Storybook
-
----
-
-## ACCESSIBILITY (WCAG AA MINIMUM)
-
-- [ ] Semantic HTML elements used
-  → Fix: Replace `<div onClick>` with `<button>`, `<div>` navigation with `<nav>`, generic containers with `<section>`/`<article>`
-- [ ] ARIA attributes present where needed
-  → Fix: Add `aria-label` for icon-only buttons, `aria-expanded` for toggles, `role` only when no native semantic equivalent
-- [ ] Color contrast ≥4.5:1 for text
-  → Fix: Use `*contrast-matrix` to find failing pairs, adjust to nearest compliant token color
-- [ ] Keyboard navigation works (Tab, Enter, Space)
-  → Fix: Ensure `onKeyDown` handles Enter/Space for custom interactive elements. Native `<button>` gets this for free
-- [ ] Focus indicators visible
-  → Fix: Add `:focus-visible` style with `outline: 2px solid var(--color-focus)` and `outline-offset: 2px`
-- [ ] Disabled state handled correctly
-  → Fix: Add `aria-disabled="true"` + visual dimming + prevent onClick via `pointer-events: none` or early return
-- [ ] Screen reader tested (or documented)
-  → Fix: Test with VoiceOver (Mac: Cmd+F5) or NVDA (Windows). Document results in component README
-
----
-
-## TESTING
-
-- [ ] Unit tests written
-  → Fix: Create `{Component}.test.tsx` using React Testing Library. Start with render test, then add interaction tests
-- [ ] All variants tested
-  → Fix: Use `test.each` to iterate over variant values. Verify each variant applies the correct CSS class
-- [ ] All sizes tested
-  → Fix: Render each size, assert expected class or computed style. Use snapshot tests for visual regression
-- [ ] Disabled state tested
-  → Fix: Render with `disabled` prop, assert `aria-disabled`, verify click handler is NOT called
-- [ ] Event handlers tested
-  → Fix: Use `fireEvent.click()` or `userEvent.click()`, assert callback was called with expected args
-- [ ] Test coverage >80%
-  → Fix: Run `--coverage` flag, check uncovered lines. Add tests for branches (if/else, ternary, early returns)
-- [ ] All tests pass
-  → Fix: Run `npm test -- --watchAll=false`. Fix failures starting with type errors, then logic errors
-
----
-
-## DOCUMENTATION
-
-- [ ] Component.md created
-  → Fix: Copy template from `docs/templates/component.md`. Fill in purpose, API, and examples sections
-- [ ] Props documented with examples
-  → Fix: Add a props table with Name, Type, Default, Description columns. Include code snippet for each prop
-- [ ] Variants explained
-  → Fix: Show visual example or code snippet for each variant. Explain when to use which variant
-- [ ] Usage examples provided
-  → Fix: Add at least 3 examples: basic usage, with all props, and composition with other components
-- [ ] Accessibility notes included
-  → Fix: Document keyboard shortcuts, ARIA attributes used, and screen reader behavior
-
----
-
-## STORYBOOK (if enabled)
-
-- [ ] Stories file created
-  → Fix: Create `{Component}.stories.tsx` with `Meta` and `StoryObj` types from `@storybook/react`
-- [ ] Story for each variant
-  → Fix: Export a named story per variant (e.g., `export const Primary: Story = { args: { variant: 'primary' } }`)
-- [ ] Interactive controls work
-  → Fix: Ensure `argTypes` are defined in Meta. Use `control: 'select'` for enums, `control: 'boolean'` for flags
-- [ ] Stories display correctly
-  → Fix: Check Storybook console for warnings. Verify all stories render without errors in multiple viewports
-
----
-
-## Edge Cases
-
-- [ ] **Empty/null state:** Component handles `undefined` props gracefully (default values or explicit empty state UI)
-  → Fix: Add default values for all optional props, test with `<Component />` (no props)
-- [ ] **Loading state:** If async, component shows loading indicator with `aria-busy="true"`
-- [ ] **Error state:** Component displays error feedback (not just console.error) with `role="alert"`
-- [ ] **Long content:** Text overflow handled (truncation with `title` attribute or expand/collapse)
-  → Fix: Add `overflow: hidden; text-overflow: ellipsis` or `word-break: break-word` as appropriate
-- [ ] **RTL support:** Layout mirrors correctly for right-to-left languages (if i18n required)
-  → Fix: Use logical properties (`margin-inline-start` instead of `margin-left`)
-- [ ] **Recursive nesting:** Component renders correctly when nested inside itself
-  → Fix: Test recursive rendering, ensure no infinite loops in useEffect
-
----
-
-**Reviewer:** ________ **Date:** ________
-**Quality Gate:** [ ] PASS [ ] FAIL
-
----
-
-## Scoring
-
-### Point System
-Each checkbox item = 1 point.
-
-| Category | Items | Weight |
-|----------|-------|--------|
-| Code Quality (API Design) | 5 | 5pts |
-| Styling (Token Integration) | 5 | 5pts |
-| Accessibility | 7 | 7pts |
-| Testing | 7 | 7pts |
-| Documentation | 5 | 5pts |
-| Storybook | 4 | 4pts |
-| Edge Cases | 6 | 6pts |
-| **Total** | **39** | **39pts** |
-
-### Pass/Fail Thresholds
-| Grade | Score | Action |
-|-------|-------|--------|
-| PASS | >= 80% (32+) | Proceed to next phase |
-| CONDITIONAL | 60-79% (24-31) | Fix critical items, re-check |
-| FAIL | < 60% (23-) | Major rework required |
-
-### Auto-Correction
-If items fail:
-- Run `*ds-build-component --validate` to check token coverage. Use `*execute-checklist` for automated validation.

package/pro/squads/design/checklists/ds-critical-eye-review-checklist.md

@@ -1,147 +0,0 @@
-# Critical Eye — Canonical Review Checklist
-
-**Purpose:** Human checkpoint for STABLE → CANONICAL and CANONICAL → DEPRECATED transitions
-**Agent:** Design Chief (Design Principal)
-**Standard:** Enterprise DS governance — only the best pattern per category becomes canonical
-**Authority:** Nathan Curtis/EightShapes, GOV.UK Contribution Criteria, USWDS Lifecycle, Salesforce 4-Point Screening
-
----
-
-## CONTEXT
-
-- **Proposal ID:** ________
-- **Cycle:** ________
-- **Variant:** ________
-- **Category:** ________
-- **Proposed Transition:** [ ] STABLE → CANONICAL  [ ] CANONICAL → DEPRECATED
-- **Current Score:** ________/100
-- **Replacing (if deprecation):** ________
-
----
-
-## SCORE VERIFICATION
-
-- [ ] Total score >= 80 (canonical threshold)
-  → Fix: If score < 80, REJECT proposal. Variant needs improvement before canonical consideration.
-- [ ] Highest score in its category
-  → Fix: If not the leader, check comparison matrix. Only the best becomes canonical.
-- [ ] All 5 dimensions have non-null scores
-  → Fix: Re-run scoring if any dimension is null. Incomplete evaluation cannot be promoted.
-- [ ] No accessibility blocker (a11y > 0)
-  → Fix: Accessibility score = 0 is absolute REJECT. Cannot be overridden.
-
----
-
-## BREADTH (Nathan Curtis — Usage Breadth Scale)
-
-- [ ] Pattern appears in 2+ sources/brands
-  → Fix: Single-source patterns are snowflakes. Need adoption across brands before canonical status.
-- [ ] Source attributions are accurate (verified against brand.json files)
-  → Fix: Cross-reference variant.sources with actual brand files. Remove phantom sources.
-- [ ] Breadth score reflects actual usage, not just registration
-  → Fix: Verify the pattern is ACTUALLY USED in source brands, not just registered.
-
----
-
-## QUALITY (EightShapes Component QA 8+1)
-
-- [ ] Token compliance: zero hardcoded values
-  → Fix: Search component source for `#hex` and `Npx` values. Replace all with CSS custom properties.
-- [ ] States coverage: all required states implemented [default, hover, focus, disabled, error, loading]
-  → Fix: Check component for missing states. Focus and disabled are non-negotiable.
-- [ ] Accessibility: WCAG AA contrast + ARIA + keyboard + focus-visible
-  → Fix: Run contrast checker. Add missing ARIA attributes. Test keyboard navigation.
-- [ ] Responsiveness: works across mobile, tablet, desktop
-  → Fix: Test at 320px, 768px, 1024px widths minimum.
-- [ ] Composability: integrates with other canonical components
-  → Fix: Test composition with 3+ other components. No CSS hacks or overrides needed.
-- [ ] Resilience: handles edge cases (empty, long text, overflow, missing image)
-  → Fix: Test with empty props, 500-character strings, missing optional data.
-
----
-
-## CONSISTENCY (GOV.UK Contribution Criteria — Consistent)
-
-- [ ] Follows DS naming conventions (kebab-case, semantic prefixes)
-  → Fix: Rename files, props, and CSS classes to match established conventions.
-- [ ] API follows established patterns (CVA + variants + slots)
-  → Fix: Align prop signatures with other canonical components. Use same variant/size pattern.
-- [ ] Visually harmonious with rest of DS (indistinguishable quality)
-  → Fix: Compare side-by-side with existing canonicals. Spacing, typography, and color should match.
-
----
-
-## MATURITY (USWDS Component Lifecycle)
-
-- [ ] Stable for 3+ cycles (no breaking changes)
-  → Fix: Check lifecycleHistory. Recent major changes disqualify from canonical. Wait for stabilization.
-- [ ] Documentation complete (guidelines + API + examples + do/dont)
-  → Fix: Create missing documentation sections. Canonical components MUST have full docs.
-- [ ] Test coverage adequate (unit + a11y minimum)
-  → Fix: Add missing tests. Canonical components must demonstrate reliability.
-
----
-
-## SIMPLICITY (Brad Frost — Death to Complexity)
-
-- [ ] Reasonable LOC count (< 150 LOC preferred)
-  → Fix: Refactor complex components. Extract utilities. Simplify branching logic.
-- [ ] Minimal dependencies (0-2 external deps preferred)
-  → Fix: Evaluate if dependencies can be removed or replaced with lighter alternatives.
-
----
-
-## DEPRECATION-SPECIFIC (only for CANONICAL → DEPRECATED)
-
-- [ ] Replacement candidate scores > current + 10 points
-  → Fix: Margin must be significant (>10%) to justify disruption of deprecating a canonical.
-- [ ] Migration path documented for consumers
-  → Fix: Document exactly how existing usage should be updated. Provide codemod if possible.
-- [ ] Deprecation timeline defined (minimum 2 cycles grace period)
-  → Fix: Deprecated components remain available for at least 2 more cycles.
-
----
-
-## FINAL DECISION
-
-**Reviewer:** ________ **Date:** ________
-
-| Decision | Criteria |
-|----------|----------|
-| [ ] **APPROVE** | All checks pass. Transition is justified and beneficial. |
-| [ ] **APPROVE WITH CONDITIONS** | Minor issues to address, but transition is warranted. |
-| [ ] **DEFER** | Not ready yet. Specific improvements needed first. |
-| [ ] **REJECT** | Does not meet canonical/deprecation criteria. |
-
-**Conditions (if applicable):**
-________________________________________________________________________
-
-**Notes:**
-________________________________________________________________________
-
----
-
-## Scoring
-
-### Point System
-Each checkbox item = 1 point.
-
-| Category | Items | Weight |
-|----------|-------|--------|
-| Score Verification | 4 | 4pts |
-| Breadth | 3 | 3pts |
-| Quality | 6 | 6pts |
-| Consistency | 3 | 3pts |
-| Maturity | 3 | 3pts |
-| Simplicity | 2 | 2pts |
-| Deprecation (if applicable) | 3 | 3pts |
-| **Total (promotion)** | **21** | **21pts** |
-| **Total (deprecation)** | **24** | **24pts** |
-
-### Pass/Fail Thresholds
-| Grade | Score | Action |
-|-------|-------|--------|
-| APPROVE | >= 90% (19+/21 or 22+/24) | Execute transition |
-| APPROVE WITH CONDITIONS | 75-89% (16-18/21 or 18-21/24) | Execute with noted conditions |
-| DEFER | 60-74% (13-15/21 or 15-17/24) | Return for improvements |
-| REJECT | < 60% (12-/21 or 14-/24) | Do not transition |

package/pro/squads/design/checklists/ds-migration-readiness-checklist.md

@@ -1,99 +0,0 @@
-# Migration Readiness Checklist
-
-**Purpose:** Validate system ready for production migration
-**Agent:** Brad (Design System Architect)
-**Phase:** Before migration rollout
-
----
-
-## FOUNDATION (Phase 1 Ready)
-
-- [ ] Tokens generated and validated
-- [ ] Token exports created (JSON, CSS, Tailwind, SCSS)
-- [ ] Token coverage >95%
-- [ ] Build pipeline configured
-- [ ] No visual regressions in test environment
-
----
-
-## COMPONENTS (Phase 2 Ready)
-
-- [ ] High-impact components built (Button, Input, Card minimum)
-- [ ] All components pass quality checklist
-- [ ] Component tests passing (>80% coverage)
-- [ ] Documentation complete
-- [ ] Storybook deployed (if using)
-
----
-
-## MIGRATION PLAN
-
-- [ ] 4-phase migration strategy documented
-- [ ] Component mapping created (old → new)
-- [ ] Rollback procedures defined
-- [ ] Timeline realistic for team velocity
-- [ ] Stakeholder approval obtained
-
----
-
-## TEAM READINESS
-
-- [ ] Team trained on design system usage
-- [ ] Migration guide distributed
-- [ ] Support channel established
-- [ ] Code review process updated
-
----
-
-## RISK MITIGATION
-
-- [ ] Backups created
-- [ ] Feature flags enabled (if using)
-- [ ] Monitoring in place
-- [ ] Rollback tested
-- [ ] Emergency contacts defined
-
----
-
-## METRICS TRACKING
-
-- [ ] Baseline metrics captured
-- [ ] ROI tracking dashboard ready
-- [ ] Pattern usage monitoring enabled
-- [ ] Velocity metrics defined
-
----
-
-**Go/No-Go Decision:**
-[ ] GO - All critical items checked
-[ ] NO-GO - Blockers:_________________
-
-**Approved By:** ________ **Date:** ________
-
----
-
-## Scoring
-
-### Point System
-Each checkbox item = 1 point.
-
-| Category | Items | Weight |
-|----------|-------|--------|
-| Foundation (Token Coverage) | 5 | 5pts |
-| Components (Component Mapping) | 5 | 5pts |
-| Migration Plan (Risk Assessment) | 5 | 5pts |
-| Team Readiness | 4 | 4pts |
-| Risk Mitigation | 5 | 5pts |
-| Metrics Tracking | 4 | 4pts |
-| **Total** | **28** | **28pts** |
-
-### Pass/Fail Thresholds
-| Grade | Score | Action |
-|-------|-------|--------|
-| PASS | >= 80% (23+) | Proceed to next phase |
-| CONDITIONAL | 60-79% (17-22) | Fix critical items, re-check |
-| FAIL | < 60% (16-) | Major rework required |
-
-### Auto-Correction
-If items fail:
-- Run `*ds-audit-codebase` to verify token coverage >=95%. Use `*ds-generate-migration-strategy` for gap analysis.

package/pro/squads/design/checklists/ds-pattern-audit-checklist.md

@@ -1,164 +0,0 @@
-# Pattern Audit Checklist
-
-**Purpose:** Validate audit results before consolidation
-**Agent:** Brad (Design System Architect)
-**References:** audit-codebase.md task
-
----
-
-## SCAN COMPLETENESS
-
-- [ ] All UI file types detected (React, Vue, HTML, CSS)
-  → Fix: Verify scan config includes all extensions: `.tsx`, `.jsx`, `.vue`, `.html`, `.css`, `.scss`, `.module.css`. Add missing globs
-- [ ] Scan completed without critical errors
-  → Fix: Check scan logs for errors. Common: memory limits (increase `--max-old-space-size`), timeout (increase `--timeout`)
-- [ ] Total file count matches expectations
-  → Fix: Re-run scan with `find $path -name "*.tsx" -o -name "*.css" | wc -l` to verify. Exclude `node_modules`, `dist`, `.next`
-- [ ] No permission errors blocking scan
-  → Fix: Run with `sudo` or exclude restricted dirs with `--exclude-dir`. Check `.gitignore` patterns aren't over-filtering
-
----
-
-## PATTERN DETECTION
-
-### Buttons
-- [ ] Button instances counted accurately
-  → Fix: Verify regex matches `<button`, `<Button`, `role="button"`. Check for custom button components with non-standard names
-- [ ] Unique button patterns identified
-  → Fix: Deduplicate by visual fingerprint (class combos), not just tag name. Two `<button>` with different styles = 2 patterns
-- [ ] Redundancy factor calculated (instances / unique)
-  → Fix: Verify denominator (unique patterns) is correct. Manual spot-check 3 patterns against source code
-- [ ] Most-used buttons captured
-  → Fix: Sort by frequency descending. If top button has <5 instances, scan may have missed variants
-
-### Colors
-- [ ] Hex colors extracted (#RGB, #RRGGBB)
-  → Fix: Regex should match both 3-digit and 6-digit hex. Include uppercase: `/#[0-9a-fA-F]{3,8}/g` (covers 8-digit alpha hex)
-- [ ] RGB/RGBA colors extracted
-  → Fix: Match `rgb(`, `rgba(`, `hsl(`, `hsla(` patterns. Normalize to hex for deduplication
-- [ ] Total unique colors counted
-  → Fix: Normalize before counting: lowercase hex, collapse `#aabbcc` to `#abc`, convert rgb to hex. Avoid double-counting
-- [ ] Top 10 most-used colors identified
-  → Fix: Sort by occurrence count. If top color is white/black/transparent, consider filtering utility colors separately
-- [ ] Redundancy factor calculated
-  → Fix: Verify denominator (unique patterns) is correct. Manual spot-check 3 patterns against source files
-
-### Spacing
-- [ ] Padding values extracted
-  → Fix: Match `padding:`, `padding-top:`, shorthand values. Include Tailwind classes like `p-4`, `px-2` if applicable
-- [ ] Margin values extracted
-  → Fix: Match `margin:`, `margin-top:`, shorthand values. Include negative margins (`-mt-2`, `margin: -8px`)
-- [ ] Unique spacing values counted
-  → Fix: Normalize units (convert `1rem` = `16px`). Group near-identical values (14px vs 15px likely same intent)
-
-### Typography
-- [ ] Font families identified
-  → Fix: Match `font-family:`, CSS variables, Tailwind `font-` classes. Include fallback stacks as single entry
-- [ ] Font sizes extracted
-  → Fix: Match `font-size:`, `text-{size}` Tailwind classes. Normalize to px for comparison (1rem = 16px)
-- [ ] Font weights counted
-  → Fix: Match `font-weight:`, numeric values (400, 700) and keywords (normal, bold). Map keywords to numbers
-
-### Forms
-- [ ] Input elements counted
-  → Fix: Match `<input`, `<textarea`, `<select`, and custom input components. Check for uncontrolled vs controlled patterns
-- [ ] Form elements counted
-  → Fix: Match `<form`, `<fieldset`, `<legend`. Include form wrapper components with non-standard names
-- [ ] Unique patterns identified
-  → Fix: Classify by input type (`text`, `email`, `password`, `checkbox`, `radio`) + wrapper pattern. Each combo = unique pattern
-
----
-
-## OUTPUT VALIDATION
-
-- [ ] pattern-inventory.json generated
-  → Fix: Check output directory exists and is writable. Verify scan command includes `--output` flag pointing to correct path
-- [ ] JSON is valid and parseable
-  → Fix: Run `cat pattern-inventory.json | python -m json.tool` to validate. Common errors: trailing commas, unescaped quotes
-- [ ] All pattern types included
-  → Fix: Verify JSON has keys for: `buttons`, `colors`, `spacing`, `typography`, `forms`. Missing = scan config incomplete
-- [ ] Metadata complete (timestamp, scan path, file counts)
-  → Fix: Check JSON root for `metadata` object with `timestamp`, `scanPath`, `totalFiles`, `scanDuration` fields
-- [ ] .state.yaml created
-  → Fix: Verify state file path matches convention: `.state.yaml` in project root or `outputs/` directory
-- [ ] State file has valid YAML syntax
-  → Fix: Run `python -c "import yaml; yaml.safe_load(open('.state.yaml'))"` to validate. Check indentation (spaces, not tabs)
-- [ ] Phase set to "audit_complete"
-  → Fix: Open `.state.yaml`, verify `phase: audit_complete`. If missing, update manually and re-run validation
-
----
-
-## METRICS VALIDATION
-
-- [ ] Redundancy factors >1 (indicates duplication)
-  → Fix: If factor is exactly 1.0, either codebase has zero duplication (unlikely) or scan missed instances. Re-verify scan coverage
-- [ ] Pattern counts seem reasonable (not artificially inflated)
-  → Fix: Cross-reference with manual count of 1-2 pattern types. If automated count is >2x manual, check for false positives in regex
-- [ ] No zero counts for major pattern types (unless truly zero)
-  → Fix: Zero buttons/colors in a UI codebase = scan failure. Verify file extensions and scan path include UI source files
-
----
-
-## Edge Cases
-
-- [ ] **Monorepo scanning:** Patterns detected across packages, not just root
-- [ ] **Dynamic classes:** Tailwind JIT/dynamic classes (`bg-${color}-500`) counted correctly
-- [ ] **CSS-in-JS:** styled-components/emotion patterns included in scan
-- [ ] **Duplicate filenames:** Same component name in different directories counted separately
-- [ ] **Generated files:** Build artifacts (dist/, .next/) excluded from scan
-- [ ] **Theme override:** Pattern still works when design tokens are overridden by theme
-  → Fix: Test with alternate theme tokens, verify no hardcoded fallbacks break
-- [ ] **Optional slots:** Pattern handles missing optional slots/children gracefully
-  → Fix: Add conditional rendering for optional slots, test with minimal props
-- [ ] **Multi-framework:** Pattern works across all supported frameworks (React, Vue, etc.)
-  → Fix: Verify framework-agnostic token usage, no framework-specific APIs in shared code
-- [ ] **No-JS fallback:** Pattern degrades gracefully when JavaScript is disabled
-  → Fix: Ensure base HTML/CSS provides functional layout without JS enhancement
-
----
-
-## NEXT STEPS DECISION
-
-**If redundancy factors >3x:**
-- Proceed to *consolidate
-- Significant pattern reduction opportunity
-
-**If redundancy factors <2x:**
-- Codebase is relatively clean
-- Consider if design system is worth investment
-
-**If colors >50 or buttons >20:**
-- Major technical debt
-- Strong candidate for consolidation
-
----
-
-**Reviewer:** ________ **Date:** ________
-**Audit Quality:** [ ] Excellent [ ] Good [ ] Needs Review
-
----
-
-## Scoring
-
-### Point System
-Each checkbox item = 1 point.
-
-| Category | Items | Weight |
-|----------|-------|--------|
-| Scan Completeness (Pattern Inventory) | 4 | 4pts |
-| Pattern Detection (Redundancy Analysis + Classification) | 18 | 18pts |
-| Output Validation (Consolidation Readiness) | 7 | 7pts |
-| Metrics Validation | 3 | 3pts |
-| Edge Cases | 9 | 9pts |
-| **Total** | **41** | **41pts** |
-
-### Pass/Fail Thresholds
-| Grade | Score | Action |
-|-------|-------|--------|
-| PASS | >= 80% (33+) | Proceed to next phase |
-| CONDITIONAL | 60-79% (25-32) | Fix critical items, re-check |
-| FAIL | < 60% (24-) | Major rework required |
-
-### Auto-Correction
-If items fail:
-- Run `*ds-consolidate-patterns` to identify merge candidates. Use `*ds-scan-artifact` for pattern detection.