release: v0.1.1 — 9lives.run footer in published package

[Desperado]

Bumps pyproject.toml to 0.1.1 so the PyPI package ships the corrected PR-comment footer (curl -sL 9lives.run | sh) that landed in #1. No functional changes — version bump only. Tagging v0.1.1 after merge fires the PyPI republish; v1 will be moved to match.

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[sigilix]

Sigilix Overview

Effort: 1/5 (trivial)

Quality gates

• ⚠️ PR title follows convention — Title doesn't match repo convention: ^(?:feat|fix|chore|docs|refactor|test|perf|style|build|ci|revert)(?:\([^)]+\))?!?: .+
• ✅ PR description is complete
• ℹ️ PR is linked to an issue — No Closes #N / Closes SIG-N keyword found in PR body or commit messages.

Summary — latest push

Bumps the package version from 0.1.0 to 0.1.1 in pyproject.toml to trigger a PyPI republish that includes the corrected 9lives.run footer from PR #1. This is a mechanical release version bump with no functional code changes.

Important files

File	Score	Notes	Next step
pyproject.toml	1/5	Updates the project version string from 0.1.0 to 0.1.1 to cut a new release containing the footer fix.	Verify the CI pipeline correctly tags v0.1.1 and moves the v1 tag upon merge.

Confidence: 5/5

Mechanical version bump in a single metadata file with no behavior or logic changes.

• Confirm the post-merge tagging workflow will create v0.1.1 and update the v1 Git tag as stated in the PR description.

---

_{Posted · 1bc0b18 · 0 findings — View review
Dismiss @sigilix dismiss <reason> (not-a-bug | bad-anchor | already-covered | too-minor | wrong-context) · Re-run /sigilix review}