aiox-core 5.0.7 → 5.0.8

package/.aiox-core/development/tasks/devops-pro-verify-status.md

@@ -0,0 +1,33 @@
+# Task: DevOps Pro Verify Status
+
+> **Version:** 1.0.0
+> **Created:** 2026-04-20
+> **Type:** SUPPORT-OPS
+> **Agent:** `@devops`
+
+## Purpose
+
+Check email verification status for an authenticated AIOX Pro session.
+
+## Input
+
+- `access_token`
+
+## Endpoint
+
+- `POST https://aiox-license-server.vercel.app/api/v1/auth/verify-status`
+
+## Execution
+
+1. Call `verify-status` with `{ accessToken }`.
+2. Report `email` and `emailVerified`.
+3. If `emailVerified=false`, route to `*pro-resend-verification`.
+
+## Pass Criteria
+
+- `200` response
+- clear verified/unverified state
+
+## Source Of Truth
+
+- `docs/guides/pro/access-grant-ops-playbook.md`

package/.aiox-core/development/tasks/qa-gate.md

@@ -420,11 +420,61 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 - Always update story with gate reference
 - Clear, actionable findings
 
+## Post-Gate Status Update (MANDATORY)
+
+**Reference:** `.claude/rules/story-lifecycle.md` — Status transitions are @qa responsibility during QA gate.
+
+**This step MUST be executed before presenting results to user.**
+
+**Change Log format:** Use `{date: YYYY-MM-DD}` and `{version: MAJOR.MINOR.PATCH}`. Version MUST follow semantic bump rules: major for breaking changes, minor for features, patch for fixes/process updates. HALT if either value cannot be resolved deterministically.
+
+### IF verdict is PASS or CONCERNS:
+
+0. **Pre-check (blocking):**
+   - If current Status is not `**InReview**`, HALT and log: "Cannot apply PASS/CONCERNS transition: expected InReview, found {current status}."
+   - If Change Log section is missing, HALT and request user to restore template structure.
+1. **Update story Status field** in the story file: change `**InReview**` to `**Done**`
+2. **Add Change Log entry:**
+   ```text
+   | {date: YYYY-MM-DD} | {version: MAJOR.MINOR.PATCH} | QA Gate {PASS|CONCERNS} — Status: InReview → Done | @qa |
+   ```
+3. **Log:** "✅ Story status updated: InReview → Done"
+
+### IF verdict is FAIL:
+
+0. **Pre-check (blocking):**
+   - If current Status is not `**InReview**`, HALT and log: "Cannot apply FAIL transition: expected InReview, found {current status}."
+   - If Change Log section is missing, HALT and request user to restore template structure.
+1. **Update story Status field** in the story file: change `**InReview**` to `**InProgress**`
+2. **Add Change Log entry:**
+   ```text
+   | {date: YYYY-MM-DD} | {version: MAJOR.MINOR.PATCH} | QA Gate FAIL — Status: InReview → InProgress — {reason} | @qa |
+   ```
+3. **Log:** "❌ Story returned to InProgress — fixes required"
+
+### IF verdict is WAIVED:
+
+0. **Pre-check (blocking):**
+   - If current Status is not `**InReview**`, HALT and log: "Cannot apply WAIVED transition: expected InReview, found {current status}."
+   - If Change Log section is missing, HALT and request user to restore template structure.
+1. **Update story Status field** in the story file: change `**InReview**` to `**Done**`
+2. **Add Change Log entry:**
+   ```text
+   | {date: YYYY-MM-DD} | {version: MAJOR.MINOR.PATCH} | QA Gate WAIVED — Status: InReview → Done — {waiver reason} | @qa |
+   ```
+3. **Log:** "⚠️ Story status updated: InReview → Done (waived)"
+
+### Rationale
+
+Status transitions defined in `story-lifecycle.md` are advisory (contextual rules). This step makes them imperative (procedural), ensuring agents always execute the transition as part of the workflow rather than relying on contextual rule awareness.
+
+---
+
 ## Handoff
 next_agent: @devops
 next_command: *push
