strictcli 0.38.0__tar.gz → 0.40.0__tar.gz

strictcli-0.40.0/.gitignore

@@ -0,0 +1,25 @@
+node_modules/
+__pycache__/
+*.pyc
+*.log
+.DS_Store
+coverage/
+dist/
+*.egg-info/
+.rlsbl-notes-*.tmp
+.rlsbl/lock
+.credentials.json
+.*-cache.json
+.env
+.env.local
+*.local-only
+
+.rlsbl-monorepo/lock
+
+build/
+target/
+
+# Test apps run with this directory as cwd write schema dumps and coverage
+# shards here. Nothing under python/ is a maintained artifact (unlike
+# conformance/.strictcli/, which is committed on purpose).
+.strictcli/

{strictcli-0.38.0 → strictcli-0.40.0}/CLAUDE.md

@@ -18,7 +18,7 @@ Releases go through [rlsbl](https://github.com/smm-h/rlsbl) monorepo releases.
   (they land in `.rlsbl-monorepo/releasables/py-strictcli/changes/unreleased.jsonl`).
 - To release: from the repo root, run `rlsbl monorepo release init`, edit the
   scaffolded release file (bump type, description, and context live in the file),
-  then run `rlsbl monorepo release run --no-allow-dirty --watch --yes`.
+  then run `rlsbl monorepo release run --no-allow-dirty --watch --approve-consequential`.
 - Never publish or push manually — CI publishes to PyPI via Trusted Publishing.
 
 ## Conventions

{strictcli-0.38.0 → strictcli-0.40.0}/PKG-INFO

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: strictcli
-Version: 0.38.0
+Version: 0.40.0
 Summary: A strict CLI framework for Python
 Project-URL: Homepage, https://github.com/smm-h/strictcli
 Project-URL: Repository, https://github.com/smm-h/strictcli
@@ -391,7 +391,19 @@ Auto-registers a `check` command with tag DSL filtering
 
 ```python
 tools = app.as_tools()
-# Each Tool has: name, description, parameters (JSON Schema), execute
+# Each Tool has: name, description, parameters (JSON Schema), effect,
+# consequential, execute
+```
+
+`effect` and `consequential` publish the effects-regime classification beside
+the argument schema, so a caller can see before it calls that a tool changes
+things and that invoking it requires stating consent:
+
+```python
+release = next(t for t in tools if t.name == "release")
+release.consequential            # True
+await release.execute()          # InvokeError: ... the call must carry confirmation
+await release.execute(approve_consequential=True)   # proceeds
 ```
 
 ### MCP server

{strictcli-0.38.0 → strictcli-0.40.0}/README.md

@@ -372,7 +372,19 @@ Auto-registers a `check` command with tag DSL filtering
 
 ```python
 tools = app.as_tools()
-# Each Tool has: name, description, parameters (JSON Schema), execute
+# Each Tool has: name, description, parameters (JSON Schema), effect,
+# consequential, execute
+```
+
+`effect` and `consequential` publish the effects-regime classification beside
+the argument schema, so a caller can see before it calls that a tool changes
+things and that invoking it requires stating consent:
+
+```python
+release = next(t for t in tools if t.name == "release")
+release.consequential            # True
+await release.execute()          # InvokeError: ... the call must carry confirmation
+await release.execute(approve_consequential=True)   # proceeds
 ```
 
 ### MCP server

{strictcli-0.38.0 → strictcli-0.40.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "strictcli"
-version = "0.38.0"
+version = "0.40.0"
 description = "A strict CLI framework for Python"
 readme = "README.md"
 license = "MIT"