boost-skill-cli 1.0.157__tar.gz → 1.0.158__tar.gz

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/CONTRIBUTING.md

@@ -37,12 +37,18 @@ auto-fixes straight back onto the branch.
 | `make mutation` | mutmut over `boost_cli/core`, **≥80% mutants killed** |
 | `ruff check boost_cli tests` | lint, zero findings |
 | `mypy` | type check, zero errors |
+| `lint-imports` | layering: `core/` imports no `commands/`/`cli`; CLI depends inward |
 
 ## Ground rules
 
 - **Stdlib only** at runtime. No third-party imports in `boost_cli/`.
 - New commands live in `boost_cli/commands/<group>.py` as
   `def cmd_<name>(argv) -> int` and are dispatched lazily from `cli.py`.
+- **Respect the layers** (`cli → commands → core`): `core/` is the engine and
+  must import neither `commands/` nor `cli`; `commands/` must not reach up into
+  `cli`. `import-linter` enforces this — see `[tool.importlinter]` in
+  `pyproject.toml` (the one allowlisted edge is `completions` reading the
+  `COMMANDS` registry).
 - Behavior changes need tests — functional tests drive the CLI in-process via
   `boost_cli.cli.main` (see `tests/conftest.py` for the fixtures).
 - Anything under `boost_cli/core/` is mutation-tested; expect to add unit

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/Makefile

@@ -14,7 +14,7 @@ EVAL_HOME := $(CURDIR)/.eval-home
 
 venv:
 	python3 -m venv $(VENV)
-	$(VENV)/bin/pip -q install pytest pytest-cov coverage mutmut ruff mypy codespell hypothesis
+	$(VENV)/bin/pip -q install pytest pytest-cov coverage mutmut ruff mypy codespell hypothesis import-linter
 
 unit:
 	$(PYTEST) tests/unit -q
@@ -39,6 +39,7 @@ mutation:
 lint:
 	$(VENV)/bin/ruff check boost_cli tests
 	$(VENV)/bin/mypy
+	$(VENV)/bin/lint-imports
 	$(VENV)/bin/codespell boost_cli docs README.md
 	@command -v actionlint >/dev/null 2>&1 && actionlint || echo "actionlint not on PATH — skipping (CI enforces it)"
 	$(PY) scripts/build_registries.py --check

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.157
+Version: 1.0.158
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.0.157'
-__version_tuple__ = version_tuple = (1, 0, 157)
+__version__ = version = '1.0.158'
+__version_tuple__ = version_tuple = (1, 0, 158)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.157
+Version: 1.0.158
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/docs/roadmap/items/layering-guard-import-linter.md

@@ -2,15 +2,15 @@
 id: layering-guard-import-linter
 board: code
 section: dx
-status: planned
+status: shipped
 category: Quality · Architecture
 complexity: M
 impact: Med
 wow: 4
 note: core/ ↛ commands/
 order: 3
-owner:
-pr:
+owner: loop/layering
+pr: 182
 title: Layering guard — <code>import-linter</code>
 ---
 Enforce the architecture boost already assumes: <code>core/</code> must

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/docs/roadmap.html

@@ -1341,7 +1341,7 @@ improvement is real (or isn't)."</p>
       </article>
 
       <article class="cap rcard">
-        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Architecture</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Quality · Architecture</span></div>
         <h3>Layering guard — <code>import-linter</code></h3>
         <p>Enforce the architecture boost already assumes: <code>core/</code> must
            never import <code>commands/</code>, and the CLI depends inward only.

{boost_skill_cli-1.0.157 → boost_skill_cli-1.0.158}/pyproject.toml

@@ -155,3 +155,24 @@ exclude_lines = [
     "if TYPE_CHECKING:",
     "raise NotImplementedError",
 ]
+
+# import-linter: turn boost's assumed layering into an enforced contract, so a
+# cross-layer import can't silently erode the engine. Run by `make lint`
+# (lint-imports) and the CI lint job. Dev/CI-only — never imported at runtime.
+[tool.importlinter]
+root_package = "boost_cli"
+
+[[tool.importlinter.contracts]]
+name = "boost_cli is layered: cli -> commands -> core"
+type = "layers"
+# Higher layers may import lower ones, never the reverse: core/ (the engine)
+# must import neither commands/ nor the CLI, and commands/ must not reach up
+# into cli. This is the structural rule CLAUDE.md documents — core is the
+# mutation-tested engine, commands/ is thin glue on top of it.
+layers = ["cli", "commands", "core"]
+containers = ["boost_cli"]
+# The one intentional upward edge: `boost completions` reads COMMANDS — the
+# command registry, which lives in cli.py by design (see CLAUDE.md) — to list
+# every command. That single metadata lookup is allowlisted; any other
+# commands -> cli import is still a violation.
+ignore_imports = ["boost_cli.commands.configuration -> boost_cli.cli"]