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

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

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

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

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.84}/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.84
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License: GNU GENERAL PUBLIC LICENSE

{boost_skill_cli-1.0.83 → boost_skill_cli-1.0.84}/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

boost_skill_cli-1.0.84/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.84/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.83 → boost_skill_cli-1.0.84}/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>87</b><span>Loop finds</span></div>
       <!-- /ROADMAP:stats -->
     </div>
   </section>
@@ -784,6 +784,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>
@@ -1399,6 +1420,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>