-condition: QA gate verdict is PASS
+condition: QA gate verdict is PASS or CONCERNS (status updated to Done)
 alternatives:
-  - agent: @dev, command: *apply-qa-fixes, condition: QA gate verdict is FAIL or CONCERNS
-  - agent: @po, command: *close-story {story-id}, condition: QA gate verdict is WAIVED
- 
+  - agent: @po, command: *review-concerns {story-id}, condition: QA gate verdict is CONCERNS (status updated to Done, has non-blocking issues)
+  - agent: @dev, command: *apply-qa-fixes, condition: QA gate verdict is FAIL (status updated to InProgress)
+  - agent: @po, command: *close-story {story-id}, condition: QA gate verdict is WAIVED (status updated to Done)

package/.aiox-core/development/tasks/validate-next-story.md

@@ -463,10 +463,47 @@ Provide a structured validation report including:
 - **Implementation Readiness Score**: 1-10 scale
 - **Confidence Level**: High/Medium/Low for successful implementation
 
+### 12. Post-Validation Status Update (MANDATORY)
+
+**Reference:** `.claude/rules/story-lifecycle.md` — Draft → Ready transition is @po responsibility.
+
+**This step MUST be executed before presenting results to user.**
+
+**Change Log format:** Use `{date: YYYY-MM-DD}` and `{version: MAJOR.MINOR.PATCH}`. Version MUST follow semantic bump rules: major for breaking changes, minor for features, patch for fixes/process updates. HALT if either value cannot be resolved deterministically.
+
+#### IF verdict is GO (score >= 7):
+
+0. **Pre-check (blocking):**
+   - If current Status is not `**Draft**`, HALT and log: "Cannot apply GO transition: expected Draft, found {current status}."
+   - If Change Log section is missing, HALT and request user to restore template structure.
+1. **Update story Status field** in the story file: change `**Draft**` to `**Ready**`
+2. **Add Change Log entry:**
+   ```text
+   | {date: YYYY-MM-DD} | {version: MAJOR.MINOR.PATCH} | Validated GO ({score}/10) — Status: Draft → Ready | @po |
+   ```
+3. **Log:** "✅ Story status updated: Draft → Ready"
+
+#### IF verdict is NO-GO (score < 7):
+
+0. **Pre-check (blocking):**
+   - If current Status is not `**Draft**`, HALT and log: "Cannot apply NO-GO outcome: expected Draft, found {current status}."
+   - If Change Log section is missing, HALT and request user to restore template structure.
+1. **Keep** story Status as `**Draft**`
+2. **Add Change Log entry:**
+   ```text
+   | {date: YYYY-MM-DD} | {version: MAJOR.MINOR.PATCH} | Validation NO-GO — {reason summary} | @po |
+   ```
+3. **Log:** "❌ Story remains Draft — fixes required before re-validation"
+
+#### Rationale
+
+Status transitions defined in `story-lifecycle.md` are advisory (contextual rules). This step makes them imperative (procedural), ensuring agents always execute the transition as part of the workflow rather than relying on contextual rule awareness.
+
+---
+
 ## Handoff
 next_agent: @dev
 next_command: *develop {story-id}
-condition: Story status is Approved (GO decision)
+condition: Story status is Ready (GO decision, status updated in Step 12)
 alternatives:
   - agent: @sm, command: *draft, condition: Story rejected (NO-GO), needs rework
- 

package/.aiox-core/framework-config.yaml

@@ -122,6 +122,7 @@ ide_sync_system:
     claude-code:
       enabled: true
       path: ".claude/commands/AIOX/agents"
+      skillsPath: ".claude/skills"
       format: "full-markdown-yaml"
     codex:
       enabled: true

package/.aiox-core/infrastructure/scripts/codex-skills-sync/README.md

