boost-skill-cli 1.2.129__tar.gz → 1.2.130__tar.gz

{boost_skill_cli-1.2.129/boost_skill_cli.egg-info → boost_skill_cli-1.2.130}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.129
+Version: 1.2.130
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/boost_cli/_version.py

@@ -18,7 +18,7 @@ version_tuple: tuple[int | str, ...]
 commit_id: str | None
 __commit_id__: str | None
 
-__version__ = version = '1.2.129'
-__version_tuple__ = version_tuple = (1, 2, 129)
+__version__ = version = '1.2.130'
+__version_tuple__ = version_tuple = (1, 2, 130)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/boost_cli/commands/discovery.py

@@ -1151,13 +1151,17 @@ def cmd_recommend(argv):
     if used_curated_fallback:
         out.info("no stack-specific matches — curated picks instead:")
     width = min(max(len(r["entry"]["name"]) for r in shown), 32)
-    cols = out.term_width()
-    for r in shown:
+    reasons = ["because: %s" % ", ".join(sorted(r["because"])) for r in shown]
+    # One description width for every row, from the widest reason. Sized per
+    # row from that row's own `because:` tag, the clip point swung 20 columns
+    # between rows (34-54 at COLUMNS=100) and neither column lined up.
+    desc_w = max(out.term_width() - 2 - width - 2
+                 - (max(map(len, reasons)) + 2), 8)
+    for r, because in zip(shown, reasons, strict=True):
         e = r["entry"]
-        because = "because: %s" % ", ".join(sorted(r["because"]))
-        desc_w = max(cols - 2 - width - 2 - (len(because) + 2), 8)
         name_cell = out.role(out.truncate(e["name"], width).ljust(width), "accent")
