fraim-framework 1.0.12 → 2.0.2

package/agents/windsurf/rules/continuous-learning.md

@@ -1,47 +0,0 @@
----
-trigger: always_on
----
-
-# Continuous Learning
-
-## Retrospectives Review
-- **Always review** the `/retrospectives/` folder before starting work on similar issues
-- **Learn from past problems** - understand root cause analysis and lessons learned
-- **Apply previous solutions** - don't repeat mistakes that have already been solved
-
-## Knowledge Integration
-- **Read related RFCs** in `/docs/rfcs/` to understand design decisions
-- **Review test cases** to see how similar problems were approached
-- **Check issue history** for patterns in failures and solutions
-
-## Local Development Benefits
-- **Avoid known pitfalls** by learning from retrospectives
-- **Build on existing solutions** rather than starting from scratch
-- **Understand system constraints** from past architectural decisions
-
-## Before Starting Work
-1. **Search retrospectives** for related issues or similar problems
-2. **Read relevant RFCs** to understand the design context
-3. **Review test cases** to see expected behavior
-4. **Check issue comments** for previous attempts and solutions
-
-## Document Your Learning
-- **Update retrospectives** if you discover new insights
-- **Add to RFCs** if you find better approaches
-- **Share solutions** with other agents through issue comments
-
-## Retrospective Triggers
-
-### **Automatic Retrospective Requirements**
-- **Complex Issues (>3 iterations)**: Must create retrospective before issue closure
-- **Process Violations**: Any workflow rule violations require retrospectives
-- **Work Loss Incidents**: Any incidents where work is lost require detailed retrospectives
-
-### **Retrospective Creation Process**
-1. **Stop Current Work**: Pause issue resolution if retrospective is required
-2. **Create Retrospective**: Use standard template in retrospectives folder
-3. **Root Cause Analysis**: Identify underlying causes, not just symptoms
-4. **Prevention Measures**: Document specific actions to prevent recurrence
-5. **Process Updates**: Update rules and workflows based on learnings
-
-Remember: The best code is often written by those who learn from history rather than repeat it.

package/agents/windsurf/rules/local-development.md

@@ -1,103 +0,0 @@
----
-trigger: manual
----
-
-# Local Development with Remote Coordination
-
-- Use local file system for development work in your own cloned repository folder
-- Push to feature branches only; never push to master
-- Do NOT open PRs; push and let Actions open/update Draft PRs
-- Always work in your own cloned repository folder: `git clone <repo> "<repo> - Issue {issue_number}"`
-- After you create the clone, do not forget to change into that working directory. All your work **MUST** be in your working directory.
-- Coordinate with other agents through GitHub issues and PRs
-- Each agent works independently in their own folder to enable true parallel development
-
-## CRITICAL RULE: Absolute Workspace Separation
-
-### Local Clone: WORK-ONLY  
-- **Directory**: `<repo> - Issue <issue number>`
-- **Purpose**: All development work happens here exclusively
-- **Rule**: ALL file operations must be within this directory
-
-## Mandatory Pre-File-Operation Checklist
-
-**Before ANY file operation (edit_file, delete_file, etc.), verify:**
-
-1. ✅ **Directory Check**: `pwd` shows local clone with issue number in path
-2. ✅ **Path Verification**: File path is relative (no "../" or main workspace name)  
-3. ✅ **Branch Check**: `git branch` shows correct feature branch
-4. ❌ **If ANY check fails**: STOP immediately and fix location
-
-**This checklist is MANDATORY, not optional.**
-
-
-## Enhanced Stop Conditions
-
-**Stop ALL work immediately if:**
-- You create a file and it appears in main workspace
-- You use edit_file with "../" paths
-- You work in directory without issue number in name  
-- `pwd` shows main workspace path
-- Any file operation targets main workspace
-
-**Take corrective action before continuing.**
-
-## Workspace Validation Commands
-
-**Before starting work, run:**
-```bash
-echo "Working in: $(pwd)"
-echo "Should contain issue number in path"
-git branch
-echo "Should show feature branch"
-```
-
-**If output doesn't match expectations, fix before proceeding.**
-
-## Tool Usage Restrictions
-
-### File Operations - Local Only
-- `edit_file()` - ONLY with relative paths in local repo
-- `delete_file()` - ONLY within local repo
-- `search_replace()` - ONLY on local repo files
-
-### Reference Operations - Main Workspace OK  
-- `read_file()` - OK to read from main workspace for reference
-- `list_dir()` - OK to explore main workspace structure
-- `grep()` - OK to search main workspace for patterns
-
-## Violation Recovery Process
-
-**If you violate workspace boundaries:**
-
-1. **Stop immediately** - Do not continue file operations
-2. **Assess damage** - Check what was created in wrong location  
-3. **Clean up** - Delete files created in main workspace
-4. **Recreate correctly** - Recreate files in local repo only
-5. **Document violation** - Update post-mortem with details
-
-
-## Enhanced Output Template
-
-```
-Summary:
-  - Work completed in local repository: [path]
-  - Files created/modified: [list with relative paths]
-  - Workspace violations: [none/details if any occurred]
-
-Artifacts:
-  - Branch: [URL]
-  - Local directory: [full path to local clone]
-```
-
-## Emergency Safeguards
-
-**If assistant shows signs of workspace confusion:**
-- User should immediately clarify working directory
-- Assistant should run `pwd` and verify location
-- All file operations should pause until location confirmed
-- Assistant should explicitly state file paths being used
-
----
-
-**Bottom Line**: The local development workflow requires absolute discipline about workspace boundaries. 

