chore: prepare the 1.1.0 release (#83)

Promotes [Unreleased] to [1.1.0], adds a pull request template stating the
Conventional Commit title requirement, and records in CLAUDE.md what an
unreleasable release-please run looks like in the log.

Release-As: 1.1.0

.github/pull_request_template.md

@@ -0,0 +1,21 @@
+<!--
+The PR title becomes the commit subject when this is squash-merged, and that
+subject is what drives the next release. Please make it a Conventional Commit:
+
+  feat: ...      new capability          -> minor version bump
+  fix: ...       bug fix                 -> patch
+  perf: / docs: / deps: ...              -> patch, listed in the release notes
+  chore: / ci: / test: / refactor: ...   -> not listed in the release notes
+  feat!: ...     or a BREAKING CHANGE:   -> major
+
+A title with no prefix contributes nothing to the next version, so the change
+can end up shipping unannounced. Scopes are welcome: fix(kernel): ...
+
+Nothing else in this template is required - delete what does not apply.
+-->
+
+## What this changes
+
+## Why
+
+## How it was verified

CHANGELOG.md

@@ -5,7 +5,7 @@ All notable changes to the MCP Server for WinDbg Crash Analysis project will be
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
-## [Unreleased]
+## [1.1.0] - 2026-08-22
 
 ### Changed
 

CLAUDE.md

@@ -120,6 +120,19 @@ A title with no recognized prefix contributes nothing. If everything since the l
 hidden-only (`chore`, `ci`, `test`, ...), release-please opens no release PR at all - by design,
 not a failure. `Release-As: X.Y.Z` in a commit body forces an exact version.
 
+**When no release PR appears and you expected one**, read the `release-please` job log. It says
+which commits it could use:
+
+```
+commit could not be parsed: 30c7dd9 Fix kernel go/break-in handling, add wait_for_break (#80)
+Considering: 1 commits
+No user facing commits found since c7ae1a6 - skipping
+```
+
+`could not be parsed` means the subject was not a Conventional Commit, so it counted for nothing.
+`No user facing commits found` means everything that did parse was a hidden type. Neither is an
+error; both mean there is nothing to release yet.
+
 **The flow.** Every push to `main` runs `release-please.yml`, which opens or rewrites a
 `chore(main): release X.Y.Z` PR carrying the version bumps. Before merging it, **add the
 `CHANGELOG.md` entry to that PR**: rename `## [Unreleased]` to `## [X.Y.Z] - YYYY-MM-DD` to match