diff --git a/.github/ISSUE_TEMPLATE/bug_issue.md b/.github/ISSUE_TEMPLATE/bug_issue.md
index aa75ae0..717e0bc 100644
--- a/.github/ISSUE_TEMPLATE/bug_issue.md
+++ b/.github/ISSUE_TEMPLATE/bug_issue.md
@@ -67,6 +67,29 @@ Tell us about your environment, including:
 …
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
 -->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/enhancement_issue.md b/.github/ISSUE_TEMPLATE/enhancement_issue.md
index c365113..17bb8e6 100644
--- a/.github/ISSUE_TEMPLATE/enhancement_issue.md
+++ b/.github/ISSUE_TEMPLATE/enhancement_issue.md
@@ -29,6 +29,29 @@ Instructions:
 
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/feature_issue.md b/.github/ISSUE_TEMPLATE/feature_issue.md
index c9611f4..94adc57 100644
--- a/.github/ISSUE_TEMPLATE/feature_issue.md
+++ b/.github/ISSUE_TEMPLATE/feature_issue.md
@@ -41,6 +41,29 @@ _[Issues should be attached as sub issues as they are created. There will probab
 
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/other_issue.md b/.github/ISSUE_TEMPLATE/other_issue.md
index d3916a4..8ba9667 100644
--- a/.github/ISSUE_TEMPLATE/other_issue.md
+++ b/.github/ISSUE_TEMPLATE/other_issue.md
@@ -8,6 +8,29 @@ about: For issues that don't fit any other category
 
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/product_issue.md b/.github/ISSUE_TEMPLATE/product_issue.md
index ef14707..f85cdba 100644
--- a/.github/ISSUE_TEMPLATE/product_issue.md
+++ b/.github/ISSUE_TEMPLATE/product_issue.md
@@ -23,6 +23,29 @@ _[Then, more detail. Provide a short summary and/or list key outcomes that the u
 
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/technical_task_issue.md b/.github/ISSUE_TEMPLATE/technical_task_issue.md
index 3c34aa1..b220cc6 100644
--- a/.github/ISSUE_TEMPLATE/technical_task_issue.md
+++ b/.github/ISSUE_TEMPLATE/technical_task_issue.md
@@ -13,12 +13,13 @@ Instructions:
 
 ## Overview
 
-<!-- 
+<!--
 Describe what needs to be done and why.
 Keep it brief - a few sentences.
 -->
 
 **Complexity:** Low | Medium | High
+**Target branch:** <!-- e.g. develop, release-0.17.x -->
 
 ### Context
 
@@ -73,7 +74,7 @@ All items should be verifiable.
 
 For frontend tasks, consider adding subsections:
 #### General
-#### Accessibility and i18n  
+#### Accessibility and i18n
 #### Testing
 
 For backend tasks, consider:
@@ -81,7 +82,7 @@ For backend tasks, consider:
 #### Testing
 -->
 
-- [ ] 
+- [ ]
 
 ### Testing
 
@@ -102,6 +103,29 @@ Links to documentation, code references, or relevant libraries.
 -->
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/ISSUE_TEMPLATE/technical_tracking_issue.md b/.github/ISSUE_TEMPLATE/technical_tracking_issue.md
index 2cc677a..c12bf39 100644
--- a/.github/ISSUE_TEMPLATE/technical_tracking_issue.md
+++ b/.github/ISSUE_TEMPLATE/technical_tracking_issue.md
@@ -14,7 +14,7 @@ Instructions:
 
 ## Overview
 
-<!-- 
+<!--
 Describe what this tracking issue encompasses and why the work matters.
 Keep it concise: 3-5 sentences covering the "what" and "why".
 -->
@@ -31,7 +31,7 @@ Define boundaries clearly.
 
 <!--
 OPTIONAL - Delete if not needed.
-Include setup instructions, documentation links, or reference materials 
+Include setup instructions, documentation links, or reference materials
 that apply across all sub-tasks. Especially useful for community-facing projects.
 -->
 
@@ -53,6 +53,29 @@ Otherwise, leave testing guidance to individual task issues.
 -->
 
 <!--
-AI DISCLOSURE: If this issue was written with AI assistance, add:
-🤖 This issue was written with AI assistance, under supervision, review and final edits by [@username] 🤖
--->
\ No newline at end of file
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this issue, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Verify claims and sources.
+  Edit - Digest and refine AI output rather than copy-pasting it.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Gemini to help draft this issue from my rough notes. I edited
+  the description for accuracy, confirmed the reproduction steps myself,
+  and trimmed the verbose output."
+
+  "This is based on a Claude summary of clearinghouse feedback. I
+  cross-checked the key points against the original feedback and rewrote
+  the requirements in my own words."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 07a4441..342a2dc 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -29,3 +29,32 @@
 -->
 
 …
+
+<!--
+OPTIONAL - Delete if not needed.
+
+AI USAGE - DEEP guidelines
+
+If AI was used in preparing this PR, please fill in the section below.
+Our DEEP guidelines ask that when using AI you:
+
+  Disclose - Be open about when you've used AI for support.
+  Engage critically - Question what is generated. Review code for correctness and unnecessary complexity.
+  Edit - Review and refine AI output. Remove unnecessary code and verify it still works after your edits.
+  Process sharing - Explain how you used the AI so others can learn.
+
+Examples of good disclosures:
+
+  "I used Claude Code to implement the component, prompting it to follow
+  the pattern in ComponentX. I reviewed the generated code, removed
+  unnecessary error handling, and verified the tests pass."
+
+  "I brainstormed the approach with Gemini, then had it write failing
+  tests for the feature. After reviewing the tests, I used Claude Code
+  to generate the implementation. I refactored the output to reduce
+  verbosity and ran the full test suite."
+
+If AI was not used, delete the section below.
+-->
+
+## AI usage
diff --git a/.github/workflows/pr-statistics.yml b/.github/workflows/pr-statistics.yml
index cc80f7b..37d33a9 100644
--- a/.github/workflows/pr-statistics.yml
+++ b/.github/workflows/pr-statistics.yml
@@ -1,13 +1,11 @@
 name: PR Statistics Report
 run-name: Generate weekly PR statistics and send to Slack
-
 on:
   schedule:
     # Every Monday at 8am GMT
     - cron: '0 8 * * 1'
   workflow_dispatch:
-    # Allow manual triggering for testing
-
+  # Allow manual triggering for testing
 jobs:
   generate-pr-statistics:
     runs-on: ubuntu-latest
@@ -18,22 +16,18 @@ jobs:
         with:
           app_id: ${{ secrets.LE_BOT_APP_ID }}
           private_key: ${{ secrets.LE_BOT_PRIVATE_KEY }}
-
       - name: Checkout .github repository
         uses: actions/checkout@v4
         with:
           repository: learningequality/.github
           ref: main
           token: ${{ steps.generate-token.outputs.token }}
-
       - name: Setup Node.js
         uses: actions/setup-node@v4
         with:
           node-version: '20'
-
       - name: Install dependencies
         run: npm install
-
       - name: Generate PR statistics
         id: stats
         uses: actions/github-script@v7
@@ -42,7 +36,6 @@ jobs:
           script: |
             const script = require('./scripts/pr-statistics.js');
             return await script({github, context, core});
-
       - name: Send Slack notification
         if: ${{ steps.stats.outputs.slack_message }}
         uses: slackapi/slack-github-action@v2.0.0
diff --git a/dependabot.yml b/dependabot.yml
index b308082..1506219 100644
--- a/dependabot.yml
+++ b/dependabot.yml
@@ -6,14 +6,12 @@ updates:
       interval: "monthly"
     cooldown:
       default-days: 7
-
   - package-ecosystem: "pip"
     directory: "/"
     schedule:
       interval: "monthly"
     cooldown:
       default-days: 7
-
   - package-ecosystem: "github-actions"
     directory: "/"
     schedule: