From 894c5caeb9544740cfe4c5db20ff7026378ec44a Mon Sep 17 00:00:00 2001 From: Rafael Costa Date: Sun, 17 May 2026 10:08:27 -0300 Subject: [PATCH 1/3] fix: align legacy path references with current directory layout (closes #741) MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The framework directory layout was reorganized at some point with templates, checklists, tasks, agents, workflows, and agent-teams moving under `.aiox-core/` subdirectories (`product/`, `development/`), but ~70 references across docs, tasks, and the knowledge base never followed. The result: `@po *validate-story-draft` (and other story-flow steps) tries to load template paths like `aiox-core/templates/story-tmpl.yaml` that no longer exist, breaking the Story Development Cycle at the validation gate as reported by @renatolhamas in #741. ## Mapping applied | Legacy path | Current path | |---|---| | `aiox-core/templates/` | `.aiox-core/product/templates/` | | `aiox-core/checklists/` | `.aiox-core/product/checklists/` | | `aiox-core/agents/` | `.aiox-core/development/agents/` | | `aiox-core/tasks/` | `.aiox-core/development/tasks/` | | `aiox-core/workflows/` | `.aiox-core/development/workflows/` | | `aiox-core/agent-teams/` | `.aiox-core/development/agent-teams/` | | `aiox-core/data/` | `.aiox-core/data/` (data did NOT move into a subdir; only the prefix gets the dot) | Note the leading dot: `aiox-core/` → `.aiox-core/`. The post-reorganization codebase already uses the dotted form (`.aiox-core/...`); only the legacy non-dotted references needed updating. A negative-lookbehind `(?/` so already-correct dotted references stay intact. Audit verifies zero remaining matches across `.aiox-core/` and `docs/`: ``` $ grep -rnE "['\\\`\\\"]aiox-core/(templates|tasks|checklists|agents|data|workflows|agent-teams)/" .aiox-core/ docs/ | grep -v "\\.aiox-core" | wc -l 0 ``` ## Out of scope (deferred) Other legacy refs that exist in the codebase but were not part of the reorganization that #741 reports: - `aiox-core/core-config.yaml` (root-level config, not a subdir reorg) - `aiox-core/tools/mcp/clickup.yaml` (only 1 occurrence in aiox-kb.md — needs separate decision on where this should live, will follow up) These are 1-off references that don't break the story flow and need their own decision per ref. Co-Authored-By: Claude Opus 4.7 (1M context) --- .../core/docs/component-creation-guide.md | 6 +- .aiox-core/data/aiox-kb.md | 16 +- .aiox-core/data/entity-registry.yaml | 176 +++++------------- .../tasks/architect-analyze-impact.md | 8 +- .../development/tasks/create-next-story.md | 4 +- .../tasks/dev-validate-next-story.md | 4 +- .aiox-core/development/tasks/modify-agent.md | 6 +- .aiox-core/development/tasks/modify-task.md | 6 +- .aiox-core/development/tasks/pr-automation.md | 10 +- .../development/tasks/sm-create-next-story.md | 4 +- .../development/tasks/validate-next-story.md | 4 +- .aiox-core/install-manifest.yaml | 44 ++--- .aiox-core/user-guide.md | 2 +- docs/core-architecture.md | 14 +- docs/es/core-architecture.md | 14 +- .../ux-design-expert-execution-trace.md | 10 +- docs/pt/core-architecture.md | 14 +- docs/zh/core-architecture.md | 14 +- 18 files changed, 133 insertions(+), 223 deletions(-) diff --git a/.aiox-core/core/docs/component-creation-guide.md b/.aiox-core/core/docs/component-creation-guide.md index be793579fc..21078ffcd9 100644 --- a/.aiox-core/core/docs/component-creation-guide.md +++ b/.aiox-core/core/docs/component-creation-guide.md @@ -397,8 +397,8 @@ This shows: ### Getting Help -1. **Check component examples**: `aiox-core/agents/examples/` -2. **Review templates**: `aiox-core/templates/` +1. **Check component examples**: `.aiox-core/development/agents/examples/` +2. **Review templates**: `.aiox-core/product/templates/` 3. **Run validation**: `*validate-component` 4. **Ask meta-agent**: `*help create-agent` @@ -406,7 +406,7 @@ This shows: ### Custom Templates -Create custom templates in `aiox-core/templates/custom/`: +Create custom templates in `.aiox-core/product/templates/custom/`: ```yaml # custom-agent-template.yaml diff --git a/.aiox-core/data/aiox-kb.md b/.aiox-core/data/aiox-kb.md index 4f5771d1be..154a32227b 100644 --- a/.aiox-core/data/aiox-kb.md +++ b/.aiox-core/data/aiox-kb.md @@ -349,20 +349,20 @@ The AIOX-Method is built around a modular architecture centered on the `aiox-cor ### Key Architectural Components -#### 1. Agents (`aiox-core/agents/`) +#### 1. Agents (`.aiox-core/development/agents/`) - **Purpose**: Each markdown file defines a specialized AI agent for a specific Agile role (PM, Dev, Architect, etc.) - **Structure**: Contains YAML headers specifying the agent's persona, capabilities, and dependencies - **Dependencies**: Lists of tasks, templates, checklists, and data files the agent can use - **Startup Instructions**: Can load project-specific documentation for immediate context -#### 2. Agent Teams (`aiox-core/agent-teams/`) +#### 2. Agent Teams (`.aiox-core/development/agent-teams/`) - **Purpose**: Define collections of agents bundled together for specific purposes - **Examples**: `team-all.yaml` (comprehensive bundle), `team-fullstack.yaml` (full-stack development) - **Usage**: Creates pre-packaged contexts for web UI environments -#### 3. Workflows (`aiox-core/workflows/`) +#### 3. Workflows (`.aiox-core/development/workflows/`) - **Purpose**: YAML files defining prescribed sequences of steps for specific project types - **Types**: Greenfield (new projects) and Brownfield (existing projects) for UI, service, and fullstack development @@ -370,10 +370,10 @@ The AIOX-Method is built around a modular architecture centered on the `aiox-cor #### 4. Reusable Resources -- **Templates** (`aiox-core/templates/`): Markdown templates for PRDs, architecture specs, user stories -- **Tasks** (`aiox-core/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" -- **Checklists** (`aiox-core/checklists/`): Quality assurance checklists for validation and review -- **Data** (`aiox-core/data/`): Core knowledge base and technical preferences +- **Templates** (`.aiox-core/product/templates/`): Markdown templates for PRDs, architecture specs, user stories +- **Tasks** (`.aiox-core/development/tasks/`): Instructions for specific repeatable actions like "shard-doc" or "create-next-story" +- **Checklists** (`.aiox-core/product/checklists/`): Quality assurance checklists for validation and review +- **Data** (`.aiox-core/data/`): Core knowledge base and technical preferences ### Dual Environment Architecture @@ -756,7 +756,7 @@ custom_fields: **Where to find examples:** - Complete workflow: `aiox-core/tools/mcp/clickup.yaml` (story_creation_workflow section) -- Task instructions: `aiox-core/tasks/create-next-story.md` (sections 5.1 and 5.3) +- Task instructions: `.aiox-core/development/tasks/create-next-story.md` (sections 5.1 and 5.3) - Validators: `aiox-core/tools/mcp/clickup.yaml` (executable_knowledge section) **Response Handling:** diff --git a/.aiox-core/data/entity-registry.yaml b/.aiox-core/data/entity-registry.yaml index 77afb35385..2c93f99525 100644 --- a/.aiox-core/data/entity-registry.yaml +++ b/.aiox-core/data/entity-registry.yaml @@ -1,6 +1,6 @@ metadata: version: 1.0.0 - lastUpdated: '2026-05-17T10:02:45.444Z' + lastUpdated: '2026-05-17T12:22:53.099Z' entityCount: 815 checksumAlgorithm: sha256 resolutionRate: 100 @@ -16,8 +16,7 @@ entities: - mcp - server - task - usedBy: - - devops + usedBy: [] dependencies: - analyst externalDeps: [] @@ -601,8 +600,7 @@ entities: - docs - links - check-docs-links - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -627,8 +625,7 @@ entities: - configure - ci/cd - pipeline - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: @@ -681,7 +678,6 @@ entities: usedBy: - list-worktrees - remove-worktree - - devops dependencies: [] externalDeps: [] plannedDeps: [] @@ -1093,7 +1089,6 @@ entities: - list-worktrees - remove-worktree - dev - - devops - auto-worktree dependencies: - worktree-manager @@ -1881,8 +1876,7 @@ entities: - access - grant - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -1904,8 +1898,7 @@ entities: - pro - activate - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -1928,8 +1921,7 @@ entities: - check - access - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -1952,8 +1944,7 @@ entities: - request - reset - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -1976,8 +1967,7 @@ entities: - resend - verification - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -2000,8 +1990,7 @@ entities: - reset - password - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -2024,8 +2013,7 @@ entities: - validate - login - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -2048,8 +2036,7 @@ entities: - verify - status - 'task:' - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -2132,7 +2119,6 @@ entities: - environment-bootstrap usedBy: - setup-github - - devops dependencies: - config-resolver - github-cli.yaml @@ -2492,7 +2478,6 @@ entities: - github-pr-automation.md usedBy: - resolve-github-issue - - devops dependencies: - repository-detector - devops-helper @@ -2526,9 +2511,7 @@ entities: - gate - pre-push-quality-gate.md usedBy: - - publish-npm - resolve-github-issue - - devops dependencies: - repository-detector - devops-helper @@ -2555,8 +2538,7 @@ entities: - repository - cleanup - repository-cleanup.md - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: @@ -2581,8 +2563,7 @@ entities: - version - management - version-management.md - usedBy: - - devops + usedBy: [] dependencies: - repository-detector externalDeps: [] @@ -2920,8 +2901,7 @@ entities: - list - mcps - list-mcps - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -2945,7 +2925,6 @@ entities: - create-worktree - remove-worktree - dev - - devops dependencies: - worktree-manager - create-worktree @@ -2994,7 +2973,6 @@ entities: - merge-worktree usedBy: - create-worktree - - devops dependencies: [] externalDeps: [] plannedDeps: [] @@ -3628,28 +3606,23 @@ entities: path: .aiox-core/development/tasks/publish-npm.md layer: L2 type: task - purpose: 'Safe, validated npm publishing using a two-phase release strategy:' + purpose: npm Publishing Pipeline keywords: - publish - npm - publishing - - 'pipeline:' - - preview - - latest + - pipeline usedBy: [] - dependencies: - - release-management - - github-devops-pre-push-quality-gate - - release-checklist + dependencies: [] externalDeps: [] plannedDeps: [] - lifecycle: experimental + lifecycle: orphan adaptability: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:d69f833690fd01256c9b99cc7bd7bb67704f5894ffa9171af7cb94253ecd98cd - lastVerified: '2026-05-17T10:02:45.143Z' + checksum: sha256:60ce8f90fbe932294dd103f507240413ad75bc2ea9be01a6224de65a9e282f54 + lastVerified: '2026-05-17T12:22:53.093Z' qa-after-creation: path: .aiox-core/development/tasks/qa-after-creation.md layer: L2 @@ -4191,31 +4164,27 @@ entities: path: .aiox-core/development/tasks/release-management.md layer: L2 type: task - purpose: 'To automate the complete software release process, including:' + purpose: Manage Software Releases keywords: - release - management - manage - software - releases - usedBy: - - publish-npm - - devops - dependencies: - - po - - devops + usedBy: [] + dependencies: [] externalDeps: [] plannedDeps: - package - github-devops-checklist - execute-task.js - lifecycle: production + lifecycle: experimental adaptability: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:80a9a1ead93c66bfe59cb75215661052e7b4abccc483cd9d01a07034fca2311c - lastVerified: '2026-05-17T10:02:45.153Z' + checksum: sha256:fc4dd795b0ebc886a0de09452a70764eab5958eae894da639ae2df1829c9dd50 + lastVerified: '2026-05-17T12:22:53.093Z' remove-mcp: path: .aiox-core/development/tasks/remove-mcp.md layer: L2 @@ -4225,8 +4194,7 @@ entities: - remove - mcp - remove-mcp - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -4250,7 +4218,6 @@ entities: - create-worktree - list-worktrees - dev - - devops dependencies: - worktree-manager - create-worktree @@ -4278,7 +4245,6 @@ entities: - resolve-github-issue.md usedBy: - triage-github-issues - - devops dependencies: - triage-github-issues - github-devops-pre-push-quality-gate @@ -4408,8 +4374,7 @@ entities: - mcp - catalog - task - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -4548,8 +4513,7 @@ entities: - setup - github - setup-github - usedBy: - - devops + usedBy: [] dependencies: - environment-bootstrap - github-cli.yaml @@ -4602,8 +4566,7 @@ entities: - mcp - docker - toolkit - usedBy: - - devops + usedBy: [] dependencies: - devops externalDeps: [] @@ -5295,7 +5258,6 @@ entities: - triage-github-issues.md usedBy: - resolve-github-issue - - devops dependencies: - resolve-github-issue - devops @@ -5986,8 +5948,7 @@ entities: keywords: - changelog - template - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -6193,8 +6154,7 @@ entities: - actions - cd - template - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -6215,8 +6175,7 @@ entities: - actions - ci - template - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -6238,8 +6197,7 @@ entities: - template - pull - request - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -14575,7 +14533,6 @@ entities: - list-worktrees - qa-gate - qa-review-story - - release-management - remove-worktree - resolve-github-issue - setup-github @@ -14588,46 +14545,7 @@ entities: - codex-rules - memory-audit-checklist - greenfield-fullstack - dependencies: - - environment-bootstrap - - setup-github - - github-devops-version-management - - github-devops-pre-push-quality-gate - - github-devops-github-pr-automation - - ci-cd-configuration - - github-devops-repository-cleanup - - release-management - - search-mcp - - add-mcp - - list-mcps - - remove-mcp - - setup-mcp-docker - - check-docs-links - - triage-github-issues - - resolve-github-issue - - devops-pro-access-grant - - devops-pro-check-access - - devops-pro-request-reset - - devops-pro-resend-verification - - devops-pro-reset-password - - devops-pro-validate-login - - devops-pro-verify-status - - devops-pro-activate - - create-worktree - - list-worktrees - - remove-worktree - - cleanup-worktrees - - merge-worktree - - github-pr-template - - github-actions-ci.yml - - github-actions-cd.yml - - changelog-template - - pre-push-checklist - - release-checklist - - github-cli - - asset-inventory.js - - path-analyzer.js - - migrate-agent.js + dependencies: [] externalDeps: - coderabbit - git @@ -14639,8 +14557,8 @@ entities: score: 0.3 constraints: [] extensionPoints: [] - checksum: sha256:260b04cc608c1ddcd9ed2cf210e5d22f045002a4c0059f8220abcd3dc67a1cd8 - lastVerified: '2026-05-17T10:02:45.316Z' + checksum: sha256:5c52cc74f923ac381fa92fb969607b80a35f34b958c02d2d1edd1115f7690d35 + lastVerified: '2026-05-17T12:22:53.091Z' pm: path: .aiox-core/development/agents/pm.md layer: L2 @@ -14723,7 +14641,6 @@ entities: - qa-backlog-add-followup - qa-fix-issues - qa-gate - - release-management - story-checkpoint - validate-next-story - design-story-tmpl @@ -16184,8 +16101,7 @@ entities: keywords: - asset - inventory - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -16896,8 +16812,7 @@ entities: keywords: - migrate - agent - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -16983,8 +16898,7 @@ entities: keywords: - path - analyzer - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -18499,7 +18413,6 @@ entities: - environment-bootstrap - setup-github - health-check-checks-services-index - - devops - po dependencies: [] externalDeps: [] @@ -19068,8 +18981,7 @@ entities: - pre-push - quality - gate - usedBy: - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] @@ -19088,9 +19000,7 @@ entities: keywords: - release - checklist - usedBy: - - publish-npm - - devops + usedBy: [] dependencies: [] externalDeps: [] plannedDeps: [] diff --git a/.aiox-core/development/tasks/architect-analyze-impact.md b/.aiox-core/development/tasks/architect-analyze-impact.md index dff82ada1b..2224a915a9 100644 --- a/.aiox-core/development/tasks/architect-analyze-impact.md +++ b/.aiox-core/development/tasks/architect-analyze-impact.md @@ -227,16 +227,16 @@ Analyze the potential impact of proposed component modifications on the broader ## Examples ```bash # Analyze impact of modifying an agent -*analyze-impact modify aiox-core/agents/weather-agent.md --depth deep --include-tests +*analyze-impact modify .aiox-core/development/agents/weather-agent.md --depth deep --include-tests # Analyze deprecation impact with visual output *analyze-impact deprecate aiox-core/scripts/old-helper.js --output-format visual --save-report reports/deprecation-impact.html # Quick impact check for refactoring -*analyze-impact refactor aiox-core/tasks/process-data.md --depth shallow --risk-threshold medium +*analyze-impact refactor .aiox-core/development/tasks/process-data.md --depth shallow --risk-threshold medium # Analyze removal with approval workflow -*analyze-impact remove aiox-core/workflows/legacy-workflow.yaml --depth deep --save-report reports/removal-impact.json +*analyze-impact remove .aiox-core/development/workflows/legacy-workflow.yaml --depth deep --save-report reports/removal-impact.json ``` ## Implementation @@ -792,7 +792,7 @@ module.exports = AnalyzeImpactTask; ```json { "success": true, - "targetComponent": "aiox-core/agents/weather-agent.md", + "targetComponent": ".aiox-core/development/agents/weather-agent.md", "riskLevel": "medium", "affectedComponents": 12, "propagationDepth": 3, diff --git a/.aiox-core/development/tasks/create-next-story.md b/.aiox-core/development/tasks/create-next-story.md index 3b8618629b..3c2568c1e2 100644 --- a/.aiox-core/development/tasks/create-next-story.md +++ b/.aiox-core/development/tasks/create-next-story.md @@ -772,14 +772,14 @@ Use the primary agent from "Specialized Agent Assignment" to determine which sel - Verify all source references are included for technical details - Ensure tasks align with both epic requirements and architecture constraints - Update status to "Draft" and save the story file -- Execute `aiox-core/tasks/execute-checklist` `aiox-core/checklists/story-draft-checklist` +- Execute `.aiox-core/development/tasks/execute-checklist` `.aiox-core/product/checklists/story-draft-checklist` - Provide summary to user including: - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md` - Status: Draft - Key technical components included from architecture docs - Any deviations or conflicts noted between epic and architecture - Checklist Results - - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `aiox-core/tasks/validate-next-story` + - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.aiox-core/development/tasks/validate-next-story` **ClickUp Integration Note:** This task now includes Epic verification (Section 5.1), ClickUp story task creation (Section 5.3), and automatic frontmatter updates (Section 5.4). Stories are created as subtasks of their parent Epic in ClickUp's Backlog list. If Epic verification or ClickUp sync fails, the story file will still be created locally with a warning message. diff --git a/.aiox-core/development/tasks/dev-validate-next-story.md b/.aiox-core/development/tasks/dev-validate-next-story.md index 686e5331e8..8f8b57ca82 100644 --- a/.aiox-core/development/tasks/dev-validate-next-story.md +++ b/.aiox-core/development/tasks/dev-validate-next-story.md @@ -225,11 +225,11 @@ To comprehensively validate a story draft before implementation begins, ensuring - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Parent epic**: The epic containing this story's requirements - **Architecture documents**: Based on configuration (sharded or monolithic) - - **Story template**: `aiox-core/templates/story-tmpl.yaml` for completeness validation + - **Story template**: `.aiox-core/product/templates/story-tmpl.yaml` for completeness validation ### 1. Template Completeness Validation -- Load `aiox-core/templates/story-tmpl.yaml` and extract all section headings from the template +- Load `.aiox-core/product/templates/story-tmpl.yaml` and extract all section headings from the template - **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Agent section verification**: Confirm all sections from template exist for future agent use diff --git a/.aiox-core/development/tasks/modify-agent.md b/.aiox-core/development/tasks/modify-agent.md index 96c61df145..d9c5179362 100644 --- a/.aiox-core/development/tasks/modify-agent.md +++ b/.aiox-core/development/tasks/modify-agent.md @@ -229,7 +229,7 @@ To safely modify existing agent definitions while preserving their structure, ma ## Prerequisites -- Target agent must exist in `aiox-core/agents/` +- Target agent must exist in `.aiox-core/development/agents/` - User must provide modification intent or specific changes - Backup system must be available for rollback - Git must be initialized for version tracking @@ -238,9 +238,9 @@ To safely modify existing agent definitions while preserving their structure, ma ### 1. Agent Analysis and Backup -- Load target agent from `aiox-core/agents/{agent-name}.md` +- Load target agent from `.aiox-core/development/agents/{agent-name}.md` - Parse YAML header and markdown content separately -- Create timestamped backup: `aiox-core/agents/.backups/{agent-name}.md.{timestamp}` +- Create timestamped backup: `.aiox-core/development/agents/.backups/{agent-name}.md.{timestamp}` - Extract current structure: - Agent metadata (name, id, title, icon, whenToUse) - Dependencies (tasks, templates, checklists, data) diff --git a/.aiox-core/development/tasks/modify-task.md b/.aiox-core/development/tasks/modify-task.md index b0910e5b5e..641ccfe95f 100644 --- a/.aiox-core/development/tasks/modify-task.md +++ b/.aiox-core/development/tasks/modify-task.md @@ -229,7 +229,7 @@ To safely modify existing task definitions while maintaining their effectiveness ## Prerequisites -- Target task must exist in `aiox-core/tasks/` +- Target task must exist in `.aiox-core/development/tasks/` - User must provide modification intent or specific changes - Backup system must be available for rollback - Understanding of task dependencies and usage @@ -238,8 +238,8 @@ To safely modify existing task definitions while maintaining their effectiveness ### 1. Task Analysis and Backup -- Load target task from `aiox-core/tasks/{task-name}.md` -- Create timestamped backup: `aiox-core/tasks/.backups/{task-name}.md.{timestamp}` +- Load target task from `.aiox-core/development/tasks/{task-name}.md` +- Create timestamped backup: `.aiox-core/development/tasks/.backups/{task-name}.md.{timestamp}` - Analyze task structure: - Purpose and prerequisites - Task execution steps diff --git a/.aiox-core/development/tasks/pr-automation.md b/.aiox-core/development/tasks/pr-automation.md index bb1d1567b5..9f51c43b7b 100644 --- a/.aiox-core/development/tasks/pr-automation.md +++ b/.aiox-core/development/tasks/pr-automation.md @@ -39,7 +39,7 @@ To help users contribute to the AIOX open-source project (`aiox-core`) by automa - **contribution_path**: `string` - **Description**: Path to new/modified files - - **Example**: `"Squads/my-new-pack/"` or `"aiox-core/agents/improved-agent.md"` + - **Example**: `"Squads/my-new-pack/"` or `".aiox-core/development/agents/improved-agent.md"` - **Validation**: Path must exist locally ### Optional Parameters @@ -109,8 +109,8 @@ To help users contribute to the AIOX open-source project (`aiox-core`) by automa 3. **Detect Contribution Type** (if not provided) - Scan modified files: - `Squads/*` → "Squad" - - `aiox-core/agents/*` → "agent" - - `aiox-core/tasks/*` → "task" + - `.aiox-core/development/agents/*` → "agent" + - `.aiox-core/development/tasks/*` → "task" - `aiox-core/tools/*` → "tool" - `*.md` in docs → "documentation" - `*.test.js` or bug fixes → "bug-fix" @@ -649,7 +649,7 @@ aiox pr create \ ```bash aiox pr create \ --type="agent" \ - --path="aiox-core/agents/improved-po.md" \ + --path=".aiox-core/development/agents/improved-po.md" \ --title="feat(agent): enhance PO agent with story validation" ``` @@ -660,7 +660,7 @@ aiox pr create \ ```bash aiox pr create \ --type="bug-fix" \ - --path="aiox-core/tasks/create-next-story.md" \ + --path=".aiox-core/development/tasks/create-next-story.md" \ --title="fix(task): correct file path validation in create-next-story" ``` diff --git a/.aiox-core/development/tasks/sm-create-next-story.md b/.aiox-core/development/tasks/sm-create-next-story.md index a28fb9446b..e5c313540c 100644 --- a/.aiox-core/development/tasks/sm-create-next-story.md +++ b/.aiox-core/development/tasks/sm-create-next-story.md @@ -468,13 +468,13 @@ custom_fields: - Verify all source references are included for technical details - Ensure tasks align with both epic requirements and architecture constraints - Update status to "Draft" and save the story file -- Execute `aiox-core/tasks/execute-checklist` `aiox-core/checklists/story-draft-checklist` +- Execute `.aiox-core/development/tasks/execute-checklist` `.aiox-core/product/checklists/story-draft-checklist` - Provide summary to user including: - Story created: `{devStoryLocation}/{epicNum}.{storyNum}.story.md` - Status: Draft - Key technical components included from architecture docs - Any deviations or conflicts noted between epic and architecture - Checklist Results - - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `aiox-core/tasks/validate-next-story` + - Next steps: For Complex stories, suggest the user carefully review the story draft and also optionally have the PO run the task `.aiox-core/development/tasks/validate-next-story` **ClickUp Integration Note:** This task now includes Epic verification (Section 5.1), ClickUp story task creation (Section 5.3), and automatic frontmatter updates (Section 5.4). Stories are created as subtasks of their parent Epic in ClickUp's Backlog list. If Epic verification or ClickUp sync fails, the story file will still be created locally with a warning message. diff --git a/.aiox-core/development/tasks/validate-next-story.md b/.aiox-core/development/tasks/validate-next-story.md index 85cc74cf3f..65164515e1 100644 --- a/.aiox-core/development/tasks/validate-next-story.md +++ b/.aiox-core/development/tasks/validate-next-story.md @@ -225,11 +225,11 @@ To comprehensively validate a story draft before implementation begins, ensuring - **Story file**: The drafted story to validate (provided by user or discovered in `devStoryLocation`) - **Parent epic**: The epic containing this story's requirements - **Architecture documents**: Based on configuration (sharded or monolithic) - - **Story template**: `aiox-core/templates/story-tmpl.yaml` for completeness validation + - **Story template**: `.aiox-core/product/templates/story-tmpl.yaml` for completeness validation ### 1. Template Completeness Validation -- Load `aiox-core/templates/story-tmpl.yaml` and extract all section headings from the template +- Load `.aiox-core/product/templates/story-tmpl.yaml` and extract all section headings from the template - **Missing sections check**: Compare story sections against template sections to verify all required sections are present - **Placeholder validation**: Ensure no template placeholders remain unfilled (e.g., `{{EpicNum}}`, `{{role}}`, `_TBD_`) - **Agent section verification**: Confirm all sections from template exist for future agent use diff --git a/.aiox-core/install-manifest.yaml b/.aiox-core/install-manifest.yaml index 2750ab68ad..8eafb37cb0 100644 --- a/.aiox-core/install-manifest.yaml +++ b/.aiox-core/install-manifest.yaml @@ -8,7 +8,7 @@ # - File types for categorization # version: 5.2.6 -generated_at: "2026-05-17T12:22:51.608Z" +generated_at: "2026-05-17T13:08:28.080Z" generator: scripts/generate-install-manifest.js file_count: 1128 files: @@ -1289,15 +1289,15 @@ files: type: data size: 10938 - path: data/aiox-kb.md - hash: sha256:958065f2d734189edf2868aae322114b16546502e213b9a948547af4e8c178f9 + hash: sha256:7ceaab838b4586a5314f0edea431f09fbc4dd82eb386f89db4442d1212add352 type: data - size: 34306 + size: 34390 - path: data/capability-detection.js hash: sha256:317d1b51b5cda2e35ac6d468e33e05c0948e6d7f05f51d750d7ce6ff5a58535a type: data size: 9590 - path: data/entity-registry.yaml - hash: sha256:7a1dc65b0661069cdccf8babb7c3320320281f10a8e5258a3cba26b8953df5ad + hash: sha256:910cf52ea4d999bccf255c431db5648663d2de5a871a18068fc443adaab3379c type: data size: 572193 - path: data/learned-patterns.yaml @@ -1845,9 +1845,9 @@ files: type: task size: 9106 - path: development/tasks/architect-analyze-impact.md - hash: sha256:251d2c073b917f0285672568f074ec0c77372e110e234b42f043c605e438d9ee + hash: sha256:73ad65e2263dac7a5a3aa64736d2c803c8a532c269b83fb98a61cb5729b689db type: task - size: 26656 + size: 26708 - path: development/tasks/audit-codebase.md hash: sha256:11a136d6e7cd6d5238a06a9298eff28d381799667612aa7668d923cc40c74ff7 type: task @@ -1965,9 +1965,9 @@ files: type: task size: 10334 - path: development/tasks/create-next-story.md - hash: sha256:0705fe3750d229b47fe194109d3ec398cb90adfdfe1a6d7cf80ca8bdf73b6ad0 + hash: sha256:4c8ce97f47ad9b0fb316bee47eae46fe7c9fbacb897f3062eaedd8a925511afc type: task - size: 30564 + size: 30599 - path: development/tasks/create-service.md hash: sha256:dd9467f3e646ca4058f0cc524f99ae102c91750fa70f412f41f50f89d8f4b4e9 type: task @@ -2101,9 +2101,9 @@ files: type: task size: 24669 - path: development/tasks/dev-validate-next-story.md - hash: sha256:6dda51884ce7a5dd814d026aab3f2125d399e89b468b2125673c19ade9091ace + hash: sha256:b3c533f925077c73d18d8c9b4b69783493f1c690fd562df9546f9169f82bbe14 type: task - size: 11364 + size: 11382 - path: development/tasks/devops-pro-access-grant.md hash: sha256:11d2b342a39a95acfbd5dbb7abe9c25a9511035b9ca46abac86ec40f60d6a011 type: task @@ -2281,13 +2281,13 @@ files: type: task size: 930 - path: development/tasks/modify-agent.md - hash: sha256:74e6ef74967508f8a05cfc629bac7d5ffd5bd67c7d598cc623fd426442049824 + hash: sha256:31d7d543b8994605e10fbbdce3ca52d5d6d0938832f053baa5a0ca50238f7e33 type: task - size: 9846 + size: 9885 - path: development/tasks/modify-task.md - hash: sha256:e81346cb686226a2bca0657e9c6367adcbf76d6cbd5d81cc892702c3a655d96a + hash: sha256:b02ca96a6ffebac281a6f0640228c39a62d723414a50481bf6ef8ad05c92cfd3 type: task - size: 10877 + size: 10916 - path: development/tasks/modify-workflow.md hash: sha256:7cbfc3488912240b0782d116b27c5410d724c7822f94efe6cd64df954c3b4b50 type: task @@ -2361,9 +2361,9 @@ files: type: task size: 6896 - path: development/tasks/pr-automation.md - hash: sha256:90bba47136ccc37c74454a4537728b958955fd487e46e3b8dca869b994c8d1c1 + hash: sha256:956147dfb7f42983b249041173b85fd75419f71b9018f9991f2b3aa7e59e3885 type: task - size: 19031 + size: 19096 - path: development/tasks/project-status.md hash: sha256:3cb76eeb42b7e0b46a06ce0827bc68d2f507a7f4021174b1bd9e68d82463e5e6 type: task @@ -2533,9 +2533,9 @@ files: type: task size: 14707 - path: development/tasks/sm-create-next-story.md - hash: sha256:86ee70cbe6ac6812dd9bbacc6e591046a9def3455efba19581155258173f91ba + hash: sha256:e5ee6bc856fba12867557c0684d566d520516b4ff0c96e9df91f260786106bd0 type: task - size: 18062 + size: 18097 - path: development/tasks/spec-assess-complexity.md hash: sha256:860d6c4641282a426840ccea8bed766c8eddeb9806e4e0a806a330f70e5b6eca type: task @@ -2661,9 +2661,9 @@ files: type: task size: 3595 - path: development/tasks/validate-next-story.md - hash: sha256:f121211b1fbe915e181399d10bd30c435aec55c0af9b49d99c533473574a4907 + hash: sha256:277faba94cba30ac3773159d641fc2b8a345efd70dcfef6bae15f8a6280128ea type: task - size: 18848 + size: 18866 - path: development/tasks/validate-tech-preset.md hash: sha256:50a65289c223c1a79b0bebe4120f3f703df45d42522309e658f6d0f5c9fdb54e type: task @@ -4441,9 +4441,9 @@ files: type: script size: 1708 - path: user-guide.md - hash: sha256:7da0c760ea094eed7ce04a1f12fa977f29f90e8e7a9b8824c671cdfc9ddede6e + hash: sha256:aa0b56817c7e438d732fd7f37a2c11ca64c9d9907ada3f31cb088b7b4c498ac7 type: documentation - size: 38240 + size: 38249 - path: workflow-intelligence/__tests__/confidence-scorer.test.js hash: sha256:237216842d3eb710ae33f3aba6c7b2a6a353cccc1dea6d4b927d8d063d9cb635 type: workflow-intelligence diff --git a/.aiox-core/user-guide.md b/.aiox-core/user-guide.md index a0b3af7d11..a792ec02b1 100644 --- a/.aiox-core/user-guide.md +++ b/.aiox-core/user-guide.md @@ -1325,7 +1325,7 @@ Workflows: data-analysis.yml, ml-model.yml ### Criar Templates Customizados -Adicione templates próprios em `aiox-core/templates/`: +Adicione templates próprios em `.aiox-core/product/templates/`: ```markdown --- diff --git a/docs/core-architecture.md b/docs/core-architecture.md index 7cc7bf4246..d8d3f7cfb4 100644 --- a/docs/core-architecture.md +++ b/docs/core-architecture.md @@ -67,7 +67,7 @@ graph TD The `aiox-core` directory contains all the definitions and resources that give the agents their capabilities. -### 3.1. Agents (`aiox-core/agents/`) +### 3.1. Agents (`.aiox-core/development/agents/`) - **Purpose**: These are the foundational building blocks of the system. Each markdown file (e.g., `aiox-master.md`, `pm.md`, `dev.md`) defines the persona, capabilities, and dependencies of a single AI agent. - **Structure**: An agent file contains a YAML header that specifies its role, persona, dependencies, and startup instructions. These dependencies are lists of tasks, templates, checklists, and data files that the agent is allowed to use. @@ -75,12 +75,12 @@ The `aiox-core` directory contains all the definitions and resources that give t - **Document Integration**: Agents can reference and load documents from the project's `docs/` folder as part of tasks, workflows, or startup sequences. Users can also drag documents directly into chat interfaces to provide additional context. - **Example**: The `aiox-master` agent lists its dependencies, which tells the build tool which files to include in a web bundle and informs the agent of its own capabilities. -### 3.2. Agent Teams (`aiox-core/agent-teams/`) +### 3.2. Agent Teams (`.aiox-core/development/agent-teams/`) - **Purpose**: Team files (e.g., `team-all.yaml`) define collections of agents and workflows that are bundled together for a specific purpose, like "full-stack development" or "backend-only". This creates a larger, pre-packaged context for web UI environments. - **Structure**: A team file lists the agents to include. It can use wildcards, such as `"*"` to include all agents. This allows for the creation of comprehensive bundles like `team-all`. -### 3.3. Workflows (`aiox-core/workflows/`) +### 3.3. Workflows (`.aiox-core/development/workflows/`) - **Purpose**: Workflows are YAML files (e.g., `greenfield-fullstack.yaml`) that define a prescribed sequence of steps and agent interactions for a specific project type. They act as a strategic guide for the user and the `aiox-orchestrator` agent. - **Structure**: A workflow defines sequences for both complex and simple projects, lists the agents involved at each step, the artifacts they create, and the conditions for moving from one step to the next. It often includes a Mermaid diagram for visualization. @@ -102,15 +102,15 @@ The AIOX framework employs a sophisticated template processing system orchestrat - **`template-format.md`** (`aiox-core/utils/`): Defines the foundational markup language used throughout all AIOX templates. This specification establishes syntax rules for variable substitution (`{{placeholders}}`), AI-only processing directives (`[[LLM: instructions]]`), and conditional logic blocks. Templates follow this format to ensure consistent processing across the system. -- **`create-doc.md`** (`aiox-core/tasks/`): Acts as the orchestration engine that manages the entire document generation workflow. This task coordinates template selection, manages user interaction modes (incremental vs. rapid generation), enforces template-format processing rules, and handles validation. It serves as the primary interface between users and the template system. +- **`create-doc.md`** (`.aiox-core/development/tasks/`): Acts as the orchestration engine that manages the entire document generation workflow. This task coordinates template selection, manages user interaction modes (incremental vs. rapid generation), enforces template-format processing rules, and handles validation. It serves as the primary interface between users and the template system. -- **`advanced-elicitation.md`** (`aiox-core/tasks/`): Provides an interactive refinement layer that can be embedded within templates through `[[LLM: instructions]]` blocks. This component offers 10 structured brainstorming actions, section-by-section review capabilities, and iterative improvement workflows to enhance content quality. +- **`advanced-elicitation.md`** (`.aiox-core/development/tasks/`): Provides an interactive refinement layer that can be embedded within templates through `[[LLM: instructions]]` blocks. This component offers 10 structured brainstorming actions, section-by-section review capabilities, and iterative improvement workflows to enhance content quality. The system maintains a clean separation of concerns: template markup is processed internally by AI agents but never exposed to users, while providing sophisticated AI processing capabilities through embedded intelligence within the templates themselves. #### 3.4.2. Technical Preferences System -AIOX includes a personalization layer through the `technical-preferences.md` file in `aiox-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects. +AIOX includes a personalization layer through the `technical-preferences.md` file in `.aiox-core/data/`. This file serves as a persistent technical profile that influences agent behavior across all projects. **Purpose and Benefits:** @@ -147,7 +147,7 @@ The framework is designed for two primary environments: local IDEs and web-based ### 4.2. Environment-Specific Usage -- **For IDEs**: Users interact with the agents directly via their markdown files in `aiox-core/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents. +- **For IDEs**: Users interact with the agents directly via their markdown files in `.aiox-core/development/agents/`. The IDE integration (for Cursor, Claude Code, etc.) knows how to call these agents. - **For Web UIs**: Users upload a pre-built bundle from `dist`. This single file provides the AI with the context of the entire team and all their required tools and knowledge. ## 5. AIOX Workflows diff --git a/docs/es/core-architecture.md b/docs/es/core-architecture.md index 1d53ab99b7..ec99f83ac6 100644 --- a/docs/es/core-architecture.md +++ b/docs/es/core-architecture.md @@ -73,7 +73,7 @@ graph TD El directorio `aiox-core` contiene todas las definiciones y recursos que dan a los agentes sus capacidades. -### 3.1. Agentes (`aiox-core/agents/`) +### 3.1. Agentes (`.aiox-core/development/agents/`) - **Propósito**: Estos son los bloques de construcción fundamentales del sistema. Cada archivo markdown (por ejemplo, `aiox-master.md`, `pm.md`, `dev.md`) define la persona, capacidades y dependencias de un único agente de IA. - **Estructura**: Un archivo de agente contiene un encabezado YAML que especifica su rol, persona, dependencias e instrucciones de inicio. Estas dependencias son listas de tareas, plantillas, checklists y archivos de datos que el agente tiene permitido usar. @@ -81,12 +81,12 @@ El directorio `aiox-core` contiene todas las definiciones y recursos que dan a l - **Integración de Documentos**: Los agentes pueden referenciar y cargar documentos desde la carpeta `docs/` del proyecto como parte de tareas, flujos de trabajo o secuencias de inicio. Los usuarios también pueden arrastrar documentos directamente a las interfaces de chat para proporcionar contexto adicional. - **Ejemplo**: El agente `aiox-master` lista sus dependencias, lo que indica a la herramienta de construcción qué archivos incluir en un paquete web e informa al agente de sus propias capacidades. -### 3.2. Equipos de Agentes (`aiox-core/agent-teams/`) +### 3.2. Equipos de Agentes (`.aiox-core/development/agent-teams/`) - **Propósito**: Los archivos de equipo (por ejemplo, `team-all.yaml`) definen colecciones de agentes y flujos de trabajo que se empaquetan juntos para un propósito específico, como "desarrollo full-stack" o "solo backend". Esto crea un contexto pre-empaquetado más grande para entornos de UI web. - **Estructura**: Un archivo de equipo lista los agentes a incluir. Puede usar comodines, como `"*"` para incluir todos los agentes. Esto permite la creación de paquetes completos como `team-all`. -### 3.3. Flujos de Trabajo (`aiox-core/workflows/`) +### 3.3. Flujos de Trabajo (`.aiox-core/development/workflows/`) - **Propósito**: Los flujos de trabajo son archivos YAML (por ejemplo, `greenfield-fullstack.yaml`) que definen una secuencia prescrita de pasos e interacciones de agentes para un tipo de proyecto específico. Actúan como una guía estratégica para el usuario y el agente `aiox-orchestrator`. - **Estructura**: Un flujo de trabajo define secuencias tanto para proyectos complejos como simples, lista los agentes involucrados en cada paso, los artefactos que crean y las condiciones para pasar de un paso al siguiente. A menudo incluye un diagrama Mermaid para visualización. @@ -107,15 +107,15 @@ El framework AIOX emplea un sistema sofisticado de procesamiento de plantillas o - **`template-format.md`** (`aiox-core/utils/`): Define el lenguaje de marcado fundamental usado en todas las plantillas de AIOX. Esta especificación establece reglas de sintaxis para sustitución de variables (`{{placeholders}}`), directivas de procesamiento solo para IA (`[[LLM: instructions]]`) y bloques de lógica condicional. Las plantillas siguen este formato para asegurar un procesamiento consistente en todo el sistema. -- **`create-doc.md`** (`aiox-core/tasks/`): Actúa como el motor de orquestación que gestiona todo el flujo de trabajo de generación de documentos. Esta tarea coordina la selección de plantillas, gestiona los modos de interacción del usuario (generación incremental vs. rápida), aplica las reglas de procesamiento de template-format y maneja la validación. Sirve como la interfaz principal entre usuarios y el sistema de plantillas. +- **`create-doc.md`** (`.aiox-core/development/tasks/`): Actúa como el motor de orquestación que gestiona todo el flujo de trabajo de generación de documentos. Esta tarea coordina la selección de plantillas, gestiona los modos de interacción del usuario (generación incremental vs. rápida), aplica las reglas de procesamiento de template-format y maneja la validación. Sirve como la interfaz principal entre usuarios y el sistema de plantillas. -- **`advanced-elicitation.md`** (`aiox-core/tasks/`): Proporciona una capa de refinamiento interactivo que puede ser incorporada dentro de plantillas a través de bloques `[[LLM: instructions]]`. Este componente ofrece 10 acciones estructuradas de lluvia de ideas, capacidades de revisión sección por sección y flujos de trabajo de mejora iterativa para mejorar la calidad del contenido. +- **`advanced-elicitation.md`** (`.aiox-core/development/tasks/`): Proporciona una capa de refinamiento interactivo que puede ser incorporada dentro de plantillas a través de bloques `[[LLM: instructions]]`. Este componente ofrece 10 acciones estructuradas de lluvia de ideas, capacidades de revisión sección por sección y flujos de trabajo de mejora iterativa para mejorar la calidad del contenido. El sistema mantiene una clara separación de responsabilidades: el marcado de plantillas es procesado internamente por agentes de IA pero nunca se expone a los usuarios, mientras proporciona capacidades sofisticadas de procesamiento de IA a través de inteligencia incorporada dentro de las propias plantillas. #### 3.4.2. Sistema de Preferencias Técnicas -AIOX incluye una capa de personalización a través del archivo `technical-preferences.md` en `aiox-core/data/`. Este archivo sirve como un perfil técnico persistente que influye en el comportamiento de los agentes en todos los proyectos. +AIOX incluye una capa de personalización a través del archivo `technical-preferences.md` en `.aiox-core/data/`. Este archivo sirve como un perfil técnico persistente que influye en el comportamiento de los agentes en todos los proyectos. **Propósito y Beneficios:** @@ -152,7 +152,7 @@ El framework está diseñado para dos entornos principales: IDEs locales e inter ### 4.2. Uso Específico por Entorno -- **Para IDEs**: Los usuarios interactúan con los agentes directamente a través de sus archivos markdown en `aiox-core/agents/`. La integración del IDE (para Cursor, Claude Code, etc.) sabe cómo llamar a estos agentes. +- **Para IDEs**: Los usuarios interactúan con los agentes directamente a través de sus archivos markdown en `.aiox-core/development/agents/`. La integración del IDE (para Cursor, Claude Code, etc.) sabe cómo llamar a estos agentes. - **Para UIs Web**: Los usuarios suben un paquete pre-construido desde `dist`. Este único archivo proporciona a la IA el contexto de todo el equipo y todas sus herramientas y conocimientos requeridos. ## 5. Flujos de Trabajo de AIOX diff --git a/docs/guides/agents/traces/ux-design-expert-execution-trace.md b/docs/guides/agents/traces/ux-design-expert-execution-trace.md index 1a9eb1866d..5003ea8696 100644 --- a/docs/guides/agents/traces/ux-design-expert-execution-trace.md +++ b/docs/guides/agents/traces/ux-design-expert-execution-trace.md @@ -929,14 +929,14 @@ graph TD ### Notes on Dependency Locations -The agent definition references dependencies using short names (e.g., `aiox-core/tasks/...`). The actual resolution paths are: +The agent definition references dependencies using short names (e.g., `.aiox-core/development/tasks/...`). The actual resolution paths are: | Dependency Type | Agent Definition Path | Actual Disk Location | |-----------------|----------------------|---------------------| -| Tasks | `aiox-core/tasks/{name}` | `.aiox-core/development/tasks/{name}` | -| Templates | `aiox-core/templates/{name}` | `.aiox-core/product/templates/{name}` | -| Checklists | `aiox-core/checklists/{name}` | `.aiox-core/product/checklists/{name}` | -| Data | `aiox-core/data/{name}` | `.aiox-core/data/{name}` or `.aiox-core/product/data/{name}` | +| Tasks | `.aiox-core/development/tasks/{name}` | `.aiox-core/development/tasks/{name}` | +| Templates | `.aiox-core/product/templates/{name}` | `.aiox-core/product/templates/{name}` | +| Checklists | `.aiox-core/product/checklists/{name}` | `.aiox-core/product/checklists/{name}` | +| Data | `.aiox-core/data/{name}` | `.aiox-core/data/{name}` or `.aiox-core/product/data/{name}` | All 9 templates, all 4 checklists, and all 7 data files resolve correctly to files in `product/` directories. The `development/data/` directory does not exist; data files live under `.aiox-core/data/` and `.aiox-core/product/data/`. diff --git a/docs/pt/core-architecture.md b/docs/pt/core-architecture.md index f43731e000..2bc305ce31 100644 --- a/docs/pt/core-architecture.md +++ b/docs/pt/core-architecture.md @@ -73,7 +73,7 @@ graph TD O diretório `aiox-core` contém todas as definições e recursos que dão aos agentes suas capacidades. -### 3.1. Agentes (`aiox-core/agents/`) +### 3.1. Agentes (`.aiox-core/development/agents/`) - **Propósito**: Estes são os blocos fundamentais do sistema. Cada arquivo markdown (ex: `aiox-master.md`, `pm.md`, `dev.md`) define a persona, capacidades e dependências de um único agente de IA. - **Estrutura**: Um arquivo de agente contém um cabeçalho YAML que especifica seu papel, persona, dependências e instruções de inicialização. Estas dependências são listas de tasks, templates, checklists e arquivos de dados que o agente tem permissão para usar. @@ -81,12 +81,12 @@ O diretório `aiox-core` contém todas as definições e recursos que dão aos a - **Integração de Documentos**: Agentes podem referenciar e carregar documentos da pasta `docs/` do projeto como parte de tasks, workflows ou sequências de inicialização. Os usuários também podem arrastar documentos diretamente para interfaces de chat para fornecer contexto adicional. - **Exemplo**: O agente `aiox-master` lista suas dependências, o que informa à ferramenta de build quais arquivos incluir em um bundle web e informa ao agente sobre suas próprias capacidades. -### 3.2. Times de Agentes (`aiox-core/agent-teams/`) +### 3.2. Times de Agentes (`.aiox-core/development/agent-teams/`) - **Propósito**: Arquivos de time (ex: `team-all.yaml`) definem coleções de agentes e workflows que são agrupados para um propósito específico, como "desenvolvimento full-stack" ou "apenas backend". Isso cria um contexto maior e pré-empacotado para ambientes de UI web. - **Estrutura**: Um arquivo de time lista os agentes a serem incluídos. Pode usar wildcards, como `"*"` para incluir todos os agentes. Isso permite a criação de bundles abrangentes como `team-all`. -### 3.3. Workflows (`aiox-core/workflows/`) +### 3.3. Workflows (`.aiox-core/development/workflows/`) - **Propósito**: Workflows são arquivos YAML (ex: `greenfield-fullstack.yaml`) que definem uma sequência prescrita de etapas e interações de agentes para um tipo específico de projeto. Eles atuam como um guia estratégico para o usuário e o agente `aiox-orchestrator`. - **Estrutura**: Um workflow define sequências para projetos complexos e simples, lista os agentes envolvidos em cada etapa, os artefatos que eles criam e as condições para passar de uma etapa para a próxima. Frequentemente inclui um diagrama Mermaid para visualização. @@ -107,15 +107,15 @@ O framework AIOX emprega um sistema sofisticado de processamento de templates or - **`template-format.md`** (`aiox-core/utils/`): Define a linguagem de marcação fundamental usada em todos os templates do AIOX. Esta especificação estabelece regras de sintaxe para substituição de variáveis (`{{placeholders}}`), diretivas de processamento exclusivas para IA (`[[LLM: instructions]]`) e blocos de lógica condicional. Templates seguem este formato para garantir processamento consistente em todo o sistema. -- **`create-doc.md`** (`aiox-core/tasks/`): Atua como o motor de orquestração que gerencia todo o workflow de geração de documentos. Esta task coordena a seleção de templates, gerencia modos de interação com o usuário (geração incremental vs. rápida), aplica regras de processamento de template-format e lida com validação. Serve como a interface principal entre usuários e o sistema de templates. +- **`create-doc.md`** (`.aiox-core/development/tasks/`): Atua como o motor de orquestração que gerencia todo o workflow de geração de documentos. Esta task coordena a seleção de templates, gerencia modos de interação com o usuário (geração incremental vs. rápida), aplica regras de processamento de template-format e lida com validação. Serve como a interface principal entre usuários e o sistema de templates. -- **`advanced-elicitation.md`** (`aiox-core/tasks/`): Fornece uma camada de refinamento interativo que pode ser incorporada dentro de templates através de blocos `[[LLM: instructions]]`. Este componente oferece 10 ações estruturadas de brainstorming, capacidades de revisão seção por seção e workflows de melhoria iterativa para aprimorar a qualidade do conteúdo. +- **`advanced-elicitation.md`** (`.aiox-core/development/tasks/`): Fornece uma camada de refinamento interativo que pode ser incorporada dentro de templates através de blocos `[[LLM: instructions]]`. Este componente oferece 10 ações estruturadas de brainstorming, capacidades de revisão seção por seção e workflows de melhoria iterativa para aprimorar a qualidade do conteúdo. O sistema mantém uma clara separação de responsabilidades: a marcação de template é processada internamente por agentes de IA mas nunca exposta aos usuários, enquanto fornece capacidades sofisticadas de processamento de IA através de inteligência incorporada nos próprios templates. #### 3.4.2. Sistema de Preferências Técnicas -O AIOX inclui uma camada de personalização através do arquivo `technical-preferences.md` em `aiox-core/data/`. Este arquivo serve como um perfil técnico persistente que influencia o comportamento dos agentes em todos os projetos. +O AIOX inclui uma camada de personalização através do arquivo `technical-preferences.md` em `.aiox-core/data/`. Este arquivo serve como um perfil técnico persistente que influencia o comportamento dos agentes em todos os projetos. **Propósito e Benefícios:** @@ -152,7 +152,7 @@ O framework é projetado para dois ambientes principais: IDEs locais e interface ### 4.2. Uso Específico por Ambiente -- **Para IDEs**: Usuários interagem com os agentes diretamente via seus arquivos markdown em `aiox-core/agents/`. A integração do IDE (para Cursor, Claude Code, etc.) sabe como chamar estes agentes. +- **Para IDEs**: Usuários interagem com os agentes diretamente via seus arquivos markdown em `.aiox-core/development/agents/`. A integração do IDE (para Cursor, Claude Code, etc.) sabe como chamar estes agentes. - **Para UIs Web**: Usuários fazem upload de um bundle pré-construído de `dist`. Este único arquivo fornece à IA o contexto de todo o time e todas as suas ferramentas e conhecimento necessários. ## 5. Workflows do AIOX diff --git a/docs/zh/core-architecture.md b/docs/zh/core-architecture.md index c9c8da3f29..cdbce5a7ce 100644 --- a/docs/zh/core-architecture.md +++ b/docs/zh/core-architecture.md @@ -73,7 +73,7 @@ graph TD `aiox-core` 目录包含赋予代理能力的所有定义和资源。 -### 3.1. 代理 (`aiox-core/agents/`) +### 3.1. 代理 (`.aiox-core/development/agents/`) - **目的**：这些是系统的基础构建块。每个 markdown 文件（例如 `aiox-master.md`、`pm.md`、`dev.md`）定义单个 AI 代理的角色、能力和依赖项。 - **结构**：代理文件包含一个 YAML 头部，指定其角色、角色设定、依赖项和启动指令。这些依赖项是代理被允许使用的任务、模板、检查清单和数据文件列表。 @@ -81,12 +81,12 @@ graph TD - **文档集成**：代理可以引用和加载项目 `docs/` 文件夹中的文档，作为任务、工作流或启动序列的一部分。用户也可以直接将文档拖入聊天界面以提供额外上下文。 - **示例**：`aiox-master` 代理列出其依赖项，这告诉构建工具要在 web 包中包含哪些文件，并告知代理其自身的能力。 -### 3.2. 代理团队 (`aiox-core/agent-teams/`) +### 3.2. 代理团队 (`.aiox-core/development/agent-teams/`) - **目的**：团队文件（例如 `team-all.yaml`）定义为特定目的（如"全栈开发"或"仅后端"）捆绑在一起的代理和工作流集合。这为 web UI 环境创建了一个更大的预打包上下文。 - **结构**：团队文件列出要包含的代理。它可以使用通配符，例如 `"*"` 包含所有代理。这允许创建像 `team-all` 这样的综合包。 -### 3.3. 工作流 (`aiox-core/workflows/`) +### 3.3. 工作流 (`.aiox-core/development/workflows/`) - **目的**：工作流是 YAML 文件（例如 `greenfield-fullstack.yaml`），为特定项目类型定义规定的步骤序列和代理交互。它们充当用户和 `aiox-orchestrator` 代理的战略指南。 - **结构**：工作流为复杂和简单项目定义序列，列出每个步骤涉及的代理、它们创建的工件以及从一个步骤移动到下一个步骤的条件。它通常包含一个用于可视化的 Mermaid 图。 @@ -107,15 +107,15 @@ AIOX 框架采用由三个关键组件编排的复杂模板处理系统： - **`template-format.md`** (`aiox-core/utils/`)：定义整个 AIOX 模板中使用的基础标记语言。此规范建立了变量替换（`{{placeholders}}`）、仅 AI 处理指令（`[[LLM: instructions]]`）和条件逻辑块的语法规则。模板遵循此格式以确保整个系统的一致处理。 -- **`create-doc.md`** (`aiox-core/tasks/`)：充当管理整个文档生成工作流的编排引擎。此任务协调模板选择、管理用户交互模式（增量与快速生成）、强制执行模板格式处理规则并处理验证。它充当用户和模板系统之间的主要接口。 +- **`create-doc.md`** (`.aiox-core/development/tasks/`)：充当管理整个文档生成工作流的编排引擎。此任务协调模板选择、管理用户交互模式（增量与快速生成）、强制执行模板格式处理规则并处理验证。它充当用户和模板系统之间的主要接口。 -- **`advanced-elicitation.md`** (`aiox-core/tasks/`)：提供可通过 `[[LLM: instructions]]` 块嵌入模板的交互式细化层。此组件提供 10 种结构化头脑风暴操作、逐节审查功能和迭代改进工作流以提高内容质量。 +- **`advanced-elicitation.md`** (`.aiox-core/development/tasks/`)：提供可通过 `[[LLM: instructions]]` 块嵌入模板的交互式细化层。此组件提供 10 种结构化头脑风暴操作、逐节审查功能和迭代改进工作流以提高内容质量。 该系统保持关注点分离：模板标记由 AI 代理内部处理但从不暴露给用户，同时通过模板本身嵌入的智能提供复杂的 AI 处理能力。 #### 3.4.2. 技术偏好系统 -AIOX 通过 `aiox-core/data/` 中的 `technical-preferences.md` 文件包含个性化层。此文件作为影响所有项目中代理行为的持久技术配置文件。 +AIOX 通过 `.aiox-core/data/` 中的 `technical-preferences.md` 文件包含个性化层。此文件作为影响所有项目中代理行为的持久技术配置文件。 **目的和好处：** @@ -152,7 +152,7 @@ AIOX 通过 `aiox-core/data/` 中的 `technical-preferences.md` 文件包含个 ### 4.2. 特定环境使用 -- **对于 IDE**：用户通过 `aiox-core/agents/` 中的 markdown 文件直接与代理交互。IDE 集成（用于 Cursor、Claude Code 等）知道如何调用这些代理。 +- **对于 IDE**：用户通过 `.aiox-core/development/agents/` 中的 markdown 文件直接与代理交互。IDE 集成（用于 Cursor、Claude Code 等）知道如何调用这些代理。 - **对于 Web UI**：用户从 `dist` 上传预构建的包。这个单一文件为 AI 提供整个团队及其所有所需工具和知识的上下文。 ## 5. AIOX 工作流 From 5a8d6317eccfdc9159bb88ac9777a310d064b9ee Mon Sep 17 00:00:00 2001 From: Rafael Costa Date: Sun, 17 May 2026 10:18:09 -0300 Subject: [PATCH 2/3] chore: regenerate install-manifest after path-ref updates The 17 file rewrites in the previous commit changed content hashes that the install-manifest tracks. CI Install Manifest Validation was failing on the stale hash; regenerating brings it back in sync. Also picks up entity-registry refresh from the IDS pre-commit hook. --- .aiox-core/data/entity-registry.yaml | 118 +++++++++++---------------- .aiox-core/install-manifest.yaml | 6 +- 2 files changed, 49 insertions(+), 75 deletions(-) diff --git a/.aiox-core/data/entity-registry.yaml b/.aiox-core/data/entity-registry.yaml index 2c93f99525..a12d8bda53 100644 --- a/.aiox-core/data/entity-registry.yaml +++ b/.aiox-core/data/entity-registry.yaml @@ -1,7 +1,7 @@ metadata: version: 1.0.0 - lastUpdated: '2026-05-17T12:22:53.099Z' - entityCount: 815 + lastUpdated: '2026-05-17T13:08:28.431Z' + entityCount: 816 checksumAlgorithm: sha256 resolutionRate: 100 entities: @@ -261,8 +261,6 @@ entities: - modification-risk-assessment - visual-impact-generator - approval-workflow - - analyst - - pm externalDeps: [] plannedDeps: - change-propagation-predictor @@ -274,8 +272,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:251d2c073b917f0285672568f074ec0c77372e110e234b42f043c605e438d9ee - lastVerified: '2026-05-17T10:02:45.089Z' + checksum: sha256:73ad65e2263dac7a5a3aa64736d2c803c8a532c269b83fb98a61cb5729b689db + lastVerified: '2026-05-17T13:08:28.424Z' audit-codebase: path: .aiox-core/development/tasks/audit-codebase.md layer: L2 @@ -935,13 +933,7 @@ entities: - task usedBy: - sm - dependencies: - - po-master-checklist - - component-generator.js - - dev - - architect - - qa - - po + dependencies: [] externalDeps: [] plannedDeps: - tech-stack @@ -961,8 +953,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:0705fe3750d229b47fe194109d3ec398cb90adfdfe1a6d7cf80ca8bdf73b6ad0 - lastVerified: '2026-05-17T10:02:45.103Z' + checksum: sha256:4c8ce97f47ad9b0fb316bee47eae46fe7c9fbacb897f3062eaedd8a925511afc + lastVerified: '2026-05-17T13:08:28.424Z' create-service: path: .aiox-core/development/tasks/create-service.md layer: L2 @@ -1849,8 +1841,7 @@ entities: - story - task usedBy: [] - dependencies: - - po-master-checklist + dependencies: [] externalDeps: [] plannedDeps: - task-runner.js @@ -1861,8 +1852,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:6dda51884ce7a5dd814d026aab3f2125d399e89b468b2125673c19ade9091ace - lastVerified: '2026-05-17T10:02:45.118Z' + checksum: sha256:b3c533f925077c73d18d8c9b4b69783493f1c690fd562df9546f9169f82bbe14 + lastVerified: '2026-05-17T13:08:28.425Z' devops-pro-access-grant: path: .aiox-core/development/tasks/devops-pro-access-grant.md layer: L2 @@ -2996,8 +2987,7 @@ entities: - task usedBy: - aiox-master - dependencies: - - change-checklist + dependencies: [] externalDeps: [] plannedDeps: - existing-task @@ -3009,8 +2999,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:74e6ef74967508f8a05cfc629bac7d5ffd5bd67c7d598cc623fd426442049824 - lastVerified: '2026-05-17T10:02:45.134Z' + checksum: sha256:31d7d543b8994605e10fbbdce3ca52d5d6d0938832f053baa5a0ca50238f7e33 + lastVerified: '2026-05-17T13:08:28.425Z' modify-task: path: .aiox-core/development/tasks/modify-task.md layer: L2 @@ -3023,8 +3013,7 @@ entities: - task usedBy: - aiox-master - dependencies: - - change-checklist + dependencies: [] externalDeps: [] plannedDeps: - Node.js @@ -3035,8 +3024,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:e81346cb686226a2bca0657e9c6367adcbf76d6cbd5d81cc892702c3a655d96a - lastVerified: '2026-05-17T10:02:45.134Z' + checksum: sha256:b02ca96a6ffebac281a6f0640228c39a62d723414a50481bf6ef8ad05c92cfd3 + lastVerified: '2026-05-17T13:08:28.425Z' modify-workflow: path: .aiox-core/development/tasks/modify-workflow.md layer: L2 @@ -3543,8 +3532,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:90bba47136ccc37c74454a4537728b958955fd487e46e3b8dca869b994c8d1c1 - lastVerified: '2026-05-17T10:02:45.141Z' + checksum: sha256:956147dfb7f42983b249041173b85fd75419f71b9018f9991f2b3aa7e59e3885 + lastVerified: '2026-05-17T13:08:28.425Z' project-status: path: .aiox-core/development/tasks/project-status.md layer: L2 @@ -4658,8 +4647,7 @@ entities: - story - task usedBy: [] - dependencies: - - po-master-checklist + dependencies: [] externalDeps: [] plannedDeps: - tech-stack @@ -4680,8 +4668,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:86ee70cbe6ac6812dd9bbacc6e591046a9def3455efba19581155258173f91ba - lastVerified: '2026-05-17T10:02:45.161Z' + checksum: sha256:e5ee6bc856fba12867557c0684d566d520516b4ff0c96e9df91f260786106bd0 + lastVerified: '2026-05-17T13:08:28.426Z' spec-assess-complexity: path: .aiox-core/development/tasks/spec-assess-complexity.md layer: L2 @@ -5486,18 +5474,7 @@ entities: - po-close-story - dev - po - dependencies: - - po-master-checklist - - dev - - data-engineer - - devops - - ux-design-expert - - analyst - - architect - - pm - - qa - - po - - sm + dependencies: [] externalDeps: [] plannedDeps: - validation-engine.js @@ -5507,8 +5484,8 @@ entities: score: 0.8 constraints: [] extensionPoints: [] - checksum: sha256:f121211b1fbe915e181399d10bd30c435aec55c0af9b49d99c533473574a4907 - lastVerified: '2026-05-17T10:02:45.172Z' + checksum: sha256:277faba94cba30ac3773159d641fc2b8a345efd70dcfef6bae15f8a6280128ea + lastVerified: '2026-05-17T13:08:28.426Z' validate-tech-preset: path: .aiox-core/development/tasks/validate-tech-preset.md layer: L2 @@ -14120,6 +14097,26 @@ entities: extensionPoints: [] checksum: sha256:dd025894f8f0d3bd22a147dbc0debef8b83e96f3c59483653404b3cd5a01d5aa lastVerified: '2026-05-17T10:02:45.300Z' + component-creation-guide: + path: .aiox-core/core/docs/component-creation-guide.md + layer: L1 + type: module + purpose: Analyzes provided dataset to identify patterns and insights + keywords: + - component + - creation + - guide + usedBy: [] + dependencies: [] + externalDeps: [] + plannedDeps: [] + lifecycle: orphan + adaptability: + score: 0.4 + constraints: [] + extensionPoints: [] + checksum: sha256:b94ec24369c9c5a3b747307b14b425c4877de0ec3f5664e000d1f61fc3c61e27 + lastVerified: '2026-05-17T13:08:28.420Z' agents: aiox-master: path: .aiox-core/development/agents/aiox-master.md @@ -14208,11 +14205,9 @@ entities: - analyst usedBy: - add-mcp - - architect-analyze-impact - brownfield-create-epic - environment-bootstrap - spec-research-dependencies - - validate-next-story - brownfield-risk-report-tmpl - design-story-tmpl - story-tmpl @@ -14263,7 +14258,6 @@ entities: - brownfield-create-epic - create-brownfield-story - create-deep-research-prompt - - create-next-story - execute-epic-plan - plan-create-context - plan-create-implementation @@ -14273,7 +14267,6 @@ entities: - spec-gather-requirements - spec-research-dependencies - spec-write-spec - - validate-next-story - validate-tech-preset - verify-subtask - design-story-tmpl @@ -14337,7 +14330,6 @@ entities: usedBy: - analyze-project-structure - brownfield-create-epic - - validate-next-story - story-tmpl - claude-rules - codex-rules @@ -14409,7 +14401,6 @@ entities: - build - cleanup-utilities - create-brownfield-story - - create-next-story - create-service - create-suite - delegate-to-external-executor @@ -14436,7 +14427,6 @@ entities: - qa-run-tests - setup-llm-routing - story-checkpoint - - validate-next-story - verify-subtask - waves - story-tmpl @@ -14539,7 +14529,6 @@ entities: - setup-mcp-docker - triage-github-issues - update-aiox - - validate-next-story - story-tmpl - claude-rules - codex-rules @@ -14567,7 +14556,6 @@ entities: keywords: - pm usedBy: - - architect-analyze-impact - brownfield-create-epic - create-deep-research-prompt - environment-bootstrap @@ -14576,7 +14564,6 @@ entities: - spec-critique - spec-gather-requirements - spec-write-spec - - validate-next-story - command-rationalization-matrix - design-story-tmpl - story-tmpl @@ -14629,7 +14616,6 @@ entities: usedBy: - brownfield-create-story - cleanup-utilities - - create-next-story - dev-backlog-debt - dev-develop-story - execute-epic-plan @@ -14642,7 +14628,6 @@ entities: - qa-fix-issues - qa-gate - story-checkpoint - - validate-next-story - design-story-tmpl - antigravity-rules - claude-rules @@ -14695,7 +14680,6 @@ entities: - apply-qa-fixes - build-autonomous - cleanup-utilities - - create-next-story - create-suite - dev-develop-story - execute-checklist @@ -14713,7 +14697,6 @@ entities: - security-scan - spec-critique - spec-write-spec - - validate-next-story - design-story-tmpl - story-tmpl - antigravity-rules @@ -14780,7 +14763,6 @@ entities: - dev-develop-story - po-close-story - project-status - - validate-next-story - design-story-tmpl - antigravity-rules - claude-rules @@ -14863,7 +14845,6 @@ entities: usedBy: - brownfield-create-epic - run-design-system-pipeline - - validate-next-story - design-story-tmpl - story-tmpl - claude-rules @@ -15280,8 +15261,8 @@ entities: score: 0.5 constraints: [] extensionPoints: [] - checksum: sha256:958065f2d734189edf2868aae322114b16546502e213b9a948547af4e8c178f9 - lastVerified: '2026-05-17T10:02:45.331Z' + checksum: sha256:7ceaab838b4586a5314f0edea431f09fbc4dd82eb386f89db4442d1212add352 + lastVerified: '2026-05-17T13:08:28.422Z' entity-registry: path: .aiox-core/data/entity-registry.yaml layer: L3 @@ -16374,7 +16355,6 @@ entities: - create-brownfield-story - create-deep-research-prompt - create-doc - - create-next-story - create-suite - create-task - create-workflow @@ -18762,8 +18742,6 @@ entities: usedBy: - brownfield-create-epic - correct-course - - modify-agent - - modify-task - modify-workflow - propose-modification - qa-review-proposal @@ -18950,13 +18928,9 @@ entities: - brownfield-create-epic - brownfield-create-story - create-brownfield-story - - create-next-story - - dev-validate-next-story - po-pull-story-from-clickup - po-sync-story-to-clickup - qa-trace-requirements - - sm-create-next-story - - validate-next-story - aiox-master - po dependencies: [] diff --git a/.aiox-core/install-manifest.yaml b/.aiox-core/install-manifest.yaml index 8eafb37cb0..9f5c9ff8ce 100644 --- a/.aiox-core/install-manifest.yaml +++ b/.aiox-core/install-manifest.yaml @@ -8,7 +8,7 @@ # - File types for categorization # version: 5.2.6 -generated_at: "2026-05-17T13:08:28.080Z" +generated_at: "2026-05-17T13:16:03.633Z" generator: scripts/generate-install-manifest.js file_count: 1128 files: @@ -1297,9 +1297,9 @@ files: type: data size: 9590 - path: data/entity-registry.yaml - hash: sha256:910cf52ea4d999bccf255c431db5648663d2de5a871a18068fc443adaab3379c + hash: sha256:3e172132eba884da71f3be868e7749feea9e7515c729cddb64542111808d384d type: data - size: 572193 + size: 571670 - path: data/learned-patterns.yaml hash: sha256:24ac0b160615583a0ff783d3da8af80b7f94191575d6db2054ec8e10a3f945dc type: data From 20a20ba866a582fedee878b2561fb1104cc130bb Mon Sep 17 00:00:00 2001 From: Rafael Costa Date: Sun, 17 May 2026 10:43:49 -0300 Subject: [PATCH 3/3] chore(sync): propagate devops.md release-procedure section to IDE projections PR #745 added a "Release Procedure (NON-NEGOTIABLE Reference)" section to .aiox-core/development/agents/devops.md but `npm run sync:ide` was not run before that PR merged, leaving the four IDE projections drifted from source: - .claude/skills/AIOX/agents/devops/SKILL.md - .codex/agents/devops.md - .gemini/rules/AIOX/agents/devops.md - .kimi/skills/aiox-devops/SKILL.md This commit runs `sync:ide` and commits the resulting projections. The CI Compatibility Parity Gate + IDE Command Sync Validation + the overall Validation Summary were failing on this branch because they inherit the drifted state from main. This unblocks both #747 (path mismatch) and #746 (internal package.json rebrand). Followup note: the SOP itself should include a step in the post-merge checklist that says "run sync:ide after any change to .aiox-core/development/agents/*.md and commit the resulting projections." Will add to docs/guides/release-procedure.md in a follow-up if it's not already there. --- .claude/skills/AIOX/agents/devops/SKILL.md | 13 +++++++++++++ .codex/agents/devops.md | 13 +++++++++++++ .gemini/rules/AIOX/agents/devops.md | 13 +++++++++++++ .kimi/skills/aiox-devops/SKILL.md | 13 +++++++++++++ 4 files changed, 52 insertions(+) diff --git a/.claude/skills/AIOX/agents/devops/SKILL.md b/.claude/skills/AIOX/agents/devops/SKILL.md index bfc7f81715..c180143768 100644 --- a/.claude/skills/AIOX/agents/devops/SKILL.md +++ b/.claude/skills/AIOX/agents/devops/SKILL.md @@ -589,6 +589,19 @@ Type `*help` to see all commands. - ❌ Creating PR before quality gates pass - ❌ Skipping CodeRabbit CRITICAL issues +### Release Procedure (NON-NEGOTIABLE Reference) + +When invoked with `*release`, `*push` followed by version-bump intent, or any task that ends with a tag push to `@aiox-squads/*`, **load and follow `docs/guides/release-procedure.md` as the canonical SOP before touching anything**. It is the authoritative playbook — the task templates `publish-npm.md` and `release-management.md` are thin wrappers around it. + +The SOP captures lessons paid for in 11 patches across 30 days: +- Two-system branch protection on `main` (modern ruleset id `13330052` + legacy `required_pull_request_reviews`); `gh pr merge --admin` bypasses neither alone — you must relax both and restore both atomically with `trap EXIT` + sanitized payloads (raw GitHub API responses include read-only fields that PUT rejects). +- 4-site version bump coordination (`package.json`, `compat/aiox-core/package.json` + its dep, `packages/installer/package.json`, `package-lock.json` + `CHANGELOG.md`). +- The `publish_legacy_aiox_core` job depends on `publish` completing (compat wrapper transitively depends on the scoped package — race against npm CDN propagation has bitten us). +- npm propagation budget for the legacy smoke (240s with dual visibility check). +- Windows path escape in workflow `node -e` interpolations of `${{ github.workspace }}` (use env vars). + +Skipping the SOP because "it's just a patch release" is how the next 30-day patch storm starts. + ### Related Agents - **@dev (Dex)** - Delegates push operations to me diff --git a/.codex/agents/devops.md b/.codex/agents/devops.md index 41fca70e16..a6576998ee 100644 --- a/.codex/agents/devops.md +++ b/.codex/agents/devops.md @@ -579,6 +579,19 @@ Type `*help` to see all commands. - ❌ Creating PR before quality gates pass - ❌ Skipping CodeRabbit CRITICAL issues +### Release Procedure (NON-NEGOTIABLE Reference) + +When invoked with `*release`, `*push` followed by version-bump intent, or any task that ends with a tag push to `@aiox-squads/*`, **load and follow `docs/guides/release-procedure.md` as the canonical SOP before touching anything**. It is the authoritative playbook — the task templates `publish-npm.md` and `release-management.md` are thin wrappers around it. + +The SOP captures lessons paid for in 11 patches across 30 days: +- Two-system branch protection on `main` (modern ruleset id `13330052` + legacy `required_pull_request_reviews`); `gh pr merge --admin` bypasses neither alone — you must relax both and restore both atomically with `trap EXIT` + sanitized payloads (raw GitHub API responses include read-only fields that PUT rejects). +- 4-site version bump coordination (`package.json`, `compat/aiox-core/package.json` + its dep, `packages/installer/package.json`, `package-lock.json` + `CHANGELOG.md`). +- The `publish_legacy_aiox_core` job depends on `publish` completing (compat wrapper transitively depends on the scoped package — race against npm CDN propagation has bitten us). +- npm propagation budget for the legacy smoke (240s with dual visibility check). +- Windows path escape in workflow `node -e` interpolations of `${{ github.workspace }}` (use env vars). + +Skipping the SOP because "it's just a patch release" is how the next 30-day patch storm starts. + ### Related Agents - **@dev (Dex)** - Delegates push operations to me diff --git a/.gemini/rules/AIOX/agents/devops.md b/.gemini/rules/AIOX/agents/devops.md index 41fca70e16..a6576998ee 100644 --- a/.gemini/rules/AIOX/agents/devops.md +++ b/.gemini/rules/AIOX/agents/devops.md @@ -579,6 +579,19 @@ Type `*help` to see all commands. - ❌ Creating PR before quality gates pass - ❌ Skipping CodeRabbit CRITICAL issues +### Release Procedure (NON-NEGOTIABLE Reference) + +When invoked with `*release`, `*push` followed by version-bump intent, or any task that ends with a tag push to `@aiox-squads/*`, **load and follow `docs/guides/release-procedure.md` as the canonical SOP before touching anything**. It is the authoritative playbook — the task templates `publish-npm.md` and `release-management.md` are thin wrappers around it. + +The SOP captures lessons paid for in 11 patches across 30 days: +- Two-system branch protection on `main` (modern ruleset id `13330052` + legacy `required_pull_request_reviews`); `gh pr merge --admin` bypasses neither alone — you must relax both and restore both atomically with `trap EXIT` + sanitized payloads (raw GitHub API responses include read-only fields that PUT rejects). +- 4-site version bump coordination (`package.json`, `compat/aiox-core/package.json` + its dep, `packages/installer/package.json`, `package-lock.json` + `CHANGELOG.md`). +- The `publish_legacy_aiox_core` job depends on `publish` completing (compat wrapper transitively depends on the scoped package — race against npm CDN propagation has bitten us). +- npm propagation budget for the legacy smoke (240s with dual visibility check). +- Windows path escape in workflow `node -e` interpolations of `${{ github.workspace }}` (use env vars). + +Skipping the SOP because "it's just a patch release" is how the next 30-day patch storm starts. + ### Related Agents - **@dev (Dex)** - Delegates push operations to me diff --git a/.kimi/skills/aiox-devops/SKILL.md b/.kimi/skills/aiox-devops/SKILL.md index 5ebdcb1218..8e79b9e047 100644 --- a/.kimi/skills/aiox-devops/SKILL.md +++ b/.kimi/skills/aiox-devops/SKILL.md @@ -663,6 +663,19 @@ Type `*help` to see all commands. - ❌ Creating PR before quality gates pass - ❌ Skipping CodeRabbit CRITICAL issues +### Release Procedure (NON-NEGOTIABLE Reference) + +When invoked with `*release`, `*push` followed by version-bump intent, or any task that ends with a tag push to `@aiox-squads/*`, **load and follow `docs/guides/release-procedure.md` as the canonical SOP before touching anything**. It is the authoritative playbook — the task templates `publish-npm.md` and `release-management.md` are thin wrappers around it. + +The SOP captures lessons paid for in 11 patches across 30 days: +- Two-system branch protection on `main` (modern ruleset id `13330052` + legacy `required_pull_request_reviews`); `gh pr merge --admin` bypasses neither alone — you must relax both and restore both atomically with `trap EXIT` + sanitized payloads (raw GitHub API responses include read-only fields that PUT rejects). +- 4-site version bump coordination (`package.json`, `compat/aiox-core/package.json` + its dep, `packages/installer/package.json`, `package-lock.json` + `CHANGELOG.md`). +- The `publish_legacy_aiox_core` job depends on `publish` completing (compat wrapper transitively depends on the scoped package — race against npm CDN propagation has bitten us). +- npm propagation budget for the legacy smoke (240s with dual visibility check). +- Windows path escape in workflow `node -e` interpolations of `${{ github.workspace }}` (use env vars). + +Skipping the SOP because "it's just a patch release" is how the next 30-day patch storm starts. + ### Related Agents - **@dev (Dex)** - Delegates push operations to me