aiox-core 5.0.3 → 5.0.4

package/pro/squads/design/tasks/ds-integrate-squad.md

@@ -1,130 +1,130 @@
-# Integrate with Squad
-
-> Task ID: atlas-integrate-squad
-> Agent: Merovingian (Design System Builder)
-> Version: 1.0.0
-> **Execution Type:** `Agent`
-> **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `integration`
-
-## Description
-
-Connect design system with MMOS, CreatorOS, or InnerLens expansion packs. Generates pack-specific patterns, token variations, and integration documentation.
-
-## Prerequisites
-
-- Design system setup complete
-- Components built
-- Target expansion pack installed
-
-## Workflow
-
-### Steps
-
-1. **Detect Target Pack** - Identify MMOS, CreatorOS, or InnerLens
-2. **Load Pack Requirements** - Read pack-specific pattern needs
-3. **Generate Token Variations** - Personality/theme-based tokens
-4. **Generate Pack-Specific Patterns** - Custom components for pack
-5. **Create Integration Hooks** - Connect pack workflows
-6. **Generate Integration Docs** - Usage guide for pack
-7. **Test Integration** - Validate pack can use patterns
-8. **Update State** - Track integration completion
-
-## Output
-
-- Pack-specific components
-- Token variations
-- Integration documentation
-- Example usage
-
-## Failure Handling
-
-- **Target pack not found in expected location:** If MMOS/CreatorOS/InnerLens directory does not exist at standard paths, prompt user for custom pack location or exit with "Pack not found — verify pack is installed and provide path"
-- **Pack-specific token variations conflict with base tokens:** If personality/theme tokens (e.g., MMOS formal mode) override base system tokens causing visual inconsistency, namespace the pack tokens (e.g., mmos-formal-*) and document in integration guide
-- **Pack imports fail due to missing dependencies:** If pack requires DS components not yet built (e.g., CreatorOS needs VideoPlayer but DS has no media components), generate placeholder component stubs and note "Stubs created for: {list} — implement full components before production"
-- **Integration test suite fails in pack context:** If DS components render incorrectly or error when imported by pack (e.g., missing context provider, broken prop types), isolate failing components, document integration requirements, and suggest pack-specific wrapper pattern
-
-## Success Criteria
-
-- [ ] Pack can import and use design system
-- [ ] Token variations work correctly
-- [ ] Pack-specific patterns functional
-- [ ] Integration documented
-- [ ] No regressions in pack functionality
-
-## Examples
-
-### MMOS Integration
-
-```typescript
-// Personality token variations
-{
-  formal: {
-    fontFamily: 'var(--font-serif)',
-    spacing: 'var(--space-formal)',
-    colorPrimary: 'var(--color-corporate)'
-  },
-  casual: {
-    fontFamily: 'var(--font-sans)',
-    spacing: 'var(--space-relaxed)',
-    colorPrimary: 'var(--color-friendly)'
-  }
-}
-
-// CloneChatInterface component
-<CloneChatInterface
-  personality="formal"
-  tokens={personalityTokens.formal}
-/>
-```
-
-### CreatorOS Integration
-
-```typescript
-// Educational token variations
-{
-  fonts: 'readable (18px)',
-  lineHeight: '1.6 (comprehension)',
-  spacing: 'generous',
-  colors: 'highlight focus'
-}
-
-// CourseVideoPlayer component
-<CourseVideoPlayer
-  tokens={educationalTokens}
-  accessibility="WCAG AAA"
-/>
-```
-
-### InnerLens Integration
-
-```typescript
-// Minimal distraction tokens
-{
-  colors: 'neutral, minimal',
-  layout: 'clean, focused',
-  spacing: 'balanced'
-}
-
-// AssessmentForm component
-<AssessmentForm
-  tokens={minimalTokens}
-  validationUI={systemValidation}
-/>
-```
-
-## Notes
-
-- Each pack has unique requirements
-- Token variations maintain consistency
-- Pack-specific components extend base system
-- Integration is bidirectional (pack ↔ design system)
-- Document in pack's README
-
-
-## Related Checklists
-
-- `squads/design/checklists/ds-component-quality-checklist.md`
-- `squads/design/checklists/ds-pattern-audit-checklist.md`
-
-## Process Guards
-- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.
+# Integrate with Squad
+
+> Task ID: atlas-integrate-squad
+> Agent: Merovingian (Design System Builder)
+> Version: 1.0.0
+> **Execution Type:** `Agent`
+> **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `integration`
+
+## Description
+
+Connect design system with MMOS, CreatorOS, or InnerLens expansion packs. Generates pack-specific patterns, token variations, and integration documentation.
+
+## Prerequisites
+
+- Design system setup complete
+- Components built
+- Target expansion pack installed
+
+## Workflow
+
+### Steps
+
+1. **Detect Target Pack** - Identify MMOS, CreatorOS, or InnerLens
+2. **Load Pack Requirements** - Read pack-specific pattern needs
+3. **Generate Token Variations** - Personality/theme-based tokens
+4. **Generate Pack-Specific Patterns** - Custom components for pack
+5. **Create Integration Hooks** - Connect pack workflows
+6. **Generate Integration Docs** - Usage guide for pack
+7. **Test Integration** - Validate pack can use patterns
+8. **Update State** - Track integration completion
+
+## Output
+
+- Pack-specific components
+- Token variations
+- Integration documentation
+- Example usage
+
+## Failure Handling
+
+- **Target pack not found in expected location:** If MMOS/CreatorOS/InnerLens directory does not exist at standard paths, prompt user for custom pack location or exit with "Pack not found — verify pack is installed and provide path"
+- **Pack-specific token variations conflict with base tokens:** If personality/theme tokens (e.g., MMOS formal mode) override base system tokens causing visual inconsistency, namespace the pack tokens (e.g., mmos-formal-*) and document in integration guide
+- **Pack imports fail due to missing dependencies:** If pack requires DS components not yet built (e.g., CreatorOS needs VideoPlayer but DS has no media components), generate placeholder component stubs and note "Stubs created for: {list} — implement full components before production"
+- **Integration test suite fails in pack context:** If DS components render incorrectly or error when imported by pack (e.g., missing context provider, broken prop types), isolate failing components, document integration requirements, and suggest pack-specific wrapper pattern
+
+## Success Criteria
+
+- [ ] Pack can import and use design system
+- [ ] Token variations work correctly
+- [ ] Pack-specific patterns functional
+- [ ] Integration documented
+- [ ] No regressions in pack functionality
+
+## Examples
+
+### MMOS Integration
+
+```typescript
+// Personality token variations
+{
+  formal: {
+    fontFamily: 'var(--font-serif)',
+    spacing: 'var(--space-formal)',
+    colorPrimary: 'var(--color-corporate)'
+  },
+  casual: {
+    fontFamily: 'var(--font-sans)',
+    spacing: 'var(--space-relaxed)',
+    colorPrimary: 'var(--color-friendly)'
+  }
+}
+
+// CloneChatInterface component
+<CloneChatInterface
+  personality="formal"
+  tokens={personalityTokens.formal}
+/>
+```
+
+### CreatorOS Integration
+
+```typescript
+// Educational token variations
+{
+  fonts: 'readable (18px)',
+  lineHeight: '1.6 (comprehension)',
+  spacing: 'generous',
+  colors: 'highlight focus'
+}
+
+// CourseVideoPlayer component
+<CourseVideoPlayer
+  tokens={educationalTokens}
+  accessibility="WCAG AAA"
+/>
+```
+
+### InnerLens Integration
+
+```typescript
+// Minimal distraction tokens
+{
+  colors: 'neutral, minimal',
+  layout: 'clean, focused',
+  spacing: 'balanced'
+}
+
+// AssessmentForm component
+<AssessmentForm
+  tokens={minimalTokens}
+  validationUI={systemValidation}
+/>
+```
+
+## Notes
+
+- Each pack has unique requirements
+- Token variations maintain consistency
+- Pack-specific components extend base system
+- Integration is bidirectional (pack ↔ design system)
+- Document in pack's README
+
+
+## Related Checklists
+
+- `squads/design/checklists/ds-component-quality-checklist.md`
+- `squads/design/checklists/ds-pattern-audit-checklist.md`
+
+## Process Guards
+- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.