-        out.info(name_cell + "  " + out.truncate(e["description"] or "", desc_w)
+        desc = out.truncate(e["description"] or "", desc_w)
+        out.info(name_cell + "  " + desc + " " * (desc_w - out.visible_len(desc))
                  + "  " + out.role(because, "muted"))
     if ai.available():
         picks = _ai_picks(stack, [r["entry"] for r in ranked[:20]])

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130/boost_skill_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.129
+Version: 1.2.130
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/docs/roadmap/items/audit-root-findings.md

@@ -2,15 +2,15 @@
 id: audit-root-findings
 board: code
 section: dx
-status: planned
+status: shipped
 category: CLI · Bug
 complexity: S
 impact: Low
 wow: 1
 note: EPIPE exits 120 with stderr noise; `help version` suggests verify; launcher gates at 3.9
 order: 245
-owner:
-pr:
+owner: loop/audit-root-closed
+pr: 827
 title: "boost ROOT: CLI audit findings (2026-08)"
 ---
 <b>EPIPE leaks past main's own handler.</b> <code>boost --help | (exec 0&lt;&amp;-; sleep 0.3)</code>
@@ -45,3 +45,13 @@ fixes touches a COMMANDS row, so <code>docs/commands.html</code> is unaffected.
 
 <br><br>Found by the 2026-08 CLI audit (clusters <code>broken-pipe-exit</code>,
 <code>help-routing-aliases</code>, <code>launcher-python-floor</code>); repro in the audit log.
+
+<br><br><b>Shipped in #827</b> (commit <code>22c9193</code>, batch train-17, 2026-09-08). The card
+was never closed. Re-measured on <code>main</code> at <code>bb1229f</code> on 2026-09-18:
+<code>--help</code>, <code>count</code>, <code>taps</code> and <code>--version</code> piped into
+<code>(exec 0&lt;&amp;-; sleep 0.3)</code> exit 0 with empty stderr, 3/3 runs each (<code>_seal_broken_stdout</code>
+plus <code>_route</code>'s <code>finally</code> flush).
+<code>boost help --help</code>, <code>help version</code> and <code>help help</code> all resolve;
+<code>boost --hepl</code> says <em>&ldquo;unknown option&rdquo;</em>, and <code>print_help</code> carries the Options line.
+The launcher gates at <code>(3, 12)</code>, pinned to <code>requires-python</code> by
+<code>tests/unit/test_launcher_python_floor.py</code>.

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/docs/roadmap/items/recommend-recomputes-its-columns-per-row.md

@@ -2,15 +2,15 @@
 id: recommend-recomputes-its-columns-per-row
 board: code
 section: planned
-status: planned
+status: shipped
 category: UX · Bug
 complexity: S
 impact: Low
 wow: 2
 note: cmd_recommend hand-rolls its rows and computes desc_w = max(cols - 2 - width - 2 - (l…
 order: 226
-owner:
-pr:
+owner: loop/recommend-columns
+pr: 881
 title: <code>boost recommend</code> sizes the description cell per row from that row's <code>because:</code> text, so neither column lines up
 ---
 <b>Measured.</b> At COLUMNS=100 the eight <code>boost recommend</code> rows truncate their descriptions at eight per-row widths spanning 34 to 54 columns — a 20-column swing, the widest cell 59% wider than the narrowest — because <code>desc_w</code> is recomputed inside the row loop from that row's own <code>because:</code> tag length (<code>boost_cli/commands/discovery.py:1062</code>); every rendered cell matched the predicted <code>desc_w</code> to the character and every description ended in an ellipsis, so this is column geometry, not natural description length.

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/docs/roadmap.html

@@ -2103,41 +2103,9 @@ Nothing else needed correcting: 7 starter registries, 962 items, 11 matches, the
       </article>
 
       <article class="cap rcard" id="recommend-recomputes-its-columns-per-row">
-        <div class="head"><span class="pill planned">Planned</span><span class="cat">UX · Bug</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">UX · Bug</span></div>
         <h3><code>boost recommend</code> sizes the description cell per row from that row's <code>because:</code> text, so neither column lines up</h3>
-        <p><b>Measured.</b> At COLUMNS=100 the eight <code>boost recommend</code> rows truncate their descriptions at eight per-row widths spanning 34 to 54 columns — a 20-column swing, the widest cell 59% wider than the narrowest — because <code>desc_w</code> is recomputed inside the row loop from that row's own <code>because:</code> tag length (<code>boost_cli/commands/discovery.py:1062</code>); every rendered cell matched the predicted <code>desc_w</code> to the character and every description ended in an ellipsis, so this is column geometry, not natural description length.
-
-<b>Reproduce it.</b>
-
-<code>cd &lt;repo&gt;</code><br>
-<code>export HOME=$TMPDIR/audit-dbi-sweep; mkdir -p "$HOME"; export BOOST_HOME=$TMPDIR/eval-home BOOST_NO_AI=1</code><br>
-<code>COLUMNS=100 ./boost recommend &gt; $TMPDIR/rec.txt 2&gt;&amp;1; cat $TMPDIR/rec.txt</code><br>
-<code>python3 - &lt;&lt;'PY'</code><br>
-<code>import re,os</code><br>
-<code>for line in open(os.environ["TMPDIR"]+"/rec.txt").read().splitlines()[1:]:</code><br>
-<code>    m=re.match(r"^  (\S+)\s+(.*?)\s\sbecause: (.*)$", line)</code><br>
-<code>    if m: print("desc_cell=%3d because_len=%2d row_len=%d %s"%(len(m.group(2)),len("because: "+m.group(3)),len(line),m.group(1)))</code><br>
-<code>PY</code><br>
-<code>sed -n '1061,1065p' boost_cli/commands/discovery.py</code><br>
-<code>sed -n '638,644p' boost_cli/core/output.py</code>
-
-<b>What adversarial verification corrected.</b> This card's numbers are the re-measured ones, not the ones first reported.
-
-The geometry numbers are all CORRECT — I re-derived every one (cells 46/38/46/42/54/34/46/54, because-lengths 19/27/19/23/11/31/19/11, spread 34..54 = 20 columns, row_len 100 on all 8 rows). Four wording/detail claims are wrong and must not ship as written:
-
-1. FALSE AS STATED: "<code>recommend</code> is also the one result table in the find group that does not go through the width-aware shared <code>out.table()</code>." <code>cmd_search</code> does not call <code>out.table()</code> either — it calls <code>out.search_layout()</code> at <code>boost_cli/commands/discovery.py:219</code> and renders through <code>SearchLayout</code>. <code>out.table()</code> in the find group is called by <code>cmd_index</code> (:857), <code>cmd_discover</code> (:954), <code>_browse_plain</code> (:1091, used by <code>browse</code>) and <code>cmd_trending</code> (:1925, :1949). The correct claim: <b><code>recommend</code> is the only find-group result renderer that uses neither <code>out.table()</code> nor a frozen <code>SearchLayout</code>.</b>
-
-2. TITLE OVERSTATES: "so neither column lines up" — and the evidence line "row_len 100 on all 8 — every row is right-flush, nothing is a column" contradicts itself. The <code>because:</code> column's RIGHT edge IS flush (col 100 at COLUMNS=100, col 120 at COLUMNS=120, on all 8 rows). What wanders is (a) the <code>because:</code> column's LEFT edge, 69..89, and (b) the description truncation point, 34..54.
-
-<b>What is NOT established.</b> Recorded because a card that overstates its own evidence is worse than no card.
-
-PROVENANCE (I checked; it partly softens the framing and the card should say so). <code>git blame</code> puts line 1062 in ff61dfeb, "fix(search): width-clamp &amp; truncate results — the D05 overflow fix (#33)", whose message states the intent: "clip each description to the remaining terminal width, so every result stays one scannable line <b>with its trailing tag (★ curated / because:) intact</b>." So preserving the trailing tag was deliberate; the per-row recompute is what that intent produced. The defect is drift, not carelessness: <code>search</code> was later rewritten onto the frozen <code>SearchLayout</code> (7f1a9a8d, "feat(ui): one design system across search and browse", #540) whose docstring states the opposite rule, and <code>recommend</code> was left on the 2026-07 scheme. Neither commit message nor any comment claims right-alignment of the reason tag as a design goal for <code>recommend</code>, so nothing in the tree defends the current shape — but a card that calls it an oversight without naming #33's stated intent is overclaiming.
-
-SCOPE OF MY REPRO. Measured only from the boost repo (detected stack: javascript, python · frameworks: pytest · also: ci) against the shared read-only 20-tap eval corpus at $TMPDIR/eval-home, with BOOST_NO_AI=1 (which suppresses the "AI picks" block — unrelated to the geometry). Which eight rows appear, and therefore the exact cell widths, depend on that corpus and that stack; the geometry itself is deterministic from :1062 and appears whenever the shown rows carry different <code>because:</code> sets.
-
-<b>Why it is worth doing.</b> <code>recommend</code> is the surface a new user hits before they know any skill names, and its output is a ragged block rather than a scannable list — the description truncation point jumps 20 columns row to row for reasons the reader cannot see (it is the length of the reason tag on the right). Two shipped design items (BOOST-D08, BOOST-D24) made <code>out.table()</code> width-aware for ~28 call sites; this one never adopted it, and the frozen-plan rule that <code>search</code> states in its own docstring is inverted here.
-
-<em>Found by an automated audit of retrieval/eval quality, the search &amp; browse surfaces, and first-run onboarding; every finding was then re-measured from scratch by an independent adversarial verifier whose instruction was to refute it. Verdict: <b>CORRECTED</b>. No fix is prescribed here — the measurement is the contribution.</em></p>
+        <p class="cardbody"><a class="writeup" href="https://github.com/jonnyeclectic/boost/blob/main/docs/roadmap/items/recommend-recomputes-its-columns-per-row.md">Write-up &middot; recommend-recomputes-its-columns-per-row.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Low</b></span>
@@ -6339,40 +6307,9 @@ untouched (no parser changes). Found by the 2026-08 CLI audit (cluster stale-pro
       </article>
 
       <article class="cap rcard" id="audit-root-findings">
-        <div class="head"><span class="pill planned">Planned</span><span class="cat">CLI · Bug</span></div>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">CLI · Bug</span></div>
         <h3>boost ROOT: CLI audit findings (2026-08)</h3>
-        <p><b>EPIPE leaks past main's own handler.</b> <code>boost --help | (exec 0&lt;&amp;-; sleep 0.3)</code>
-exits <b>120</b> with <em>&ldquo;Exception ignored on flushing sys.stdout: BrokenPipeError&rdquo;</em>
-&mdash; 3/3 runs, and <code>count</code>, <code>taps</code> and <code>--version</code> leak the same way.
-<code>cli.py:327-331</code> deliberately catches BrokenPipeError and returns 0, but stdout is never
-flushed inside the try, so any output that fits the stdio buffer raises at interpreter exit &mdash; and
-the <code>--help</code>/<code>--version</code> early returns (<code>cli.py:292-302</code>) sit before
-the try with no handler at all. Fix: cover the early returns, flush <code>sys.stdout</code> inside the
-try, and <code>os.dup2</code> a devnull fd over stdout in the handler so the exit flush cannot raise.
-
-<br><br><b>Help routing rejects main's own aliases.</b> <code>boost help --help</code> &rarr;
-<em>&ldquo;unknown command: --help / hint: did you mean: heal?&rdquo;</em> exit 2;
-<code>boost help version</code> suggests <em>verify</em> while <code>boost version</code> works;
-even <code>boost help help</code> fails. The aliases live only in <code>cli.main</code>
-(<code>cli.py:292-302</code>) and <code>print_command_help</code> resolves against COMMANDS alone,
-then difflib-guesses any token &mdash; dash-prefixed ones included. And <code>boost --help</code>
-documents none of the working global flags (<code>-V</code>/<code>-v</code>/<code>--debug</code>/<code>-q</code>).
-Fix: short-circuit the aliases in <code>print_command_help</code> before difflib, say
-<em>unknown option</em> for dash tokens in <code>_unknown</code> (<code>cli.py:231-236</code>), and add
-one dim Options line under Usage in <code>print_help</code>.
-
-<br><br><b>The <code>./boost</code> launcher still gates at Python 3.9</b> &mdash; tuple
-(<code>boost:27</code>), hint text (<code>boost:37</code>) and header comment (<code>boost:5</code>) all
-say 3.9+ while <code>pyproject.toml:22</code> requires <code>&gt;=3.12</code>. On a stock macOS whose
-only <code>python3</code> is 3.9 the launcher selects it and the user gets a SyntaxError from
-<code>core/workflows.py</code>'s match statements instead of the friendly hint. The shipped
-<em>python-floor-moves-to-312</em> item enumerated every floor touchpoint and missed this one. Fix:
-bump all three sites to 3.12 and add a unit test pinning the launcher's floor to
-<code>requires-python</code>. README already says 3.12+ &mdash; no doc change needed; none of the three
-fixes touches a COMMANDS row, so <code>docs/commands.html</code> is unaffected.
-
-<br><br>Found by the 2026-08 CLI audit (clusters <code>broken-pipe-exit</code>,
-<code>help-routing-aliases</code>, <code>launcher-python-floor</code>); repro in the audit log.</p>
+        <p class="cardbody"><a class="writeup" href="https://github.com/jonnyeclectic/boost/blob/main/docs/roadmap/items/audit-root-findings.md">Write-up &middot; audit-root-findings.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Low</b></span>

{boost_skill_cli-1.2.129 → boost_skill_cli-1.2.130}/tests/functional/test_cli_discovery.py

@@ -1131,6 +1131,19 @@ class TestRecommend:
         assert "because: pytest, python" in r.out
         assert "because: javascript, react" in r.out
 
+    @pytest.mark.parametrize("cols", ["60", "100"])
+    def test_rows_share_one_column_plan(self, boost, stack_tap, react_project,
+                                        monkeypatch, cols):
+        # The description width used to be sized per row from that row's own
+        # `because:` tag, so the clip point swung row to row and the reason
+        # column started wherever each description happened to end.
+        monkeypatch.setenv("COLUMNS", cols)
+        r = boost("recommend", "--path", react_project)
+        rows = [ln for ln in r.out.splitlines() if "because: " in ln]
+        reasons = {ln.split("because: ")[1] for ln in rows}
+        assert len(rows) >= 2 and len({len(x) for x in reasons}) >= 2, rows
+        assert len({ln.index("because: ") for ln in rows}) == 1, rows
+
     def test_json_purity(self, boost, stack_tap, react_project):
         r = boost("recommend", "--path", react_project, "--json")
         data = json.loads(r.out)