chore: prepare release v0.3.0

.github/instructions/changelog.instructions.md

@@ -0,0 +1,9 @@
+---
+applyTo: "CHANGELOG.md"
+description: "Changelog conventions. Read when adding, editing, or reviewing release entries in CHANGELOG.md."
+---
+
+# Changelog instructions
+
+Follow the [README changelog guidance](../../README.md#changelog) when adding,
+editing, or reviewing changelog entries.

CHANGELOG.md

@@ -7,6 +7,32 @@ All notable changes to `azldev` are documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [0.3.0] - 2026-08-10
+
+### Added
+
+- **Agent skills and docs integration.** Add agent skill rendering core, add
+  component/build/runtime skills, and expose skills through the docs agent.
+  ([#287](https://github.com/microsoft/azure-linux-dev-tools/pull/287),
+  [#295](https://github.com/microsoft/azure-linux-dev-tools/pull/295),
+  [#305](https://github.com/microsoft/azure-linux-dev-tools/pull/305))
+- **Archive overlay pipeline support.** Wire archive overlays into prep-sources
+  with post-overlay hash tracking.
+  ([#276](https://github.com/microsoft/azure-linux-dev-tools/pull/276))
+- **Local image test execution.** Run LISA test suites locally via `azldev
+  image test`.
+  ([#292](https://github.com/microsoft/azure-linux-dev-tools/pull/292))
+- **RPM provenance macros.** Add opt-in `%fedora_upstream_*` provenance
+  macros. ([#290](https://github.com/microsoft/azure-linux-dev-tools/pull/290))
+
+### Fixed
+
+- **Dry-run defaults extraction.** Extract embedded defaults during dry runs.
+  ([#278](https://github.com/microsoft/azure-linux-dev-tools/pull/278))
+- **Deterministic archive directory copy.** Ensure archive dir is copied
+  deterministically.
+  ([#301](https://github.com/microsoft/azure-linux-dev-tools/pull/301))
+
 ## [0.2.0] - 2026-07-15
 
 ### Added

README.md

@@ -72,6 +72,14 @@ For development setup and workflow, please consult our [Developer Guide](./docs/
 
 Notable changes for each release are recorded in the [changelog](./CHANGELOG.md).
 
+When preparing a release:
+
+* Match the wording and formatting of existing entries, including inline code
+  for commands and identifiers.
+* End each new entry with links to its pull requests, such as
+  [#123](https://github.com/microsoft/azure-linux-dev-tools/pull/123).
+* Leave entries for earlier releases unchanged.
+
 ## Getting Help
 
 Have questions, found a bug, or need a new feature? Open an issue in our [GitHub repository](https://github.com/microsoft/azure-linux-dev-tools/issues/new/choose). For guidance on how to file an issue, see [how to report issues](https://aka.ms/azurelinux-reportissues).