We need to read changelog.md. Let's read file.

The user says: "prepare release notes for latest version from changelog.md"

We have the changelog content. We need to produce release notes for latest version. The changelog shows entries, each with date and changes.

We need to gather the latest version: We see in file content we have multiple entries. The topmost after header is:

## [0.4.14] - 2026-06-28

So latest version is 0.4.14 released on 2026-06-28.

The file includes details: "Added plugin system, etc." We need to prepare release notes summarizing changes.

We should produce a release notes output. Format? Not specified, but typical release notes are like bullet points summarizing changes.

We likely want to produce a brief summary of the new features, bug fixes, and other changes. The user asked "prepare release notes for latest version from changelog.md". So likely we should produce a nicely formatted release notes entry summarizing the changes in that version.

We could output:

• Title: "Release Notes – Version 0.4.14"
• Date
• Summary of added, changed, fixed features.

Let's parse the entry:

## [0.4.14] - 2026-06-28
### Added
- Implemented Tiles plugin system [#171](https://github.com/tilesprivacy/tiles/pull/171).  - `tiles plugin install <url / filesystem-path>`, `tiles plugin uninstall <plugin-name>`, `tiles plugin list` (for installed plugins).    - Plugins should be a `.zip` or `.tar.gz` file either hosted or available in local filesystem.    ```markdown
      ## Plugin folder structure
      plugin_name        - extensions          - extension_1            - ...          - extension_2            - ...        - skills          - skill_1            - SKILLS.md      ```    - Added skills support via plugins      - In repl use `/skills` for list of skills and `$<skill-name>` to use the skill directly. Tiles can use available skills as needed too.

So we have an "Added" bullet for plugin system. Next:

Changed

• Upgraded project dependencies #168, #170.

Thus only two changes: "Upgraded project dependencies".

Thus the release notes should include:

• Added plugin system
• Changed: Upgraded dependencies

Maybe also "Changed" indicates other changes but only dependency updates.

Let's produce release notes accordingly. Possibly we need to include bullet lists of added and changed items.

Will provide in plain text. Use bold or markdown.

Let's output something like:

Release Notes – Version 0.4.14 (2026-06-28)

Features added

• Tiles plugin system: commands for installing/uninstalling/listing plugins.
• Plugins may be .zip/.tar.gz; plugin structure described.
• Skills support via plugins; in REPL use /skills for list and $<skill-name> to invoke skill.

Changes

• Upgraded project dependencies (#168, #170).

Fixed none? No "Fixed" in this entry.

We should mention that it's a new release. Provide summary.

Thus answer: Release notes for latest version: summarizing added and changed features.

Ok.