napkinstack 0.7.4__tar.gz → 0.7.6__tar.gz

{napkinstack-0.7.4 → napkinstack-0.7.6}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: napkinstack
-Version: 0.7.4
+Version: 0.7.6
 Summary: Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI.
 License-Expression: MIT
 License-File: LICENSE
@@ -20,7 +20,7 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.7.4, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> **Status: v0.7.6, published** on [PyPI](https://pypi.org/project/napkinstack/).
 > What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
 > What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
@@ -84,8 +84,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.4" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.4"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.6" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.6"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a

{napkinstack-0.7.4 → napkinstack-0.7.6}/README.md

@@ -5,7 +5,7 @@ modules, contracts, guardrails in CI. On the Django or Rails model, one command
 the project, which then receives new versions on demand; no application stack is imposed.
 Positioning and vocabulary: [`PRODUCT.md`](PRODUCT.md) §1.
 
-> **Status: v0.7.4, published** on [PyPI](https://pypi.org/project/napkinstack/).
+> **Status: v0.7.6, published** on [PyPI](https://pypi.org/project/napkinstack/).
 > What each version changes, engine and project apart: [`CHANGELOG.md`](CHANGELOG.md).
 > What is open: [`docs/governance/workstreams.md`](docs/governance/workstreams.md).
 
@@ -69,8 +69,8 @@ To try it without installing anything, or to install it from this repository ins
 registry — always pinned to a release tag:
 
 ```bash
-uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.4" nstack init my-project
-uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.4"
+uvx --from "git+https://github.com/NapkinStack/engineering-os@v0.7.6" nstack init my-project
+uv tool install "napkinstack @ git+https://github.com/NapkinStack/engineering-os@v0.7.6"
 ```
 
 **Two channels, one published artefact.** The registry publishes: the PyPI artefact of a

{napkinstack-0.7.4 → napkinstack-0.7.6}/pyproject.toml

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.7.4"
+version = "0.7.6"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"

{napkinstack-0.7.4 → napkinstack-0.7.6}/pyproject.toml.orig

@@ -1,6 +1,6 @@
 [project]
 name = "napkinstack"
-version = "0.7.4"
+version = "0.7.6"
 description = "Engineering framework for several teams and their agents working in one repository: modules, contracts, guardrails in CI."
 requires-python = ">=3.12"
 license = "MIT"

{napkinstack-0.7.4 → napkinstack-0.7.6}/src/napkinstack/fitness/hygiene.py

@@ -12,9 +12,10 @@ Rules:
 
 Refused: the home of a named user, on any of the three systems, and a tilde followed by a
 real folder. Accepted, because they are true on every machine: a tilde followed by a
-dot-directory (`~/.config`, `~/.cache`, `~/.ssh` — tooling is documented legitimately), a
-tilde inside an address, the repository's placeholders (`<workspace>`), environment
-variables, and the home of an image's own user — `node`, `vscode`, `runner`, `codespace`,
+dot-directory (`~/.config`, `~/.cache`, `~/.ssh` — tooling is documented legitimately) and
+its macOS counterpart, `~/Library`, where every Mac keeps software's own files and a macOS
+app documents its storage (D97); a tilde inside an address, the repository's placeholders
+(`<workspace>`), environment variables, and the home of an image's own user — `node`, `vscode`, `runner`, `codespace`,
 `gitpod`, `jovyan` — which is the same wherever the image runs (D41).
 
 The patterns are written so that this file, the rule's tests and any document describing
@@ -45,7 +46,7 @@ IMAGE_USERS = r"(?:node|vscode|runner|codespace|gitpod|jovyan)(?![A-Za-z0-9_.-])
 SEGMENT = r"[A-Za-z0-9_.-]+"
 HOME_PATH = re.compile(
     rf"(?:/home/(?!{IMAGE_USERS}){SEGMENT}|/Users/{SEGMENT}|[A-Za-z]:\\Users\\{SEGMENT}"
-    r"|(?<![\w/:])~(?=/[A-Za-z0-9]))"
+    r"|(?<![\w/:])~(?=/[A-Za-z0-9])(?!/Library(?![\w.-])))"
     r"[^\s'\"`,;)\]]*"
 )
 ACTION = ("write what the step needs: a path relative to the repository, a placeholder such "