Merge branch 'main' into fix/bb-file-bucket-removal-policy

Author: soberm

.changeset/bench-report-redesign.md

@@ -0,0 +1,21 @@
+---
+---
+
+feat(bench): redesign agent-bench PR-vs-`main` report + fix baseline selection
+
+Internal CI tooling — no published-package changes.
+
+- The report is now two tables built from the same rows: a colors-only
+  **Overview** (🟢/🟡/🔴 per metric) and a numbers **Detailed results**
+  (`baseline -> pr`, with a multi-line per-dimension judge cell + stop reason),
+  preceded by a collapsible glossary and followed by a short executive summary
+  (paragraph + bullets), a **Potential issues** section, and a collapsed
+  per-cell analysis. Dropped the old build/verdict/composite columns and the raw
+  per-dimension blurb.
+- New per-metric coloring vs the `main` baseline with a single tunable
+  `MARGIN_PCT` (±5%), and a new **SCORE = composite ÷ cost** (composite points
+  per dollar) priced from builder tokens at Bedrock Opus 4.8 rates
+  (`PRICING`/`cellCost`/`scorePerDollar` in `scoring.mjs`).
+- Baseline-selection fix: a PR now always diffs against `latest-main.json` (the
+  current `main` tip), never the PR's stale recorded `base.sha`; a push to `main`
+  diffs against the preceding main commit (`github.event.before`) by exact sha.

.changeset/bench-throttling-build-once.md

@@ -0,0 +1,8 @@
+---
+---
+
+fix: agent-bench throttling resilience (max-parallel=5 + within-wave startup stagger + throttle-retry with a unit-tested retry classifier) and build the monorepo/dist-registry once per run
+
+Internal CI tooling only — changes are confined to the private, unpublished `@aws-blocks/agent-bench` workspace and the bench GitHub Actions workflow. No published-package (`packages/*`) changes, so this needs no release (empty changeset).
+
+Follow-up review hardening (same PR): the pure retry classifier now lives in `steps/lib/bedrock-retry.mjs` with a table-driven `node --test` suite (`bedrock-retry.test.mjs`); the dist-registry reuse guard requires an actual packed `*.tgz` (not just the dir) so a continue-on-error download that leaves an empty dir falls back to a local build; and the startup stagger keys off the within-wave slot (`index % max-parallel`) so the second wave no longer sleeps 35–63s.

.changeset/dsql-index-sort-order.md

@@ -1,6 +1,7 @@
+# Labels are applied by the issue-triage-opened workflow, not this template.
+# Adding a labels: field here would race with that workflow on the 'opened' event.
 name: Bug Report
 description: Create a report to help us improve AWS Blocks
