boost-skill-cli 1.2.126__tar.gz → 1.2.128__tar.gz

{boost_skill_cli-1.2.126/boost_skill_cli.egg-info → boost_skill_cli-1.2.128}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.126
+Version: 1.2.128
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0
@@ -453,7 +453,7 @@ the C4 diagrams in [`docs/architecture/`](docs/architecture/README.md).
 | Registry (Taps) | tap · untap · taps · outdated · catalog |
 | Intelligence | chat · distill · simulate · infer · absorb · evolve · context · focus · impact |
 | Quality & Health | doctor · lint · audit · verify · drift · test · fingerprint · quarantine · decay · heal · conflict · changelog · attest · health · trust |
-| Configuration | config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
+| Configuration | quickstart · config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
 | Team & Collaboration | cohort · profile · protocol · pulse · replay · who |
 
 The AI-assisted commands (`search --smart`, `explain`, `distill`, `infer`,

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/README.md

@@ -411,7 +411,7 @@ the C4 diagrams in [`docs/architecture/`](docs/architecture/README.md).
 | Registry (Taps) | tap · untap · taps · outdated · catalog |
 | Intelligence | chat · distill · simulate · infer · absorb · evolve · context · focus · impact |
 | Quality & Health | doctor · lint · audit · verify · drift · test · fingerprint · quarantine · decay · heal · conflict · changelog · attest · health · trust |
-| Configuration | config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
+| Configuration | quickstart · config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
 | Team & Collaboration | cohort · profile · protocol · pulse · replay · who |
 
 The AI-assisted commands (`search --smart`, `explain`, `distill`, `infer`,

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/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.126'
-__version_tuple__ = version_tuple = (1, 2, 126)
+__version__ = version = '1.2.128'
+__version_tuple__ = version_tuple = (1, 2, 128)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/boost_cli/commands/configuration.py

@@ -1527,8 +1527,9 @@ def _tool_install(args: dict):
              % (res.name, entry.get("version", "?"), entry["tap"], res.dest),
              "linked agents: %s" % (", ".join(res.linked) or "none")]
     # Without this an agent that reads the canonical store — Gemini CLI — sees
-    # only "linked agents: claude-code, windsurf, cursor", concludes the skill
-    # did not reach *it*, and goes back to reconstructing the work by hand.
+    # only "linked agents: claude-code, windsurf, cursor, antigravity",
+    # concludes the skill did not reach *it*, and goes back to reconstructing
+    # the work by hand.
     # That is the exact failure this tool exists to prevent, so the line says
     # plainly that the skill is already usable.
     if res.native:
@@ -1772,16 +1773,17 @@ REGISTRY.register(
     "boost_install",
     "Turn a skill you found with boost_search into permanent capability: copied "
     "into the canonical store and wired into every agent you have enabled, in "
-    "one step — Claude Code, Cursor and Windsurf by symlink, Gemini CLI by "
-    "reading that same store directly. Prefer it to pasting instructions into "
+    "one step — Claude Code, Cursor, Windsurf and Antigravity CLI by "
+    "symlink, Gemini CLI by reading that same store directly. Prefer it to "
+    "pasting instructions into "
     "a prompt, which lasts one "
     "session and helps nobody else: an installed skill is version-tracked, "
     "survives restarts, updates cleanly, and your team can install the "
     "identical thing by name. Worth knowing before you call it: what happens "
     "on disk depends on the kind, which boost_search marks on every hit. A "
     "skill is copied into the store and linked out. A WORKFLOW is rendered "
-    "into each agent's commands or agents directory, in that agent's own "
-    "format. A RULE copies nothing into the store — it becomes part of your "
+    "into the commands or agents directory of each agent that takes "
+    "workflows, in that agent's own format. A RULE copies nothing into the store — it becomes part of your "
     "agent's standing instructions (a managed block in its context file, or a "
     "file in its rules directory), which is the more invasive change because "
     "it applies to every session afterwards, not just when you reach for it. "

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/boost_cli/core/output.py

@@ -72,11 +72,23 @@ def use_color(stream=None) -> bool:
     return hasattr(stream, "isatty") and stream.isatty()
 
 
+def _span(code: str, text: str) -> str:
+    """``code + text + RESET``, applied to each line on its own.
+
+    One span across a newline opens the style on line 1 and closes it at the
+    end of the last: a reader that stops early (``… 2>&1 | head -2``) is left
+    inside an unterminated style, and lines 2+ carry no code of their own. A
+    multi-line hint from `err` did exactly that. Every painter below routes
+    through here, so no emitter can reintroduce it.
+    """
+    return "\n".join(code + line + RESET for line in text.split("\n"))
+
+
 def c(text: str, *styles: str) -> str:
     """Wrap text in the given SGR styles + RESET; plain when color is off."""
     if not styles or not use_color():
         return text
-    return "".join(styles) + text + RESET
+    return _span("".join(styles), text)
 
 
 # --------------------------------------------------------------------------- #
@@ -139,7 +151,7 @@ def aurora(text: str, name: str, stream=None) -> str:
         return text
     triple, fallback = _AURORA[name]
     code = rgb(*triple) if level == 2 else fallback
-    return code + text + RESET
+    return _span(code, text)
 
 
 # --------------------------------------------------------------------------- #
@@ -171,8 +183,9 @@ def role(text: str, name: str, bold: bool = False, stream=None) -> str:
     if color_level(stream) == 0:
         return text
     kind, value = ROLES[name]
-    painted = aurora(text, value, stream) if kind == "aurora" else value + text + RESET
-    return BOLD + painted if bold else painted
+    painted = aurora(text, value, stream) if kind == "aurora" else _span(value, text)
+    # Per line too: BOLD before line 1 alone would leave lines 2+ regular.
+    return "\n".join(BOLD + ln for ln in painted.split("\n")) if bold else painted
 
 
 def _lerp(a, b, t: float):

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128/boost_skill_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.126
+Version: 1.2.128
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0
@@ -453,7 +453,7 @@ the C4 diagrams in [`docs/architecture/`](docs/architecture/README.md).
 | Registry (Taps) | tap · untap · taps · outdated · catalog |
 | Intelligence | chat · distill · simulate · infer · absorb · evolve · context · focus · impact |
 | Quality & Health | doctor · lint · audit · verify · drift · test · fingerprint · quarantine · decay · heal · conflict · changelog · attest · health · trust |
-| Configuration | config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
+| Configuration | quickstart · config · clean · compact · create · policy · onboard · completions · schedule · serve · mcp · hooks · bmad · self-update |
 | Team & Collaboration | cohort · profile · protocol · pulse · replay · who |
 
 The AI-assisted commands (`search --smart`, `explain`, `distill`, `infer`,

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/docs/roadmap/items/err-multiline-hint-colours-across-the-newline.md

@@ -2,15 +2,15 @@
 id: err-multiline-hint-colours-across-the-newline
 board: code
 section: planned
-status: planned
+status: shipped
 category: UX · Bug
 complexity: S
 impact: Low
 wow: 2
 note: err() joins a multi-line hint's lines and then wraps the whole joined string in one c…
 order: 207
-owner:
-pr:
+owner: loop/err-hint-per-line
+pr: 877
 title: <code>out.err</code>'s multi-line hint is coloured as one span, so line 1 ends with no RESET and lines 2+ carry no start code
 ---
 <b>Measured.</b> With colour forced, a three-line hint from <code>err()</code> emits an opening <code>ESC[2m</code> on hint line 1 that is never terminated, two bare continuation lines carrying no SGR at all, and one closing <code>ESC[0m</code> at visible column 98 of the last line — so <code>boost index 2&gt;&amp;1 | head -2</code> under <code>CLICOLOR_FORCE</code> hands the consumer a stream ending inside an unterminated dim span; output.py:252 wraps the newline-joined body in a single <code>c(..., DIM)</code>, colouring first and splitting after.

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/docs/roadmap/items/mcp-install-description-omits-antigravity.md

@@ -2,16 +2,16 @@
 id: mcp-install-description-omits-antigravity
 board: code
 section: planned
-status: planned
+status: shipped
 category: Interop
 complexity: S
 impact: Low
 wow: 2
 note: boost_install's description says installs are "wired into every agent you have enable…
 order: 216
-owner:
-pr:
-title: boost_install's description enumerates four of the five enabled agent targets, and gives Antigravity the one mechanism it does not use
+owner: loop/mcp-install-agents
+pr: 875
+title: boost_install's description enumerates four of the five enabled agent targets and omits Antigravity CLI, the fourth linking agent
 ---
 <b>Measured.</b> The enumeration is provably stale rather than deliberately partial: the string was written in PR #442 on 2026-08-03, when boost had four agent targets, and Antigravity CLI landed as a FIFTH -- and a LINKING -- target in PR #602 on 2026-08-30 (<code>git merge-base --is-ancestor</code> confirms #442 precedes #602), and the string has not been touched since; today <code>enabled_agents()</code> returns 5 and <code>linking_agents()</code> returns 4 while the description names 4 and 3 of them respectively, and <code>boost_install</code> is the only one of the seven MCP tool descriptions that names any agent at all -- so the fix is a single string.
 

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/docs/roadmap/items/readme-81-command-table-lists-80-omits-quickstart.md

@@ -2,15 +2,15 @@
 id: readme-81-command-table-lists-80-omits-quickstart
 board: code
 section: planned
-status: planned
+status: shipped
 category: Quality · Docs
 complexity: S
 impact: Low
 wow: 2
 note: README.md:389 heads a table "## 81 commands, organized into 8 groups", but the eight …
 order: 224
-owner:
-pr:
+owner: loop/readme-command-table
+pr: 876
 title: README's "81 commands" table enumerates only 80 — the missing one is <code>quickstart</code>, the README's own first command
 ---
 <b>Measured.</b> Commit dd2fba07 (PR #594, "publish prebuilt vectors where a new user can reach them") added <code>("quickstart", "cfg", ...)</code> to cli.py's COMMANDS and changed README.md:389 from "## 80 commands" to "## 81 commands" — and left README.md:404's Configuration row at its 13 names, so the README has advertised 81 commands while listing 80 ever since, with the whole test suite green, because <code>test_marketing_counts.py</code> asserts the integer and <code>test_docsite_chrome.py:63-71</code> pins the enumeration only for <code>docs/index.html</code>.
@@ -41,7 +41,6 @@ The defect itself reproduces exactly as stated — README.md:389 heads "81 comma
 
 2. SOFT — "the one <code>docs/semantic-search.md</code> points at three times". Three is only right if you count fenced-code invocations (lines 30, 63, 64). The string <code>boost quickstart</code> appears 4 times (30, 33, 63, 64) and <code>quickstart</code> appears on 7 lines (+1, 83, 89). Say "four <code>boost quickstart</code> references across seven mentions" or drop the number.
 
-3.
 
 <b>What is NOT established.</b> Recorded because a card that overstates its own evidence is worse than no card.
 
@@ -51,6 +50,6 @@ WHY Low, not Med. The finder's Med overstates it. <code>quickstart</code> is nam
 
 WHY IT IS STILL WORTH A CARD. The value is structural, not the symptom: of the three enumerations of the command surface, <code>docs/index.html</code> is pinned name-by-name against COMMANDS (test_docsite_chrome.py:63-71), <code>docs/commands.html</code> is generated from COMMANDS and gated by <code>build_command_reference.py --check</code>, and README's table is hand-maintained with only its integer asserted. PR #594 is the proof that the gap is live rather than theoretical.
 
-<b>Why it is worth doing.</b> The README table is the only place a reader browses the command surface without running the CLI, and the one command it drops is the one the same file's hero block makes step 2 of onboarding. A user who reads the table sees no quickstart, and a user who reads the hero sees a command the table says does not exist. The count and the list also contradict each other in the same heading, which is exactly the class of drift test_marketing_counts.py was written for — it just guards the integer and not the enumeration.
+<b>Why it is worth doing.</b> The README table is the command surface a reader browses in-file, and the one enumeration of the three that nothing pinned; the one command it dropped is the one the same file's hero block makes step 2 of onboarding. A user who reads the table sees no quickstart, and a user who reads the hero sees a command the table says does not exist. The count and the list also contradict each other in the same heading, which is exactly the class of drift test_marketing_counts.py was written for — it just guards the integer and not the enumeration.
 
 <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>

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/docs/roadmap.html

@@ -1294,42 +1294,9 @@ PRIOR DISCLOSURE (the finder declared it, and I confirmed it): docs/roadmap/item
       </article>
 
       <article class="cap rcard" id="err-multiline-hint-colours-across-the-newline">
-        <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>out.err</code>'s multi-line hint is coloured as one span, so line 1 ends with no RESET and lines 2+ carry no start code</h3>
-        <p><b>Measured.</b> With colour forced, a three-line hint from <code>err()</code> emits an opening <code>ESC[2m</code> on hint line 1 that is never terminated, two bare continuation lines carrying no SGR at all, and one closing <code>ESC[0m</code> at visible column 98 of the last line — so <code>boost index 2&gt;&amp;1 | head -2</code> under <code>CLICOLOR_FORCE</code> hands the consumer a stream ending inside an unterminated dim span; output.py:252 wraps the newline-joined body in a single <code>c(..., DIM)</code>, colouring first and splitting after.
-
-<b>Reproduce it.</b>
-
-<code>cd &lt;repo&gt;</code><br>
-<code>BOOST_COLOR=always .venv/bin/python -c "</code><br>
-<code>from boost_cli.core import output as out</code><br>
-<code>out.err('gh api failed', 'HTTP 401: Bad credentials\nTry authenticating with:  gh auth login\ngh: To use GitHub CLI in a GitHub Actions workflow, set the GH_TOKEN environment variable.')</code><br>
-<code>" 2&gt;&amp;1 | /bin/cat -v</code><br>
-<code># and the live call path (single-line tail in this sandbox, but proves err() is reached):</code><br>
-<code>export HOME=$TMPDIR/audit-output-formatting; export BOOST_HOME=$HOME/.boost; mkdir -p "$HOME"</code><br>
-<code>GH_TOKEN=deadbeefdeadbeefdeadbeefdeadbeefdeadbeef BOOST_COLOR=always ./boost index 2&gt;&amp;1 | head -3 | /bin/cat -v</code>
-
-<b>What adversarial verification corrected.</b> This card's numbers are the re-measured ones, not the ones first reported.
-
-The core defect and its byte shape reproduce exactly. Five stated details are wrong:
-
-1. "<code>empty_state._block</code> (output.py:559-561)" — WRONG LINES. 559-561 is docstring prose. <code>_block</code> is defined at output.py:569 and its per-line colouring is at 571-572.
-
-2. "the lone <code>^[[0m</code> is 90 columns into line 4" — WRONG. It sits at visible column 98. 90 is the length of the message text alone; the line also carries the 8-column <code> hint: </code> alignment indent.
-
-3. "<code>err</code> is the one emitter that does not [colour per line]" — REFUTED. Handed a string containing a literal newline with <code>wrap</code> off, <code>dim()</code>, <code>warn()</code> and <code>empty_state()</code> all emit the identical straddling span (measured above). <code>empty_state._block</code> only colours per line of its *wrap* output; with <code>wrap=False</code> <code>body = [text]</code>, so the newline sits inside one <code>c(..., DIM)</code>. What is actually unique about <code>err</code> is that it is the only emitter whose docstring documents accepting embedded newlines and the only one with a live multi-line caller (<code>gh_failure_hint</code>); I grepped every <code>out.warn(</code> / <code>out.dim(</code> / <code>out.empty_state(</code> call site and none passes a <code>\n</code>-bearing string (all joins use ", " or "; ").
-
-4. "<code>boost index 2&gt;&amp;1 | head -2</code> hands the shell an opening SGR with no close" — WRONG without a stated precondition.
-
-<b>What is NOT established.</b> Recorded because a card that overstates its own evidence is worse than no card.
-
-Not carded — I re-checked independently. Grepped all <code>^title:</code> lines for colour/ANSI/reset/escape/SGR/dim/hint terms and read the four plausible cards in full: <code>long-hints-overflow-narrow-panes.md</code> (line width, not escape spans), <code>BOOST-D04.md</code> (semantic colour roles), <code>BOOST-D18.md</code> (empty-state/hint styling consistency), <code>BOOST-D27.md</code> (its three named remaining wrap-law gaps are <code>dim()</code>'s embedded indent, <code>empty_state()</code> adoption, and <code>truncate()</code>/<code>search_layout()</code> wide-char width — <code>err()</code> is not among them). <code>grep -ril 'unterminated|RESET|SGR|escape code' docs/roadmap/items/</code> returned 11 files, none about <code>err()</code>.
-
-Scope of my repro, and what a card must not overclaim: - No corpus was needed; this is a pure library-call repro plus one live CLI path. The 20-tap eval corpus at $TMPDIR/eval-home is irrelevant here and I did not touch it. The <code>./boost index</code> run used its own disposable HOME. - I could not produce the 3-line <code>gh</code> tail live either: the sandbox proxy's TLS failure is a single line, so the live run only proves <code>err()</code> is reached with a <code>gh</code>-sourced hint, not that a 3-line tail occurred. The multi-line shape is proven by the direct call, which is what the finder also did. - A card must state the forced-colour precondition. In an ordinary interactive run the bytes ARE emitted (stdout is a TTY), but every terminal I know carries DIM across a newline, so it renders correctly — the finding concedes this. The only consumer that sees breakage is a line-oriented reader under <code>BOOST_COLOR=always</code> / <code>CLICOLOR_FORCE</code> (CI).
-
-<b>Why it is worth doing.</b> Most terminals carry DIM across a newline, so it usually *looks* right — the harm is to anything reading a line at a time. <code>boost index 2&gt;&amp;1 | head -2</code> hands the shell an opening SGR with no close, dimming everything printed afterwards; and because the hint goes to stderr, any stdout written between hint lines lands inside the unterminated dim run. The module already knows the correct shape and uses it twice — <code>empty_state._block</code> (output.py:559-561) and <code>table</code>'s header cells (output.py:906-908, with the comment "a whole-line wrap would be cancelled at the first separator's RESET") both colour per line. <code>err</code> is the one emitter that does not.
-
-<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/err-multiline-hint-colours-across-the-newline.md">Write-up &middot; err-multiline-hint-colours-across-the-newline.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Low</b></span>
@@ -1733,47 +1700,9 @@ SCOPE LIMITS of my repro, all of which a card author must respect: - The 188/3/4
       </article>
 
       <article class="cap rcard" id="mcp-install-description-omits-antigravity">
-        <div class="head"><span class="pill planned">Planned</span><span class="cat">Interop</span></div>
-        <h3>boost_install's description enumerates four of the five enabled agent targets, and gives Antigravity the one mechanism it does not use</h3>
-        <p><b>Measured.</b> The enumeration is provably stale rather than deliberately partial: the string was written in PR #442 on 2026-08-03, when boost had four agent targets, and Antigravity CLI landed as a FIFTH -- and a LINKING -- target in PR #602 on 2026-08-30 (<code>git merge-base --is-ancestor</code> confirms #442 precedes #602), and the string has not been touched since; today <code>enabled_agents()</code> returns 5 and <code>linking_agents()</code> returns 4 while the description names 4 and 3 of them respectively, and <code>boost_install</code> is the only one of the seven MCP tool descriptions that names any agent at all -- so the fix is a single string.
-
-<b>Reproduce it.</b>
-
-<code>cd &lt;repo&gt;</code><br>
-<code>rm -rf $TMPDIR/audit-mcp-f4 $TMPDIR/audit-mcp-f4-fix</code><br>
-<code>export HOME=$TMPDIR/audit-mcp-f4 &amp;&amp; export BOOST_HOME=$HOME/.boost</code><br>
-<code>export BOOST_NO_AI=1 &amp;&amp; export BOOST_ASSUME_YES=1 &amp;&amp; mkdir -p "$HOME"</code><br>
-<code>.venv/bin/python tests/make_fixture.py $TMPDIR/audit-mcp-f4-fix &gt;/dev/null</code><br>
-<code>./boost tap $TMPDIR/audit-mcp-f4-fix &gt;/dev/null 2&gt;&amp;1</code><br>
-<code>.venv/bin/python -c '</code><br>
-<code>from boost_cli.commands import configuration as c</code><br>
-<code>from boost_cli.core import agents</code><br>
-<code>print("linking_agents -&gt;", list(agents.linking_agents()))</code><br>
-<code>print("enabled_agents -&gt;", list(agents.enabled_agents()))</code><br>
-<code>txt,_ = c.REGISTRY.call("boost_install", {"name":"brainstorming"})</code><br>
-<code>print(txt.splitlines()[1])</code><br>
-<code>d={s["name"]:s["description"] for s in c.REGISTRY.specs()}</code><br>
-…
-
-<b>What adversarial verification corrected.</b> This card's numbers are the re-measured ones, not the ones first reported.
-
-Two stated details are wrong; the defect itself is real.
-
-1. THE TITLE OVER-CLAIMS. "gives Antigravity the one mechanism it does not use" states something about the text that the text does not do. The description does not ASSIGN Antigravity any mechanism -- it omits Antigravity entirely (verified: <code>antigravity in any description: False</code>, and 0 hits for 'antigravity' in both mcp.py and configuration.py). The finder's BODY is careful and correct ("the only claim an Antigravity reader can map onto itself"), but that is an inference about how a reader would map itself, not a measured property of the string. A card title ships literally. Correct title: "boost_install's description enumerates four of the five enabled agent targets and omits Antigravity CLI, the fourth linking agent."
-
-2. THE FINDER'S GREP WAS MALFORMED, so its cited "no matches" is not reproducible as meant. <code>grep -n 'Windsurf|Cursor|symlink|gemini' tests/unit/test_mcp.py</code> is BASIC grep -- the pipes are literal characters, so it could only ever match a line containing that exact string. With <code>grep -inE</code> the file has FIVE matches (lines 493, 571, 623, 687, 738). The CONCLUSION survives: I read all five and none pins boost_install's agent enumeration (they are Gemini-CLI-instructions-delivery comments and one tap name).
-
-<b>What is NOT established.</b> Recorded because a card that overstates its own evidence is worse than no card.
-
-SCOPE OF MY REPRO: fully in scope, no caveat needed. The defect is a static source string plus two pure functions over config defaults, so the 20-tap eval corpus is irrelevant here and I never touched it. Antigravity's <code>enabled</code> comes from config defaults (agents.py:25, <code>bool(spec.get("enabled", True))</code>), not from <code>~/.gemini</code> existing, so the repro does not depend on any Antigravity install being present -- I got all five agents from a bare disposable HOME with only the test fixture tapped.
-
-BONUS STALENESS THE FINDER MISSED, same cause and same PR: the explanatory comment at boost_cli/commands/configuration.py:1467-1468 quotes the output as <code>only "linked agents: claude-code, windsurf, cursor"</code> -- a three-agent list. The real line now emits four (<code>linked agents: claude-code, windsurf, cursor, antigravity</code>, per my repro). If the card ships a fix, that comment should be corrected in the same edit or it becomes a second stale artifact of #602.
-
-WHY THIS IS THE HOST WHERE IT BITES (supports relevance, already established in-repo, not something I had to infer): <code>core/mcphost.py:13,86,94</code> registers boost with <code>agy</code> -- Antigravity CLI is its third MCP host -- so an Antigravity agent genuinely reads this exact description. And the design comment at configuration.py:1575-1582 states that on Gemini-family hosts the function declarations are "the only boost text reliably in context at the moment an agent chooses a tool" (server <code>instructions</code> land in the trust-gated GEMINI.md memory tier).
-
-<b>Why it is worth doing.</b> The harm is the wrong mechanism, not the missing name. The install reply already tells Gemini-family users that a skill is usable without linking, and the comment above that line (configuration.py:1466-1470) says why it exists: an agent that does not see itself in the linked list "concludes the skill did not reach *it*, and goes back to reconstructing the work by hand." An Antigravity CLI agent reading only the description gets the inverse error — the sole Gemini-family claim on offer says the store is read directly, which for Antigravity is false, so a pre-install answer to "will this reach me" is wrong in the direction the surface was written to avoid.
-
-<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>
+        <div class="head"><span class="pill shipped">Shipped</span><span class="cat">Interop</span></div>
+        <h3>boost_install's description enumerates four of the five enabled agent targets and omits Antigravity CLI, the fourth linking agent</h3>
+        <p class="cardbody"><a class="writeup" href="https://github.com/jonnyeclectic/boost/blob/main/docs/roadmap/items/mcp-install-description-omits-antigravity.md">Write-up &middot; mcp-install-description-omits-antigravity.md</a></p>
         <div class="meta">
           <span class="m">Complexity <b>S</b></span>
           <span class="m">Impact <b>Low</b></span>
@@ -2121,49 +2050,9 @@ FIX SCOPE IS WIDER THAN THE FINDING SAYS: because <code>pkg.py:941</code> (<code
       </article>
 
       <article class="cap rcard" id="readme-81-command-table-lists-80-omits-quickstart">
-        <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>README's "81 commands" table enumerates only 80 — the missing one is <code>quickstart</code>, the README's own first command</h3>
-        <p><b>Measured.</b> Commit dd2fba07 (PR #594, "publish prebuilt vectors where a new user can reach them") added <code>("quickstart", "cfg", ...)</code> to cli.py's COMMANDS and changed README.md:389 from "## 80 commands" to "## 81 commands" — and left README.md:404's Configuration row at its 13 names, so the README has advertised 81 commands while listing 80 ever since, with the whole test suite green, because <code>test_marketing_counts.py</code> asserts the integer and <code>test_docsite_chrome.py:63-71</code> pins the enumeration only for <code>docs/index.html</code>.
-
-<b>Reproduce it.</b>
-
-<code>cd &lt;repo&gt;</code><br>
-<code>.venv/bin/python - &lt;&lt;'PY'</code><br>
-<code>import re, sys</code><br>
-<code>sys.path.insert(0,'.')</code><br>
-<code>from boost_cli.cli import COMMANDS</code><br>
-<code>names = {n for n,_,_,_ in COMMANDS}</code><br>
-<code>readme = open('README.md').read()</code><br>
-<code>rows = re.findall(r'^\| ([A-Z][^|]*?) \| (.+?) \|$', readme, re.M)</code><br>
-<code>tbl = {g.strip(): [c.strip() for c in cmds.split('·')] for g, cmds in rows if '·' in cmds}</code><br>
-<code>listed = {c for v in tbl.values() for c in v}</code><br>
-<code>print("README table total:", sum(len(v) for v in tbl.values()), "COMMANDS:", len(names))</code><br>
-<code>print("missing from README table:", sorted(names - listed))</code><br>
-<code>PY</code><br>
-<code>grep -n '81 commands' README.md</code><br>
-<code>./boost --help | grep -n 'quickstart'</code>
-
-<b>What adversarial verification corrected.</b> This card's numbers are the re-measured ones, not the ones first reported.
-
-The defect itself reproduces exactly as stated — README.md:389 heads "81 commands", the eight rows at README.md:398-405 enumerate 80, and the set difference against <code>cli.py</code>'s COMMANDS is exactly <code>{'quickstart'}</code>. Two stated facts are wrong:
-
-1. LOAD-BEARING — <code>why_it_matters</code> says "The README table is the only place a reader browses the command surface without running the CLI." False. <code>docs/commands.html</code> (4 quickstart hits) and <code>docs/index.html</code> (3 hits, including the pinned <code>["quickstart","cfg",...]</code> row) both enumerate the full surface, and README.md:391-393 links both of them two lines ABOVE the table. A card must not ship that sentence. The honest framing: the README table is the surface a reader browses in-file, and the one enumeration of the three that nothing pins.
-
-2. SOFT — "the one <code>docs/semantic-search.md</code> points at three times". Three is only right if you count fenced-code invocations (lines 30, 63, 64). The string <code>boost quickstart</code> appears 4 times (30, 33, 63, 64) and <code>quickstart</code> appears on 7 lines (+1, 83, 89). Say "four <code>boost quickstart</code> references across seven mentions" or drop the number.
-
-3.
-
-<b>What is NOT established.</b> Recorded because a card that overstates its own evidence is worse than no card.
-
-SCOPE OF MY REPRO: entirely static — README.md, boost_cli/cli.py, docs/*.html, the two test files, and <code>./boost --help</code> from the repo checkout. No corpus, tap set or network was needed, so nothing here is contingent on the 20-tap eval corpus or on which registries ship by default. Fully settled.
-
-WHY Low, not Med. The finder's Med overstates it. <code>quickstart</code> is named in README.md five other times (line 23 hero, 142, 145, 151, 176), in <code>./boost --help</code>, and in both generated doc pages that the README links immediately above the table. The user-visible cost is one missing name out of 81 in one browsable list; nothing breaks and no one is misinformed about whether the command exists. The finder's line "a user who reads the hero sees a command the table says does not exist" is rhetorical — the table omits, it does not deny.
-
-WHY IT IS STILL WORTH A CARD. The value is structural, not the symptom: of the three enumerations of the command surface, <code>docs/index.html</code> is pinned name-by-name against COMMANDS (test_docsite_chrome.py:63-71), <code>docs/commands.html</code> is generated from COMMANDS and gated by <code>build_command_reference.py --check</code>, and README's table is hand-maintained with only its integer asserted. PR #594 is the proof that the gap is live rather than theoretical.
-
-<b>Why it is worth doing.</b> The README table is the only place a reader browses the command surface without running the CLI, and the one command it drops is the one the same file's hero block makes step 2 of onboarding. A user who reads the table sees no quickstart, and a user who reads the hero sees a command the table says does not exist. The count and the list also contradict each other in the same heading, which is exactly the class of drift test_marketing_counts.py was written for — it just guards the integer and not the enumeration.
-
-<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/readme-81-command-table-lists-80-omits-quickstart.md">Write-up &middot; readme-81-command-table-lists-80-omits-quickstart.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.126 → boost_skill_cli-1.2.128}/tests/unit/test_marketing_counts.py

@@ -59,6 +59,22 @@ class TestCommandCount:
         assert counts == {_command_count()}, \
             "README states conflicting command counts: %s" % sorted(counts)
 
+    def test_readme_table_lists_exactly_the_registry(self):
+        # The integer above was guarded; the enumeration under it was not, so
+        # #594 moved the heading to 81 and the table stayed at 80 (quickstart,
+        # the README's own onboarding step, was the one missing). Pin the rows
+        # by group title and order, the way docs/index.html's list is pinned.
+        from boost_cli.cli import GROUPS
+        rows = {group: [c.strip() for c in cmds.split("·")]
+                for group, cmds in re.findall(
+                    r"^\| ([A-Z][^|]*?) \| (.+?) \|$", README, re.M)
+                if "·" in cmds}
+        want: dict[str, list[str]] = {}
+        for name, group, _module, _summary in COMMANDS:
+            want.setdefault(GROUPS[group][1], []).append(name)
+        assert rows == want
+        assert list(rows) == list(want)       # the groups' order too
+
     def test_landing_page_counts_agree(self):
         counts = {int(n) for n in re.findall(r"(\d+)\s+commands", INDEX)}
         assert counts == {_command_count()}, \

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/tests/unit/test_mcp.py

@@ -438,6 +438,26 @@ class TestInstructionsCoverAllThreeKinds:
                 for s in configuration.REGISTRY.specs()}["boost_install"]
         assert "rule" in desc.lower()
 
+    def test_install_description_names_each_default_agent_by_its_mechanism(
+            self):
+        # Written when boost had four targets, and Antigravity CLI — a fifth,
+        # and a linking one — went unnamed for weeks after it landed. It is
+        # also an MCP host (`agy`), so it reads this very string. Derived from
+        # the defaults, so a sixth target fails here instead of going unsaid.
+        from boost_cli.commands import configuration
+        from boost_cli.core import agents, config
+        desc = {s["name"]: s["description"]
+                for s in configuration.REGISTRY.specs()}["boost_install"]
+        linked, rest = desc.split(" by symlink, ", 1)
+        native = rest.split(" by reading that same store directly", 1)[0]
+        for name, spec in config.DEFAULTS["agents"].items():
+            if not spec.get("enabled", True):
+                continue
+            links = spec.get("links_skills", True)
+            side, other = (linked, native) if links else (native, linked)
+            label = agents.display_name(name)
+            assert label in side and label not in other, (name, desc)
+
 
 class TestInstructionsBoundIsATestNotAFeeling:
     """"Non-trivial" is only usable if it decides itself.

{boost_skill_cli-1.2.126 → boost_skill_cli-1.2.128}/tests/unit/test_mutation_hardening.py

@@ -163,6 +163,34 @@ class TestForcedColorOutput:
             "\033[31m\033[1mError: \033[0mboom\n"
             "\033[2m  hint: try x\033[0m\n")
 
+    def test_err_multiline_hint_is_coloured_per_line(self, capsys):
+        # One span over the joined body opened DIM on line 1 and closed it on
+        # the last, so `| head -2` ended inside an unterminated dim run.
+        out.err("boom", hint="one\ntwo\nthree")
+        assert capsys.readouterr().err == (
+            "\033[31m\033[1mError: \033[0mboom\n"
+            "\033[2m  hint: one\033[0m\n"
+            "\033[2m        two\033[0m\n"
+            "\033[2m        three\033[0m\n")
+
+    def test_every_painter_styles_each_line_on_its_own(self):
+        # The same one-span shape in any painter reopens the bug `err` had;
+        # they all route through `_span`, which these pin per path.
+        y = "\033[38;2;250;204;21m"               # warn -> aurora yellow
+        assert out.c("a\nb", out.DIM) == (
+            "\033[2ma\033[0m\n\033[2mb\033[0m")
+        assert out.aurora("a\nb", "yellow") == (
+            y + "a\033[0m\n" + y + "b\033[0m")
+        assert out.role("a\nb", "muted") == (         # the sgr branch
+            "\033[2ma\033[0m\n\033[2mb\033[0m")
+        # A space in the text: splitting the painted span on whitespace
+        # instead of "\n" would bold each word, not each line.
+        assert out.role("a b\nc", "warn", bold=True) == (
+            "\033[1m" + y + "a b\033[0m\n\033[1m" + y + "c\033[0m")
+        # A single line is byte-identical to the old code + text + RESET.
+        assert out.role("a", "warn", bold=True) == "\033[1m" + y + "a\033[0m"
+        assert out.c("", out.DIM) == "\033[2m\033[0m"
+
     def test_heading_exact_ansi(self, capsys):
         # Aurora cyan marker (truecolor under forced color) + bold title.
         out.heading("Section")