zettcode 0.3.0__tar.gz → 0.3.1__tar.gz

{zettcode-0.3.0 → zettcode-0.3.1}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: zettcode
-Version: 0.3.0
+Version: 0.3.1
 Summary: A focused terminal coding agent powered by zett-agent
 Project-URL: Repository, https://github.com/Chang-LeHung/zettcode
 Project-URL: Issues, https://github.com/Chang-LeHung/zettcode/issues
@@ -36,6 +36,8 @@ Requires-Dist: uvicorn<1,>=0.35
 Requires-Dist: wcwidth<1,>=0.2
 Requires-Dist: websockets<17,>=15
 Requires-Dist: zett-agent<0.3,>=0.2.2
+Provides-Extra: monitor
+Requires-Dist: zettcode-monitor<0.3,>=0.2; extra == 'monitor'
 Description-Content-Type: text/markdown
 
 # ZettCode

{zettcode-0.3.0 → zettcode-0.3.1}/pyproject.toml

@@ -64,6 +64,15 @@ dependencies = [
   "zett-agent>=0.2.2,<0.3",
 ]
 
+[project.optional-dependencies]
+# A plugin this repository ships, for reading what a session actually sent and received: `pip install
+# "zettcode[monitor]"` adds `/monitor`. It is an extra and not a dependency on purpose — it records every model
+# request and response unredacted, which is a debugging tool and not something to hand everyone — and a hard edge
+# would tie the two projects' releases together: a new minor line of zettcode would need a monitor published first
+# that accepts it (its range has to allow both lines in between), or `pip install zettcode==<new>` would fail to
+# resolve, and so would the environment the VS Code extension builds for itself.
+monitor = ["zettcode-monitor>=0.2,<0.3"]
+
 [project.scripts]
 zettcode = "zettcode.cli:main"
 zettcode-server = "zettcode.server.cli:main"

{zettcode-0.3.0 → zettcode-0.3.1}/src/zettcode/__init__.py

@@ -7,7 +7,7 @@ from typing import TYPE_CHECKING
 
 #: The one place the version is written. ``pyproject.toml`` reads it from here
 #: and the release workflow checks the tag against it, so a bump is one edit.
-__version__ = "0.3.0"
+__version__ = "0.3.1"
 
 #: Where each public name lives; read by :func:`__getattr__` on first use.
 _EXPORTS = {