duet-cli 0.2.1__tar.gz → 0.2.3__tar.gz

{duet_cli-0.2.1/duet_cli.egg-info → duet_cli-0.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: duet-cli
-Version: 0.2.1
+Version: 0.2.3
 Summary: Two CLI agents in conversation. One Python file. Stdlib only.
 Author: Volkan Altan
 License-Expression: MIT
@@ -47,6 +47,38 @@ a worktree until they converge. Pass any upstream command as the kickoff:
 install that first (see below) and make sure `command -v duet` passes in Claude
 Code's shell. Full guide:
 [docs/CLAUDE_CODE_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CLAUDE_CODE_PLUGIN.md).
+If Claude Code disambiguates plugin commands with namespaces, `/duet:duet` is
+the same command.
+
+Autonomous handoff example:
+
+![Claude Code handoff using duet](./docs/assets/claude-duet-workflow.png?raw=true)
+
+While the handoff runs, Claude Code shows the shell in auto mode and exposes
+the exact `duet` command under shell details:
+
+![Claude Code auto mode shell status](./docs/assets/claude-duet-auto-mode.png?raw=true)
+
+![Claude Code shell details running duet](./docs/assets/claude-duet-shell-details.png?raw=true)
+
+Copy-ready version:
+
+```text
+/loop /goal Create a temporary todo.md from the plan above and the remaining
+tasks in todo_codex.md.
+
+1. Use /duet:duet with max reasoning to confirm the plan.
+2. After the plan is confirmed, implement it.
+3. Once the first implementation is done, use /duet:duet with max reasoning
+   for code review.
+4. Use /duet:duet with max reasoning to review the second plan, then implement
+   it.
+5. When the process is complete and all checks are green, merge the approved
+   changes.
+
+P.S. I will not be around, so handle decisions without me. If you need another
+opinion, use /duet:duet to discuss it with Codex.
+```
 
 ### 2. Inside Codex — `$duet`
 
@@ -64,16 +96,26 @@ Codex's shell. Full guide:
 ### 3. From the terminal — `duet`
 
 ```bash
-pipx install duet-cli        # the command it installs is `duet`
+pipx install duet-cli        # recommended; the command it installs is `duet`
 duet --task "Fix the failing test" --cwd ~/code/myrepo
 ```
 
-The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
-so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
-`--config foo.yaml`. One-shot, no install:
+`pipx` is the recommended install. Two other persistent options put `duet` on
+PATH the same way:
+
+```bash
+uv tool install duet-cli
+python3 -m pip install --user duet-cli
+```
+
+The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library).
+Add the `[yaml]` extra for `--config foo.yaml` support — `pipx install
+'duet-cli[yaml]'`, `uv tool install 'duet-cli[yaml]'`, or `python3 -m pip
+install --user 'duet-cli[yaml]'`. One-shot, no install:
 `uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
 `duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
-(`pipx install duet-cli` or `make install`) instead.
+(`pipx install duet-cli`, `uv tool install duet-cli`,
+`python3 -m pip install --user duet-cli`, or `make install`) instead.
 
 ## Examples
 

{duet_cli-0.2.1 → duet_cli-0.2.3}/README.md

@@ -26,6 +26,38 @@ a worktree until they converge. Pass any upstream command as the kickoff:
 install that first (see below) and make sure `command -v duet` passes in Claude
 Code's shell. Full guide:
 [docs/CLAUDE_CODE_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CLAUDE_CODE_PLUGIN.md).
+If Claude Code disambiguates plugin commands with namespaces, `/duet:duet` is
+the same command.
+
+Autonomous handoff example:
+
+![Claude Code handoff using duet](./docs/assets/claude-duet-workflow.png?raw=true)
+
+While the handoff runs, Claude Code shows the shell in auto mode and exposes
+the exact `duet` command under shell details:
+
+![Claude Code auto mode shell status](./docs/assets/claude-duet-auto-mode.png?raw=true)
+
+![Claude Code shell details running duet](./docs/assets/claude-duet-shell-details.png?raw=true)
+
+Copy-ready version:
+
+```text
+/loop /goal Create a temporary todo.md from the plan above and the remaining
+tasks in todo_codex.md.
+
+1. Use /duet:duet with max reasoning to confirm the plan.
+2. After the plan is confirmed, implement it.
+3. Once the first implementation is done, use /duet:duet with max reasoning
+   for code review.
+4. Use /duet:duet with max reasoning to review the second plan, then implement
+   it.
+5. When the process is complete and all checks are green, merge the approved
+   changes.
+
+P.S. I will not be around, so handle decisions without me. If you need another
+opinion, use /duet:duet to discuss it with Codex.
+```
 
 ### 2. Inside Codex — `$duet`
 
@@ -43,16 +75,26 @@ Codex's shell. Full guide:
 ### 3. From the terminal — `duet`
 
 ```bash
-pipx install duet-cli        # the command it installs is `duet`
+pipx install duet-cli        # recommended; the command it installs is `duet`
 duet --task "Fix the failing test" --cwd ~/code/myrepo
 ```
 
