boost-skill-cli 1.0.83__tar.gz → 1.0.85__tar.gz

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/Makefile

@@ -10,7 +10,7 @@ PYTEST  := $(VENV)/bin/pytest
 
 venv:
 	python3 -m venv $(VENV)
-	$(VENV)/bin/pip -q install pytest pytest-cov coverage mutmut ruff mypy
+	$(VENV)/bin/pip -q install pytest pytest-cov coverage mutmut ruff mypy codespell
 
 unit:
 	$(PYTEST) tests/unit -q
@@ -35,6 +35,7 @@ mutation:
 lint:
 	$(VENV)/bin/ruff check boost_cli tests
 	$(VENV)/bin/mypy
+	$(VENV)/bin/codespell boost_cli docs README.md
 	$(PY) scripts/build_registries.py --check
 	$(PY) scripts/build_roadmap.py --check
 

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.83
+Version: 1.0.85
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -726,6 +726,16 @@ update all of them, you run one command.
   <sub><em>tap a registry → search → install into every agent → doctor — one flow</em></sub>
 </p>
 
+## Roadmap
+
+boost is built in the open. Two living boards — generated from
+`docs/roadmap/items/*.md` — track what's shipped, in flight, and planned:
+
+- **[Code roadmap](https://jonnyeclectic.github.io/boost/roadmap.html)** — engine, correctness, and tooling work
+- **[Design roadmap](https://jonnyeclectic.github.io/boost/design-roadmap.html)** — the Visual Guide and docsite aesthetics
+
+Both are reachable from the [Visual Guide](https://jonnyeclectic.github.io/boost/) nav.
+
 ## What's a "skill," exactly?
 
 A **skill** is just a `SKILL.md` file — Markdown plus a bit of YAML up top —

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/README.md

@@ -20,6 +20,16 @@ update all of them, you run one command.
   <sub><em>tap a registry → search → install into every agent → doctor — one flow</em></sub>
 </p>
 
+## Roadmap
+
+boost is built in the open. Two living boards — generated from
+`docs/roadmap/items/*.md` — track what's shipped, in flight, and planned:
+
+- **[Code roadmap](https://jonnyeclectic.github.io/boost/roadmap.html)** — engine, correctness, and tooling work
+- **[Design roadmap](https://jonnyeclectic.github.io/boost/design-roadmap.html)** — the Visual Guide and docsite aesthetics
+
+Both are reachable from the [Visual Guide](https://jonnyeclectic.github.io/boost/) nav.
+
 ## What's a "skill," exactly?
 
 A **skill** is just a `SKILL.md` file — Markdown plus a bit of YAML up top —

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/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.83'
-__version_tuple__ = version_tuple = (1, 0, 83)
+__version__ = version = '1.0.85'
+__version_tuple__ = version_tuple = (1, 0, 85)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/boost_skill_cli.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.0.83
+Version: 1.0.85
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE
@@ -726,6 +726,16 @@ update all of them, you run one command.
   <sub><em>tap a registry → search → install into every agent → doctor — one flow</em></sub>
 </p>
 
+## Roadmap
+
+boost is built in the open. Two living boards — generated from
+`docs/roadmap/items/*.md` — track what's shipped, in flight, and planned:
+
+- **[Code roadmap](https://jonnyeclectic.github.io/boost/roadmap.html)** — engine, correctness, and tooling work
+- **[Design roadmap](https://jonnyeclectic.github.io/boost/design-roadmap.html)** — the Visual Guide and docsite aesthetics
+
+Both are reachable from the [Visual Guide](https://jonnyeclectic.github.io/boost/) nav.
+
 ## What's a "skill," exactly?
 
 A **skill** is just a `SKILL.md` file — Markdown plus a bit of YAML up top —

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/boost_skill_cli.egg-info/SOURCES.txt

@@ -127,9 +127,11 @@ docs/roadmap/items/layering-guard-import-linter.md
 docs/roadmap/items/lighthouse-ci-on-the-pages-site.md
 docs/roadmap/items/localize-the-stored-bm25-snippet.md
 docs/roadmap/items/lockfile-enforcement-and-commit-pinning.md
+docs/roadmap/items/log-timestamps-mislabeled-utc.md
 docs/roadmap/items/lowest-version-resolution-uv-resolution-lowest-d.md
 docs/roadmap/items/make-the-roadmaps-discoverable.md
 docs/roadmap/items/markdown-consistency-markdownlint-cli2.md
+docs/roadmap/items/mcp-launch-objc-fork-safety.md
 docs/roadmap/items/memoize-config-load-in-process.md
 docs/roadmap/items/modernization-smells-refurb-pyupgrade.md
 docs/roadmap/items/mutation-hardening-core-frontmatter-py.md
@@ -152,6 +154,7 @@ docs/roadmap/items/reconcile-the-theme-drift.md
 docs/roadmap/items/refresh-the-marketing-surface.md
 docs/roadmap/items/reuse-helpers-kill-minor-dead-work.md
 docs/roadmap/items/robust-tag-argument-parsing.md
+docs/roadmap/items/rule-install-native-materialization.md
 docs/roadmap/items/runner-egress-monitoring-stepsecurity-harden-run.md
 docs/roadmap/items/sbom-aware-scanning-osv-scanner.md
 docs/roadmap/items/sbom-on-every-release-cyclonedx-syft.md

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/docs/index.html

@@ -447,6 +447,7 @@
       <li><a href="#capabilities">Capabilities</a></li>
       <li><a href="#registries">Registries</a></li>
       <li><a href="roadmap.html">Roadmap&nbsp;↗</a></li>
+      <li><a href="design-roadmap.html">Design&nbsp;↗</a></li>
       <li><a href="https://jonnyeclectic.github.io/portfolio/">Portfolio&nbsp;↗</a></li>
       <li><a class="cta" href="#start">Get started</a></li>
     </ul>

boost_skill_cli-1.0.85/docs/roadmap/items/log-timestamps-mislabeled-utc.md

@@ -0,0 +1,25 @@
+---
+id: log-timestamps-mislabeled-utc
+board: code
+section: health
+status: planned
+category: Observability · Diagnostics
+complexity: S
+impact: Med
+wow: 2
+note: converter = time.gmtime
+order: 10
+owner:
+pr:
+title: Log timestamps are local time mislabeled <code>Z</code>
+---
+<code>core/logs.py</code> builds the <code>logging.Formatter</code> with
+           <code>datefmt="%Y-%m-%dT%H:%M:%SZ"</code> but never sets
+           <code>converter = time.gmtime</code>, so <code>%(asctime)s</code> uses
+           <em>local</em> time while stamping a literal <code>Z</code> (UTC)
+           suffix. Every line in <code>~/.boost/logs/boost.log</code> is therefore
+           off by the machine's UTC offset — which nearly caused a 5-hour
+           mis-correlation when matching the log against an OS crash report. Set
+           the formatter's <code>converter</code> to <code>time.gmtime</code> (or
+           drop the <code>Z</code>) so the trail is honestly UTC, making the
+           pid/ppid crash-correlation breadcrumbs trustworthy.

boost_skill_cli-1.0.85/docs/roadmap/items/make-the-roadmaps-discoverable.md

@@ -0,0 +1,22 @@
+---
+id: make-the-roadmaps-discoverable
+board: code
+section: docsite
+status: shipped
+category: Docs · Discoverability
+complexity: S
+impact: Med
+wow: 3
+note: nav + README links
+order: 1
+owner: loop/roadmaps-discoverable
+pr: 101
+title: Make the roadmaps discoverable
+---
+The living roadmaps were unreachable unless you knew the URL:
+<code>design-roadmap.html</code> was linked nowhere and the README had no
+roadmap link at all. The Visual Guide nav now carries both boards (a
+<code>Design&nbsp;↗</code> entry beside the existing <code>Roadmap&nbsp;↗</code>),
+and the README opens with a <b>Roadmap</b> section linking the code and design
+boards plus the Visual Guide — so the two data-driven boards are one click away
+and the work stays visible.

boost_skill_cli-1.0.85/docs/roadmap/items/mcp-launch-objc-fork-safety.md

@@ -0,0 +1,26 @@
+---
+id: mcp-launch-objc-fork-safety
+board: code
+section: compat
+status: planned
+category: Compatibility · macOS
+complexity: S
+impact: Med
+wow: 3
+note: OBJC_DISABLE_INITIALIZE_FORK_SAFETY
+order: 9
+owner:
+pr:
+title: Harden <code>boost mcp</code> launch against macOS Obj-C fork aborts
+---
+On macOS, a host that spawns <code>boost mcp --stdio</code> via <code>fork()</code>
+           can abort on the child side pre-<code>exec</code> when Obj-C is touched
+           post-fork (CFPreferences / <code>_scproxy</code> proxy lookup) — the
+           classic <em>"crashed on child side of fork pre-exec"</em>
+           <code>SIGABRT</code>. Not boost's own code (it aborts before boost
+           runs), but boost can make its integration robust: when registering the
+           MCP server (<code>boost mcp register</code> / the emitted client
+           config), set <code>OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES</code> (and
+           <code>no_proxy=*</code>) in the launch environment so the host's fork
+           into boost can't trip the Obj-C fork-safety abort. Document it for
+           hosts that launch boost directly.

boost_skill_cli-1.0.85/docs/roadmap/items/rule-install-native-materialization.md

@@ -0,0 +1,29 @@
+---
+id: rule-install-native-materialization
+board: code
+section: internals
+status: planned
+category: Install engine · Rules
+complexity: L
+impact: High
+wow: 4
+note: rules are indexed but never installed
+order: 21
+owner:
+pr:
+title: Rule install — materialize rules into each agent's native format
+---
+Today <code>store.install</code> refuses every non-skill kind
+           (<em>"rules and workflows show up in <code>boost search</code>/<code>boost taps</code>
+           for now"</em>), so rules are indexed for discovery but land nowhere —
+           there is no <code>boost install</code> path for a rule. Add one that
+           writes each rule into the form the target agent actually reads, since
+           there is no single cross-agent "rules folder": Cursor/Windsurf/Cline
+           consume a rules directory (<code>.cursorrules</code> /
+           <code>.windsurfrules</code> / <code>.clinerules</code> / <code>.mdc</code>),
+           but <strong>Claude Code has no rules folder</strong> — its standing
+           rules are <code>CLAUDE.md</code>. So installing a rule for Claude means
+           merging it into <code>CLAUDE.md</code> (a managed, idempotent block),
+           while for the others it means dropping the file into their rules dir.
+           Needs a store/lock model for rules (uninstall must cleanly remove the
+           merged block), mirroring how skills symlink into <code>enabled_agents()</code>.

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/docs/roadmap/items/typo-detection-codespell.md

@@ -2,15 +2,15 @@
 id: typo-detection-codespell
 board: code
 section: dx
-status: planned
+status: shipped
 category: Quality · Docs
 complexity: S
 impact: Med
 wow: 2
 note: user-facing text
 order: 4
-owner:
-pr:
+owner: loop/codespell-gate
+pr: 100
 title: Typo detection — <code>codespell</code>
 ---
 Cheap, high-signal for a project this documentation-heavy: scan the

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/docs/roadmap.html

@@ -118,7 +118,7 @@
       <div class="stat"><b>10</b><span>Shipped</span></div>
       <div class="stat"><b>3</b><span>Next up</span></div>
       <div class="stat"><b>4</b><span>Planned</span></div>
-      <div class="stat"><b>85</b><span>Loop finds</span></div>
+      <div class="stat"><b>88</b><span>Loop finds</span></div>
       <!-- /ROADMAP:stats -->
     </div>
   </section>
@@ -615,6 +615,31 @@
           <span class="m">Wow <b class="wow">★</b></span>
         </div>
       </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Install engine · Rules</span></div>
+        <h3>Rule install — materialize rules into each agent's native format</h3>
+        <p>Today <code>store.install</code> refuses every non-skill kind
+           (<em>"rules and workflows show up in <code>boost search</code>/<code>boost taps</code>
+           for now"</em>), so rules are indexed for discovery but land nowhere —
+           there is no <code>boost install</code> path for a rule. Add one that
+           writes each rule into the form the target agent actually reads, since
+           there is no single cross-agent "rules folder": Cursor/Windsurf/Cline
+           consume a rules directory (<code>.cursorrules</code> /
+           <code>.windsurfrules</code> / <code>.clinerules</code> / <code>.mdc</code>),
+           but <strong>Claude Code has no rules folder</strong> — its standing
+           rules are <code>CLAUDE.md</code>. So installing a rule for Claude means
+           merging it into <code>CLAUDE.md</code> (a managed, idempotent block),
+           while for the others it means dropping the file into their rules dir.
+           Needs a store/lock model for rules (uninstall must cleanly remove the
+           merged block), mirroring how skills symlink into <code>enabled_agents()</code>.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>L</b></span>
+          <span class="m hi">Impact <b>High</b></span>
+          <span class="m">Wow <b class="wow">★★★★</b></span>
+          <span class="m">rules are indexed but never installed</span>
+        </div>
+      </article>
       <!-- /ROADMAP:cards -->
 
     </div>
@@ -784,6 +809,27 @@
           <span class="m">avoid macOS _scproxy Obj-C path</span>
         </div>
       </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Observability · Diagnostics</span></div>
+        <h3>Log timestamps are local time mislabeled <code>Z</code></h3>
+        <p><code>core/logs.py</code> builds the <code>logging.Formatter</code> with
+           <code>datefmt="%Y-%m-%dT%H:%M:%SZ"</code> but never sets
+           <code>converter = time.gmtime</code>, so <code>%(asctime)s</code> uses
+           <em>local</em> time while stamping a literal <code>Z</code> (UTC)
+           suffix. Every line in <code>~/.boost/logs/boost.log</code> is therefore
+           off by the machine's UTC offset — which nearly caused a 5-hour
+           mis-correlation when matching the log against an OS crash report. Set
+           the formatter's <code>converter</code> to <code>time.gmtime</code> (or
+           drop the <code>Z</code>) so the trail is honestly UTC, making the
+           pid/ppid crash-correlation breadcrumbs trustworthy.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★</b></span>
+          <span class="m">converter = time.gmtime</span>
+        </div>
+      </article>
       <!-- /ROADMAP:cards -->
 
     </div>
@@ -991,7 +1037,7 @@
       </article>
 
       <article class="cap rcard">
-        <div class="head"><span class="pill planned">Planned</span><span class="cat">Quality · Docs</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Quality · Docs</span></div>
         <h3>Typo detection — <code>codespell</code></h3>
         <p>Cheap, high-signal for a project this documentation-heavy: scan the
            README, <code>docs/*.html</code>, docstrings and every user-facing CLI
@@ -1097,18 +1143,20 @@
 
       <!-- ROADMAP:cards section=docsite -->
       <article class="cap rcard">
-        <div class="head"><span class="pill next">Next</span><span class="cat">Docs · Discoverability</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Docs · Discoverability</span></div>
         <h3>Make the roadmaps discoverable</h3>
-        <p>Neither <code>roadmap.html</code> nor <code>design-roadmap.html</code> is
-           linked from <code>docs/index.html</code> or the README — the living
-           roadmaps are unreachable unless you already know the URL. Add nav entries
-           on the Visual Guide and a "Roadmap" link in the README so the two boards
-           are one click away and the work stays visible.</p>
+        <p>The living roadmaps were unreachable unless you knew the URL:
+<code>design-roadmap.html</code> was linked nowhere and the README had no
+roadmap link at all. The Visual Guide nav now carries both boards (a
+<code>Design&nbsp;↗</code> entry beside the existing <code>Roadmap&nbsp;↗</code>),
+and the README opens with a <b>Roadmap</b> section linking the code and design
+boards plus the Visual Guide — so the two data-driven boards are one click away
+and the work stays visible.</p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Med</b></span>
           <span class="m">Wow <b class="wow">★★★</b></span>
-          <span class="m">2 nav links</span>
+          <span class="m">nav + README links</span>
         </div>
       </article>
 
@@ -1399,6 +1447,28 @@
           <span class="m">local == CI</span>
         </div>
       </article>
+
+      <article class="cap rcard">
+        <div class="head"><span class="pill planned">Planned</span><span class="cat">Compatibility · macOS</span></div>
+        <h3>Harden <code>boost mcp</code> launch against macOS Obj-C fork aborts</h3>
+        <p>On macOS, a host that spawns <code>boost mcp --stdio</code> via <code>fork()</code>
+           can abort on the child side pre-<code>exec</code> when Obj-C is touched
+           post-fork (CFPreferences / <code>_scproxy</code> proxy lookup) — the
+           classic <em>"crashed on child side of fork pre-exec"</em>
+           <code>SIGABRT</code>. Not boost's own code (it aborts before boost
+           runs), but boost can make its integration robust: when registering the
+           MCP server (<code>boost mcp register</code> / the emitted client
+           config), set <code>OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES</code> (and
+           <code>no_proxy=*</code>) in the launch environment so the host's fork
+           into boost can't trip the Obj-C fork-safety abort. Document it for
+           hosts that launch boost directly.</p>
+        <div class="meta">
+          <span class="m">Complexity <b>S</b></span>
+          <span class="m">Impact <b>Med</b></span>
+          <span class="m">Wow <b class="wow">★★★</b></span>
+          <span class="m">OBJC_DISABLE_INITIALIZE_FORK_SAFETY</span>
+        </div>
+      </article>
       <!-- /ROADMAP:cards -->
 
     </div>

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.85}/pyproject.toml

@@ -63,6 +63,13 @@ target-version = "py39"
 # short throwaway names and lambda helpers are fine in tests
 "tests/*" = ["E741", "E731"]
 
+[tool.codespell]
+# Spell-check user-facing text (see `make lint`: boost_cli, docs, README).
+# Generated boards and the setuptools-scm version stub aren't ours to check.
+skip = "docs/roadmap.html,docs/design-roadmap.html,boost_cli/_version.py,*.tar.gz"
+# Valid English that codespell's dictionary flags as misspellings.
+ignore-words-list = "unparseable,accreting"
+
 [tool.mypy]
 python_version = "3.9"
 files = ["boost_cli"]

boost_skill_cli-1.0.83/docs/roadmap/items/make-the-roadmaps-discoverable.md

@@ -1,20 +0,0 @@
----
-id: make-the-roadmaps-discoverable
-board: code
-section: docsite
-status: next
-category: Docs · Discoverability
-complexity: S
-impact: Med
-wow: 3
-note: 2 nav links
-order: 1
-owner:
-pr:
-title: Make the roadmaps discoverable
----
-Neither <code>roadmap.html</code> nor <code>design-roadmap.html</code> is
-           linked from <code>docs/index.html</code> or the README — the living
-           roadmaps are unreachable unless you already know the URL. Add nav entries
-           on the Visual Guide and a "Roadmap" link in the README so the two boards
-           are one click away and the work stays visible.