aiox-core 5.0.3 → 5.0.4

package/pro/package.json

@@ -1,39 +1,39 @@
-{
-  "name": "@aiox-fullstack/pro",
-  "version": "0.2.0",
-  "description": "AIOX Pro: Premium features for Synkra AIOX",
-  "private": false,
-  "dependencies": {
-    "yaml": "^2.8.2"
-  },
-  "peerDependencies": {
-    "aiox-core": ">=4.0.0"
-  },
-  "engines": {
-    "node": ">=18"
-  },
-  "files": [
-    "squads/index.js",
-    "squads/README.md",
-    "squads/squad-creator-pro/",
-    "squads/design/",
-    "memory/",
-    "metrics/",
-    "integrations/",
-    "license/",
-    "feature-registry.yaml",
-    "pro-config.yaml",
-    "LICENSE",
-    "README.md"
-  ],
-  "publishConfig": {
-    "access": "public",
-    "registry": "https://registry.npmjs.org"
-  },
-  "repository": {
-    "type": "git",
-    "url": "git+https://github.com/SynkraAI/aios-pro.git"
-  },
-  "author": "SynkraAI",
-  "license": "SEE LICENSE IN LICENSE"
-}
+{
+  "name": "@aiox-fullstack/pro",
+  "version": "0.2.0",
+  "description": "AIOX Pro: Premium features for Synkra AIOX",
+  "private": false,
+  "dependencies": {
+    "yaml": "^2.8.2"
+  },
+  "peerDependencies": {
+    "aiox-core": ">=4.0.0"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "files": [
+    "squads/index.js",
+    "squads/README.md",
+    "squads/squad-creator-pro/",
+    "squads/design/",
+    "memory/",
+    "metrics/",
+    "integrations/",
+    "license/",
+    "feature-registry.yaml",
+    "pro-config.yaml",
+    "LICENSE",
+    "README.md"
+  ],
+  "publishConfig": {
+    "access": "public",
+    "registry": "https://registry.npmjs.org"
+  },
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/SynkraAI/aios-pro.git"
+  },
+  "author": "SynkraAI",
+  "license": "SEE LICENSE IN LICENSE"
+}

package/pro/pro-config.yaml

@@ -1,63 +1,63 @@
-# AIOS Pro Extension Configuration
-# This file is loaded by aios-core's config-resolver when pro/ submodule is present.
-# Reference: ADR-PRO-002 (Configuration Hierarchy)
-#
-# Merge behavior: Deep merge into project config at the "pro" namespace.
-# Priority: After L2 (project-config), before L3 (app-config).
-
-# Pro extension enabled flag
-# Set to false to disable all pro features without removing the submodule
-pro:
-  enabled: true
-  version: "0.1.0"
-
-# Premium Squads Configuration
-# Defines available premium squad templates and marketplace settings
-squads:
-  # Enable premium squad templates
-  premium_templates: true
-  # Marketplace integration (requires pro.integrations for full functionality)
-  marketplace:
-    enabled: false
-    # registry_url: "https://marketplace.synkra.ai/squads"
-
-# Persistent Memory Configuration
-# Cross-session context and memory analytics
-memory:
-  # Enable persistent memory store
-  persistent: false
-  # Storage backend (local | cloud)
-  backend: local
-  # Cross-session context sharing
-  cross_session: false
-  # Memory analytics and optimization
-  analytics: false
-
-# Usage Metrics Configuration
-# Dashboards, team analytics, and cost tracking
-metrics:
-  # Enable usage dashboards
-  dashboards: false
-  # Team-level analytics
-  team_analytics: false
-  # AI provider cost tracking
-  cost_tracking: false
-
-# Enterprise Integrations Configuration
-# Adapters for project management and collaboration tools
-integrations:
-  # Each integration can be enabled independently
-  gitlab:
-    enabled: false
-    # url: "https://gitlab.example.com"
-  bitbucket:
-    enabled: false
-  jira:
-    enabled: false
-    # url: "https://jira.example.com"
-  azure_devops:
-    enabled: false
-  clickup:
-    enabled: false
-  google_drive:
-    enabled: false
+# AIOS Pro Extension Configuration
+# This file is loaded by aios-core's config-resolver when pro/ submodule is present.
+# Reference: ADR-PRO-002 (Configuration Hierarchy)
+#
+# Merge behavior: Deep merge into project config at the "pro" namespace.
+# Priority: After L2 (project-config), before L3 (app-config).
+
+# Pro extension enabled flag
+# Set to false to disable all pro features without removing the submodule
+pro:
+  enabled: true
+  version: "0.1.0"
+
+# Premium Squads Configuration
+# Defines available premium squad templates and marketplace settings
+squads:
+  # Enable premium squad templates
+  premium_templates: true
+  # Marketplace integration (requires pro.integrations for full functionality)
+  marketplace:
+    enabled: false
+    # registry_url: "https://marketplace.synkra.ai/squads"
+
+# Persistent Memory Configuration
+# Cross-session context and memory analytics
+memory:
+  # Enable persistent memory store
+  persistent: false
+  # Storage backend (local | cloud)
+  backend: local
+  # Cross-session context sharing
+  cross_session: false
+  # Memory analytics and optimization
+  analytics: false
+
+# Usage Metrics Configuration
+# Dashboards, team analytics, and cost tracking
+metrics:
+  # Enable usage dashboards
+  dashboards: false
+  # Team-level analytics
+  team_analytics: false
+  # AI provider cost tracking
+  cost_tracking: false
+
+# Enterprise Integrations Configuration
+# Adapters for project management and collaboration tools
+integrations:
+  # Each integration can be enabled independently
+  gitlab:
+    enabled: false
+    # url: "https://gitlab.example.com"
+  bitbucket:
+    enabled: false
+  jira:
+    enabled: false
+    # url: "https://jira.example.com"
+  azure_devops:
+    enabled: false
+  clickup:
+    enabled: false
+  google_drive:
+    enabled: false

