air: dedicated nextchanges section

.agents/rules/changelog.md

@@ -5,4 +5,4 @@ globs:
   - ".nextchanges/**"
 ---
 
-**RULE: Do not add new release entries to `CHANGELOG.md`.** For a user-visible change, add a fragment file under `.nextchanges/<section>/` (sections: `notable-changes`, `cli`, `bundles`, `dependency-updates`, `api-changes`). Each PR adds its own file, so entries never conflict. `CHANGELOG.md` is generated automatically from these fragments by the release process — never hand-edit it. See `.nextchanges/README.md`.
+**RULE: Do not add new release entries to `CHANGELOG.md`.** For a user-visible change, add a fragment file under `.nextchanges/<section>/` (sections: `notable-changes`, `cli`, `air`, `bundles`, `dependency-updates`, `api-changes`). Each PR adds its own file, so entries never conflict. `CHANGELOG.md` is generated automatically from these fragments by the release process — never hand-edit it. See `.nextchanges/README.md`.

.agents/skills/pr-checklist/SKILL.md

@@ -59,6 +59,7 @@ Add a changelog fragment under `.nextchanges/` when your change is user-visible.
 
 **When to add an entry:**
 - New or changed CLI command, flag, or subcommand behavior
+- User-visible change to a `databricks air` command, including preview commands (put it under `air`)
 - New or changed bundle config field, schema, or engine behavior
 - New direct dependency (annotate under `Dependency updates`)
 - Bug fix that users will notice
@@ -69,7 +70,7 @@ Add a changelog fragment under `.nextchanges/` when your change is user-visible.
 - Auto-generated output changes without a corresponding user-facing change
 
 **How to add:**
-- Create `.nextchanges/<section>/<name>.md`, picking the section folder that fits: `cli`, `bundles`, `dependency-updates`, `notable-changes`, or `api-changes`. `<name>` is arbitrary (a feature name or your PR number) — just keep it unique.
+- Create `.nextchanges/<section>/<name>.md`, picking the section folder that fits: `cli`, `air`, `bundles`, `dependency-updates`, `notable-changes`, or `api-changes`. `<name>` is arbitrary (a feature name or your PR number) — just keep it unique.
 - Write a single line in user-facing language, no Jira links: start it with a `* ` bullet marker and end it with a period.
 - **Voice and tense: imperative mood, active voice.** Lead with a verb that names the change — `Add`, `Fix`, `Bump`, `Remove`, `Deprecate`, `Support`, `Reject`, `Warn` — and describe the user-facing effect, not the implementation. Never use past tense (`Added`/`Fixed`) or first person (`we`/`I`/`our`). When a change reads better as a resulting behavior than as a verb, lead with the affected command, flag, or field in the present tense with "now".
   - GOOD: Add support for the `cluster_policies` resource type.

.codegen.json

@@ -11,6 +11,7 @@
     "nextchanges_sections": {
         "notable-changes": "Notable Changes",
         "cli": "CLI",
+        "air": "AI Runtime",
         "bundles": "Bundles",
         "dependency-updates": "Dependency Updates",
         "api-changes": "API Changes"

.github/CODEOWNERS

@@ -77,6 +77,7 @@
 # AI Runtime
 /cmd/air/                               @databricks/eng-deco-cli @databricks/eng-ai-custom-training
 /acceptance/air/                        @databricks/eng-deco-cli @databricks/eng-ai-custom-training
+/.nextchanges/air/                      @databricks/eng-deco-cli @databricks/eng-ai-custom-training
 
 # CLI compatibility manifest
 /internal/build/cli-compat.json         @databricks/eng-deco-cli @databricks/eng-apps-devex @databricks/eng-deco-platform

.nextchanges/README.md

@@ -42,8 +42,9 @@ type the path (e.g. `.nextchanges/cli/quickstart.md`), write the entry, commit.
 | --- | --- |
 | `.nextchanges/notable-changes/` | Notable Changes (prominent, called out at the top) |
 | `.nextchanges/cli/` | CLI |
+| `.nextchanges/air/` | AI Runtime |
 | `.nextchanges/bundles/` | Bundles |
-| `.nextchanges/dependency-updates/` | Dependency updates |
+| `.nextchanges/dependency-updates/` | Dependency Updates |
 | `.nextchanges/api-changes/` | API Changes |
 
 See [`.agents/skills/pr-checklist/SKILL.md`](../.agents/skills/pr-checklist/SKILL.md)

.nextchanges/air/README.md

@@ -0,0 +1,6 @@
+# AI Runtime
+
+Fragments here render under **AI Runtime** in the released changelog. Add a
+<name>.md file describing your change.
+
+See [`../README.md`](../README.md) for how fragments are written and released.