chore(main): release 0.5.2

[eoleedi]

🤖 I have created a release beep boop

0.5.2 (2026-07-06)

Documentation

• update the example to match the new behavior (057f190)

---

This PR was generated with Release Please. See documentation.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e8f5221190

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Update uv.lock with the release version

After bumping [project].version to 0.5.2, the tracked uv.lock still records the local syllabify package as version = "0.5.1" at uv.lock:211-214. Because this repo enables the uv-lock pre-commit hook in .pre-commit-config.yaml:10-13, a release checkout that runs the standard hooks or an up-to-date lock check will rewrite/fail on the lockfile instead of staying clean; please regenerate and commit uv.lock with this version bump.

Useful? React with 👍 / 👎.