chore(main): release 0.1.2

[beaubhp]

🤖 I have created a release beep boop

0.1.2 (2026-06-29)

Bug Fixes

• update CLI help summary (2320008)
• update PyPI package metadata (8417f95)

---

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: 4f055f7d27

ℹ️ 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]

Regenerate Cargo.lock for the released version

This version bump leaves the checked-in lockfile stale: Cargo.lock still records the workspace crates (culler-cli, culler-core, and culler-python) as 0.1.1 while the manifests now resolve them as 0.1.2. Any consumer or CI job that builds this release with Cargo’s --locked mode (confirmed via cargo check --help: it asserts Cargo.lock remains unchanged) will fail because Cargo needs to rewrite those package entries. Please regenerate and commit Cargo.lock with the release bump.

Useful? React with 👍 / 👎.

[beaubhp]

Closing this Release Please PR because it was generated from the temporary release-recovery history after cleanup, not from a new intended 0.1.2 release.