-The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
-so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
-`--config foo.yaml`. One-shot, no install:
+`pipx` is the recommended install. Two other persistent options put `duet` on
+PATH the same way:
+
+```bash
+uv tool install duet-cli
+python3 -m pip install --user duet-cli
+```
+
+The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library).
+Add the `[yaml]` extra for `--config foo.yaml` support — `pipx install
+'duet-cli[yaml]'`, `uv tool install 'duet-cli[yaml]'`, or `python3 -m pip
+install --user 'duet-cli[yaml]'`. One-shot, no install:
 `uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
 `duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
-(`pipx install duet-cli` or `make install`) instead.
+(`pipx install duet-cli`, `uv tool install duet-cli`,
+`python3 -m pip install --user duet-cli`, or `make install`) instead.
 
 ## Examples
 

{duet_cli-0.2.1 → duet_cli-0.2.3/duet_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: duet-cli
-Version: 0.2.1
+Version: 0.2.3
 Summary: Two CLI agents in conversation. One Python file. Stdlib only.
 Author: Volkan Altan
 License-Expression: MIT
@@ -47,6 +47,38 @@ a worktree until they converge. Pass any upstream command as the kickoff:
 install that first (see below) and make sure `command -v duet` passes in Claude
 Code's shell. Full guide:
 [docs/CLAUDE_CODE_PLUGIN.md](https://github.com/volkan/duet/blob/main/docs/CLAUDE_CODE_PLUGIN.md).
+If Claude Code disambiguates plugin commands with namespaces, `/duet:duet` is
+the same command.
+
+Autonomous handoff example:
+
+![Claude Code handoff using duet](./docs/assets/claude-duet-workflow.png?raw=true)
+
+While the handoff runs, Claude Code shows the shell in auto mode and exposes
+the exact `duet` command under shell details:
+
+![Claude Code auto mode shell status](./docs/assets/claude-duet-auto-mode.png?raw=true)
+
+![Claude Code shell details running duet](./docs/assets/claude-duet-shell-details.png?raw=true)
+
+Copy-ready version:
+
+```text
+/loop /goal Create a temporary todo.md from the plan above and the remaining
+tasks in todo_codex.md.
+
+1. Use /duet:duet with max reasoning to confirm the plan.
+2. After the plan is confirmed, implement it.
+3. Once the first implementation is done, use /duet:duet with max reasoning
+   for code review.
+4. Use /duet:duet with max reasoning to review the second plan, then implement
+   it.
+5. When the process is complete and all checks are green, merge the approved
+   changes.
+
+P.S. I will not be around, so handle decisions without me. If you need another
+opinion, use /duet:duet to discuss it with Codex.
+```
 
 ### 2. Inside Codex — `$duet`
 
@@ -64,16 +96,26 @@ Codex's shell. Full guide:
 ### 3. From the terminal — `duet`
 
 ```bash
-pipx install duet-cli        # the command it installs is `duet`
+pipx install duet-cli        # recommended; the command it installs is `duet`
 duet --task "Fix the failing test" --cwd ~/code/myrepo
 ```
 
-The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library),
-so `pipx`/`uvx` isolation is recommended. Add `'duet-cli[yaml]'` if you want
-`--config foo.yaml`. One-shot, no install:
+`pipx` is the recommended install. Two other persistent options put `duet` on
+PATH the same way:
+
+```bash
+uv tool install duet-cli
+python3 -m pip install --user duet-cli
+```
+
+The PyPI package is `duet-cli` (bare `duet` on PyPI is Google's async library).
+Add the `[yaml]` extra for `--config foo.yaml` support — `pipx install
+'duet-cli[yaml]'`, `uv tool install 'duet-cli[yaml]'`, or `python3 -m pip
+install --user 'duet-cli[yaml]'`. One-shot, no install:
 `uvx --from duet-cli duet --task "..."` — note this is ephemeral and does not put
 `duet` on PATH, so the `/duet` and `$duet` plugins need a persistent install
-(`pipx install duet-cli` or `make install`) instead.
+(`pipx install duet-cli`, `uv tool install duet-cli`,
+`python3 -m pip install --user duet-cli`, or `make install`) instead.
 
 ## Examples
 

{duet_cli-0.2.1 → duet_cli-0.2.3}/duet_cli.egg-info/SOURCES.txt

@@ -8,4 +8,5 @@ duet_cli.egg-info/dependency_links.txt
 duet_cli.egg-info/entry_points.txt
 duet_cli.egg-info/requires.txt
 duet_cli.egg-info/top_level.txt
+tests/test_bump_release_version.py
 tests/test_duet.py

{duet_cli-0.2.1 → duet_cli-0.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "duet-cli"
-version = "0.2.1"
+version = "0.2.3"
 description = "Two CLI agents in conversation. One Python file. Stdlib only."
 readme = "README.md"
 requires-python = ">=3.9"

duet_cli-0.2.3/tests/test_bump_release_version.py

@@ -0,0 +1,106 @@
+"""Unit tests for scripts/bump_release_version.py (stdlib unittest, no subprocess)."""
+import json
+import sys
+import tempfile
+import unittest
+from pathlib import Path
+
+_REPO_ROOT = Path(__file__).resolve().parent.parent
+sys.path.insert(0, str(_REPO_ROOT / "scripts"))
+
+import bump_release_version as brv  # noqa: E402
+
+PYPROJECT = """\
+[build-system]
+requires = ["setuptools>=77"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "duet-cli"
+version = "0.2.1"
+description = "x"
+"""
+
+CLAUDE_PLUGIN = {"name": "duet", "version": "0.2.1", "author": {"name": "Volkan Altan"}}
+CODEX_PLUGIN = {"name": "duet", "version": "0.2.1", "skills": "./skills/"}
+
+
+def _make_repo(tmp: Path) -> None:
+    (tmp / "pyproject.toml").write_text(PYPROJECT, encoding="utf-8")
+    claude = tmp / "plugins" / "duet-claude" / ".claude-plugin"
+    codex = tmp / "plugins" / "duet" / ".codex-plugin"
+    claude.mkdir(parents=True)
+    codex.mkdir(parents=True)
+    (claude / "plugin.json").write_text(json.dumps(CLAUDE_PLUGIN, indent=2) + "\n", encoding="utf-8")
+    (codex / "plugin.json").write_text(json.dumps(CODEX_PLUGIN, indent=2) + "\n", encoding="utf-8")
+
+
+class TestParseStrictSemver(unittest.TestCase):
+    def test_valid(self):
+        self.assertEqual(brv.parse_strict_semver("1.2.3"), (1, 2, 3))
+        self.assertEqual(brv.parse_strict_semver("0.2.10"), (0, 2, 10))
+
+    def test_rejects(self):
+        for bad in ("v1.2.3", "0.3.0-rc1", "0.3.0+build", "1.2", "1.2.3.4", "1.2.x", ""):
+            with self.assertRaises(brv.BumpError, msg=bad):
+                brv.parse_strict_semver(bad)
+
+
+class TestBump(unittest.TestCase):
+    def setUp(self):
+        self._tmp = tempfile.TemporaryDirectory()
+        self.root = Path(self._tmp.name)
+        _make_repo(self.root)
+
+    def tearDown(self):
+        self._tmp.cleanup()
+
+    def _versions(self):
+        py = brv.read_current_version((self.root / "pyproject.toml").read_text())
+        cl = json.loads((self.root / "plugins/duet-claude/.claude-plugin/plugin.json").read_text())
+        cx = json.loads((self.root / "plugins/duet/.codex-plugin/plugin.json").read_text())
+        return py, cl["version"], cx["version"]
+
+    def test_read_current_version(self):
+        self.assertEqual(brv.read_current_version(PYPROJECT), "0.2.1")
+
+    def test_bump_updates_all_three(self):
+        prev = brv.bump(self.root, "0.3.0")
+        self.assertEqual(prev, "0.2.1")
+        self.assertEqual(self._versions(), ("0.3.0", "0.3.0", "0.3.0"))
+
+    def test_bump_preserves_json_structure(self):
+        brv.bump(self.root, "0.2.2")
+        cl = json.loads((self.root / "plugins/duet-claude/.claude-plugin/plugin.json").read_text())
+        self.assertEqual(cl["name"], "duet")
+        self.assertEqual(cl["author"], {"name": "Volkan Altan"})
+        # only the build-system version-like string and [project] survive; the bump
+        # must not touch the [build-system] requires line.
+        py = (self.root / "pyproject.toml").read_text()
+        self.assertIn('requires = ["setuptools>=77"]', py)
+        self.assertIn('version = "0.2.2"', py)
+
+    def test_reject_downgrade(self):
+        with self.assertRaises(brv.BumpError):
+            brv.bump(self.root, "0.2.0")
+        self.assertEqual(self._versions(), ("0.2.1", "0.2.1", "0.2.1"))  # unchanged
+
+    def test_reject_same_version(self):
+        with self.assertRaises(brv.BumpError):
+            brv.bump(self.root, "0.2.1")
+
+    def test_reject_invalid_before_write(self):
+        with self.assertRaises(brv.BumpError):
+            brv.bump(self.root, "v0.3.0")
+        self.assertEqual(self._versions(), ("0.2.1", "0.2.1", "0.2.1"))  # no partial write
+
+    def test_missing_project_version_raises(self):
+        (self.root / "pyproject.toml").write_text(
+            "[build-system]\nrequires = []\n", encoding="utf-8"
+        )
+        with self.assertRaises(brv.BumpError):
+            brv.bump(self.root, "0.3.0")
+
+
+if __name__ == "__main__":
+    unittest.main()