@@ -0,0 +1,69 @@
+# Codex Skills Sync
+
+Tools for generating local Codex skills (`.codex/skills/aiox-*`) from AIOX agent and squad definitions.
+
+## When To Use Which
+
+There are two complementary entry points:
+
+| Tool | Scope | Use case |
+|------|-------|----------|
+| `npm run sync:skills:codex` (`index.js`) | **Core agents only** (`.aiox-core/development/agents/*.md`) | CI / incremental sync. Tightly coupled with the shared `agent-parser.js` from `ide-sync/`. Used after editing core agent files to keep `.codex/skills/` in step. |
+| `npm run setup:codex-skills` (`bootstrap.js`) | **Core agents + squad entry chiefs** (`squads/*/config.yaml` → entry agent) | First-time / operator bootstrap. Standalone with vendored `js-yaml` fallback. Use after a fresh checkout, after adding a new squad, or when the `$` menu in Codex is missing skills (e.g. squad chiefs not loading). |
+
+If a skill exists in `.codex/skills/` but does not contain the marker `<!-- AIOX-CODEX-LOCAL-SKILLS: generated -->`, `bootstrap.js` skips it by default to preserve hand-edits. Pass `--force` to overwrite (a `.bak-<timestamp>` copy is created first).
+
+## bootstrap.js
+
+```
+npm run setup:codex-skills              # generate / update
+npm run setup:codex-skills:dry          # preview without writes
+node bootstrap.js --force               # overwrite non-generated skills (creates .bak)
+node bootstrap.js --help                # full options
+```
+
+Discovery rules:
+
+1. **Core agents** — every `*.md` in `.aiox-core/development/agents/` becomes a `aiox-<id>` skill.
+2. **Squad chiefs** — every `squads/*/config.yaml` is parsed; the entry agent is resolved via:
+   - explicit `entry_agent`, `squad.entry_agent`, `pack.entry_agent`, `orchestrator.agent`, or `tier_system.orchestrator` field
+   - first agent with `tier: orchestrator` or id matching `*chief`
+   - file matching `*-chief.md` in `squads/<name>/agents/`
+   - first agent file as fallback
+3. **Skill ID** — `aiox-<entry>` if the entry name is squad-specific (e.g. `mega-brain-chief`); otherwise `aiox-<squad>-<entry>` to avoid collisions.
+
+After running, restart Codex CLI from the project root if the `$` menu does not refresh automatically.
+
+## index.js (canonical incremental sync)
+
+```
+npm run sync:skills:codex               # local .codex/skills only
+npm run sync:skills:codex:global        # also write to ~/.codex/skills
+```
+
+Used by CI and by the unified ide-sync pipeline. Does not generate squad-chief skills — use `bootstrap.js` for that.
+
+## validate.js
+
+```
+npm run validate:codex-skills           # validate aiox-* skill / agent parity (strict)
+```
+
+Verifies that every core agent has a corresponding `.codex/skills/aiox-<id>/SKILL.md`. Squad-chief skills are out of scope for this validator.
+
+## Files generated
+
+Output directory defaults to `.codex/skills/<skill-id>/SKILL.md`. The generated files include:
+
+- A YAML frontmatter (`name`, `description`)
+- The `<!-- AIOX-CODEX-LOCAL-SKILLS: generated -->` marker (used by future runs to detect ownership)
+- A pointer to the source-of-truth file (loaded on demand by Codex)
+- A short activation protocol and starter command list
+
+The source files in `.aiox-core/development/agents/` and `squads/*/agents/` remain authoritative. Generated skills are activator stubs.
+
+## Story reference
+
+Story 123.9 — Codex local skills bootstrap (squad chief coverage).
+
+Background: students reported that squad-chief skills (e.g. `mega-brain-chief`, `slides-chief`) did not appear in Codex's `$` menu. Root cause: `index.js` only generated skills from `.aiox-core/development/agents/` — squad chiefs in `squads/*/agents/` were not covered. A provisional standalone script was distributed manually; this directory captures the definitive vendored solution.