package/pro/squads/design/tasks/ds-integrate-workspace.md

@@ -1,100 +1,100 @@
-# Integrate Design System with Workspace Structure
-
-> Task ID: brad-ds-integrate-workspace
-> Agent: Brad (Design System Architect)
-> Version: 1.0.0
-
-## Description
-
-Align the design system with the workspace topology:
-
-- `workspace/domains/design-system`
-- `workspace/system`
-- `workspace/ui`
-
-This task creates clear boundaries for tokens, primitives, patterns, and product-ready components.
-
-## Prerequisites
-
-- Existing design squad setup (`squads/design`)
-- Workspace directory available
-- Tailwind v4 strategy defined (`@theme`)
-- Decision on registry-first distribution (Shadcn model)
-
-## Workflow
-
-1. **Map Current State**
-- Inventory token files, component files, and style utilities.
-- Classify by role: token source, primitive, product UI.
-
-2. **Create Target Workspace Structure**
-- `workspace/domains/design-system/tokens/primitives`
-- `workspace/domains/design-system/tokens/semantic`
-- `workspace/domains/design-system/tokens/component`
-- `workspace/domains/design-system/themes`
-- `workspace/domains/design-system/metadata`
-- `workspace/system/primitives`
-- `workspace/system/patterns`
-- `workspace/ui/components`
-- `workspace/ui/blocks`
-
-3. **Define Ownership Boundaries**
-- `domains/design-system`: token truth and themes.
-- `system`: reusable Radix/Shadcn primitives and patterns.
-- `ui`: app-facing composed components and blocks.
-
-4. **Wire Configuration**
-- Add mapping files under `config/mappings/`:
-  - `colors.json`
-  - `spacing.json`
-  - `components.json`
-- Ensure mappings are generated from tokens, not hardcoded.
-
-5. **Integrate with Registry Flow**
-- Place `registry.json` in `workspace/ui/`.
-- Ensure component metadata references source paths and dependencies.
-
-6. **Validation**
-- Verify no circular dependencies between `domains`, `system`, and `ui`.
-- Verify component imports only flow upward:
-  - `domains` -> `system` -> `ui`
-- Validate with lint, typecheck, and tests.
-
-7. **Documentation**
-- Generate migration notes:
-  - old path -> new path
-  - rollback plan
-  - unresolved gaps
-
-## Deliverables
-
-- Workspace-aligned folder topology
-- Token ownership boundaries documented
-- Mapping config files added/updated
-- `workspace/ui/registry.json` strategy in place
-- Migration report with file move matrix
-
-## Success Criteria
-
-- [ ] Workspace layers are explicit and stable
-- [ ] Token hierarchy is split (primitives/semantic/component)
-- [ ] Registry flow resolves components from `workspace/ui`
-- [ ] Import direction is deterministic (`domains` -> `system` -> `ui`)
-- [ ] Migration steps documented and reproducible
-
-## Notes
-
-- Prefer configuration over hardcoded mappings.
-- Keep token names stable to avoid migration churn.
-- Treat workspace topology as architecture, not temporary structure.
-
-
-## Related Checklists
-
-- `squads/design/checklists/ds-component-quality-checklist.md`
-- `squads/design/checklists/ds-pattern-audit-checklist.md`
-
-## Process Guards
-- **Execution Type:** `Hybrid`
-- **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `design-system`
-- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.
+# Integrate Design System with Workspace Structure
+
+> Task ID: brad-ds-integrate-workspace
+> Agent: Brad (Design System Architect)
+> Version: 1.0.0
+
+## Description
+
+Align the design system with the workspace topology:
+
+- `workspace/domains/design-system`
+- `workspace/system`
+- `workspace/ui`
+
+This task creates clear boundaries for tokens, primitives, patterns, and product-ready components.
+
+## Prerequisites
+
+- Existing design squad setup (`squads/design`)
+- Workspace directory available
+- Tailwind v4 strategy defined (`@theme`)
+- Decision on registry-first distribution (Shadcn model)
+
+## Workflow
+
+1. **Map Current State**
+- Inventory token files, component files, and style utilities.
+- Classify by role: token source, primitive, product UI.
+
+2. **Create Target Workspace Structure**
+- `workspace/domains/design-system/tokens/primitives`
+- `workspace/domains/design-system/tokens/semantic`
+- `workspace/domains/design-system/tokens/component`
+- `workspace/domains/design-system/themes`
+- `workspace/domains/design-system/metadata`
+- `workspace/system/primitives`
+- `workspace/system/patterns`
+- `workspace/ui/components`
+- `workspace/ui/blocks`
+
+3. **Define Ownership Boundaries**
+- `domains/design-system`: token truth and themes.
+- `system`: reusable Radix/Shadcn primitives and patterns.
+- `ui`: app-facing composed components and blocks.
+
+4. **Wire Configuration**
+- Add mapping files under `config/mappings/`:
+  - `colors.json`
+  - `spacing.json`
+  - `components.json`
+- Ensure mappings are generated from tokens, not hardcoded.
+
+5. **Integrate with Registry Flow**
+- Place `registry.json` in `workspace/ui/`.
+- Ensure component metadata references source paths and dependencies.
+
+6. **Validation**
+- Verify no circular dependencies between `domains`, `system`, and `ui`.
+- Verify component imports only flow upward:
+  - `domains` -> `system` -> `ui`
+- Validate with lint, typecheck, and tests.
+
+7. **Documentation**
+- Generate migration notes:
+  - old path -> new path
+  - rollback plan
+  - unresolved gaps
+
+## Deliverables
+
+- Workspace-aligned folder topology
+- Token ownership boundaries documented
+- Mapping config files added/updated
+- `workspace/ui/registry.json` strategy in place
+- Migration report with file move matrix
+
+## Success Criteria
+
+- [ ] Workspace layers are explicit and stable
+- [ ] Token hierarchy is split (primitives/semantic/component)
+- [ ] Registry flow resolves components from `workspace/ui`
+- [ ] Import direction is deterministic (`domains` -> `system` -> `ui`)
+- [ ] Migration steps documented and reproducible
+
+## Notes
+
+- Prefer configuration over hardcoded mappings.
+- Keep token names stable to avoid migration churn.
+- Treat workspace topology as architecture, not temporary structure.
+
+
+## Related Checklists
+
+- `squads/design/checklists/ds-component-quality-checklist.md`
+- `squads/design/checklists/ds-pattern-audit-checklist.md`
+
+## Process Guards
+- **Execution Type:** `Hybrid`
+- **Dependencies:** depends_on: `[]` · enables: `[]` · workflow: `design-system`
+- **On Fail:** Stop execution, capture evidence, and return remediation steps before proceeding.