Merge branch 'main' into paul/spec-yaml-gpu

Author: coignetp

.adms/bazel/adms.mirror.cfg

@@ -9,6 +9,9 @@ allow depot-read-api-bzl.us1.ddbuild.io
 allow depot-read-api-cli.us1.ddbuild.io
 allow depot-read-api-generic.us1.ddbuild.io
 allow depot-read-api-go.us1.ddbuild.io
+# Preferred first in GOPROXY (see .adms/go/gitlab.yaml); allow it here so Bazel's
+# downloader doesn't block it.
+allow depot-read-api-go.rapid-dependency-management-depot.all-clusters.local-dc.fabric.dog
 allow depot-read-api-java.us1.ddbuild.io
 allow depot-read-api-python.us1.ddbuild.io
 allow mass-read.us1.ddbuild.io
@@ -74,6 +77,7 @@ rewrite (github.com)/(.*) depot-read-api-bzl.us1.ddbuild.io/$1/$2
 rewrite (raw.githubusercontent.com)/(.*) depot-read-api-bzl.us1.ddbuild.io/$1/$2
 rewrite (cdn.jsdelivr.net)/(.*) depot-read-api-bzl.us1.ddbuild.io/$1/$2
 rewrite (dl.google.com)/(.*) depot-read-api-bzl.us1.ddbuild.io/$1/$2
+rewrite (agent-int-packages.datadoghq.com)/(.*) depot-read-api-bzl.us1.ddbuild.io/$1/$2
 
 # Taken from https://blog.aspect.build/configuring-bazels-downloader
 # > For some reason the bazel team decided that mirror.bazel.build should be the source of truth for these 3 files, let

.adms/go/gitlab.yaml

@@ -1,6 +1,6 @@
 # DO NOT EDIT
 
 variables:
-    GOPROXY: "https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/"
+    GOPROXY: "https://depot-read-api-go.rapid-dependency-management-depot.all-clusters.local-dc.fabric.dog:8443/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/magicmirror/@current/|https://depot-read-api-go.us1.ddbuild.io/magicmirror/testing/@current/|direct"
     GONOSUMDB: "github.com/DataDog,go.ddbuild.io"
     GOPRIVATE: ""

.agents/README.md

