DEV-1235: uv support

[AivanF]

Summary by CodeRabbit

• Documentation

  • Quick Start rewritten to use a one-command uvx launch (SQLite defaults)
  • Added a recommended "With uv" installation flow and a standalone tool install option; pip-based instructions retained and re-ordered

• Chores

  • Migrated packaging metadata to the newer project format and bumped the package version
  • Made minimum Python requirement explicit (>=3.11)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 99b268df-1b07-4ab6-aec6-1939ba7da993

📥 Commits

Reviewing files that changed from the base of the PR and between 7c2773e and a5a026b.

📒 Files selected for processing (3)

• README.md
• docs/getting-started.md
• pyproject.toml

✅ Files skipped from review due to trivial changes (1)

• docs/getting-started.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md

---

📝 Walkthrough

Walkthrough

Installation docs now recommend running via uvx/uv tool (default SQLite supported) with examples; pip-based install examples retained and reordered. Packaging metadata in pyproject.toml migrated from Poetry's [tool.poetry] to PEP 621 [project], version set to 0.2.0 and console script declared under [project.scripts].

Changes

Cohort / File(s)	Summary
Documentation README.md, docs/getting-started.md	Added a “With uv (recommended)” installation flow (uvx --from motley-slayer ..., uv tool install 'motley-slayer[...]') and reordered/slimmed pip instructions; noted SQLite works out of the box and included standalone tool variant.
Packaging / Build Config pyproject.toml	Migrated metadata from [tool.poetry] to PEP 621 [project]: bumped version to 0.2.0, set requires-python = ">=3.11", structured authors, moved slayer = "slayer.cli:main" into [project.scripts], and relaxed poetry-core build requirement.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~20 minutes

Poem

🐰 I hopped through docs with a cheerful grin,
Nudged uvx to start the server spin,
PEP 621 polished my tiny hat,
SQLite nods, and off I scat,
Tiny changes, big-hearted vim ✨

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title 'uv support' clearly and concisely describes the main change—adding uv tool integration across documentation and project configuration.
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.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch aivan/dev-1235-distribution-standalone-install-via-uv

---

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

[coderabbitai]

Actionable comments posted: 3

🤖 Prompt for all review comments with AI agents

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

Inline comments:
In `@docs/getting-started.md`:
- Around line 7-13: The docs use the wrong uvx invocation ("uvx motley-slayer
serve ...") — replace those lines to call the installed console script name and
add the --from flag to point to the package, e.g. use "uvx --from motley-slayer
slayer serve --models-dir ./slayer_data" (and similarly for the postgres
variant) so the uvx command runs the "slayer" executable from the
"motley-slayer" package.

In `@pyproject.toml`:
- Around line 60-64: Remove the duplicate console script declaration by deleting
the redundant [tool.poetry.scripts] entry that defines slayer =
"slayer.cli:main"; keep only the canonical [project.scripts] section with slayer
= "slayer.cli:main" so the entry point (slayer -> slayer.cli:main) is declared
once. Ensure no other duplicate script entries remain and run your packaging
tool to verify the single entry point is used.

In `@README.md`:
- Around line 49-50: Update the example command so uvx runs the package's entry
point: replace the incorrect "uvx motley-slayer serve --models-dir ./my_models"
with a command that uses the --from flag to load the motley-slayer package and
invoke its slayer entry point, e.g. "uvx --from motley-slayer slayer serve
--models-dir ./my_models"; ensure the README example references uvx, --from,
motley-slayer, and slayer exactly as shown.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 5998125b-04cf-44f4-8b3e-1abece37d371

📥 Commits

Reviewing files that changed from the base of the PR and between ab813ed and 574593e.

⛔ Files ignored due to path filters (1)

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

📒 Files selected for processing (3)

• README.md
• docs/getting-started.md
• pyproject.toml

[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 `@pyproject.toml`:
- Around line 60-61: Update build-system.requires to pin poetry-core to a
minimum version that supports [project.scripts]; change the
build-system.requires entry (currently "poetry-core") to "poetry-core>=2.0.0" so
the CLI entry point under [project.scripts] (slayer = "slayer.cli:main") is
supported across environments.

🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

• Push a commit to this branch (recommended)
• Create a new PR with the fixes

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 044cd4a3-72a4-4644-80c9-2060616e0681

📥 Commits

Reviewing files that changed from the base of the PR and between 574593e and 7c2773e.

📒 Files selected for processing (3)

• README.md
• docs/getting-started.md
• pyproject.toml

✅ Files skipped from review due to trivial changes (1)

• docs/getting-started.md

🚧 Files skipped from review as they are similar to previous changes (1)

• README.md