package/agents/windsurf/rules/remote-development.md

@@ -1,22 +0,0 @@
----
-trigger: manual
----
-
-# Remote-only, headless execution, bot-authored PRs
-- Use GitHub MCP for file edits, commits, and labels. Do not touch the local FS or run local servers.
-- Push to feature branches only; never push to master.
-- Do NOT open PRs via MCP; push and let Actions open/update Draft PRs (authored by bot).
-
-
-# Stop Criteria
-- When the work given to you is complete.
-- When workflows tied to your PR are successful. If workflows fail, your work is not complete. Keep at it.
-
-Output Template (use verbatim)
-- Summary:
-  - …
-  - …
-- Artifacts:
-  - Branch: <url>
-  - PR: <url>
-  - Issue: <url>

package/agents/windsurf/rules/simplicity.md

@@ -1,17 +0,0 @@
----
-trigger: always_on
----
-
-
-****Keep it simple. Don't over-engineer. *****
-Don't over-think it. 
-While fixing an issue, focus on that issue only. Don't fix other issues. Don't make unrelated changes. Instead, file a Git issue if you find other issues that aren't already tracked by an existing Git issue.
-
-
-Always verify the action you have taken. Do not expect the user to verify it for you. 
-If you kicked off a Git workflow, verify it completed successfully (e.g., gh checks: list or PR status).
-If you wrote a test and expect it to pass, run it yourself and verify it passes; if you expect it to fail, verify it fails.
-Always link work to the issue (use “Closes #<n>” in the Implementation PR).
-Open Draft PRs early; review happens in the PR, not in chat.
-
-Agents must not run gh pr create. Push to the feature branch and let Actions open Draft PRs.

package/agents/windsurf/rules/windsurf-workflow.md

@@ -1,28 +0,0 @@
----
-trigger: always_on
----
-
-# Windsurf Development Workflow
-
-## Goal
-Work efficiently in local environment while maintaining coordination with remote repository and other agents.
-
-## Behavior
-- Use local file system for development work
-- ***NEVER*** commit unless asked to do so
-- Produce clear progress updates with:
-  1. Actions executed (imperative, past tense)
-  2. Local progress (files modified, tests run)
-  3. Remote artifacts (branch, PR status)
-  4. Next steps for this issue
-  5. Blocking issues (if any)
-
-## Stop Criteria
-- When the assigned work is complete
-- When tests pass and PR is ready for review
-- When waiting for reviewer feedback
-
-## Output Template
-- Summary:
-  - Local progress: [what you accomplished locally]
-  - Remote status: [branch/PR status]

package/agents/windsurf/workflows/prep.md

@@ -1,20 +0,0 @@
----
-description: Prep environment for issue
-auto_execution_mode: 3
----
-
-Step 1: Ask for {issue_number}
-
-Step 2: Clone the repo to "<repo> - Issue {issue_number}" 
-- **CRITICAL**: Clone ONE LEVEL ABOVE the current workspace directory
-- **DO NOT** clone inside the current workspace folder
-- **VERIFY LOCATION**: Use `pwd` to confirm you're in the parent directory before cloning
-
-Step 3: Confirm items in the checklist and say "Huzzah!"
-
-
-## Safety Checklist
-- [ ] Confirmed current workspace path with `pwd`
-- [ ] Changed to parent directory (`cd ..`) before cloning
-- [ ] Verified clone location is outside current workspace
-- [ ] Successfully changed into cloned repository

package/agents/windsurf/workflows/resolve-issue.md

@@ -1,47 +0,0 @@
----
-description: Resolve issue (once confirmed complete)
-auto_execution_mode: 3
----
-
-Ensure branch: feature/{issue}-{slug} is checked out (create if needed).
-
-Commit & push any pending changes.
-
-Sync from origin/master into this branch (merge or rebase), resolve conflicts, push again.
-
-Check the results of GitHub Action that runs the full tests in the cloud.
-
-If they pass: open/update the Implementation PR, label it, and enable auto-merge.
-
-If they fail: no PR is opened/updated; fix, push again, repeat.
-
-Once PR is approved and related actions succeed, do the following: 
-- **MANDATORY**: Verify PR is actually merged to master before proceeding
-- **MANDATORY**: Run merge verification checks (see below)
-- Close the issue ONLY after merge verification passes
-- Delete the branch remotely.
-- If operating locally, delete the local branch and the local codebase.
-- Say Hoorah !
-
-## Mandatory Merge Verification
-
-**Before closing ANY issue, verify the following:**
-
-1. ✅ **PR Status**: PR shows "merged" status, not just "closed"
-2. ✅ **Merge Commit**: Verify merge commit exists in master
-3. ✅ **Files in Master**: Confirm expected files are present in master
-
-### **Verification Commands**
-```bash
-# Check PR is merged, not just closed
-gh pr view <PR_NUMBER> --json merged
-
-# Verify merge commit in master
-git fetch origin master
-git log origin/master --oneline | grep "PR #<PR_NUMBER>"
-
-# Verify files in master
-git show origin/master:path/to/expected/file
-```
-
-**CRITICAL**: Do not close the issue until merge verification passes. This prevents work loss incidents like Issue #112.

package/agents/windsurf/workflows/start-design.md

@@ -1,26 +0,0 @@
----
-description: Start working on the issue
-auto_execution_mode: 3
----
-
-Step 1: Ask for {issue_number} (and optional {slug})
-
-Step 2: Label the issue 'phase:design' (GitHub Action will automatically create a branch, label the issue `status:wip`, create a draft PR)
-
-Step 3: Using GitHub MCP, wait for the branch to get created, then do a checkout to start your work.
-
-*** IMPORTANT IF YOU ARE WORKING LOCALLY **** switch into your branch and ensure you work in your own folder. 
-
-Step 4: Do your work either remotely or locally as defined by the user. If unsure, ask the user. Once sure, let the user know.
-
-Step 5: Your work entails the following
-
- - Create docs/rfcs/{issue_number}-{slug}.md.  
-
- - If the issue requires a small fix or bug fix, use this template - docs/rfcs/BUG-TEMPLATE.md 
-
- - If the issue requires major changes, use this template - docs/rfcs/RFC-TEMPLATE.md 
-
- - When ready for review, flip issue to 'status:needs-review' and remove 'status:wip'
-
-Step 6: 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.

package/agents/windsurf/workflows/start-impl.md

@@ -1,27 +0,0 @@
----
-description: Implement issue
-auto_execution_mode: 3
----
-
-Step 1: Ask for {issue_number} (and optional {slug}); confirm target branch feature/{issue_number}-{slug}.
-
-Step 2: Ensure the branch exists (your GitHub Action will usually auto-create it) and checkout it. 
-
-Step 3: Label the issue 'phase:impl'. (GitHub Action will automatically label the issue `status:wip`, create a draft PR)
-
-Step 4: Do your work either remotely or locally as defined by the user. If unsure, ask the user. Once sure, let the user know.
-
-Step 5: Your work entails the following
-
- - Review the RFC associated with this issue.
-
- - Determine whether changes need to be made to existing code, or brand new code needs to be written.
-
- - Write the minimal set of code and test cases needed for this issue.
-
- - **Test cases must inherit from test-utils and follow the structure of the rest of the test suite**
- - Ensure test cases pass.
-
- - When ready for review, flip issue to 'status:needs-review' and remove 'status:wip'
-
-Step 6: 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.

package/agents/windsurf/workflows/start-tests.md

@@ -1,26 +0,0 @@
----
-description: Start writing tests
-auto_execution_mode: 3
----
-
-Step 1: Ask for {issue_number} (and optional {slug}); confirm target branch feature/{issue_number}-{slug}.
-
-Step 2: Using GitHub MCP, ensure the branch exists (your GitHub Action will usually auto-create it) and checkout it.
-
-Step 3: Label the issue 'phase:tests'. (GitHub Action will automatically label the issue `status:wip`, create a draft PR)
-
-Step 4: Do your work either remotely or locally as defined by the user. If unsure, ask the user. Once sure, let the user know. 
-
-Step 5: 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.
-
- - Write the minimal set of test cases that accurately reproduce the issue
-
- - Run the test cases to ensure they fail
-
- - Flip issue to 'status:needs-review' and remove 'status:wip'
-
-Step 6: 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.

package/github/phase-change.yml

@@ -1,218 +0,0 @@
-name: Phase Change Handler
-
-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: Ensure branch exists and sync
-        run: |
-          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
-          BASE="master"
-    
-          git fetch origin "$BASE"
-    
-          if git ls-remote --exit-code --heads origin "$BRANCH_NAME" >/dev/null 2>&1; then
-              echo "Branch $BRANCH_NAME exists, syncing..."
-              git fetch origin "$BRANCH_NAME"
-              git switch "$BRANCH_NAME"
-              git pull --rebase origin "$BRANCH_NAME"
-          else
-              echo "Branch $BRANCH_NAME does not exist, creating from $BASE..."
-              git switch -c "$BRANCH_NAME" "origin/$BASE"
-              git push -u origin "$BRANCH_NAME"
-          fi
-
-            # Design: add EMPTY commit to guarantee a diff
-      - name: phase:design → ensure empty commit (commit if missing)
-        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 empty commit to guarantee branch has commits
-          git commit --allow-empty -m "Design phase initiated for Issue #$ISSUE_NUMBER: $ISSUE_TITLE"
-          git push origin "$BRANCH_NAME"
-          
-          # Create or update Design PR
-          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.
-
-          "
-
-          # Check if PR already exists
-          EXISTING_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number' 2>/dev/null || echo "")
-          
-          if [ -n "$EXISTING_PR" ]; then
-            echo "Updating existing PR #$EXISTING_PR"
-            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
-            gh pr edit "$EXISTING_PR" --add-label "phase:design" --remove-label "phase:tests" --remove-label "phase:impl" 
-          else
-            echo "Creating new Design PR"
-            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
-            # Add labels to the new PR
-            sleep 2  # Brief delay to ensure PR is created
-            NEW_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number')
-            gh pr edit "$NEW_PR" --add-label "phase:design" --remove-label "phase:tests" --remove-label "phase:impl" 
-          fi
-
-      - name: Handle 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 Test Implementation PR
-          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.
-
-          "
-
-          # Check if PR already exists
-          EXISTING_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number' 2>/dev/null || echo "")
-          
-          if [ -n "$EXISTING_PR" ]; then
-            echo "Updating existing PR #$EXISTING_PR"
-            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
-            gh pr edit "$EXISTING_PR" --add-label "phase:tests" --remove-label "phase:design" --remove-label "phase:impl"
-          else
-            echo "Creating new Test Plan PR"
-            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
-            # Add labels to the new PR
-            sleep 2  # Brief delay to ensure PR is created
-            NEW_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number')
-            gh pr edit "$NEW_PR" --add-label "phase:tests" --remove-label "phase:design" --remove-label "phase:impl"
-          fi
-
-      - name: Handle 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 Implementation PR
-          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
-
-          "
-
-          # Check if PR already exists
-          EXISTING_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number' 2>/dev/null || echo "")
-          
-          if [ -n "$EXISTING_PR" ]; then
-            echo "Updating existing PR #$EXISTING_PR"
-            gh pr edit "$EXISTING_PR" --title "$PR_TITLE" --body "$PR_BODY"
-            gh pr edit "$EXISTING_PR" --add-label "phase:impl" --remove-label "phase:design" --remove-label "phase:tests"
-          else
-            echo "Creating new Implementation PR"
-            gh pr create --title "$PR_TITLE" --body "$PR_BODY" --base master --head "$BRANCH_NAME" --draft
-            # Add labels to the new PR
-            sleep 2  # Brief delay to ensure PR is created
-            NEW_PR=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number')
-            gh pr edit "$NEW_PR" --add-label "phase:impl" --remove-label "phase:design" --remove-label "phase:tests"
-          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
-          
-          # Get the PR number for the current branch and normalize its status
-          BRANCH_NAME="${{ steps.issue-details.outputs.branch_name }}"
-          PR_NUMBER=$(gh pr list --head "$BRANCH_NAME" --json number --jq '.[0].number' 2>/dev/null || echo "")
-          
-          if [ -n "$PR_NUMBER" ]; then
-            gh pr edit "$PR_NUMBER" --add-label "status:wip" --remove-label "status:needs-review" --remove-label "status:complete" || true
-          fi

package/github/status-change.yml

@@ -1,68 +0,0 @@
-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