@@ -0,0 +1,26 @@
+# AI agent assets
+
+This `/.agents/` directory stores configuration and other assets that are meant to be shared amongst all agent harnesses like Claude, Codex, Pi, etc.
+
+## Skills
+
+Agent skills are stored in the `skills/` subdirectory. Claude does not [yet](https://github.com/anthropics/claude-code/issues/6235) support this [convention](https://agentskills.io/client-implementation/adding-skills-support#where-to-scan), so we symlink `/.claude/skills/` to that directory.
+
+## MCP config
+
+The MCP servers are declared in `/agents.toml`, and will be moved to this directory when our tooling supports it.
+
+### Synchronizing
+
+Config is written into each tool's own config file by [dotagents](https://github.com/getsentry/dotagents), run through [mise](https://mise.en.dev). After changing a declaration, run:
+
+```
+mise run dotagents install   # or `mise run dotagents sync` to reconcile/repair offline
+```
+
+dotagents writes to every tool listed in the `agents` key of `agents.toml`, repairing the servers it declares while preserving undeclared servers and unrelated content in each file.
+
+### Maintained by hand
+
+- **Zed** (`/.zed/settings.json`) - not yet a dotagents target.
+- **`dd-slack`** - Slack has no dynamic client registration, so each client needs its own pre-registered Slack app bound to a fixed redirect URI. We configure this for Claude and Cursor because that's all Slack publishes at the time of writing. Registering our own Slack app with dynamic client registration will likely be required for broader support.

.agents/skills/agent-supply-chain-newsletter/SKILL.md

@@ -0,0 +1,108 @@
+---
+name: agent-supply-chain-newsletter
+description: Generate the Agent Supply Chain newsletter by researching team activity on GitHub and Confluence, then creating a Confluence draft and Gmail draft
+argument-hint: "<period e.g. 'February-March 2026'>"
+model: sonnet
+---
+
+Generate the Agent Supply Chain newsletter for the period **$ARGUMENTS** by researching what team members accomplished on GitHub and Confluence, then producing both a Confluence blog post draft and a Gmail draft.
+
+## Step 1: Gather team members
+
+Fetch the current list of agent-supply-chain team members from GitHub:
+
+```bash
+gh api orgs/DataDog/teams/agent-supply-chain/members --paginate --jq '.[].login'
+```
+
+Ask the user if any members should be excluded (e.g. people who moved teams).
+
+## Step 2: Read past newsletters for format reference
+
+1. Search for the latest blog posts in the ASC1 Confluence space:
+   - `mcp__claude_ai_Atlassian__searchConfluenceUsingCql` with `cql`: `type = "blogpost" AND space = "ASC1" ORDER BY created DESC` (limit 3)
+2. Read the most recent newsletter with `mcp__claude_ai_Atlassian__getConfluencePage` (contentFormat: `markdown`, contentType: `blog`) to match its structure and tone.
+
+The newsletter format is:
+- **Header**: greeting, team links (ASC1, ABLD, BARX, ADX spaces), OKR link, support channel link
+- **"What's new?"** section organized by sub-team (Agent Developer Experience, Agent Build, Agent Delivery)
+- Each item has: a short title, **quantified impact** (time saved, percentage improvement, count), and **links to PRs or docs**
+- **"Did you know?"** section with one fun/useful tip
+- **Footer**: link to all newsletters, support channel reminder
+
+## Step 3: Research GitHub activity
+
+For each team member, launch background agents (use `run_in_background: true`) to search merged PRs during the period. Split into batches of ~8 members per agent to parallelize.
+
+Each agent should run, for every user:
+
+```bash
+# PRs in datadog-agent
+gh pr list --repo DataDog/datadog-agent --author USERNAME --state merged --search "merged:START_DATE..END_DATE" --limit 50 --json title,url,mergedAt,labels
+
+# PRs across the DataDog org (catches buildimages, k8s-ops, integrations-core, etc.)
+gh search prs --author USERNAME --owner DataDog --merged --limit 20 --json repository,title,url -- "merged:START_DATE..END_DATE"
+```
+
+Each agent should return a summary per user, grouped thematically (build improvements, CI/CD, new features, bug fixes, etc.). Skip trivial PRs (version bumps, dependency updates). Focus on items that **impact teams outside Agent Supply Chain**.
+
+## Step 4: Research Confluence activity
+
+Launch a background agent to search for relevant documentation created during the period:
+
+```
+mcp__claude_ai_Atlassian__searchConfluenceUsingCql
+```
+
+With CQL queries:
+- `space = "ASC1" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25)
+- `space = "ADX" AND lastModified >= "START_DATE" AND lastModified <= "END_DATE" ORDER BY lastModified DESC` (limit 25)
+
+Identify RFCs, design docs, operational reports, and guides that are newsletter-worthy.
+
+## Step 5: Synthesize and write the newsletter
+
+Apply the newsletter guide's filter: **"Is this information impacting a team outside of the Agent Supply Chain group?"** Only include items where the answer is yes.
+
+For each item:
+- Provide a **quantifiable improvement** (time saved, percentage change, cost reduction) when available
+- Link to the relevant **PR, Confluence page, or documentation**
+- Keep descriptions concise (2-4 sentences max per item)
+
+Group items under:
+1. **Agent Developer Experience** (CI speed, developer tools, workflows, open source)
+2. **Agent Build** (Bazel migration, build system, platform support)
+3. **Agent Delivery** (releases, deployments, registries, security)
+
+End with a **"Did you know?"** section highlighting one interesting tool, feature, or tip.
+
+## Step 6: Create outputs
+
+### 6a. Confluence blog post draft
+
+Use `mcp__claude_ai_Atlassian__createConfluencePage` with:
+- `cloudId`: `datadoghq.atlassian.net`
+- `spaceId`: `4662624793` (ASC1 space)
+- `title`: `<Period> - Agent Supply Chain Monthly Update`
+- `contentType`: `blog`
+- `status`: `draft`
+- `contentFormat`: `markdown`
+
+### 6b. Gmail draft
+
+Use `mcp__claude_ai_Gmail__gmail_create_draft` with:
+- `to`: `agent-community@datadoghq.com`
+- `subject`: `<Period> - Agent Supply Chain Monthly Update`
+- `contentType`: `text/html`
+- Rich HTML body matching the Confluence content
+
+## Step 7: Present results
+
+Return to the user:
+1. Links to both the Confluence draft and Gmail draft
+2. A bullet-point summary of the sections covered
+3. Remind them to:
+   - Review both outputs for accuracy
+   - Send the Gmail to themselves first to verify formatting
+   - Schedule the final send between **2-4pm CET**, not on a Friday
+   - Ask for review in `#agent-devx-private` / from Damien Desmarets before publishing

.agents/skills/allium/SKILL.md

@@ -5,6 +5,7 @@ version: 3
 auto_trigger:
   - file_patterns: ["**/*.allium"]
   - keywords: ["allium", "allium spec", "allium specification", ".allium file"]
+model: sonnet
 ---
 
 # Allium

.agents/skills/allium/skills/distill/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: distill
 description: "Extract an Allium specification from an existing codebase. Use when the user has existing code and wants to distil behaviour into a spec, reverse engineer a specification from implementation, generate a spec from code, turn implementation into a behavioural specification, or document what a codebase does in Allium terms."
+model: sonnet
 ---
 
 # Distillation guide

.agents/skills/allium/skills/elicit/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: elicit
 description: "Run a structured discovery session to build an Allium specification through conversation. Use when the user wants to create a new spec from scratch, elicit or gather requirements, capture domain behaviour, specify a feature or system, define what a system should do, or is describing functionality and needs help shaping it into a specification."
+model: sonnet
 ---
 
 # Elicitation

.agents/skills/allium/skills/propagate/SKILL.md

@@ -1,6 +1,7 @@
 ---
 name: propagate
 description: "Generate tests from Allium specifications. Use when the user wants to propagate tests, generate test files from a spec, write tests for a specification, create property-based tests, produce state machine tests, check test coverage against spec obligations, or understand what tests a specification requires."
+model: sonnet
 ---
 
 # Propagation