chore(release): 0.18.0

[anderskev]

Summary

• Bump version to 0.18.0
• Update CHANGELOG.md with changes since v0.17.0

Post-merge steps

After merging, run:

/release-tag 0.18.0

---

Generated with Claude Code

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 551315b7-a7cb-47e9-9b0c-71bd7135f3a2

📥 Commits

Reviewing files that changed from the base of the PR and between bd31210 and 1dd0a64.

⛔ Files ignored due to path filters (1)

• uv.lock is excluded by !**/*.lock

📒 Files selected for processing (1)

• CHANGELOG.md

---

Walkthrough

This pull request increments the project to version 0.18.0, updating version constants and package manifest versions. CHANGELOG.md receives a new [0.18.0] release entry dated 2026-03-07 with Added, Changed, Fixed, and Security subsections. The docs/site roadmap is reorganized: phases are renumbered, consolidated, and references adjusted. No public API signatures or exported entities were changed.

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore(release): 0.18.0' clearly and concisely summarizes the main change: a version bump to 0.18.0, which is reflected across all modified files (CHANGELOG.md, init.py, package.json files, pyproject.toml, and roadmap.md).
Description check	✅ Passed	The description directly relates to the changeset, outlining the two main objectives: bumping the version to 0.18.0 and updating CHANGELOG.md with changes since v0.17.0, both of which are evident in the file summaries.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 1

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Inline comments:
In `@CHANGELOG.md`:
- Around line 10-35: The changelog added the "## [0.18.0] - 2026-03-07" release
header but did not update the reference link definitions at the bottom (leaving
[Unreleased] still comparing from v0.16.0 and no [0.18.0] link), breaking
release diff links; update CHANGELOG.md reference footers so [Unreleased]
compares from the new tag (e.g., v0.18.0...HEAD) and add a [0.18.0] comparison
link (e.g., v0.17.0...v0.18.0) matching the release date, and then ensure the
package versions are synced across pyproject.toml, amelia/__init__.py,
dashboard/package.json, and docs/site/package.json to reflect 0.18.0.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: e97898fb-4323-4411-b6b3-4dec6d97228b

📥 Commits

Reviewing files that changed from the base of the PR and between dc50bf8 and 89d18ac.

📒 Files selected for processing (5)

• CHANGELOG.md
• amelia/__init__.py
• dashboard/package.json
• docs/site/package.json
• pyproject.toml