-labels: ["bug", "pending-triage"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/bug-report.yaml

@@ -1,6 +1,7 @@
+# Labels are applied by the issue-triage-opened workflow, not this template.
+# Adding a labels: field here would race with that workflow on the 'opened' event.
 name: Feature Request
 description: Suggest an idea to help us improve AWS Blocks
-labels: ["feature-request", "pending-triage"]
 body:
   - type: markdown
     attributes:

.github/ISSUE_TEMPLATE/feature-request.yaml

@@ -0,0 +1,26 @@
+name: Close stale questions (pending-community-response)
+on:
+  schedule:
+    - cron: '30 2 * * *'
+  workflow_dispatch: {}
+
+permissions:
+  issues: write
+
+jobs:
+  cleanup:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/stale@5bef64f19d7facfb25b37b414482c7164d639639 # v9.1.0
+        with:
+          only-issue-labels: pending-community-response,question
+          stale-issue-label: pending-community-response
+          days-before-issue-stale: -1
+          days-before-issue-close: 14
+          close-issue-message: >
+            This issue has been automatically closed due to a lack of recent activity.
+            Please feel free to reopen it if you have any further questions or information.
+          days-before-pr-stale: -1
+          days-before-pr-close: -1
+          remove-issue-stale-when-updated: false
+          operations-per-run: 100

.github/workflows/agent-bench.yml

@@ -0,0 +1,23 @@
+name: Issue Triage - Closed
+on:
+  issues:
+    types: [closed]
+
+concurrency:
+  group: issue-triage-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
+permissions:
+  issues: write
+
+jobs:
+  cleanup-labels:
+    if: ${{ contains(github.event.issue.labels.*.name, 'pending-community-response') || contains(github.event.issue.labels.*.name, 'pending-maintainer-response') || contains(github.event.issue.labels.*.name, 'pending-triage') }}
+    runs-on: ubuntu-latest
+    env:
+      ISSUE_NUMBER: ${{ github.event.issue.number }}
+      REPOSITORY_NAME: ${{ github.repository }}
+      GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    steps:
+      - name: Remove all pending-* labels
+        run: gh issue edit "$ISSUE_NUMBER" --repo "$REPOSITORY_NAME" --remove-label "pending-community-response" --remove-label "pending-maintainer-response" --remove-label "pending-triage"

.github/workflows/close-stale-issues.yml

@@ -0,0 +1,29 @@
+name: Issue Triage - Comment
+on:
+  issue_comment:
+    types: [created]
+
+concurrency:
+  group: issue-triage-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
+permissions:
+  issues: write
+
+jobs:
+  update-response-labels:
+    runs-on: ubuntu-latest
+    env:
+      ISSUE_NUMBER: ${{ github.event.issue.number }}
+      REPOSITORY_NAME: ${{ github.repository }}
+      GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    steps:
+      - name: Swap to pending-maintainer-response when a community member comments on an open issue
+        if: ${{ !contains(fromJSON('["MEMBER", "OWNER", "COLLABORATOR"]'), github.event.comment.author_association) && github.event.issue.state == 'open' && !github.event.issue.pull_request }}
+        run: gh issue edit "$ISSUE_NUMBER" --repo "$REPOSITORY_NAME" --remove-label "pending-community-response" --add-label "pending-maintainer-response"
+      - name: Move to awaiting-community when a maintainer comments on an open issue
+        if: ${{ contains(fromJSON('["MEMBER", "OWNER", "COLLABORATOR"]'), github.event.comment.author_association) && github.event.issue.state == 'open' && !github.event.issue.pull_request && !contains(github.event.issue.labels.*.name, 'pending-triage') }}
+        run: gh issue edit "$ISSUE_NUMBER" --repo "$REPOSITORY_NAME" --remove-label "pending-maintainer-response" --add-label "pending-community-response"
+      - name: Remove pending-maintainer-response when a maintainer comments on a closed issue
+        if: ${{ contains(fromJSON('["MEMBER", "OWNER", "COLLABORATOR"]'), github.event.comment.author_association) && github.event.issue.state != 'open' && !github.event.issue.pull_request }}
+        run: gh issue edit "$ISSUE_NUMBER" --repo "$REPOSITORY_NAME" --remove-label "pending-maintainer-response"

.github/workflows/issue-triage-closed.yml

@@ -0,0 +1,23 @@
+name: Issue Triage - Labeled
+on:
+  issues:
+    types: [labeled]
+
+concurrency:
+  group: issue-triage-${{ github.event.issue.number }}
+  cancel-in-progress: false
+
+permissions:
+  issues: write
+
+jobs:
+  remove-pending-triage-label:
+    if: ${{ contains(fromJSON('["question", "bug", "feature-request", "enhancement"]'), github.event.label.name) }}
+    runs-on: ubuntu-latest
+    env:
+      ISSUE_NUMBER: ${{ github.event.issue.number }}
+      REPOSITORY_NAME: ${{ github.repository }}
+      GH_TOKEN: ${{ secrets.GITHUB_TOKEN }}
+    steps:
+      - name: Remove the pending-triage label
+        run: gh issue edit "$ISSUE_NUMBER" --repo "$REPOSITORY_NAME" --remove-label "pending-triage"