package/pro/squads/README.md

@@ -1,24 +1,24 @@
-# Premium Squads
-
-Pre-built agent squads installed during `npx aiox-core install` after Pro license activation.
-
-## Available Squads
-
-| Squad | Agents | Description |
-|-------|--------|-------------|
-| **squad-creator-pro** | 3 | Meta-squad for creating AI agent squads based on real elite minds |
-| **design** | 8 | Design System squad — tokens, components, accessibility, DesignOps |
-
-## How It Works
-
-1. User runs `npx aiox-core install` and activates Pro license
-2. `@aiox-fullstack/pro` npm package is installed
-3. Scaffolder copies all squads from this directory into the user's project `squads/`
-4. Agent commands are auto-installed into active IDEs (Claude Code, Codex, Gemini, Cursor)
-
-## Adding New Squads
-
-1. Develop in `pro/private-squads/` (not published)
-2. When ready, move to `pro/squads/`
-3. Add to `package.json` `files` array
-4. Bump version and publish
+# Premium Squads
+
+Pre-built agent squads installed during `npx aiox-core install` after Pro license activation.
+
+## Available Squads
+
+| Squad | Agents | Description |
+|-------|--------|-------------|
+| **squad-creator-pro** | 3 | Meta-squad for creating AI agent squads based on real elite minds |
+| **design** | 8 | Design System squad — tokens, components, accessibility, DesignOps |
+
+## How It Works
+
+1. User runs `npx aiox-core install` and activates Pro license
+2. `@aiox-fullstack/pro` npm package is installed
+3. Scaffolder copies all squads from this directory into the user's project `squads/`
+4. Agent commands are auto-installed into active IDEs (Claude Code, Codex, Gemini, Cursor)
+
+## Adding New Squads
+
+1. Develop in `pro/private-squads/` (not published)
+2. When ready, move to `pro/squads/`
+3. Add to `package.json` `files` array
+4. Bump version and publish

package/pro/squads/design/HEADLINE.md

@@ -1,3 +1,3 @@
-# DESIGN — HEADLINE v3 (Copy Squad)
-
-Eu vou criar um design system unificado para todos os seus produtos em 30 dias — sem contratar 4 designers e sem cada tela ter uma cara diferente.
+# DESIGN — HEADLINE v3 (Copy Squad)
+
+Eu vou criar um design system unificado para todos os seus produtos em 30 dias — sem contratar 4 designers e sem cada tela ter uma cara diferente.

package/pro/squads/design/README.md

