aios-core 4.2.15 → 4.4.0

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

@@ -208,6 +208,7 @@ tools:
   - context7          # Research testing best practices and standards
 checklists:
   - qa-master-checklist.md
+execution_mode: programmatic  # TOK-3: PTC-eligible — batch lint+typecheck+test in single Bash block
 ---
 
 # qa-gate
@@ -289,6 +290,53 @@ waiver:
   approved_by: 'Product Owner'
 ```
 
+## Code Intelligence Enhancement (Optional)
+
+> These steps are **conditional** — they only execute when a code intelligence provider is available.
+> If `isCodeIntelAvailable()` returns false, skip silently and proceed with standard gate criteria.
+
+### Code Intelligence: Blast Radius
+
+After completing manual review, if code intelligence is available:
+
+1. Collect the list of modified files from the story's File List
+2. Call `getBlastRadius(files)` from `.aios-core/core/code-intel/helpers/qa-helper.js`
+3. If result is not null, add a "Blast Radius" section to the gate report:
+   ```
+   ### Blast Radius
+   - Files analyzed: {count}
+   - Total references affected: {blastRadius}
+   - Risk Level: {riskLevel} (LOW/MEDIUM/HIGH)
+   ```
+4. If risk level is HIGH, call `suggestGateInfluence('HIGH')` and include the advisory in the gate decision notes
+
+### Code Intelligence: Test Coverage
+
+After blast radius analysis, if code intelligence is available:
+
+1. Extract symbol names (function/class names) from modified files
+2. Call `getTestCoverage(symbols)` from `qa-helper.js`
+3. If result is not null, add a "Test Coverage" section to the gate report:
+   ```
+   ### Test Coverage (Code Intelligence)
+   | Symbol | Status | Test Count |
+   |--------|--------|------------|
+   | {symbol} | {NO_TESTS/INDIRECT/MINIMAL/GOOD} | {testCount} |
+   ```
+4. Symbols with NO_TESTS status should be flagged as potential CONCERNS
+
+### Code Intelligence: Gate Influence
+
+If blast radius returned HIGH risk:
+
+1. The `suggestGateInfluence('HIGH')` advisory is **informational only**
+2. It suggests CONCERNS but does NOT automatically change the gate verdict
+3. @qa makes the final decision — the advisory is logged in the gate file under `code_intel_advisory`
+
+> **Fallback guarantee:** If code intelligence is unavailable or any call returns null, the gate process continues exactly as before — no sections are added, no errors are raised.
+
+---
+
 ## Gate Decision Criteria
 
 ### PASS
@@ -371,4 +419,12 @@ Gate: CONCERNS → qa.qaLocation/gates/{epic}.{story}-{slug}.yml
 - Always write to standard path
 - Always update story with gate reference
 - Clear, actionable findings
+
+## Handoff
+next_agent: @devops
+next_command: *push
+condition: QA gate verdict is PASS
+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
  

package/.aios-core/development/tasks/qa-review-story.md

@@ -252,7 +252,7 @@ Execute CodeRabbit self-healing **FIRST** before manual review:
 │  WHILE iteration < max_iterations:                                │
 │    ┌─────────────────────────────────────────────────────────┐   │
 │    │ 1. Run CodeRabbit CLI                                   │   │
-│    │    wsl bash -c 'cd /mnt/c/.../@synkra/aios-core &&         │   │
+│    │    wsl bash -c 'cd /mnt/c/.../aios-core &&         │   │
 │    │    ~/.local/bin/coderabbit --prompt-only                │   │
 │    │    -t committed --base main'                            │   │
 │    │                                                          │   │
@@ -370,6 +370,29 @@ If self-healing fails:
 
 ---
 
+### 0b. Code Intelligence: Reference Impact (Optional)
+
+> This step is **conditional** — only executes when a code intelligence provider is available.
+> If `isCodeIntelAvailable()` returns false, skip silently and proceed to Risk Assessment.
+
+After CodeRabbit self-healing (Step 0), if code intelligence is available:
+
+1. Collect modified files from the story's File List
+2. Call `getReferenceImpact(files)` from `.aios-core/core/code-intel/helpers/qa-helper.js`
+3. If result is not null, include reference impact in the review:
+   ```
+   ### Reference Impact (Code Intelligence)
+   | Modified File | Consumers Affected |
+   |--------------|-------------------|
+   | {file} | {consumers.length} consumers ({list of consumer files}) |
+   ```
+4. Files with many consumers (>10) should trigger deeper review of those changes
+5. This data supplements Risk Assessment (Step 1) — high consumer count may auto-escalate to deep review
+
+> **Fallback guarantee:** If code intelligence is unavailable or `getReferenceImpact` returns null, the review continues exactly as before — no reference impact section is added.
+
+---
+
 ### 1. Risk Assessment (Determines Review Depth)
 
 **Auto-escalate to deep review when:**
@@ -680,4 +703,12 @@ After review:
 
 - **No Action Required**: The sync happens transparently when using story-manager utilities. If sync fails, story file is still saved locally with a warning message.
 
+## Handoff
+next_agent: @dev
+next_command: *apply-qa-fixes
+condition: QA verdict is REJECT
+alternatives:
+  - agent: @devops, command: *push, condition: QA verdict is APPROVE
+  - agent: @dev, command: *fix-qa-issues, condition: Structured fix from QA_FIX_REQUEST.md
+
 - **Manual Sync**: If needed, use: `npm run sync-story -- --story {epic}.{story}` 

package/.aios-core/development/tasks/release-management.md

@@ -750,3 +750,10 @@ Migration: Replace /v1/users with /v2/users in API calls.
 
 - `ci-cd-configuration` - Set up CI to run before releases
 - `pr-automation` - Help users create PRs with proper commit formats
+
+## Handoff
+next_agent: @po
+next_command: *close-story {story-id}
+condition: Release published successfully
+alternatives:
+  - agent: @devops, command: *cleanup, condition: Post-release branch cleanup needed