fix: align legacy path references with current directory layout (closes #741)

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/<X>` | `.aiox-core/product/templates/<X>` |
| `aiox-core/checklists/<X>` | `.aiox-core/product/checklists/<X>` |
| `aiox-core/agents/<X>` | `.aiox-core/development/agents/<X>` |
| `aiox-core/tasks/<X>` | `.aiox-core/development/tasks/<X>` |
| `aiox-core/workflows/<X>` | `.aiox-core/development/workflows/<X>` |
| `aiox-core/agent-teams/<X>` | `.aiox-core/development/agent-teams/<X>` |
| `aiox-core/data/<X>` | `.aiox-core/data/<X>` (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 `(?<![\.])` in the
substitution script protects existing dotted references from being rewritten
twice.

## Files touched (17 — one extra came in from the pre-commit hook
regenerating `entity-registry.yaml`)

- **Runtime-affecting (story flow, agent flow):**
  - `.aiox-core/development/tasks/validate-next-story.md` (the file @renatolhamas pointed at — Line 228 was the trigger)
  - `.aiox-core/development/tasks/dev-validate-next-story.md`
  - `.aiox-core/development/tasks/create-next-story.md`
  - `.aiox-core/development/tasks/sm-create-next-story.md`
  - `.aiox-core/development/tasks/modify-agent.md`
  - `.aiox-core/development/tasks/modify-task.md`
  - `.aiox-core/development/tasks/architect-analyze-impact.md`
  - `.aiox-core/development/tasks/pr-automation.md`
- **Documentation (operator-facing):**
  - `.aiox-core/user-guide.md`
  - `.aiox-core/core/docs/component-creation-guide.md`
  - `.aiox-core/data/aiox-kb.md`
  - `docs/core-architecture.md` (+ pt/es/zh localizations)
  - `docs/guides/agents/traces/ux-design-expert-execution-trace.md`
- **Generated (regenerated by pre-commit hook, not authored):**
  - `.aiox-core/data/entity-registry.yaml`

## Method

Substitution was scripted (not freehand `sed`) with a negative-lookbehind
guard `(?<![\.])aiox-core/<subdir>/` 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) <noreply@anthropic.com>

Author: rafaelscosta

.aiox-core/core/docs/component-creation-guide.md

@@ -397,16 +397,16 @@ 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`
 
 ## Advanced Features
 
 ### Custom Templates
 
-Create custom templates in `aiox-core/templates/custom/`:
+Create custom templates in `.aiox-core/product/templates/custom/`:
 
 ```yaml
 # custom-agent-template.yaml

.aiox-core/data/aiox-kb.md

@@ -349,31 +349,31 @@ 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
 - **Structure**: Defines agent interactions, artifacts created, and transition conditions
 
 #### 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:**