@@ -1,109 +1,109 @@
-# Design System Squad
-
-**Version:** 4.2.0  
-**Command:** `/DS`  
-**Type:** Specialist Squad
-
-## Overview
-
-The Design System Squad is focused only on:
-
-- token architecture and governance
-- component system design and composition
-- accessibility governance (WCAG)
-- design system operations and adoption
-- registry and AI-readable metadata
-
-Domain work like brand, logo, thumbnails, photo, and editing was moved to dedicated squads:
-
-- `squads/brand`
-- `squads/content-visual`
-
-## Agents
-
-| Agent | Command | Specialty |
-|---|---|---|
-| Design Chief | `@design-chief` | Orchestration and routing |
-| Brad Frost | `@brad-frost` | Atomic design, components, tokens |
-| Dan Mall | `@dan-mall` | Stakeholder buy-in and DS adoption |
-| Dave Malouf | `@dave-malouf` | DesignOps and operating model |
-| Nano Banana | `@nano-banana-generator` | Visual utility support |
-| Atlas | `@ds-token-architect` | Figma-to-tokens/component specs |
-| Foundations Lead | `@ds-foundations-lead` | Orchestrates F1/F2/F3 foundations pipeline |
-| Storybook Expert | `@storybook-expert` | Story architecture, interaction tests, visual regression |
-
-## Routing
-
-Use Design Chief as entrypoint:
-
-- `"auditar design system"` -> `@brad-frost`
-- `"escalar operacao de design"` -> `@dave-malouf`
-- `"preciso vender DS internamente"` -> `@dan-mall`
-- `"metadata/registry para AI"` -> `@brad-frost`
-- `"preciso de logo/brand"` -> handoff to `/Brand`
-- `"thumbnail/foto/video"` -> handoff to `/ContentVisual`
-
-## Core Tasks
-
-- `ds-*`: architecture, audit, tokenization, migration, registry, metadata, MCP
-- `agentic-*`: machine-readability audit and AI-ready setup
-- `token-*`: W3C DTCG extraction and token modes governance
-- `motion-*`: motion quality and visual regression baselines
-- `fluent-*`: Fluent 2 audit/build compatibility tracks
-- `ds-govern`, `ds-designops`: governance model and DesignOps operating playbook
-- `figma-pipeline`: Figma MCP integration and design-to-code mapping
-- `f1-*`, `f2-*`, `f3-*`: foundations pipeline with blocking QA gates
-- `a11y-*`: accessibility audits and governance
-- `atomic-refactor-*`: decomposition and execution
-- `designops-*`: maturity, scaling, process and tooling
-- `design-triage`, `design-review-orchestration`: orchestration gates
-
-## Workflows
-
-- `workflows/audit-only.yaml`
-- `workflows/brownfield-complete.yaml`
-- `workflows/greenfield-new.yaml`
-- `workflows/self-healing-workflow.yaml`
-- `workflows/agentic-readiness.yaml`
-- `workflows/dtcg-tokens-governance.yaml`
-- `workflows/motion-quality.yaml`
-- `workflows/foundations-pipeline.yaml`
-- `workflows/critical-eye.yaml`
-
-## Modelo de Governance
-
-### Princípio: Governance cria, Execution usa
-
-O squad segue a regra fundamental de separação entre **governance** e **execution**:
-
-- **Governance** define tokens, regras, templates, checklists e protocolos. Esses artefatos são criados e mantidos pelos agentes do squad dentro de `squads/design/`.
-- **Execution** consome esses artefatos sem modificá-los. Agentes de desenvolvimento, CI/CD e IDEs leem as definições e aplicam as regras durante a implementação.
-
-O protocolo completo está documentado em `squads/design/protocols/ai-first-governance.md`.
-
-### Tier System
-
-Definido em `squads/design/config.yaml`:
-
-| Tier | Papel |
-|------|-------|
-| **tier_0_foundation** | Agentes de entrada para operações e estratégia de adoção |
-| **tier_1_masters** | Masters de execução com práticas especialistas |
-| **tier_2_specialists** | Especialistas profundos para implementação de DS |
-| **orchestrator** | Design Chief — roteia requisições para o agente adequado |
-
-### Hierarquia de Fontes Canônicas
-
-Ordem de precedência para resolução de conflitos:
-
-1. `workspace/` — fonte de verdade global (system, ui, domains)
-2. `squads/design/` — governança e conhecimento local do squad
-3. `docs/` — evidência de suporte, nunca fonte final de verdade
-
-Quando dois artefatos conflitam, prevalece a fonte de maior precedência. Conflitos devem ser registrados conforme o protocolo de governance.
-
-## Notes
-
-- Source hierarchy: `workspace/` -> `squads/design/` -> `docs/`
-- This squad is DS-only by design.
-- Cross-domain requests are routed to specialized squads instead of being executed here.
+# Design System Squad
+
+**Version:** 4.2.0  
+**Command:** `/DS`  
+**Type:** Specialist Squad
+
+## Overview
+
+The Design System Squad is focused only on:
+
+- token architecture and governance
+- component system design and composition
+- accessibility governance (WCAG)
+- design system operations and adoption
+- registry and AI-readable metadata
+
+Domain work like brand, logo, thumbnails, photo, and editing was moved to dedicated squads:
+
+- `squads/brand`
+- `squads/content-visual`
+
+## Agents
+
+| Agent | Command | Specialty |
+|---|---|---|
+| Design Chief | `@design-chief` | Orchestration and routing |
+| Brad Frost | `@brad-frost` | Atomic design, components, tokens |
+| Dan Mall | `@dan-mall` | Stakeholder buy-in and DS adoption |
+| Dave Malouf | `@dave-malouf` | DesignOps and operating model |
+| Nano Banana | `@nano-banana-generator` | Visual utility support |
+| Atlas | `@ds-token-architect` | Figma-to-tokens/component specs |
+| Foundations Lead | `@ds-foundations-lead` | Orchestrates F1/F2/F3 foundations pipeline |
+| Storybook Expert | `@storybook-expert` | Story architecture, interaction tests, visual regression |
+
+## Routing
+
+Use Design Chief as entrypoint:
+
+- `"auditar design system"` -> `@brad-frost`
+- `"escalar operacao de design"` -> `@dave-malouf`
+- `"preciso vender DS internamente"` -> `@dan-mall`
+- `"metadata/registry para AI"` -> `@brad-frost`
+- `"preciso de logo/brand"` -> handoff to `/Brand`
+- `"thumbnail/foto/video"` -> handoff to `/ContentVisual`
+
+## Core Tasks
+
+- `ds-*`: architecture, audit, tokenization, migration, registry, metadata, MCP
+- `agentic-*`: machine-readability audit and AI-ready setup
+- `token-*`: W3C DTCG extraction and token modes governance
+- `motion-*`: motion quality and visual regression baselines
+- `fluent-*`: Fluent 2 audit/build compatibility tracks
+- `ds-govern`, `ds-designops`: governance model and DesignOps operating playbook
+- `figma-pipeline`: Figma MCP integration and design-to-code mapping
+- `f1-*`, `f2-*`, `f3-*`: foundations pipeline with blocking QA gates
+- `a11y-*`: accessibility audits and governance
+- `atomic-refactor-*`: decomposition and execution
+- `designops-*`: maturity, scaling, process and tooling
+- `design-triage`, `design-review-orchestration`: orchestration gates
+
+## Workflows
+
+- `workflows/audit-only.yaml`
+- `workflows/brownfield-complete.yaml`
+- `workflows/greenfield-new.yaml`
+- `workflows/self-healing-workflow.yaml`
+- `workflows/agentic-readiness.yaml`
+- `workflows/dtcg-tokens-governance.yaml`
+- `workflows/motion-quality.yaml`
+- `workflows/foundations-pipeline.yaml`
+- `workflows/critical-eye.yaml`
+
+## Modelo de Governance
+
+### Princípio: Governance cria, Execution usa
+
+O squad segue a regra fundamental de separação entre **governance** e **execution**:
+
+- **Governance** define tokens, regras, templates, checklists e protocolos. Esses artefatos são criados e mantidos pelos agentes do squad dentro de `squads/design/`.
+- **Execution** consome esses artefatos sem modificá-los. Agentes de desenvolvimento, CI/CD e IDEs leem as definições e aplicam as regras durante a implementação.
+
+O protocolo completo está documentado em `squads/design/protocols/ai-first-governance.md`.
+
+### Tier System
+
+Definido em `squads/design/config.yaml`:
+
+| Tier | Papel |
+|------|-------|
+| **tier_0_foundation** | Agentes de entrada para operações e estratégia de adoção |
+| **tier_1_masters** | Masters de execução com práticas especialistas |
+| **tier_2_specialists** | Especialistas profundos para implementação de DS |
+| **orchestrator** | Design Chief — roteia requisições para o agente adequado |
+
+### Hierarquia de Fontes Canônicas
+
+Ordem de precedência para resolução de conflitos:
+
+1. `workspace/` — fonte de verdade global (system, ui, domains)
+2. `squads/design/` — governança e conhecimento local do squad
+3. `docs/` — evidência de suporte, nunca fonte final de verdade
+
+Quando dois artefatos conflitam, prevalece a fonte de maior precedência. Conflitos devem ser registrados conforme o protocolo de governance.
+
+## Notes
+
+- Source hierarchy: `workspace/` -> `squads/design/` -> `docs/`
+- This squad is DS-only by design.
+- Cross-domain requests are routed to specialized squads instead of being executed here.