chore(release): prepare 0.11.0 beta

[benvinegar]

Summary

• Bump hunkdiff to 0.11.0-beta.0.
• Move current Unreleased changelog entries into the 0.11.0-beta.0 release section and add missing user-visible fixes.
• Refresh the README note for hunk skill path now that 0.10.0 is already released.

Validation

• bun run ./scripts/check-release-version.ts v0.11.0-beta.0
• bun run format:check
• bun run typecheck
• bun test src/core/cli.test.ts src/core/loaders.gitLog.test.ts src/ui/AppHost.responsive.test.tsx src/ui/AppHost.interactions.test.tsx src/ui/lib/ui-lib.test.ts

This PR description was generated by Pi using OpenAI GPT-5.1 Codex

[greptile-apps]

Greptile Summary

This is a standard release-preparation PR that bumps the package version to 0.11.0, promotes the current Unreleased changelog entries into the [0.11.0] block, and refreshes a stale README note about hunk skill path.

• package.json: Version field changed from 0.10.0 to 0.11.0.
• CHANGELOG.md: Unreleased entries moved into a new [0.11.0] - 2026-05-09 section (with two additional Fixed entries), Unreleased reset to empty placeholders, and comparison links updated.
• README.md: The hunk skill path NOTE updated from future-tense to present-tense now that 0.10.0 is shipped.

Confidence Score: 4/5

Safe to merge — all three files contain straightforward, low-risk release-bookkeeping changes.

The version bump, changelog restructuring, and README refresh are all consistent with each other. The only issue is an empty ### Changed section inside the [0.11.0] release block, which is inconsistent with how other released versions are formatted but has no functional impact.

CHANGELOG.md — the empty ### Changed section in the [0.11.0] block is worth cleaning up before tagging.

Important Files Changed

Filename	Overview
CHANGELOG.md	Moves Unreleased entries into [0.11.0] block and resets Unreleased placeholders; adds two new Fixed entries. Has an empty ### Changed section in the released block inconsistent with other release entries.
README.md	Updates the hunk skill path NOTE from future-tense to present-tense reflecting that 0.10.0 is already released.
package.json	Version bumped from 0.10.0 to 0.11.0, consistent with CHANGELOG and PR intent.

Prompt To Fix All With AI

Fix the following 1 code review issue. Work through them one at a time, proposing concise fixes.

---

### Issue 1 of 1
CHANGELOG.md:20-21
**Empty `### Changed` section in released version**

The `[0.11.0]` block contains an empty `### Changed` header with no entries. Past released versions (e.g. `[0.10.0]`) only include `### Changed` when there are actual entries. An empty section in a published release may confuse readers and is inconsistent with the pattern elsewhere in this file — consider removing it before tagging.

_{Reviews (1): Last reviewed commit: "chore(release): prepare 0.11.0" | Re-trigger Greptile}

[greptile-apps]

Empty ### Changed section in released version

The [0.11.0] block contains an empty ### Changed header with no entries. Past released versions (e.g. [0.10.0]) only include ### Changed when there are actual entries. An empty section in a published release may confuse readers and is inconsistent with the pattern elsewhere in this file — consider removing it before tagging.

Prompt To Fix With AI

This is a comment left during a code review.
Path: CHANGELOG.md
Line: 20-21

Comment:
**Empty `### Changed` section in released version**

The `[0.11.0]` block contains an empty `### Changed` header with no entries. Past released versions (e.g. `[0.10.0]`) only include `### Changed` when there are actual entries. An empty section in a published release may confuse readers and is inconsistent with the pattern elsewhere in this file — consider removing it before tagging.

How can I resolve this? If you propose a fix, please make it concise.