devready-cli 0.0.2__tar.gz → 0.0.4__tar.gz

{devready_cli-0.0.2 → devready_cli-0.0.4}/.claude-plugin/plugin.json

@@ -1,6 +1,7 @@
 {
   "name": "devready",
-  "version": "0.0.2",
+  "version": "0.0.4",
+  "homepage": "https://devready-ten.vercel.app/",
   "description": "Read-only environment preflight: compares a project's declared Node/Python versions with what is installed.",
   "author": { "name": "DevReady contributors" },
   "license": "MIT"

{devready_cli-0.0.2 → devready_cli-0.0.4}/AGENTS.md

@@ -1,6 +1,6 @@
 # Agent instructions
 
-Before running installs, builds or tests in a project, or when setup errors mention versions or missing tools, run `devready check --format json` (or `uvx --from devready-cli devready check --format json`) and read the result.
+Before running installs, builds or tests in a project, or when setup errors mention versions or missing tools, run `devready check --format json` and read the result. If `devready` is not on PATH, try `python -m devready check --format json`, then `uvx --from devready-cli devready check --format json`; if neither works, tell the user (`pipx install devready-cli`) instead of installing it yourself.
 
 - `fail` means a declared requirement is unmet: tell the user and suggest switching versions; do not work around it.
 - `skip`/`error` mean "not evaluated", not "ok".

{devready_cli-0.0.2 → devready_cli-0.0.4}/CHANGELOG.md

@@ -1,5 +1,13 @@
 # Changelog
 
+## 0.0.4 - 2026-10-16
+- `python -m devready` entry point.
+- Skill, `/devready:doctor` and `AGENTS.md` now fall back to `python -m devready`, `uvx`, then `pipx run`, and tell the user how to install instead of failing.
+- Docs: requirements (`uv` for the plugin MCP server), no-`uv` MCP config and a troubleshooting table.
+
+## 0.0.3 - 2026-10-16
+- Add project website (https://devready-ten.vercel.app/) to package metadata.
+
 ## 0.0.2 - 2026-10-16
 - Docker CLI/daemon check (only when a Dockerfile or compose file exists), `.tool-versions`, `.env.example` vs `.env` key names (values never read), git identity presence, free disk space.
 - `devready explain <check_id>`.

{devready_cli-0.0.2 → devready_cli-0.0.4}/PKG-INFO

@@ -1,8 +1,9 @@
 Metadata-Version: 2.5
 Name: devready-cli
-Version: 0.0.2
+Version: 0.0.4
 Summary: A local-first, read-only CLI that checks a project's environment requirements against what is installed.
-Project-URL: Homepage, https://github.com/Evalogical-Inc/devReady
+Project-URL: Homepage, https://devready-ten.vercel.app/
+Project-URL: Repository, https://github.com/Evalogical-Inc/devReady
 Project-URL: Issues, https://github.com/Evalogical-Inc/devReady/issues
 Author: Evalogical Inc
 License-Expression: MIT
@@ -32,6 +33,7 @@ Built for humans, CI, and AI coding agents (Claude Code, Codex, any MCP client).
 
 [![CI](https://github.com/Evalogical-Inc/devReady/actions/workflows/ci.yml/badge.svg)](https://github.com/Evalogical-Inc/devReady/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/devready-cli)](https://pypi.org/project/devready-cli/)
+[![Website](https://img.shields.io/badge/website-devready--ten.vercel.app-ff6a35)](https://devready-ten.vercel.app/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue)
 ![Dependencies: 0](https://img.shields.io/badge/dependencies-0-brightgreen)
@@ -150,7 +152,7 @@ devready --version
 
 DevReady ships the same engine three ways, so your agent can verify the environment *before* it installs, builds or tests.
 
-**Claude Code** - plugin with a skill, a `/devready:doctor` command and an MCP server:
+**Claude Code** - plugin with a skill, a `/devready:doctor` command and an MCP server (the MCP server needs [`uv`](https://docs.astral.sh/uv/); the rest works without it once `devready-cli` is installed):
 
 ```text
 /plugin marketplace add Evalogical-Inc/devReady

{devready_cli-0.0.2 → devready_cli-0.0.4}/README.md

@@ -9,6 +9,7 @@ Built for humans, CI, and AI coding agents (Claude Code, Codex, any MCP client).
 
 [![CI](https://github.com/Evalogical-Inc/devReady/actions/workflows/ci.yml/badge.svg)](https://github.com/Evalogical-Inc/devReady/actions/workflows/ci.yml)
 [![PyPI](https://img.shields.io/pypi/v/devready-cli)](https://pypi.org/project/devready-cli/)
+[![Website](https://img.shields.io/badge/website-devready--ten.vercel.app-ff6a35)](https://devready-ten.vercel.app/)
 [![License: MIT](https://img.shields.io/badge/license-MIT-green.svg)](LICENSE)
 ![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-blue)
 ![Dependencies: 0](https://img.shields.io/badge/dependencies-0-brightgreen)
@@ -127,7 +128,7 @@ devready --version
 
 DevReady ships the same engine three ways, so your agent can verify the environment *before* it installs, builds or tests.
 
-**Claude Code** - plugin with a skill, a `/devready:doctor` command and an MCP server:
+**Claude Code** - plugin with a skill, a `/devready:doctor` command and an MCP server (the MCP server needs [`uv`](https://docs.astral.sh/uv/); the rest works without it once `devready-cli` is installed):
 
 ```text
 /plugin marketplace add Evalogical-Inc/devReady

devready_cli-0.0.4/commands/doctor.md

@@ -0,0 +1,5 @@
+---
+description: Run DevReady and explain any environment problems
+---
+
+Run `devready check --format json` in the current project. If the command is missing, follow the fallback order in the devready skill (`python -m devready`, then `uvx`, then `pipx run`) and, if none work, tell the user how to install it instead of installing anything yourself. Summarize failures first, then warnings, each with the suggested next step. Do not change anything without asking.

{devready_cli-0.0.2 → devready_cli-0.0.4}/docs/agents.md

@@ -2,6 +2,11 @@
 
 DevReady is a CLI; agents call `devready check --format json` (schema: `schema.json`).
 
+## Requirements
+
+- Python 3.10+ for the CLI itself.
+- For the **plugin's MCP server** and the `uvx` examples below: [`uv`](https://docs.astral.sh/uv/) installed and on PATH. Without it the MCP server reports "Connection closed". The skill and `/devready:doctor` still work without it if `devready` is installed (`pipx install devready-cli` or `pip install devready-cli`).
+
 ## Claude Code
 
 ```text
@@ -23,4 +28,12 @@ command = "uvx"
 args = ["--from", "devready-cli", "devready", "mcp"]
 ```
 
-The CLI must be installed first: `pipx install devready-cli`.
+No `uv`? Install the CLI (`pipx install devready-cli` or `pip install devready-cli`) and use `command = "devready"`, `args = ["mcp"]` instead.
+
+## Troubleshooting
+
+| Symptom | Cause and fix |
+|---|---|
+| MCP server "Connection closed" | `uvx` not found. Install `uv`, or install the CLI and point the MCP config at `devready mcp`. |
+| `devready: command not found` | Not installed, or its scripts folder is not on PATH. Run `python -m devready check` or reinstall with `pipx`. |
+| `python -m devready` fails | The package is not installed for that Python. `pip install devready-cli`. |

{devready_cli-0.0.2 → devready_cli-0.0.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "devready-cli"
-version = "0.0.2"
+version = "0.0.4"
 description = "A local-first, read-only CLI that checks a project's environment requirements against what is installed."
 readme = "README.md"
 requires-python = ">=3.10"
@@ -26,7 +26,8 @@ dependencies = []
 dev = ["pytest>=8", "ruff>=0.6", "jsonschema>=4"]
 
 [project.urls]
-Homepage = "https://github.com/Evalogical-Inc/devReady"
+Homepage = "https://devready-ten.vercel.app/"
+Repository = "https://github.com/Evalogical-Inc/devReady"
 Issues = "https://github.com/Evalogical-Inc/devReady/issues"
 
 [project.scripts]

{devready_cli-0.0.2 → devready_cli-0.0.4}/skills/devready/SKILL.md

@@ -11,7 +11,13 @@ Run from the project root:
 devready check --format json
 ```
 
-If `devready` is not installed, use `uvx --from devready-cli devready check --format json` or `pipx run --spec devready-cli devready check --format json`. Do not install anything without asking the user.
+If `devready` is not found, try these in order and use the first that works:
+
+1. `python -m devready check --format json` (or `python3 -m ...`), if the package is installed for that Python.
+2. `uvx --from devready-cli devready check --format json`, if `uv` is installed.
+3. `pipx run --spec devready-cli devready check --format json`, if `pipx` is installed.
+
+If none work, tell the user and offer `pipx install devready-cli` (or `pip install --user devready-cli`). Do not install anything without asking.
 
 ## Reading the result
 

devready_cli-0.0.4/src/devready/__init__.py

@@ -0,0 +1 @@
+__version__ = "0.0.4"

devready_cli-0.0.4/src/devready/__main__.py

@@ -0,0 +1,5 @@
+import sys
+
+from devready.cli import main
+
+sys.exit(main())

{devready_cli-0.0.2 → devready_cli-0.0.4}/tests/unit/test_cli.py

@@ -23,3 +23,13 @@ def test_bad_usage_exit_code():
 def test_version(capsys):
     assert main(["--version"]) == 0
     assert "devready" in capsys.readouterr().out
+
+
+def test_python_dash_m_entry_point():
+    import subprocess
+    import sys
+
+    p = subprocess.run(
+        [sys.executable, "-m", "devready", "--version"], capture_output=True, text=True
+    )
+    assert p.returncode == 0 and "devready" in p.stdout

devready_cli-0.0.2/commands/doctor.md

@@ -1,5 +0,0 @@
----
-description: Run DevReady and explain any environment problems
----
-
-Run `devready check --format json` in the current project (see the devready skill if the command is missing). Summarize failures first, then warnings, each with the suggested next step. Do not change anything without asking.

devready_cli-0.0.2/src/devready/__init__.py

@@ -1 +0,0 @@
-__version__ = "0.0.2"