From 9a465bf6aa61b2eda956c6a344b08efdebb037de Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 08:31:40 +0200
Subject: [PATCH 1/7] chore(ci): add issue triage, stale, and Slack PR
 automation

- add issue forms (bug/feature) with required EW, scope, request-type,
  and priority fields; disable blank issues
- triage-assign: apply `ew` and `scope:*` labels and auto-assign area owners
- issue-completeness: flag missing info with `triage-incomplete` plus an
  OP-tagged comment that clears once the issue is complete
- stale: warn then close inactive issues (60d + 21d) and PRs (49d + 14d)
- slack-pr-ticker: route core vs outside-contributor PRs to two channels
- document the automation in CONTRIBUTING.md

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/ISSUE_TEMPLATE/bug_report.yml      | 114 +++++++++++++++++++++
 .github/ISSUE_TEMPLATE/config.yml          |   5 +
 .github/ISSUE_TEMPLATE/feature_request.yml |  82 +++++++++++++++
 .github/pull_request_template.md           |   7 ++
 .github/workflows/issue-completeness.yml   | 100 ++++++++++++++++++
 .github/workflows/pr-ew-review.yml         |  48 +++++++++
 .github/workflows/slack-pr-ticker.yml      |  71 +++++++++++++
 .github/workflows/stale.yml                |  63 ++++++++++++
 .github/workflows/triage-assign.yml        |  84 +++++++++++++++
 CONTRIBUTING.md                            |  48 +++++++++
 10 files changed, 622 insertions(+)
 create mode 100644 .github/ISSUE_TEMPLATE/bug_report.yml
 create mode 100644 .github/ISSUE_TEMPLATE/config.yml
 create mode 100644 .github/ISSUE_TEMPLATE/feature_request.yml
 create mode 100644 .github/workflows/issue-completeness.yml
 create mode 100644 .github/workflows/pr-ew-review.yml
 create mode 100644 .github/workflows/slack-pr-ticker.yml
 create mode 100644 .github/workflows/stale.yml
 create mode 100644 .github/workflows/triage-assign.yml

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 000000000..501ec2d0e
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,114 @@
+name: Bug report
+description: Report something that is broken or not behaving as expected.
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for filing a bug. Fields marked required drive our triage automation
+        (the `ew` label, area assignment, and the completeness check). Please fill in
+        as much as you can — a bot will tag you if anything required is missing.
+
+  - type: dropdown
+    id: ew
+    attributes:
+      label: Experience Workspace (EW) related?
+      description: Does this issue involve the Experience Workspace (EW) assistant / AI experience?
+      options:
+        - "No"
+        - "Yes"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope / Area
+      description: Which part of the product does this touch? This drives auto-assignment.
+      options:
+        - Editor / Canvas
+        - Blocks / Rendering
+        - Heli
+        - Config / Sheets
+        - Auth / Permissions
+        - AI Assistant / Agent
+        - MCP / Tooling
+        - Infra / CI
+        - Docs
+        - Other / Unsure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: request-type
+    attributes:
+      label: Customer request or developer need?
+      description: Where is this coming from?
+      options:
+        - Customer request
+        - Developer need
+    validations:
+      required: true
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: |
+        P0 = production down / data loss, P1 = major broken, no workaround,
+        P2 = important but has a workaround, P3 = minor / nice to have.
+        Maintainers may adjust this during triage.
+      options:
+        - P0
+        - P1
+        - P2
+        - P3
+    validations:
+      required: true
+
+  - type: textarea
+    id: what-happened
+    attributes:
+      label: What happened?
+      description: A clear description of the bug, including what you expected instead.
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro-steps
+    attributes:
+      label: Steps to reproduce
+      description: Minimal, numbered steps someone else can follow.
+      placeholder: |
+        1. Go to ...
+        2. Click ...
+        3. See error
+    validations:
+      required: true
+
+  - type: textarea
+    id: repro-links
+    attributes:
+      label: Reproduction link(s)
+      description: URL(s) where the bug can be observed (before/after, test site, deployed branch).
+      placeholder: |
+        - Before: https://main--{repo}--{owner}.aem.live/
+        - After:  https://<branch>--{repo}--{owner}.aem.live/
+    validations:
+      required: true
+
+  - type: input
+    id: video
+    attributes:
+      label: Video (optional)
+      description: A short screen recording helps a lot, but it is not required.
+    validations:
+      required: false
+
+  - type: input
+    id: version
+    attributes:
+      label: Environment / version
+      description: Branch, commit, or deployed URL where you saw this.
+    validations:
+      required: false
diff --git a/.github/ISSUE_TEMPLATE/config.yml b/.github/ISSUE_TEMPLATE/config.yml
new file mode 100644
index 000000000..39ad2c6af
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/config.yml
@@ -0,0 +1,5 @@
+blank_issues_enabled: false
+contact_links:
+  - name: Question or discussion
+    url: https://github.com/adobe/da-nx/discussions
+    about: For open-ended questions and ideas, please start a discussion instead of an issue.
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
new file mode 100644
index 000000000..68685f3bd
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,82 @@
+name: Feature request
+description: Suggest a new capability or an improvement.
+labels: ["enhancement"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Thanks for the idea. Fields marked required drive our triage automation
+        (the `ew` label, area assignment, and the completeness check). A bot will
+        tag you if anything required is missing.
+
+  - type: dropdown
+    id: ew
+    attributes:
+      label: Experience Workspace (EW) related?
+      description: Does this request involve the Experience Workspace (EW) assistant / AI experience?
+      options:
+        - "No"
+        - "Yes"
+    validations:
+      required: true
+
+  - type: dropdown
+    id: scope
+    attributes:
+      label: Scope / Area
+      description: Which part of the product does this touch? This drives auto-assignment.
+      options:
+        - Editor / Canvas
+        - Blocks / Rendering
+        - Heli
+        - Config / Sheets
+        - Auth / Permissions
+        - AI Assistant / Agent
+        - MCP / Tooling
+        - Infra / CI
+        - Docs
+        - Other / Unsure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: request-type
+    attributes:
+      label: Customer request or developer need?
+      description: Where is this coming from?
+      options:
+        - Customer request
+        - Developer need
+    validations:
+      required: true
+
+  - type: dropdown
+    id: priority
+    attributes:
+      label: Priority
+      description: |
+        P0 = critical / blocking, P1 = high, P2 = medium, P3 = low.
+        Maintainers may adjust this during triage.
+      options:
+        - P0
+        - P1
+        - P2
+        - P3
+    validations:
+      required: true
+
+  - type: textarea
+    id: problem
+    attributes:
+      label: Problem / motivation
+      description: What are you trying to do, and why is it hard today?
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposed solution
+      description: What would you like to see happen?
+    validations:
+      required: false
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 026dac98f..9d19d0c9a 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -5,3 +5,10 @@ Fix #<gh-issue-id>
 Test URLs:
 - Before: https://main--{repo}--{owner}.hlx.live/
 - After: https://<branch>--{repo}--{owner}.hlx.live/
+
+## Experience Workspace (EW)
+
+- [ ] This PR touches Experience Workspace (EW)
+
+<!-- If checked, the `ew` label is applied and the core team is added as reviewers automatically. -->
+
diff --git a/.github/workflows/issue-completeness.yml b/.github/workflows/issue-completeness.yml
new file mode 100644
index 000000000..f09f09bdc
--- /dev/null
+++ b/.github/workflows/issue-completeness.yml
@@ -0,0 +1,100 @@
+name: Issue completeness check
+
+# Verifies a new/edited issue has the information triage needs. If anything is
+# missing it applies the `triage-incomplete` label and leaves a single comment
+# (tagging the reporter) listing what's needed. The comment is updated in place
+# as the issue is fixed, and both the comment and label clear once it's complete.
+#
+# Required: a description, customer-vs-developer, a priority (P0-P3), and — for
+# bugs — reproduction steps and a reproduction link. A video is prompted but
+# never blocks.
+
+on:
+  issues:
+    types: [opened, edited]
+
+permissions:
+  issues: write
+
+jobs:
+  check:
+    # Don't react to issues opened by bots (avoids automation loops).
+    if: ${{ github.event.issue.user.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            const MARKER = '<!-- issue-completeness-bot -->';
+            const INCOMPLETE = 'triage-incomplete';
+
+            const body = context.payload.issue.body || '';
+            const author = context.payload.issue.user.login;
+            const { owner, repo } = context.repo;
+            const issue_number = context.payload.issue.number;
+            const labels = (context.payload.issue.labels || []).map(l => l.name);
+            const isBug = labels.includes('bug');
+
+            const esc = (s) => s.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+            // Grab the first non-empty line under a "### <label>" heading.
+            const val = (label) => {
+              const m = body.match(new RegExp('###\\s*' + esc(label) + '\\s*\\n+([^\\n]+)'));
+              return m ? m[1].trim() : '';
+            };
+            const isEmpty = (v) => !v || /^_no response_$/i.test(v.trim());
+
+            const missing = [];
+            const description = val('What happened?') || val('Problem / motivation');
+            if (isEmpty(description)) missing.push('A description of the issue');
+            if (isEmpty(val('Customer request or developer need?')))
+              missing.push('Whether this is a **customer request** or a **developer need**');
+            if (isEmpty(val('Priority'))) missing.push('A **priority** (P0, P1, P2, or P3)');
+            if (isBug) {
+              if (isEmpty(val('Steps to reproduce'))) missing.push('**Steps to reproduce**');
+              if (isEmpty(val('Reproduction link(s)'))) missing.push('A **reproduction link**');
+            }
+            const videoMissing = isBug && isEmpty(val('Video (optional)'));
+
+            // Find our existing tracked comment, if any.
+            const comments = await github.paginate(github.rest.issues.listComments, {
+              owner, repo, issue_number, per_page: 100,
+            });
+            const existing = comments.find(c => (c.body || '').includes(MARKER));
+
+            const hasLabel = labels.includes(INCOMPLETE);
+            const upsert = async (bodyMd) => {
+              if (existing) {
+                await github.rest.issues.updateComment({ owner, repo, comment_id: existing.id, body: bodyMd });
+              } else {
+                await github.rest.issues.createComment({ owner, repo, issue_number, body: bodyMd });
+              }
+            };
+
+            if (missing.length) {
+              if (!hasLabel) {
+                await github.rest.issues.addLabels({ owner, repo, issue_number, labels: [INCOMPLETE] });
+              }
+              let md = `${MARKER}\nHi @${author} :wave: thanks for opening this! `
+                + `Before we can triage it, please add the following:\n\n`
+                + missing.map(m => `- [ ] ${m}`).join('\n') + '\n';
+              if (videoMissing) {
+                md += `\n_Optional:_ a short screen recording of the problem helps a lot, but it is not required.\n`;
+              }
+              md += `\nEdit the issue description to add these — this notice and the \`${INCOMPLETE}\` `
+                + `label clear automatically once everything is filled in.`;
+              await upsert(md);
+              core.info('Marked incomplete. Missing: ' + missing.join('; '));
+            } else {
+              if (hasLabel) {
+                await github.rest.issues.removeLabel({ owner, repo, issue_number, name: INCOMPLETE }).catch(() => {});
+              }
+              if (existing) {
+                const done = `${MARKER}\nThanks @${author} — everything triage needs is here. :white_check_mark:`
+                  + (videoMissing ? ` (A short screen recording would still help if you can add one.)` : '');
+                await github.rest.issues.updateComment({ owner, repo, comment_id: existing.id, body: done });
+              } else if (videoMissing) {
+                await upsert(`${MARKER}\nThanks @${author} — this looks complete. If you can, a short screen `
+                  + `recording would help us reproduce faster. Not required, just helpful!`);
+              }
+              core.info('Issue is complete.');
+            }
diff --git a/.github/workflows/pr-ew-review.yml b/.github/workflows/pr-ew-review.yml
new file mode 100644
index 000000000..fa2b6655a
--- /dev/null
+++ b/.github/workflows/pr-ew-review.yml
@@ -0,0 +1,48 @@
+name: PR Experience Workspace check
+
+# When a PR's "Experience Workspace (EW)" box is checked, apply the `ew` label
+# and request review from the core team (excluding the PR author). Unchecking it
+# later removes the label. Uses pull_request_target so it has write access for
+# PRs from forks; it only reads the PR body, never checks out PR code.
+
+on:
+  pull_request_target:
+    types: [opened, edited, reopened, ready_for_review]
+
+permissions:
+  contents: read
+  issues: write
+  pull-requests: write
+
+jobs:
+  ew:
+    if: ${{ github.event.pull_request.user.type != 'Bot' }}
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/github-script@v7
+        with:
+          script: |
+            const CORE = ['svynod', 'hannesolo', 'mhaack', 'anfibiacreativa'];
+
+            const pr = context.payload.pull_request;
+            const body = pr.body || '';
+            const isEW = /- \[[xX]\]\s*This PR touches Experience Workspace/.test(body);
+            const { owner, repo } = context.repo;
+            const pull_number = pr.number;
+            const author = (pr.user.login || '').toLowerCase();
+            const labels = (pr.labels || []).map(l => l.name);
+
+            if (isEW) {
+              if (!labels.includes('ew')) {
+                await github.rest.issues.addLabels({ owner, repo, issue_number: pull_number, labels: ['ew'] });
+                const reviewers = CORE.filter(u => u.toLowerCase() !== author);
+                try {
+                  await github.rest.pulls.requestReviewers({ owner, repo, pull_number, reviewers });
+                  core.info('Requested review from: ' + reviewers.join(', '));
+                } catch (e) {
+                  core.warning('requestReviewers failed: ' + e.message);
+                }
+              }
+            } else if (labels.includes('ew')) {
+              await github.rest.issues.removeLabel({ owner, repo, issue_number: pull_number, name: 'ew' }).catch(() => {});
+            }
diff --git a/.github/workflows/slack-pr-ticker.yml b/.github/workflows/slack-pr-ticker.yml
new file mode 100644
index 000000000..25e52dc75
--- /dev/null
+++ b/.github/workflows/slack-pr-ticker.yml
@@ -0,0 +1,71 @@
+name: Slack PR Ticker
+
+# Posts a one-line notice to Slack when a PR is opened / marked ready / reopened.
+# Core PRs go to one channel, external PRs to another. Core vs external is decided
+# from an explicit allowlist of core author usernames (CORE_AUTHORS below).
+#
+# Uses pull_request_target so the org secrets (webhook URLs) are available even
+# for PRs from forks. This job only reads event metadata and never checks out or
+# runs code from the PR, so it is not exposed to the pull_request_target risk of
+# executing untrusted code.
+#
+# Required secrets:
+#   SLACK_WEBHOOK_CORE_PRS       Incoming Webhook URL for the core-team channel
+#   SLACK_WEBHOOK_COMMUNITY_PRS  Incoming Webhook URL for the contributor channel
+
+on:
+  pull_request_target:
+    types: [opened, ready_for_review, reopened]
+
+permissions:
+  contents: read
+
+jobs:
+  notify:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Route and post to Slack
+        env:
+          CORE_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_CORE_PRS }}
+          COMMUNITY_WEBHOOK: ${{ secrets.SLACK_WEBHOOK_COMMUNITY_PRS }}
+          PR_TITLE: ${{ github.event.pull_request.title }}
+          PR_URL: ${{ github.event.pull_request.html_url }}
+          PR_NUMBER: ${{ github.event.pull_request.number }}
+          PR_AUTHOR: ${{ github.event.pull_request.user.login }}
+          PR_DRAFT: ${{ github.event.pull_request.draft }}
+          REPO: ${{ github.repository }}
+          # Core contributors (edit to keep in sync with the team).
+          CORE_AUTHORS: 'svynod hannesolo mhaack anfibiacreativa'
+        run: |
+          set -euo pipefail
+
+          # Don't ticker drafts; the ready_for_review event covers them later.
+          if [ "$PR_DRAFT" = "true" ]; then
+            echo "Draft PR; skipping."
+            exit 0
+          fi
+
+          WEBHOOK="$COMMUNITY_WEBHOOK"; TIER="External Contribution"
+          for u in $CORE_AUTHORS; do
+            if [ "$(echo "$u" | tr '[:upper:]' '[:lower:]')" = "$(echo "$PR_AUTHOR" | tr '[:upper:]' '[:lower:]')" ]; then
+              WEBHOOK="$CORE_WEBHOOK"; TIER="Core Contribution"; break
+            fi
+          done
+
+          if [ -z "${WEBHOOK:-}" ]; then
+            echo "No webhook configured for tier=$TIER; skipping."
+            exit 0
+          fi
+
+          # Send discrete fields so a Slack Workflow Builder webhook can map them
+          # to variables (repo, number, title, author, url, tier) and compose the
+          # message itself. Raw URLs auto-linkify in Slack.
+          PAYLOAD="$(jq -n \
+            --arg repo "$REPO" \
+            --arg number "$PR_NUMBER" \
+            --arg title "$PR_TITLE" \
+            --arg author "$PR_AUTHOR" \
+            --arg url "$PR_URL" \
+            --arg tier "$TIER" \
+            '{repo: $repo, number: $number, title: $title, author: $author, url: $url, tier: $tier}')"
+          curl -sS -X POST -H 'Content-type: application/json' --data "$PAYLOAD" "$WEBHOOK"
diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
new file mode 100644
index 000000000..6bf537c2e
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,63 @@
+name: Close stale issues and PRs
+
+# Two-phase housekeeping. An item goes idle -> gets a `stale` label + a warning
+# comment (which notifies the original poster, who is subscribed to their own
+# thread) -> is closed after a grace period if still untouched. ANY activity, or
+# removing the `stale` label, resets the clock.
+#
+#   Issues:        stale after 60 days (2 months) -> close 21 days (3 weeks) later
+#   Pull requests: stale after 49 days (7 weeks)  -> close 14 days (2 weeks) later
+
+on:
+  schedule:
+    - cron: '30 1 * * *' # daily at 01:30 UTC
+  workflow_dispatch: {}
+
+permissions:
+  issues: write
+  pull-requests: write
+
+jobs:
+  stale:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@v9
+        with:
+          # Process oldest items first so the longest-idle backlog clears first.
+          ascending: true
+          # Raise from the default 30 so the initial backlog sweep isn't truncated.
+          operations-per-run: 150
+
+          # ---- Issues: 2 months idle, then 3 weeks' grace ----
+          days-before-issue-stale: 60
+          days-before-issue-close: 21
+          stale-issue-label: stale
+          stale-issue-message: >
+            This issue has had no activity for 2 months, so it has been marked
+            `stale`. It will be closed in **3 weeks** if there is no further
+            activity. If it is still relevant, please leave a comment (or remove
+            the `stale` label) and we will keep it open. Thanks for helping keep
+            the backlog tidy!
+          close-issue-message: >
+            Closing this issue after 3 weeks of inactivity following the stale
+            notice. If it is still relevant, feel free to reopen it or open a new
+            issue with fresh context.
+
+          # ---- Pull requests: 7 weeks idle, then 2 weeks' grace ----
+          days-before-pr-stale: 49
+          days-before-pr-close: 14
+          stale-pr-label: stale
+          stale-pr-message: >
+            This pull request has had no activity for 7 weeks, so it has been
+            marked `stale`. It will be closed in **2 weeks** if there is no
+            further activity. If you are still working on it, please push a
+            commit or leave a comment (or remove the `stale` label). Thanks!
+          close-pr-message: >
+            Closing this pull request after 2 weeks of inactivity following the
+            stale notice. If you would like to continue the work, please reopen
+            it or open a fresh PR.
+
+          # Never auto-close things that are intentionally long-lived.
+          exempt-issue-labels: 'pinned,security,keep-open,roadmap'
+          exempt-pr-labels: 'pinned,security,keep-open,work-in-progress'
+          exempt-all-milestones: true
diff --git a/.github/workflows/triage-assign.yml b/.github/workflows/triage-assign.yml
new file mode 100644
index 000000000..15a264fbb
--- /dev/null
+++ b/.github/workflows/triage-assign.yml
@@ -0,0 +1,84 @@
+name: Issue Triage & Assign
+
+# Reads the required dropdowns from the issue-form body and, without any
+# third-party actions:
+#   1. applies the `ew` label when the reporter marked the issue EW-related
+#   2. applies a `scope:*` label and assigns the area owner based on Scope / Area
+#
+# The field labels parsed below MUST match the `label:` values in
+# .github/ISSUE_TEMPLATE/bug_report.yml and feature_request.yml exactly.
+
+on:
+  issues:
+    types: [opened, edited]
+
+permissions:
+  issues: write
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Apply EW label, scope label and assignee
+        uses: actions/github-script@v7
+        with:
+          script: |
+            // ---- Roster: map each Scope / Area option to GitHub usernames ----
+            const ALL = ['svynod', 'hannesolo', 'mhaack', 'anfibiacreativa'];
+            const SCOPE_ASSIGNEES = {
+              'Editor / Canvas':      ['svynod', 'hannesolo'],
+              'Blocks / Rendering':   ['svynod', 'hannesolo', 'mhaack'],
+              'Heli':                 ['mhaack', 'hannesolo'],
+              'Config / Sheets':      ['mhaack', 'hannesolo', 'anfibiacreativa'],
+              'Auth / Permissions':   ['mhaack', 'hannesolo', 'anfibiacreativa'],
+              'AI Assistant / Agent': ['anfibiacreativa', 'mhaack'],
+              'MCP / Tooling':        ['anfibiacreativa'],
+              'Infra / CI':           ['mhaack', 'hannesolo', 'anfibiacreativa'],
+              'Docs':                 ALL,
+              'Other / Unsure':       ALL,
+            };
+            // Optional short slug used for the `scope:*` label.
+            const SCOPE_SLUG = {
+              'Editor / Canvas':      'editor',
+              'Blocks / Rendering':   'blocks',
+              'Heli':                 'heli',
+              'Config / Sheets':      'config',
+              'Auth / Permissions':   'auth',
+              'AI Assistant / Agent': 'assistant',
+              'MCP / Tooling':        'mcp',
+              'Infra / CI':           'infra',
+              'Docs':                 'docs',
+              'Other / Unsure':       'triage',
+            };
+
+            const body = context.payload.issue.body || '';
+
+            // Issue forms render each field as "### <label>\n\n<value>".
+            const readField = (label) => {
+              const esc = label.replace(/[.*+?^${}()|[\]\\]/g, '\\$&');
+              const m = body.match(new RegExp('###\\s*' + esc + '\\s*\\n+([^\\n]+)'));
+              return m ? m[1].trim() : '';
+            };
+
+            const ew = readField('Experience Workspace (EW) related?');
+            const scope = readField('Scope / Area');
+
+            const { owner, repo } = context.repo;
+            const issue_number = context.payload.issue.number;
+
+            const labels = [];
+            if (/^yes\b/i.test(ew)) labels.push('ew');
+            if (scope && SCOPE_SLUG[scope]) labels.push('scope:' + SCOPE_SLUG[scope]);
+
+            if (labels.length) {
+              await github.rest.issues.addLabels({ owner, repo, issue_number, labels });
+              core.info('Added labels: ' + labels.join(', '));
+            }
+
+            const assignees = (SCOPE_ASSIGNEES[scope] || []).filter(Boolean);
+            if (assignees.length) {
+              await github.rest.issues.addAssignees({ owner, repo, issue_number, assignees });
+              core.info('Assigned: ' + assignees.join(', '));
+            } else {
+              core.info('No assignee configured for scope: ' + (scope || '(none)'));
+            }
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index c62879cec..326f4c437 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -75,3 +75,51 @@ One of the maintainers will look at the pull request within one week. Feedback o
 The project's committers will release to the [Adobe organization on npmjs.org](https://www.npmjs.com/org/adobe).
 Please contact the [Adobe Open Source Advisory Board](https://git.corp.adobe.com/OpenSourceAdvisoryBoard/discuss/issues) to get access to the npmjs organization.
 
+# Issue and PR Housekeeping Automation
+
+To keep the backlog healthy, this repo runs a few GitHub Actions bots. Here is what to expect.
+
+## Filing an issue
+
+Issues are created through issue forms (blank issues are disabled). A few fields are **required** and power automatic triage:
+
+- **Experience Workspace (EW) related?** — choosing **Yes** automatically applies the `ew` label.
+- **Scope / Area** — applies a `scope:*` label and **auto-assigns** the area owner(s):
+
+  | Scope / Area | Auto-assigned |
+  | --- | --- |
+  | Editor / Canvas | @svynod, @hannesolo |
+  | Blocks / Rendering | @svynod, @hannesolo, @mhaack |
+  | Heli | @mhaack, @hannesolo |
+  | Config / Sheets | @mhaack, @hannesolo, @anfibiacreativa |
+  | Auth / Permissions | @mhaack, @hannesolo, @anfibiacreativa |
+  | AI Assistant / Agent | @anfibiacreativa, @mhaack |
+  | MCP / Tooling | @anfibiacreativa |
+  | Infra / CI | @mhaack, @hannesolo, @anfibiacreativa |
+  | Docs | whole team |
+  | Other / Unsure | whole team |
+
+- **Customer request or developer need?** and **Priority (P0–P3)** — required so we can rank work.
+- For **bugs**: a description, **steps to reproduce**, and a **reproduction link**. A short **video is optional** but appreciated.
+
+### Completeness check
+
+When an issue is opened or edited, a bot verifies the required information is present. If anything is missing it applies the `triage-incomplete` label and leaves a comment (tagging you) listing exactly what to add. The comment and label clear automatically once the issue is complete, so just edit the description — no need to open a new issue.
+
+## Pull request notifications
+
+When a PR is opened, marked ready for review, or reopened, a short notice is posted to Slack. PRs from the **core team** and from **outside contributors** are routed to separate channels so nothing slips through.
+
+Check the **Experience Workspace (EW)** box in the PR description to automatically apply the `ew` label and request review from the core team.
+
+## Stale issues and PRs (auto-close)
+
+Inactive items are closed automatically after a warning period. **Any activity** — a comment, a new commit, or removing the `stale` label — resets the clock.
+
+| Type | Marked `stale` after | Closed after the warning |
+| --- | --- | --- |
+| Issues | 60 days (2 months) of inactivity | 21 days (3 weeks) later |
+| Pull requests | 49 days (7 weeks) of inactivity | 14 days (2 weeks) later |
+
+When an item goes stale the bot comments so you are notified with time to act. To keep something open, comment on it or remove the `stale` label. Items labeled `pinned`, `security`, `keep-open`, or assigned to a milestone are never auto-closed.
+

From f5565561f5a44f260a79a0ee3624431a8d877df3 Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 09:34:22 +0200
Subject: [PATCH 2/7] chore(ci): reword PR Experience Workspace checkbox

- change checkbox to "This PR's scope is Experience Workspace"
- keep pr-ew-review detection regex in sync with the new wording

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/pull_request_template.md   | 2 +-
 .github/workflows/pr-ew-review.yml | 2 +-
 2 files changed, 2 insertions(+), 2 deletions(-)

diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 9d19d0c9a..63b059dc5 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -8,7 +8,7 @@ Test URLs:
 
 ## Experience Workspace (EW)
 
-- [ ] This PR touches Experience Workspace (EW)
+- [ ] This PR's scope is Experience Workspace
 
 <!-- If checked, the `ew` label is applied and the core team is added as reviewers automatically. -->
 
diff --git a/.github/workflows/pr-ew-review.yml b/.github/workflows/pr-ew-review.yml
index fa2b6655a..b17c709c0 100644
--- a/.github/workflows/pr-ew-review.yml
+++ b/.github/workflows/pr-ew-review.yml
@@ -26,7 +26,7 @@ jobs:
 
             const pr = context.payload.pull_request;
             const body = pr.body || '';
-            const isEW = /- \[[xX]\]\s*This PR touches Experience Workspace/.test(body);
+            const isEW = /- \[[xX]\]\s*This PR's scope is Experience Workspace/.test(body);
             const { owner, repo } = context.repo;
             const pull_number = pr.number;
             const author = (pr.user.login || '').toLowerCase();

From afa7d59554135590bc2656eba7804342aefa2465 Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 14:00:01 +0200
Subject: [PATCH 3/7] chore(ci): remove Experience Workspace question from
 issue and PR templates

- drop the "EW related?" dropdown from bug/feature forms
- drop the EW checkbox from the PR template
- remove the pr-ew-review workflow and ew labeling in triage-assign

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/ISSUE_TEMPLATE/bug_report.yml      | 15 +------
 .github/ISSUE_TEMPLATE/feature_request.yml | 15 +------
 .github/pull_request_template.md           |  6 ---
 .github/workflows/pr-ew-review.yml         | 48 ----------------------
 .github/workflows/triage-assign.yml        | 12 ++----
 CONTRIBUTING.md                            |  3 --
 6 files changed, 8 insertions(+), 91 deletions(-)
 delete mode 100644 .github/workflows/pr-ew-review.yml

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 501ec2d0e..1ef7e48b4 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -6,19 +6,8 @@ body:
     attributes:
       value: |
         Thanks for filing a bug. Fields marked required drive our triage automation
-        (the `ew` label, area assignment, and the completeness check). Please fill in
-        as much as you can — a bot will tag you if anything required is missing.
-
-  - type: dropdown
-    id: ew
-    attributes:
-      label: Experience Workspace (EW) related?
-      description: Does this issue involve the Experience Workspace (EW) assistant / AI experience?
-      options:
-        - "No"
-        - "Yes"
-    validations:
-      required: true
+        (area assignment and the completeness check). Please fill in as much as you
+        can — a bot will tag you if anything required is missing.
 
   - type: dropdown
     id: scope
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index 68685f3bd..dbad0cd89 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -6,19 +6,8 @@ body:
     attributes:
       value: |
         Thanks for the idea. Fields marked required drive our triage automation
-        (the `ew` label, area assignment, and the completeness check). A bot will
-        tag you if anything required is missing.
-
-  - type: dropdown
-    id: ew
-    attributes:
-      label: Experience Workspace (EW) related?
-      description: Does this request involve the Experience Workspace (EW) assistant / AI experience?
-      options:
-        - "No"
-        - "Yes"
-    validations:
-      required: true
+        (area assignment and the completeness check). A bot will tag you if
+        anything required is missing.
 
   - type: dropdown
     id: scope
diff --git a/.github/pull_request_template.md b/.github/pull_request_template.md
index 63b059dc5..83cbff67b 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -6,9 +6,3 @@ Test URLs:
 - Before: https://main--{repo}--{owner}.hlx.live/
 - After: https://<branch>--{repo}--{owner}.hlx.live/
 
-## Experience Workspace (EW)
-
-- [ ] This PR's scope is Experience Workspace
-
-<!-- If checked, the `ew` label is applied and the core team is added as reviewers automatically. -->
-
diff --git a/.github/workflows/pr-ew-review.yml b/.github/workflows/pr-ew-review.yml
deleted file mode 100644
index b17c709c0..000000000
--- a/.github/workflows/pr-ew-review.yml
+++ /dev/null
@@ -1,48 +0,0 @@
-name: PR Experience Workspace check
-
-# When a PR's "Experience Workspace (EW)" box is checked, apply the `ew` label
-# and request review from the core team (excluding the PR author). Unchecking it
-# later removes the label. Uses pull_request_target so it has write access for
-# PRs from forks; it only reads the PR body, never checks out PR code.
-
-on:
-  pull_request_target:
-    types: [opened, edited, reopened, ready_for_review]
-
-permissions:
-  contents: read
-  issues: write
-  pull-requests: write
-
-jobs:
-  ew:
-    if: ${{ github.event.pull_request.user.type != 'Bot' }}
-    runs-on: ubuntu-latest
-    steps:
-      - uses: actions/github-script@v7
-        with:
-          script: |
-            const CORE = ['svynod', 'hannesolo', 'mhaack', 'anfibiacreativa'];
-
-            const pr = context.payload.pull_request;
-            const body = pr.body || '';
-            const isEW = /- \[[xX]\]\s*This PR's scope is Experience Workspace/.test(body);
-            const { owner, repo } = context.repo;
-            const pull_number = pr.number;
-            const author = (pr.user.login || '').toLowerCase();
-            const labels = (pr.labels || []).map(l => l.name);
-
-            if (isEW) {
-              if (!labels.includes('ew')) {
-                await github.rest.issues.addLabels({ owner, repo, issue_number: pull_number, labels: ['ew'] });
-                const reviewers = CORE.filter(u => u.toLowerCase() !== author);
-                try {
-                  await github.rest.pulls.requestReviewers({ owner, repo, pull_number, reviewers });
-                  core.info('Requested review from: ' + reviewers.join(', '));
-                } catch (e) {
-                  core.warning('requestReviewers failed: ' + e.message);
-                }
-              }
-            } else if (labels.includes('ew')) {
-              await github.rest.issues.removeLabel({ owner, repo, issue_number: pull_number, name: 'ew' }).catch(() => {});
-            }
diff --git a/.github/workflows/triage-assign.yml b/.github/workflows/triage-assign.yml
index 15a264fbb..f2671445d 100644
--- a/.github/workflows/triage-assign.yml
+++ b/.github/workflows/triage-assign.yml
@@ -1,11 +1,9 @@
 name: Issue Triage & Assign
 
-# Reads the required dropdowns from the issue-form body and, without any
-# third-party actions:
-#   1. applies the `ew` label when the reporter marked the issue EW-related
-#   2. applies a `scope:*` label and assigns the area owner based on Scope / Area
+# Reads the Scope / Area dropdown from the issue-form body and, without any
+# third-party actions, applies a `scope:*` label and assigns the area owner.
 #
-# The field labels parsed below MUST match the `label:` values in
+# The field label parsed below MUST match the `label:` value in
 # .github/ISSUE_TEMPLATE/bug_report.yml and feature_request.yml exactly.
 
 on:
@@ -19,7 +17,7 @@ jobs:
   triage:
     runs-on: ubuntu-latest
     steps:
-      - name: Apply EW label, scope label and assignee
+      - name: Apply scope label and assignee
         uses: actions/github-script@v7
         with:
           script: |
@@ -60,14 +58,12 @@ jobs:
               return m ? m[1].trim() : '';
             };
 
-            const ew = readField('Experience Workspace (EW) related?');
             const scope = readField('Scope / Area');
 
             const { owner, repo } = context.repo;
             const issue_number = context.payload.issue.number;
 
             const labels = [];
-            if (/^yes\b/i.test(ew)) labels.push('ew');
             if (scope && SCOPE_SLUG[scope]) labels.push('scope:' + SCOPE_SLUG[scope]);
 
             if (labels.length) {
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 326f4c437..abae609a4 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -83,7 +83,6 @@ To keep the backlog healthy, this repo runs a few GitHub Actions bots. Here is w
 
 Issues are created through issue forms (blank issues are disabled). A few fields are **required** and power automatic triage:
 
-- **Experience Workspace (EW) related?** — choosing **Yes** automatically applies the `ew` label.
 - **Scope / Area** — applies a `scope:*` label and **auto-assigns** the area owner(s):
 
   | Scope / Area | Auto-assigned |
@@ -110,8 +109,6 @@ When an issue is opened or edited, a bot verifies the required information is pr
 
 When a PR is opened, marked ready for review, or reopened, a short notice is posted to Slack. PRs from the **core team** and from **outside contributors** are routed to separate channels so nothing slips through.
 
-Check the **Experience Workspace (EW)** box in the PR description to automatically apply the `ew` label and request review from the core team.
-
 ## Stale issues and PRs (auto-close)
 
 Inactive items are closed automatically after a warning period. **Any activity** — a comment, a new commit, or removing the `stale` label — resets the clock.

From a898ba27134aabe09b1784f6a1e941b7baacdf31 Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 14:22:38 +0200
Subject: [PATCH 4/7] chore(ci): remove Helix from the Scope / Area options

- drop the placeholder "Heli" scope from bug/feature forms
- remove its triage-assign mapping and CONTRIBUTING table row

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/ISSUE_TEMPLATE/bug_report.yml      | 1 -
 .github/ISSUE_TEMPLATE/feature_request.yml | 1 -
 .github/workflows/triage-assign.yml        | 2 --
 CONTRIBUTING.md                            | 1 -
 4 files changed, 5 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 1ef7e48b4..043a624a8 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -17,7 +17,6 @@ body:
       options:
         - Editor / Canvas
         - Blocks / Rendering
-        - Heli
         - Config / Sheets
         - Auth / Permissions
         - AI Assistant / Agent
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index dbad0cd89..9c9bcb269 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -17,7 +17,6 @@ body:
       options:
         - Editor / Canvas
         - Blocks / Rendering
-        - Heli
         - Config / Sheets
         - Auth / Permissions
         - AI Assistant / Agent
diff --git a/.github/workflows/triage-assign.yml b/.github/workflows/triage-assign.yml
index f2671445d..f971c47d9 100644
--- a/.github/workflows/triage-assign.yml
+++ b/.github/workflows/triage-assign.yml
@@ -26,7 +26,6 @@ jobs:
             const SCOPE_ASSIGNEES = {
               'Editor / Canvas':      ['svynod', 'hannesolo'],
               'Blocks / Rendering':   ['svynod', 'hannesolo', 'mhaack'],
-              'Heli':                 ['mhaack', 'hannesolo'],
               'Config / Sheets':      ['mhaack', 'hannesolo', 'anfibiacreativa'],
               'Auth / Permissions':   ['mhaack', 'hannesolo', 'anfibiacreativa'],
               'AI Assistant / Agent': ['anfibiacreativa', 'mhaack'],
@@ -39,7 +38,6 @@ jobs:
             const SCOPE_SLUG = {
               'Editor / Canvas':      'editor',
               'Blocks / Rendering':   'blocks',
-              'Heli':                 'heli',
               'Config / Sheets':      'config',
               'Auth / Permissions':   'auth',
               'AI Assistant / Agent': 'assistant',
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index abae609a4..af585a403 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -89,7 +89,6 @@ Issues are created through issue forms (blank issues are disabled). A few fields
   | --- | --- |
   | Editor / Canvas | @svynod, @hannesolo |
   | Blocks / Rendering | @svynod, @hannesolo, @mhaack |
-  | Heli | @mhaack, @hannesolo |
   | Config / Sheets | @mhaack, @hannesolo, @anfibiacreativa |
   | Auth / Permissions | @mhaack, @hannesolo, @anfibiacreativa |
   | AI Assistant / Agent | @anfibiacreativa, @mhaack |

From 0f01a904beae867dbfc2420bea4ac2d0d4282954 Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 14:33:57 +0200
Subject: [PATCH 5/7] feat(ci): three-stage stale flow with re-engage and final
 notice

- Notice #1 (re-engage): no-pressure check-in at the stale threshold
- Notice #2 (final): companion step posts a closing-soon warning ~7 days out
- close after the grace period
- scope to items created on/after 2026-03-01 (start-date)
- exempt `hold` and `awaiting-maintainer` labels for PTO / on-us cases

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/workflows/stale.yml | 119 ++++++++++++++++++++++++++++--------
 1 file changed, 92 insertions(+), 27 deletions(-)

diff --git a/.github/workflows/stale.yml b/.github/workflows/stale.yml
index 6bf537c2e..37c021b75 100644
--- a/.github/workflows/stale.yml
+++ b/.github/workflows/stale.yml
@@ -1,12 +1,20 @@
 name: Close stale issues and PRs
 
-# Two-phase housekeeping. An item goes idle -> gets a `stale` label + a warning
-# comment (which notifies the original poster, who is subscribed to their own
-# thread) -> is closed after a grace period if still untouched. ANY activity, or
-# removing the `stale` label, resets the clock.
+# Three-stage, contributor-friendly housekeeping:
+#   1. Re-engage  - at the stale threshold, actions/stale adds `stale` and posts a
+#      no-pressure check-in (Notice #1). ANY activity, or removing `stale`, resets it.
+#   2. Final notice - a companion step posts a "closing soon" warning (Notice #2)
+#      ~7 days before the close date, based on how long `stale` has been applied.
+#   3. Close  - actions/stale closes after the grace period.
 #
-#   Issues:        stale after 60 days (2 months) -> close 21 days (3 weeks) later
-#   Pull requests: stale after 49 days (7 weeks)  -> close 14 days (2 weeks) later
+#   Issues:        stale after 60 days -> final notice ~day 74 -> close ~day 81
+#   Pull requests: stale after 49 days -> final notice ~day 56 -> close ~day 63
+#
+# Scope: `start-date` means only items created on/after 2026-03-01 are considered.
+# Anything older is left for manual review. Note the first run will re-engage
+# (Notice #1) any in-scope items already past the idle threshold.
+# Exempt from all of this: pinned / security / keep-open / hold / awaiting-maintainer
+# labels, and anything assigned to a milestone.
 
 on:
   schedule:
@@ -17,47 +25,104 @@ permissions:
   issues: write
   pull-requests: write
 
+env:
+  FINAL_NOTICE_LEAD_DAYS: '7'   # Notice #2 fires this many days before close
+  CLOSE_AFTER_ISSUE_DAYS: '21'  # must match days-before-issue-close
+  CLOSE_AFTER_PR_DAYS: '14'     # must match days-before-pr-close
+
 jobs:
   stale:
     runs-on: ubuntu-latest
     steps:
-      - uses: actions/stale@v9
+      - name: Mark stale, re-engage, and close
+        uses: actions/stale@v9
         with:
-          # Process oldest items first so the longest-idle backlog clears first.
           ascending: true
-          # Raise from the default 30 so the initial backlog sweep isn't truncated.
           operations-per-run: 150
+          # Only govern items created on/after this date (not retroactive).
+          start-date: '2026-03-01T00:00:00Z'
 
           # ---- Issues: 2 months idle, then 3 weeks' grace ----
           days-before-issue-stale: 60
           days-before-issue-close: 21
           stale-issue-label: stale
           stale-issue-message: >
-            This issue has had no activity for 2 months, so it has been marked
-            `stale`. It will be closed in **3 weeks** if there is no further
-            activity. If it is still relevant, please leave a comment (or remove
-            the `stale` label) and we will keep it open. Thanks for helping keep
-            the backlog tidy!
+            Just checking in on this one. It has been quiet for a while, so we have
+            labeled it `stale` to make sure it does not get forgotten. Is it still
+            relevant? A quick comment (or removing the `stale` label) keeps it active.
+            If you were waiting on a review from us, that is on our side, not yours,
+            so give us a nudge. No action needed right now; we will post a final
+            notice before anything closes.
           close-issue-message: >
-            Closing this issue after 3 weeks of inactivity following the stale
-            notice. If it is still relevant, feel free to reopen it or open a new
-            issue with fresh context.
+            Closing this issue after a period of inactivity following the stale
+            notice. Nothing is lost: if it is still relevant, reopen it or open a
+            new issue with fresh context and we will pick it up.
 
           # ---- Pull requests: 7 weeks idle, then 2 weeks' grace ----
           days-before-pr-stale: 49
           days-before-pr-close: 14
           stale-pr-label: stale
           stale-pr-message: >
-            This pull request has had no activity for 7 weeks, so it has been
-            marked `stale`. It will be closed in **2 weeks** if there is no
-            further activity. If you are still working on it, please push a
-            commit or leave a comment (or remove the `stale` label). Thanks!
+            Checking in on this PR. It has been quiet for a while, so we have labeled
+            it `stale` to keep it on our radar. Are you still working on it, or waiting
+            on us? A comment or a new commit keeps it open. If the delay is on our
+            side, that is on us. We will post a final notice before it would close.
           close-pr-message: >
-            Closing this pull request after 2 weeks of inactivity following the
-            stale notice. If you would like to continue the work, please reopen
-            it or open a fresh PR.
+            Closing this pull request after a period of inactivity following the stale
+            notice. Nothing is lost: reopen it or open a fresh PR whenever you are
+            ready and we will continue.
 
-          # Never auto-close things that are intentionally long-lived.
-          exempt-issue-labels: 'pinned,security,keep-open,roadmap'
-          exempt-pr-labels: 'pinned,security,keep-open,work-in-progress'
+          # Never touch things that are intentionally long-lived or explicitly held.
+          exempt-issue-labels: 'pinned,security,keep-open,roadmap,hold,awaiting-maintainer'
+          exempt-pr-labels: 'pinned,security,keep-open,work-in-progress,hold,awaiting-maintainer'
           exempt-all-milestones: true
+
+      - name: Post final notice before close
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const LEAD = Number(process.env.FINAL_NOTICE_LEAD_DAYS);
+            const CLOSE_AFTER = {
+              issue: Number(process.env.CLOSE_AFTER_ISSUE_DAYS),
+              pr: Number(process.env.CLOSE_AFTER_PR_DAYS),
+            };
+            const MARKER = '<!-- stale-final-notice';
+            const { owner, repo } = context.repo;
+
+            const items = await github.paginate(github.rest.issues.listForRepo, {
+              owner, repo, state: 'open', labels: 'stale', per_page: 100,
+            });
+
+            for (const it of items) {
+              const isPR = !!it.pull_request;
+              const grace = isPR ? CLOSE_AFTER.pr : CLOSE_AFTER.issue;
+              const fireAfter = grace - LEAD; // days since `stale` was applied
+
+              // When was `stale` most recently applied?
+              const events = await github.paginate(github.rest.issues.listEvents, {
+                owner, repo, issue_number: it.number, per_page: 100,
+              });
+              const staleLabelings = events.filter(
+                e => e.event === 'labeled' && e.label && e.label.name === 'stale'
+              );
+              if (!staleLabelings.length) continue;
+              const staledAt = new Date(staleLabelings[staleLabelings.length - 1].created_at);
+              const ageDays = (Date.now() - staledAt.getTime()) / 86400000;
+              if (ageDays < fireAfter) continue;
+
+              // One final notice per stale cycle (marker carries the stale timestamp).
+              const marker = `${MARKER}:${staledAt.toISOString()} -->`;
+              const comments = await github.paginate(github.rest.issues.listComments, {
+                owner, repo, issue_number: it.number, per_page: 100,
+              });
+              if (comments.some(c => (c.body || '').includes(marker))) continue;
+
+              const daysLeft = Math.max(1, Math.ceil(grace - ageDays));
+              const kind = isPR ? 'pull request' : 'issue';
+              const body = `${marker}\n**Final notice:** this ${kind} will close in about `
+                + `${daysLeft} day(s) unless there is a reply or a new commit. If it is `
+                + `still relevant, just comment or remove the \`stale\` label. If you were `
+                + `waiting on us, say so and we will pick it up.`;
+              await github.rest.issues.createComment({ owner, repo, issue_number: it.number, body });
+              core.info(`Final notice posted on #${it.number} (${Math.round(ageDays)}d stale).`);
+            }

From 45532e76ab18deb8a931deb2b485276db9a9370d Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 15:29:36 +0200
Subject: [PATCH 6/7] docs(contributing): document stale cadence and pause
 labels

- explain the two notices (re-engage, then final notice) before close
- note `hold` and `awaiting-maintainer` pause stale for PTO / on-us cases
- note the flow only applies to items created on/after 2026-03-01

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 CONTRIBUTING.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index af585a403..2f34d065b 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -117,5 +117,5 @@ Inactive items are closed automatically after a warning period. **Any activity**
 | Issues | 60 days (2 months) of inactivity | 21 days (3 weeks) later |
 | Pull requests | 49 days (7 weeks) of inactivity | 14 days (2 weeks) later |
 
-When an item goes stale the bot comments so you are notified with time to act. To keep something open, comment on it or remove the `stale` label. Items labeled `pinned`, `security`, `keep-open`, or assigned to a milestone are never auto-closed.
+You get two heads-ups before anything closes: a no-pressure check-in when it is marked `stale`, then a final notice about a week before close. To keep something open, just comment or remove the `stale` label. Anything labeled `pinned`, `security`, `keep-open`, `hold`, or `awaiting-maintainer`, or assigned to a milestone, is never auto-closed. Use `hold` or `awaiting-maintainer` when the owner is away or the wait is on us. This only applies to items created on or after 2026-03-01.
 

From b8e0b86e8c778a48ad378b27144820408ffcf6b4 Mon Sep 17 00:00:00 2001
From: Natalia Venditto <nvenditto@adobe.com>
Date: Mon, 7 Sep 2026 16:00:42 +0200
Subject: [PATCH 7/7] refactor(ci): simplify triage per review feedback

- triage-assign: apply scope label only, drop auto-assignment (work from the board)
- issue forms: replace "Customer request or developer need?" with "Who is affected?"
  (customer-facing / internal)
- issue forms: remove the Priority field
- issue-completeness: check "Who is affected?", drop the priority check
- CONTRIBUTING: reflect label-only triage and the new field

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
---
 .github/ISSUE_TEMPLATE/bug_report.yml      | 30 +++----------
 .github/ISSUE_TEMPLATE/feature_request.yml | 29 +++---------
 .github/workflows/issue-completeness.yml   |  5 +--
 .github/workflows/triage-assign.yml        | 51 +++++++---------------
 CONTRIBUTING.md                            | 17 +-------
 5 files changed, 34 insertions(+), 98 deletions(-)

diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
index 043a624a8..f2b71b0e5 100644
--- a/.github/ISSUE_TEMPLATE/bug_report.yml
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -6,14 +6,14 @@ body:
     attributes:
       value: |
         Thanks for filing a bug. Fields marked required drive our triage automation
-        (area assignment and the completeness check). Please fill in as much as you
+        (scope labeling and the completeness check). Please fill in as much as you
         can — a bot will tag you if anything required is missing.
 
   - type: dropdown
     id: scope
     attributes:
       label: Scope / Area
-      description: Which part of the product does this touch? This drives auto-assignment.
+      description: Which part of the product does this touch?
       options:
         - Editor / Canvas
         - Blocks / Rendering
@@ -28,29 +28,13 @@ body:
       required: true
 
   - type: dropdown
-    id: request-type
+    id: affected
     attributes:
-      label: Customer request or developer need?
-      description: Where is this coming from?
+      label: Who is affected?
+      description: Is this customer-facing or internal?
       options:
-        - Customer request
-        - Developer need
-    validations:
-      required: true
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: |
-        P0 = production down / data loss, P1 = major broken, no workaround,
-        P2 = important but has a workaround, P3 = minor / nice to have.
-        Maintainers may adjust this during triage.
-      options:
-        - P0
-        - P1
-        - P2
-        - P3
+        - Customer-facing
+        - Internal
     validations:
       required: true
 
diff --git a/.github/ISSUE_TEMPLATE/feature_request.yml b/.github/ISSUE_TEMPLATE/feature_request.yml
index 9c9bcb269..419424c24 100644
--- a/.github/ISSUE_TEMPLATE/feature_request.yml
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -6,14 +6,14 @@ body:
     attributes:
       value: |
         Thanks for the idea. Fields marked required drive our triage automation
-        (area assignment and the completeness check). A bot will tag you if
+        (scope labeling and the completeness check). A bot will tag you if
         anything required is missing.
 
   - type: dropdown
     id: scope
     attributes:
       label: Scope / Area
-      description: Which part of the product does this touch? This drives auto-assignment.
+      description: Which part of the product does this touch?
       options:
         - Editor / Canvas
         - Blocks / Rendering
@@ -28,28 +28,13 @@ body:
       required: true
 
   - type: dropdown
-    id: request-type
+    id: affected
     attributes:
-      label: Customer request or developer need?
-      description: Where is this coming from?
+      label: Who is affected?
+      description: Is this customer-facing or internal?
       options:
-        - Customer request
-        - Developer need
-    validations:
-      required: true
-
-  - type: dropdown
-    id: priority
-    attributes:
-      label: Priority
-      description: |
-        P0 = critical / blocking, P1 = high, P2 = medium, P3 = low.
-        Maintainers may adjust this during triage.
-      options:
-        - P0
-        - P1
-        - P2
-        - P3
+        - Customer-facing
+        - Internal
     validations:
       required: true
 
diff --git a/.github/workflows/issue-completeness.yml b/.github/workflows/issue-completeness.yml
index f09f09bdc..f35e63e2f 100644
--- a/.github/workflows/issue-completeness.yml
+++ b/.github/workflows/issue-completeness.yml
@@ -46,9 +46,8 @@ jobs:
             const missing = [];
             const description = val('What happened?') || val('Problem / motivation');
             if (isEmpty(description)) missing.push('A description of the issue');
-            if (isEmpty(val('Customer request or developer need?')))
-              missing.push('Whether this is a **customer request** or a **developer need**');
-            if (isEmpty(val('Priority'))) missing.push('A **priority** (P0, P1, P2, or P3)');
+            if (isEmpty(val('Who is affected?')))
+              missing.push('Who is affected (**customer-facing** or **internal**)');
             if (isBug) {
               if (isEmpty(val('Steps to reproduce'))) missing.push('**Steps to reproduce**');
               if (isEmpty(val('Reproduction link(s)'))) missing.push('A **reproduction link**');
diff --git a/.github/workflows/triage-assign.yml b/.github/workflows/triage-assign.yml
index f971c47d9..b107e5bb8 100644
--- a/.github/workflows/triage-assign.yml
+++ b/.github/workflows/triage-assign.yml
@@ -1,7 +1,8 @@
-name: Issue Triage & Assign
+name: Issue Triage
 
-# Reads the Scope / Area dropdown from the issue-form body and, without any
-# third-party actions, applies a `scope:*` label and assigns the area owner.
+# Reads the Scope / Area dropdown from the issue-form body and applies a
+# `scope:*` label, without any third-party actions. Ownership is worked from a
+# prioritized board rather than auto-assignment.
 #
 # The field label parsed below MUST match the `label:` value in
 # .github/ISSUE_TEMPLATE/bug_report.yml and feature_request.yml exactly.
@@ -17,24 +18,10 @@ jobs:
   triage:
     runs-on: ubuntu-latest
     steps:
-      - name: Apply scope label and assignee
+      - name: Apply scope label
         uses: actions/github-script@v7
         with:
           script: |
-            // ---- Roster: map each Scope / Area option to GitHub usernames ----
-            const ALL = ['svynod', 'hannesolo', 'mhaack', 'anfibiacreativa'];
-            const SCOPE_ASSIGNEES = {
-              'Editor / Canvas':      ['svynod', 'hannesolo'],
-              'Blocks / Rendering':   ['svynod', 'hannesolo', 'mhaack'],
-              'Config / Sheets':      ['mhaack', 'hannesolo', 'anfibiacreativa'],
-              'Auth / Permissions':   ['mhaack', 'hannesolo', 'anfibiacreativa'],
-              'AI Assistant / Agent': ['anfibiacreativa', 'mhaack'],
-              'MCP / Tooling':        ['anfibiacreativa'],
-              'Infra / CI':           ['mhaack', 'hannesolo', 'anfibiacreativa'],
-              'Docs':                 ALL,
-              'Other / Unsure':       ALL,
-            };
-            // Optional short slug used for the `scope:*` label.
             const SCOPE_SLUG = {
               'Editor / Canvas':      'editor',
               'Blocks / Rendering':   'blocks',
@@ -57,22 +44,16 @@ jobs:
             };
 
             const scope = readField('Scope / Area');
-
-            const { owner, repo } = context.repo;
-            const issue_number = context.payload.issue.number;
-
-            const labels = [];
-            if (scope && SCOPE_SLUG[scope]) labels.push('scope:' + SCOPE_SLUG[scope]);
-
-            if (labels.length) {
-              await github.rest.issues.addLabels({ owner, repo, issue_number, labels });
-              core.info('Added labels: ' + labels.join(', '));
+            if (!scope || !SCOPE_SLUG[scope]) {
+              core.info('No mappable scope found: ' + (scope || '(none)'));
+              return;
             }
 
-            const assignees = (SCOPE_ASSIGNEES[scope] || []).filter(Boolean);
-            if (assignees.length) {
-              await github.rest.issues.addAssignees({ owner, repo, issue_number, assignees });
-              core.info('Assigned: ' + assignees.join(', '));
-            } else {
-              core.info('No assignee configured for scope: ' + (scope || '(none)'));
-            }
+            const { owner, repo } = context.repo;
+            await github.rest.issues.addLabels({
+              owner,
+              repo,
+              issue_number: context.payload.issue.number,
+              labels: ['scope:' + SCOPE_SLUG[scope]],
+            });
+            core.info('Added label scope:' + SCOPE_SLUG[scope]);
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 2f34d065b..73ca65ebb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -83,21 +83,8 @@ To keep the backlog healthy, this repo runs a few GitHub Actions bots. Here is w
 
 Issues are created through issue forms (blank issues are disabled). A few fields are **required** and power automatic triage:
 
-- **Scope / Area** — applies a `scope:*` label and **auto-assigns** the area owner(s):
-
-  | Scope / Area | Auto-assigned |
-  | --- | --- |
-  | Editor / Canvas | @svynod, @hannesolo |
-  | Blocks / Rendering | @svynod, @hannesolo, @mhaack |
-  | Config / Sheets | @mhaack, @hannesolo, @anfibiacreativa |
-  | Auth / Permissions | @mhaack, @hannesolo, @anfibiacreativa |
-  | AI Assistant / Agent | @anfibiacreativa, @mhaack |
-  | MCP / Tooling | @anfibiacreativa |
-  | Infra / CI | @mhaack, @hannesolo, @anfibiacreativa |
-  | Docs | whole team |
-  | Other / Unsure | whole team |
-
-- **Customer request or developer need?** and **Priority (P0–P3)** — required so we can rank work.
+- **Scope / Area** — applies a `scope:*` label so the board can filter by area. Work is picked up from the prioritized board.
+- **Who is affected?** — customer-facing or internal, so we can triage impact.
 - For **bugs**: a description, **steps to reproduce**, and a **reproduction link**. A short **video is optional** but appreciated.
 
 ### Completeness check