diff --git a/.github/ISSUE_TEMPLATE/bug_report.yml b/.github/ISSUE_TEMPLATE/bug_report.yml
new file mode 100644
index 000000000..f2b71b0e5
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/bug_report.yml
@@ -0,0 +1,86 @@
+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
+        (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?
+      options:
+        - Editor / Canvas
+        - Blocks / Rendering
+        - Config / Sheets
+        - Auth / Permissions
+        - AI Assistant / Agent
+        - MCP / Tooling
+        - Infra / CI
+        - Docs
+        - Other / Unsure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: affected
+    attributes:
+      label: Who is affected?
+      description: Is this customer-facing or internal?
+      options:
+        - Customer-facing
+        - Internal
+    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..419424c24
--- /dev/null
+++ b/.github/ISSUE_TEMPLATE/feature_request.yml
@@ -0,0 +1,55 @@
+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
+        (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?
+      options:
+        - Editor / Canvas
+        - Blocks / Rendering
+        - Config / Sheets
+        - Auth / Permissions
+        - AI Assistant / Agent
+        - MCP / Tooling
+        - Infra / CI
+        - Docs
+        - Other / Unsure
+    validations:
+      required: true
+
+  - type: dropdown
+    id: affected
+    attributes:
+      label: Who is affected?
+      description: Is this customer-facing or internal?
+      options:
+        - Customer-facing
+        - Internal
+    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..83cbff67b 100644
--- a/.github/pull_request_template.md
+++ b/.github/pull_request_template.md
@@ -5,3 +5,4 @@ Fix #<gh-issue-id>
 Test URLs:
 - Before: https://main--{repo}--{owner}.hlx.live/
 - After: https://<branch>--{repo}--{owner}.hlx.live/
+
diff --git a/.github/workflows/issue-completeness.yml b/.github/workflows/issue-completeness.yml
new file mode 100644
index 000000000..f35e63e2f
--- /dev/null
+++ b/.github/workflows/issue-completeness.yml
@@ -0,0 +1,99 @@
+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('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**');
+            }
+            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/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..37c021b75
--- /dev/null
+++ b/.github/workflows/stale.yml
@@ -0,0 +1,128 @@
+name: Close stale issues and PRs
+
+# 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 -> 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:
+    - cron: '30 1 * * *' # daily at 01:30 UTC
+  workflow_dispatch: {}
+
+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:
+      - name: Mark stale, re-engage, and close
+        uses: actions/stale@v9
+        with:
+          ascending: true
+          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: >
+            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 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: >
+            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 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 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).`);
+            }
diff --git a/.github/workflows/triage-assign.yml b/.github/workflows/triage-assign.yml
new file mode 100644
index 000000000..b107e5bb8
--- /dev/null
+++ b/.github/workflows/triage-assign.yml
@@ -0,0 +1,59 @@
+name: Issue Triage
+
+# 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.
+
+on:
+  issues:
+    types: [opened, edited]
+
+permissions:
+  issues: write
+
+jobs:
+  triage:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Apply scope label
+        uses: actions/github-script@v7
+        with:
+          script: |
+            const SCOPE_SLUG = {
+              'Editor / Canvas':      'editor',
+              'Blocks / Rendering':   'blocks',
+              '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 scope = readField('Scope / Area');
+            if (!scope || !SCOPE_SLUG[scope]) {
+              core.info('No mappable scope found: ' + (scope || '(none)'));
+              return;
+            }
+
+            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 c62879cec..73ca65ebb 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -75,3 +75,34 @@ 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:
+
+- **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
+
+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.
+
+## 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 |
+
+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.
+