fraim-framework 2.0.4 → 2.0.7

package/.ai-agents/workflows/test.md

@@ -1,90 +1,90 @@
-# Testing Phase
-
-## INTENT
-To create comprehensive test coverage that accurately reproduces issues and validates solutions, ensuring robust testing through proper test structure, failure verification, and systematic test execution.
-
-## PRINCIPLES
-- **Test-Driven**: Write tests that reproduce the issue before fixing
-- **Comprehensive Coverage**: Ensure all scenarios are tested
-- **Failure Verification**: Confirm tests fail before implementation
-- **Proper Structure**: Use established test patterns and frameworks
-- **Systematic Execution**: Follow consistent testing procedures
-
-## TESTING WORKFLOW
-
-### Step 1: Issue Identification
-Ask for {issue_number} (and optional {slug}); confirm target branch feature/{issue_number}-{slug}.
-
-### Step 2: Phase Initiation
-Label the issue 'phase:tests'. (GitHub Action will automatically label the issue `status:wip` and update the existing draft PR)
-
-### Step 3: Environment Setup
-**IMPORTANT**: The user has already run `prep-issue.sh` which has:
-- ✅ Created the feature branch
-- ✅ Checked out the branch
-- ✅ Created draft PR
-- ✅ Indexed the codebase with Serena
-- ✅ Opened the editor in the prepared workspace
-
-You can start working immediately in the prepared environment. No need to create branches or wait for GitHub Actions.
-
-### Step 4: Work Location
-You are already in the correct workspace prepared by the user. Confirm you're on the right branch and start working. 
-
-### Step 5: Testing Work
-Your work entails the following:
-
-- Review the RFC associated with this issue.
-- Determine whether tests need to be added to an existing test suite, or a new one needs to be created.
-- **CRITICAL: Write INTEGRATION tests that demonstrate the REAL USER SCENARIO**
-  - Test the actual end-to-end user experience, not unit tests for hypothetical fixes
-  - Use real services and APIs where possible (not mocks)
-  - Verify the issue occurs in the real system as described in the issue
-  - Example: For messaging threading issues, actually send messages and verify they appear as new messages vs replies
-- Run the test cases to ensure they fail (demonstrating the issue exists)
-- Flip issue to 'status:needs-review' and remove 'status:wip'
-
-**❌ DO NOT:**
-- Write unit tests for code that doesn't exist yet
-- Test hypothetical fixes or solutions
-- Create mock tests that don't use real services
-- Test individual components in isolation
-
-**✅ DO:**
-- Test the complete user workflow end-to-end
-- Use real APIs and services when possible
-- Verify the actual problem described in the issue
-- Create tests that will pass AFTER the fix is implemented
-
-### Step 6: Iteration
-If workflow actions or reviewer feedback indicates more work is needed, ensure the issue is set back to `status:wip` and continue working as above.
-
-## EXAMPLES
-
-### Good: Comprehensive Testing Process
-```
-Issue #84: "Fix API integration timeout"
-1. ✅ Identified: Issue #84, branch feature/84-fix-api
-2. ✅ Phase: Set phase:tests, PR created
-3. ✅ Environment: User ran prep-issue.sh, ready to work
-4. ✅ Location: Working in prepared workspace with Serena indexing
-5. ✅ RFC Review: Read docs/rfcs/84-fix-api-timeout.md
-6. ✅ Analysis: Determined need to add timeout tests
-7. ✅ Test Creation: Added test cases for timeout scenarios
-8. ✅ Failure Verification: Confirmed tests fail before fix
-9. ✅ Review: Set status:needs-review
-10. ✅ Iteration: Incorporated feedback, updated tests
-Result: Comprehensive test coverage with proper structure
-```
-
-### Bad: Incomplete Testing Process
-```
-Issue #84: "Fix API integration timeout"
-1. ✅ Identified: Issue #84
-2. ❌ Skip: Didn't review RFC
-3. ❌ Skip: Started testing without understanding requirements
-4. ❌ Skip: No test cases written
-5. ❌ Skip: Didn't verify tests fail
-6. ❌ Skip: No test structure followed
-Result: Incomplete, ineffective testing
+# Testing Phase
+
+## INTENT
+To create comprehensive test coverage that accurately reproduces issues and validates solutions, ensuring robust testing through proper test structure, failure verification, and systematic test execution.
+
+## PRINCIPLES
+- **Test-Driven**: Write tests that reproduce the issue before fixing
+- **Comprehensive Coverage**: Ensure all scenarios are tested
+- **Failure Verification**: Confirm tests fail before implementation
+- **Proper Structure**: Use established test patterns and frameworks
+- **Systematic Execution**: Follow consistent testing procedures
+
+## TESTING WORKFLOW
+
+### Step 1: Issue Identification
+Ask for {issue_number} (and optional {slug}); confirm target branch feature/{issue_number}-{slug}.
+
+### Step 2: Phase Initiation
+Label the issue 'phase:tests'. (GitHub Action will automatically label the issue `status:wip` and update the existing draft PR)
+
+### Step 3: Environment Setup
+**IMPORTANT**: The user has already run `prep-issue.sh` which has:
+- ✅ Created the feature branch
+- ✅ Checked out the branch
+- ✅ Created draft PR
+- ✅ Indexed the codebase with Serena
+- ✅ Opened the editor in the prepared workspace
+
+You can start working immediately in the prepared environment. No need to create branches or wait for GitHub Actions.
+
+### Step 4: Work Location
+You are already in the correct workspace prepared by the user. Confirm you're on the right branch and start working. 
+
+### Step 5: Testing Work
+Your work entails the following:
+
+- Review the RFC associated with this issue.
+- Determine whether tests need to be added to an existing test suite, or a new one needs to be created.
+- **CRITICAL: Write INTEGRATION tests that demonstrate the REAL USER SCENARIO**
+  - Test the actual end-to-end user experience, not unit tests for hypothetical fixes
+  - Use real services and APIs where possible (not mocks)
+  - Verify the issue occurs in the real system as described in the issue
+  - Example: For messaging threading issues, actually send messages and verify they appear as new messages vs replies
+- Run the test cases to ensure they fail (demonstrating the issue exists)
+- Flip issue to 'status:needs-review' and remove 'status:wip'
+
+**❌ DO NOT:**
+- Write unit tests for code that doesn't exist yet
+- Test hypothetical fixes or solutions
+- Create mock tests that don't use real services
+- Test individual components in isolation
+
+**✅ DO:**
+- Test the complete user workflow end-to-end
+- Use real APIs and services when possible
+- Verify the actual problem described in the issue
+- Create tests that will pass AFTER the fix is implemented
+
+### Step 6: Iteration
+If workflow actions or reviewer feedback indicates more work is needed, ensure the issue is set back to `status:wip` and continue working as above.
+
+## EXAMPLES
+
+### Good: Comprehensive Testing Process
+```
+Issue #84: "Fix API integration timeout"
+1. ✅ Identified: Issue #84, branch feature/84-fix-api
+2. ✅ Phase: Set phase:tests, PR created
+3. ✅ Environment: User ran prep-issue.sh, ready to work
+4. ✅ Location: Working in prepared workspace with Serena indexing
+5. ✅ RFC Review: Read docs/rfcs/84-fix-api-timeout.md
+6. ✅ Analysis: Determined need to add timeout tests
+7. ✅ Test Creation: Added test cases for timeout scenarios
+8. ✅ Failure Verification: Confirmed tests fail before fix
+9. ✅ Review: Set status:needs-review
+10. ✅ Iteration: Incorporated feedback, updated tests
+Result: Comprehensive test coverage with proper structure
+```
+
+### Bad: Incomplete Testing Process
+```
+Issue #84: "Fix API integration timeout"
+1. ✅ Identified: Issue #84
+2. ❌ Skip: Didn't review RFC
+3. ❌ Skip: Started testing without understanding requirements
+4. ❌ Skip: No test cases written
+5. ❌ Skip: Didn't verify tests fail
+6. ❌ Skip: No test structure followed
+Result: Incomplete, ineffective testing
 ```

package/.github/workflows/ci.yml

@@ -0,0 +1,51 @@
+name: CI
+
+on:
+  push:
+    branches:
+      - 'master'
+  schedule:
+    - cron: '0 6 * * *' # 11 PM PST is 6 AM UTC
+      
+# Sets permissions of the GITHUB_TOKEN
+permissions:
+  contents: read
+  checks: write
+
+# Cancel in-progress runs on same branch
+concurrency:
+  group: ci-${{ github.workflow }}-${{ github.ref }}
+  cancel-in-progress: true
+
+jobs:
+  build:
+    if: github.event_name == 'push'
+    runs-on: ubuntu-latest
+    timeout-minutes: 15
+    
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - run: npm install
+      - name: Build
+        run: npm run build
+      - name: Test Smoke CI
+        run: npm run test-smoke-ci
+
+  full-test:
+    runs-on: ubuntu-latest
+    if: github.event_name == 'schedule' && github.ref == 'refs/heads/master'
+    
+    steps:
+      - uses: actions/checkout@v4
+      - uses: actions/setup-node@v4
+        with:
+          node-version: 20
+      - run: npm install
+      - name: Build
+        run: npm run build
+      - name: Test All CI
+        run: npm run test-all-ci
+        timeout-minutes: 30

package/.github/workflows/phase-change.yml

@@ -0,0 +1,251 @@
+name: Phase Change Handler
+
+# This workflow now assumes branches are created by prep-issue.sh
+# It only handles PR creation/updating and status management
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  issues: write
+  pull-requests: write
+  contents: write
+
+jobs:
+  handle-phase-change:
+    runs-on: ubuntu-latest
+    if: |
+      contains(github.event.label.name, 'phase:') ||
+      (github.event.action == 'unlabeled' && contains(github.event.label.name, 'phase:'))
+    
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          fetch-depth: 0
+
+      - name: Setup Git
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Auth GitHub CLI
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | gh auth login --with-token
+
+      - name: Extract issue details
+        id: issue-details
+        run: |
+          ISSUE_NUMBER="${{ github.event.issue.number }}"
+          ISSUE_TITLE="${{ github.event.issue.title }}"
+          BRANCH_NAME="feature/${ISSUE_NUMBER}-$(echo "$ISSUE_TITLE" | tr '[:upper:]' '[:lower:]' | sed 's/[^a-z0-9]/-/g' | sed 's/--*/-/g' | sed 's/^-\|-$//g')"
+          
+          echo "issue_number=$ISSUE_NUMBER" >> $GITHUB_OUTPUT
+          echo "branch_name=$BRANCH_NAME" >> $GITHUB_OUTPUT
+          echo "issue_title=$ISSUE_TITLE" >> $GITHUB_OUTPUT
+
+      - name: Determine current phase
+        id: current-phase
+        run: |
+          LABELS='${{ toJson(github.event.issue.labels) }}'
+          CURRENT_PHASE=""
+          
+          # Extract current phase from labels
+          for label in $(echo "$LABELS" | jq -r '.[].name'); do
+            if [[ $label == phase:* ]]; then
+              CURRENT_PHASE=$label
+              break
+            fi
+          done
+          
+          echo "current_phase=$CURRENT_PHASE" >> $GITHUB_OUTPUT
+          echo "Current phase: $CURRENT_PHASE"
+
+      - name: Verify branch exists (created by prep-issue.sh)
+        run: |
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          
+          # Check if branch exists remotely
+          if git ls-remote --exit-code --heads origin "$BRANCH_NAME" >/dev/null 2>&1; then
+              echo "✓ Branch $BRANCH_NAME exists remotely"
+              git fetch origin "$BRANCH_NAME"
+          else
+              echo "⚠️  Branch $BRANCH_NAME does not exist remotely"
+              echo "   This should have been created by prep-issue.sh"
+              echo "   Please run prep-issue.sh before invoking agent workflows"
+              exit 1
+          fi
+
+      - name: Check if PR already exists
+        id: pr-check
+        run: |
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          EXISTING_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number' 2>/dev/null || echo "")
+          echo "existing_pr=$EXISTING_PR" >> $GITHUB_OUTPUT
+          if [ -n "$EXISTING_PR" ]; then
+            echo "✓ PR #$EXISTING_PR already exists"
+          else
+            echo "ℹ️  No PR exists yet, will create one for phase: ${{ steps.current-phase.outputs.current_phase }}"
+          fi
+
+      - name: phase:spec → create/update PR for Specification phase
+        if: steps.current-phase.outputs.current_phase == 'phase:spec'
+        shell: bash
+        env:
+          ISSUE: ${{ github.event.issue.number }}
+        run: |
+          ISSUE_NUMBER="${{ steps.issue-details.outputs.issue_number }}"
+          ISSUE_TITLE="${{ steps.issue-details.outputs.issue_title }}"
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          
+          # Create or update PR for Specification phase
+          PR_TITLE="[Specification] Feature Spec for Issue #$ISSUE_NUMBER: $ISSUE_TITLE"
+          PR_BODY="## Feature Specification for Issue #$ISSUE_NUMBER
+
+          This PR contains the feature specification for: $ISSUE_TITLE
+
+          **Phase:** Specification
+          **Issue:** #$ISSUE_NUMBER
+          **Branch:** \`$BRANCH_NAME\`
+
+          ### Specification Document
+          - 📋 [Feature Specification]($SPEC_FILE)
+
+          **Note:** This is a Specification PR. Design and Implementation will follow after specification approval.
+
+          "
+
+          EXISTING_PR="${{ steps.pr-check.outputs.existing_pr }}"
+          
+          if [ -n "$EXISTING_PR" ]; then
+            echo "Updating existing PR #$EXISTING_PR for Specification phase"
+            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
+            gh pr edit "$EXISTING_PR" --add-label "phase:spec" --remove-label "phase:design" --remove-label "phase:tests" --remove-label "phase:impl" 
+          else
+            echo "Creating new PR for Specification phase"
+            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
+            gh pr edit --add-label "phase:spec"
+          fi
+
+      - name: phase:design → create/update PR for Design phase
+        if: steps.current-phase.outputs.current_phase == 'phase:design'
+        shell: bash
+        env:
+          ISSUE: ${{ github.event.issue.number }}
+        run: |
+          ISSUE_NUMBER="${{ steps.issue-details.outputs.issue_number }}"
+          ISSUE_TITLE="${{ steps.issue-details.outputs.issue_title }}"
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          
+          # Create or update PR for Design phase
+          PR_TITLE="[Design] RFC for Issue #$ISSUE_NUMBER: $ISSUE_TITLE"
+          PR_BODY="## Design RFC for Issue #$ISSUE_NUMBER
+
+          This PR contains the design RFC for: $ISSUE_TITLE
+
+          **Phase:** Design
+          **Issue:** #$ISSUE_NUMBER
+          **Branch:** \`$BRANCH_NAME\`
+
+          ### RFC Document
+          - 📋 [RFC Document]($RFC_FILE)
+
+          **Note:** This is a Design PR. Implementation will follow in a separate PR after design approval.
+
+          "
+
+          EXISTING_PR="${{ steps.pr-check.outputs.existing_pr }}"
+          
+          if [ -n "$EXISTING_PR" ]; then
+            echo "Updating existing PR #$EXISTING_PR for Design phase"
+            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
+            gh pr edit "$EXISTING_PR" --add-label "phase:design" --remove-label "phase:spec" --remove-label "phase:tests" --remove-label "phase:impl" 
+          else
+            echo "Creating new PR for Design phase"
+            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
+            gh pr edit --add-label "phase:design"
+          fi
+
+      - name: phase:tests → create/update PR for Test phase
+        if: steps.current-phase.outputs.current_phase == 'phase:tests'
+        run: |
+          ISSUE_NUMBER="${{ steps.issue-details.outputs.issue_number }}"
+          ISSUE_TITLE="${{ steps.issue-details.outputs.issue_title }}"
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          
+          # Create or update PR for Test phase
+          PR_TITLE="[Testing] Test Cases for Issue #$ISSUE_NUMBER: $ISSUE_TITLE"
+          PR_BODY="## Test cases for Issue #$ISSUE_NUMBER
+
+          This PR contains the test cases for: $ISSUE_TITLE
+
+          **Phase:** Tests
+          **Issue:** #$ISSUE_NUMBER
+          **Branch:** \`$BRANCH_NAME\`
+
+          ### Test Cases
+    
+
+          **Note:** This is a Test PR. Implementation will follow after test approval.
+
+          "
+
+          EXISTING_PR="${{ steps.pr-check.outputs.existing_pr }}"
+          
+          if [ -n "$EXISTING_PR" ]; then
+            echo "Updating existing PR #$EXISTING_PR for Test phase"
+            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
+            gh pr edit "$EXISTING_PR" --add-label "phase:tests" --remove-label "phase:spec" --remove-label "phase:design" --remove-label "phase:impl"
+          else
+            echo "Creating new PR for Test phase"
+            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
+            gh pr edit --add-label "phase:tests"
+          fi
+
+      - name: phase:impl → create/update PR for Implementation phase
+        if: steps.current-phase.outputs.current_phase == 'phase:impl'
+        run: |
+          ISSUE_NUMBER="${{ steps.issue-details.outputs.issue_number }}"
+          ISSUE_TITLE="${{ steps.issue-details.outputs.issue_title }}"
+          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
+          
+          # Create or update PR for Implementation phase
+          PR_TITLE="[Implementation] Fixes for Issue #$ISSUE_NUMBER: $ISSUE_TITLE"
+          PR_BODY="## Fixes for Issue #$ISSUE_NUMBER
+
+          This PR contains the fixes for: $ISSUE_TITLE
+
+          **Phase:** Implementation
+          **Issue:** #$ISSUE_NUMBER
+          **Branch:** \`$BRANCH_NAME\`
+
+          ### Fixes
+          
+
+          Closes #$ISSUE_NUMBER
+
+          "
+
+          EXISTING_PR="${{ steps.pr-check.outputs.existing_pr }}"
+          
+          if [ -n "$EXISTING_PR" ]; then
+            echo "Updating existing PR #$EXISTING_PR for Implementation phase"
+            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
+            gh pr edit "$EXISTING_PR" --add-label "phase:impl" --remove-label "phase:spec" --remove-label "phase:design" --remove-label "phase:tests"
+          else
+            echo "Creating new PR for Implementation phase"
+            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
+            gh pr edit --add-label "phase:impl"
+          fi
+
+      - name: Normalize ISSUE and PR status to WIP (authoritative)
+        run: |
+          gh issue edit ${{ github.event.issue.number }} --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
+          
+          # Use the PR number from the check step
+          EXISTING_PR="${{ steps.pr-check.outputs.existing_pr }}"
+          
+          if [ -n "$EXISTING_PR" ]; then
+            gh pr edit "$EXISTING_PR" --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
+          fi

package/.github/workflows/status-change.yml

@@ -0,0 +1,68 @@
+name: Status Change → Flip PR Draft/Ready
+
+on:
+  issues:
+    types: [labeled]
+
+permissions:
+  pull-requests: write
+  issues: read
+  contents: write
+
+# Serialize per ISSUE; last status wins
+concurrency:
+  group: status-change-${{ github.event.issue.number }}
+  cancel-in-progress: true
+
+jobs:
+  status-change:
+    if: startsWith(github.event.label.name, 'status:')
+    runs-on: ubuntu-latest
+    steps:
+      - name: Checkout repository
+        uses: actions/checkout@v4
+        with:
+          token: ${{ secrets.GITHUB_TOKEN }}
+          fetch-depth: 0
+
+      - name: Setup Git
+        run: |
+          git config --global user.name "github-actions[bot]"
+          git config --global user.email "github-actions[bot]@users.noreply.github.com"
+
+      - name: Auth GitHub CLI
+        run: echo "${{ secrets.GITHUB_TOKEN }}" | gh auth login --with-token
+        
+      - name: Derive branch + find PR
+        id: pr
+        shell: bash
+        env:
+          ISSUE_NUMBER: ${{ github.event.issue.number }}
+          ISSUE_TITLE:  ${{ github.event.issue.title }}
+        run: |
+          set -euo pipefail
+          slug=$(echo "$ISSUE_TITLE" | tr '[:upper:]' '[:lower:]' | sed -E 's/[^a-z0-9]+/-/g;s/^-+|-+$//g')
+          BR="feature/${ISSUE_NUMBER}-${slug}"
+          PR=$(gh pr list --state open --head "$BR" --json number --jq '.[0].number')
+          echo "pr=$PR" >> $GITHUB_OUTPUT
+          echo "label=${{ github.event.label.name }}" >> $GITHUB_OUTPUT
+
+      - name: Flip PR state (Draft/Ready) based on label
+        if: steps.pr.outputs.pr != ''
+        shell: bash
+        env:
+          PR:    ${{ steps.pr.outputs.pr }}
+          LABEL: ${{ steps.pr.outputs.label }}
+        run: |
+          set -euo pipefail
+          case "$LABEL" in
+            status:needs-review)
+              gh pr ready "$PR"
+              gh pr edit  "$PR" --add-label "status:needs-review" --remove-label "status:wip" --remove-label "status:complete" || true
+              ;;
+            status:wip)
+              gh pr edit "$PR" --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
+              ;;
+            *)
+              echo "No action for label: $LABEL" ;;
+          esac

package/.github/workflows/sync-on-pr-review.yml

@@ -0,0 +1,66 @@
+name: Sync Issue on PR Review
+on:
+  pull_request_review:
+    types: [submitted]
+
+permissions:
+  pull-requests: write
+  issues: write
+
+concurrency:
+  group: review-sync-${{ github.event.pull_request.number }}
+  cancel-in-progress: true
+
+jobs:
+  sync-on-review:
+    runs-on: ubuntu-latest
+    # no job-level `if` — we branch inside the script
+    env:
+      GH_TOKEN: ${{ secrets.PR_AUTOMATION_TOKEN || secrets.GITHUB_TOKEN }}
+      REPO: ${{ github.repository }}
+    steps:
+      - name: Derive review state, issue number, and branch
+        id: vars
+        shell: bash
+        run: |
+          set -euo pipefail
+          STATE="${{ github.event.review.state }}"
+          BR="${{ github.event.pull_request.head.ref }}"   # e.g., feature/26-slug
+          ISSUE="$(sed -nE 's#^feature/([0-9]+)-.*#\1#p' <<< "$BR" || true)"
+          echo "state=$STATE" >> $GITHUB_OUTPUT
+          echo "issue=$ISSUE" >> $GITHUB_OUTPUT
+          echo "branch=$BR" >> $GITHUB_OUTPUT
+          echo "Detected review state: $STATE; branch: $BR; issue: $ISSUE"
+
+      - name: Handle review states
+        if: steps.vars.outputs.issue != ''
+        shell: bash
+        env:
+          STATE:  ${{ steps.vars.outputs.state }}
+          ISSUE:  ${{ steps.vars.outputs.issue }}
+          PRNUM:  ${{ github.event.pull_request.number }}
+          REPO:   ${{ env.REPO }}
+        run: |
+          set -euo pipefail
+          case "$STATE" in
+            changes_requested)
+              # Flip to WIP
+              gh issue edit "$ISSUE" --repo "$REPO" \
+                --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
+              gh pr edit "$PRNUM" --repo "$REPO" \
+                --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
+              ;;
+            approved)
+              # Flip to Complete
+              gh issue edit "$ISSUE" --repo "$REPO" \
+                --add-label "status:complete" --remove-label "status:wip" --remove-label "status:needs-review" || true
+              gh pr edit "$PRNUM" --repo "$REPO" --add-label "status:complete" --remove-label "status:wip" --remove-label "status:needs-review" || true
+              ;;
+            commented)
+              # No-op; comments don't change state
+              echo "Review was 'commented' — no state change."
+              ;;
+            *)
+              echo "Unknown review state: $STATE"
+              ;;
+          esac

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "fraim-framework",
-  "version": "2.0.4",
+  "version": "2.0.7",
   "description": "FRAIM v2: Framework for Rigor-based AI Management - Transform from solo developer to AI manager orchestrating production-ready code with enterprise-grade discipline",
   "main": "index.js",
   "bin": {
@@ -51,6 +51,7 @@
   },
   "files": [
     ".ai-agents/",
+    ".github/",
     "examples/",
     "bin/",
     "*.js",