boost-skill-cli 1.2.111__tar.gz → 1.2.112__tar.gz

{boost_skill_cli-1.2.111/boost_skill_cli.egg-info → boost_skill_cli-1.2.112}/PKG-INFO

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

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/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.111'
-__version_tuple__ = version_tuple = (1, 2, 111)
+__version__ = version = '1.2.112'
+__version_tuple__ = version_tuple = (1, 2, 112)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/commands/bmad.py

@@ -16,7 +16,7 @@ of the thinking lives in :mod:`boost_cli.core.bmad`; this module is glue.
 
     boost bmad on                          # <- the one command. global.
     boost bmad off                         # remove hooks + boost-written personas
-    boost bmad personas                    # the roster, and whether it is installed
+    boost bmad personas                    # the roster + whether installed, both scopes
     boost bmad route [PROMPT] [--plain]    # hook target; pipeable for debugging
 
 **The full method** is `boost bmad install`, unchanged: it delegates to the
@@ -100,7 +100,8 @@ def cmd_bmad(argv) -> int:
     p.add_argument("value", nargs="?",
                    help="startup: on | off | status · route: the prompt to classify")
     p.add_argument("-s", "--scope", choices=("project", "global"), default=None,
-                   help="target scope (on/off default: global; others: project)")
+                   help="target scope (on/off default: global; personas and "
+                        "status: both; others: project)")
     p.add_argument("--modules", default=DEFAULT_MODULES,
                    help="BMAD modules to install (default: %s)" % DEFAULT_MODULES)
     p.add_argument("-y", "--yes", action="store_true",
@@ -363,7 +364,25 @@ _PERSONA_STATE_LABEL = {
 
 
 def _personas(scope) -> int:
-    scope = scope or "global"
+    """List personas: one scope if asked, otherwise both.
+
+    This is a query, so with no ``--scope`` it reports BOTH — exactly what
+    ``bmad status`` already does, and for the same reason. Picking one scope by
+    default made the answer wrong whenever the personas lived in the other: it
+    defaulted to global, so after `boost bmad on --scope project` it read
+    ``~/.claude/agents``, found nothing, and reported seven personas sitting on
+    disk as "not installed" — contradicting `boost bmad status` run a moment
+    later in the same directory. Flipping the default to project would only
+    move the false statement to the global install, which is the more common
+    one; a query that inspects both places cannot be wrong about either.
+    """
+    for sc in (scope,) if scope else ("global", "project"):
+        _personas_scope(sc)
+    return 0
+
+
+def _personas_scope(scope) -> None:
+    """Report the persona roster for exactly one scope."""
     agents = _agents_dir(scope)
     states = core.persona_states(agents)
     out.heading("BMAD personas — %s" % scope)
@@ -376,7 +395,6 @@ def _personas(scope) -> int:
     out.dim("  → %s" % paths.tilde(agents))
     if all(state == "absent" for state in states.values()):
         out.dim("  install them with `boost bmad on`")
-    return 0
 
 
 # ------------------------------------------------------------------- provisioning

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/commands/configuration.py

@@ -496,9 +496,19 @@ def cmd_create(argv) -> int:
         "version": "0.1.0",
     }
     title = name.replace("-", " ").title()
-    target.mkdir(parents=True, exist_ok=True)
-    skill_md.write_text(frontmatter.dump(meta) + "\n\n"
-                        + _CREATE_BODY % {"title": title}, encoding="utf-8")
+    # `--dir` is user input, so an OSError here is a mistyped path — a file
+    # standing where the parent should be, or a directory boost cannot write —
+    # not a defect in boost. Unframed it exited 70 and wrote a crash report
+    # inviting the reader to file a GitHub issue. `boost import` already
+    # answers the same mistake with "no such directory: X"; match it.
+    try:
+        target.mkdir(parents=True, exist_ok=True)
+        skill_md.write_text(frontmatter.dump(meta) + "\n\n"
+                            + _CREATE_BODY % {"title": title}, encoding="utf-8")
+    except OSError as exc:
+        raise BoostError("cannot create %s: %s" % (_tilde(skill_md),
+                                                   exc.strerror or exc),
+                         hint="--dir takes a writable directory") from exc
     journal.log("create", name, path=str(target))
     out.ok("created %s" % _tilde(skill_md))
     if args.install:
@@ -1270,7 +1280,7 @@ def cmd_serve(argv) -> int:
     p = cliparse.parser(
         prog="boost serve",
         description="Browse the catalogue in a browser: search, facets and a tap graph")
-    p.add_argument("--port", type=int, default=default_port,
+    p.add_argument("--port", type=util.port_number, default=default_port,
                    help="port to listen on (default: config serve.port)")
     p.add_argument("--host", default="127.0.0.1",
                    help="address to bind (default: 127.0.0.1)")

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/commands/discovery.py

@@ -1101,6 +1101,13 @@ def cmd_recommend(argv):
     agg: dict[str, dict[str, Any]] = {}
     for kw in stack["keywords"]:
         for e, s in catalog.search(kw, entries):
+            # `search` ranks substrings, which is right for a search box and
+            # wrong for the `because:` column below — that column is a causal
+            # claim, and `ci` matching re*ci*pes made it a false one. Filtering
+            # here rather than inside `search` leaves the shared (and
+            # eval-gated) ranker exactly as it is; see catalog.mentions_keyword.
+            if not catalog.mentions_keyword(catalog.entry_text(e), kw):
+                continue
             rec = agg.setdefault(e["name"], {"entry": e, "score": 0,
                                              "because": set()})
             rec["score"] += s

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/commands/taps.py

@@ -26,6 +26,7 @@ from ..core import (
 )
 from ..core import output as out
 from ..errors import BoostError
+from ._common import _s
 
 _tilde = paths.tilde
 
@@ -161,7 +162,7 @@ def cmd_tap(argv) -> int:
     p.add_argument("--at", metavar="SHA",
                    help="pin the clone to one 40-character commit, as a "
                         "published vector shard requires")
-    p.add_argument("--jobs", type=int, metavar="N",
+    p.add_argument("--jobs", type=util.positive_int, metavar="N",
                    help="clone this many registries at once (default %d, max "
                         "%d)" % (registry.DEFAULT_TAP_JOBS,
                                  registry.MAX_TAP_JOBS))
@@ -351,7 +352,8 @@ def cmd_taps(argv) -> int:
     out.table(rows, headers=("NAME", "ITEMS", "UPDATED", "", "URL"),
               keep=("NAME",))
     print()
-    out.dim("%d taps · %d items" % (len(taps), total))
+    out.dim("%d tap%s · %d item%s"
+            % (len(taps), _s(len(taps)), total, _s(total)))
     if any(t["pin"] for t in taps):
         out.dim("@sha = pinned; `boost update` skips it")
     return 0

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/core/catalog.py

@@ -808,6 +808,57 @@ def _search_blob(name: str, description: str, meta) -> str:
     return " ".join([name.lower(), (description or "").lower(), _meta_text(meta)])  # noqa: FURB143
 
 
+def entry_text(entry: dict) -> str:
+    """The searchable text of one entry — the cached blob, or rebuilt.
+
+    One definition of "everything we know about this entry as text", so a
+    caller asking a question *about* an entry reads the same string
+    :func:`search` ranks on.
+    """
+    blob = entry.get("search_blob")
+    if blob is None:
+        blob = _search_blob(entry["name"], entry.get("description", ""),
+                            entry.get("meta", {}))
+    return blob
+
+
+#: Suffixes a language/framework keyword may grow when it appears in prose:
+#: `next` should reach `nextjs`, `go` should reach `golang`. Deliberately
+#: one-way and additive — a keyword may match a LONGER token, never a shorter
+#: one, which is why `java` still cannot reach `javascript` (that would need
+#: `java` + `script`, and `script` is not on this list).
+_KEYWORD_SUFFIXES = ("js", "lang")
+
+_WORDS = re.compile(r"[a-z0-9]+")
+
+
+def mentions_keyword(text: str, keyword: str) -> bool:
+    """True when ``text`` mentions ``keyword`` as a WORD, not as a substring.
+
+    :func:`search` scores substrings, which is right for a free-text search box
+    — someone typing `docker` wants `dockerfile` back. It is wrong for
+    ``boost recommend``, which prints ``because: <keyword>`` and thereby makes
+    a causal claim about why a skill suits a project.
+
+    The stack vocabulary is short words that live inside longer unrelated ones,
+    so the false claims were the common case rather than the edge: ``ci`` was
+    found inside "recipes", "delicious", "facilitation" and "discipline";
+    ``rust`` inside "trust", of which boost ships a whole command; ``java``
+    inside "javascript", so a JavaScript project was recommended Java skills;
+    and ``go`` inside "algorithms", "django" and "goals".
+    """
+    want = _WORDS.findall(keyword.strip().lower())
+    if not want:
+        return False
+    have = set(_WORDS.findall(text.lower()))
+    # A multi-word keyword needs all of its words. None of the built-in stack
+    # keywords carry a space, but callers pass user-shaped strings.
+    if len(want) > 1:
+        return all(w in have for w in want)
+    w = want[0]
+    return w in have or any(w + suf in have for suf in _KEYWORD_SUFFIXES)
+
+
 def curated_entries(entries: list[dict]) -> list[dict]:
     """Curated entries, deduped by name (first occurrence wins).
 
@@ -848,12 +899,9 @@ def search(query: str, entries: list[dict] | None = None):
     for e in entries:
         name = e["name"].lower()
         desc = (e["description"] or "").lower()
-        # Precomputed at index time; fall back for older caches / entries
+        # Precomputed at index time; falls back for older caches / entries
         # constructed without a blob (e.g. tests passing raw dicts).
-        blob = e.get("search_blob")
-        if blob is None:
-            blob = _search_blob(e["name"], e.get("description", ""),
-                                e.get("meta", {}))
+        blob = entry_text(e)
         score = 0
         if q == name:
             score += 100

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/core/gitutil.py

@@ -41,7 +41,18 @@ def branch_state(cwd: Path | None = None) -> BranchState:
     if wt.returncode != 0 or wt.stdout.strip() != "true":
         return BranchState(has_git=True, in_repo=False, branch=None)
     proc = run(["-C", str(cwd), "rev-parse", "--abbrev-ref", "HEAD"], check=False)
-    branch = proc.stdout.strip() if proc.returncode == 0 else None
+    if proc.returncode == 0:
+        return BranchState(has_git=True, in_repo=True,
+                           branch=proc.stdout.strip() or None)
+    # rev-parse resolves HEAD to a COMMIT, so it also fails on an unborn HEAD —
+    # a repo between `git init` and its first commit. Readers here take a
+    # `None` branch inside a repo for "not a repo at all": `boost context
+    # status` printed "(not in a git repository)" while standing in one, and
+    # `boost context apply` declined to do anything there. `symbolic-ref` reads
+    # the ref HEAD points at without requiring it to exist yet, so the branch
+    # is named from the first `git init` onward.
+    sym = run(["-C", str(cwd), "symbolic-ref", "--short", "HEAD"], check=False)
+    branch = sym.stdout.strip() or None if sym.returncode == 0 else None
     return BranchState(has_git=True, in_repo=True, branch=branch)
 
 

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/core/registry.py

@@ -106,13 +106,20 @@ def parse_spec(spec: str):
                 hint="`git init` it, or `boost import %s` to copy it in "
                      "without a tap" % spec)
         return _checked(p.resolve().name, str(p.resolve()), spec)
-    # A spec shaped like a path (starts with ./, ../ or ~, or is absolute —
-    # `p.is_absolute()` rather than a literal "/" prefix so a Windows
-    # `C:\...` spec is caught too, not just a POSIX `/...` one) that is not an
-    # actual directory must not fall through to the owner/repo branch below —
-    # that branch prepends "https://github.com/" to *anything* containing a
-    # "/", so a typo'd local path was silently cloned as a bogus GitHub URL.
-    if spec.startswith(("./", "../", "~")) or p.is_absolute():
+    # A spec shaped like a path (starts with ./, ../, ~, or a root separator,
+    # or is absolute) that is not an actual directory must not fall through to
+    # the owner/repo branch below — that branch prepends
+    # "https://github.com/" to *anything* containing a "/", so a typo'd local
+    # path was silently cloned as a bogus GitHub URL.
+    #
+    # `p.is_absolute()` catches a Windows `C:\...` spec, but it is NOT a
+    # superset of the literal "/" prefix it replaced: on Windows a leading
+    # slash is rooted-but-relative (it has no drive), so
+    # `PureWindowsPath("/no/such/dir").is_absolute()` is False and
+    # `boost tap /no/such/dir` was still cloning
+    # `https://github.com//no/such/dir`. Both tests are needed, and this is
+    # what the Windows CI leg caught that three POSIX legs could not.
+    if spec.startswith(("./", "../", "~", "/", "\\")) or p.is_absolute():
         raise BoostError("no such directory: %s" % p,
                         hint="boost tap needs an existing local git repository")
     if spec.startswith(("http://", "https://", "git@", "ssh://")):

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/core/store.py

@@ -324,6 +324,12 @@ def sideline(name: str, by: str) -> list[str]:
     entry = lockfile.get_skill(name)
     if entry is not None:
         entry["sidelined_by"] = by
+        # `agents` is defined as the links measured from disk, and the links
+        # have just been removed — so leaving the old list had `boost list`
+        # keep advertising the skill to agents that could no longer see it.
+        # `quarantine` clears it for the same reason; :func:`unsideline`
+        # recomputes it, exactly as `quarantine --release` does.
+        entry["agents"] = []
         lockfile.set_skill(name, entry)
     return removed
 
@@ -339,8 +345,10 @@ def unsideline(name: str) -> InstallResult:
     """
     res = link_agents(name)
     entry = lockfile.get_skill(name)
-    if entry is not None and entry.get("sidelined_by"):
-        del entry["sidelined_by"]
+    if entry is not None:
+        # Record the links this just made, since sideline() emptied the list.
+        entry["agents"] = res.linked
+        entry.pop("sidelined_by", None)
         lockfile.set_skill(name, entry)
     return res
 

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_cli/core/util.py

@@ -170,6 +170,31 @@ def positive_int(s: str) -> int:
     return v
 
 
+def port_number(s: str) -> int:
+    """argparse ``type=`` for a TCP port (``serve --port``): an int in 0-65535.
+
+    The ceiling is the point: an out-of-range number travelled all the way to
+    ``socket.bind``, which raises ``OverflowError`` — not an ``OSError`` boost
+    frames — so a typo exited 70 and wrote a crash report inviting the reader
+    to file a GitHub issue.
+
+    **Zero is valid and deliberately allowed**, which is why this is not
+    :func:`positive_int` with a maximum bolted on. ``bind(("127.0.0.1", 0))``
+    is the standard "give me any free port", and boost's own functional tests
+    start the server that way; rejecting it would turn a working idiom into a
+    parse error to make the bound look tidier.
+    """
+    import argparse
+
+    try:
+        v = int(s)
+    except (TypeError, ValueError):
+        raise argparse.ArgumentTypeError("invalid int value: %r" % s) from None
+    if not 0 <= v <= 65535:
+        raise argparse.ArgumentTypeError("must be 0-65535")
+    return v
+
+
 def score_int(s: str) -> int:
     """argparse ``type=`` for ``lint --min``: an int in [0, 100].
 

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112/boost_skill_cli.egg-info}/PKG-INFO

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

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/boost_skill_cli.egg-info/SOURCES.txt

@@ -324,6 +324,7 @@ docs/roadmap/items/audit-verify-findings.md
 docs/roadmap/items/audit-who-findings.md
 docs/roadmap/items/autonomous-ship-workflow-and-isolated-worktree.md
 docs/roadmap/items/bare-boost-never-names-an-entry-point.md
+docs/roadmap/items/because-that-was-not-the-reason.md
 docs/roadmap/items/bm25-empty-tokenization-kills-catalog-fallback.md
 docs/roadmap/items/bm25-has-no-stemming.md
 docs/roadmap/items/bm25-index-is-one-json-blob.md
@@ -366,6 +367,7 @@ docs/roadmap/items/concurrent-rag-builds-delete-each-others-temp-index.md
 docs/roadmap/items/consolidate-skill-staleness-drift-logic-into-cor.md
 docs/roadmap/items/corpus-refresh-updates-data-not-prose.md
 docs/roadmap/items/corrupt-config-reads-as-ready-to-set-up.md
+docs/roadmap/items/count-flags-that-silently-invert.md
 docs/roadmap/items/coverage-dashboard-codecov-free-for-oss.md
 docs/roadmap/items/coverage-guided-fuzzing-atheris-oss-fuzz.md
 docs/roadmap/items/crash-listing-branch-untested.md
@@ -463,6 +465,7 @@ docs/roadmap/items/lint-tap-misscopes-rule-workflow-entries.md
 docs/roadmap/items/list-rules-and-workflows.md
 docs/roadmap/items/localize-the-stored-bm25-snippet.md
 docs/roadmap/items/lock-invariant-cannot-parse-extras-pins.md
+docs/roadmap/items/lock-kept-links-it-had-just-removed.md
 docs/roadmap/items/lockfile-enforcement-and-commit-pinning.md
 docs/roadmap/items/log-timestamps-mislabeled-utc.md
 docs/roadmap/items/long-hints-overflow-narrow-panes.md
@@ -639,6 +642,7 @@ docs/roadmap/items/tool-call-eval-tier.md
 docs/roadmap/items/two-ci-controls-that-could-not-act.md
 docs/roadmap/items/two-crashes-that-should-have-been-messages.md
 docs/roadmap/items/typo-detection-codespell.md
+docs/roadmap/items/typos-reported-as-boost-bugs.md
 docs/roadmap/items/typosquat-and-name-confusion-detection.md
 docs/roadmap/items/unify-tilde-two-copies-have-a-boundary-bug.md
 docs/roadmap/items/uninstall-has-no-confirmation-prompt.md
@@ -767,7 +771,9 @@ tests/eval/taps-scale.txt
 tests/eval/taps.txt
 tests/eval/tool_calls.jsonl
 tests/eval/fixtures/claude_init_event.jsonl
+tests/functional/test_bad_input_is_not_a_crash.py
 tests/functional/test_bmad_all_hosts.py
+tests/functional/test_bmad_personas_scope.py
 tests/functional/test_capabilities_policy.py
 tests/functional/test_cli_adapt.py
 tests/functional/test_cli_bmad.py
@@ -787,10 +793,14 @@ tests/functional/test_cli_quickstart.py
 tests/functional/test_cli_tap_pins.py
 tests/functional/test_cli_taps.py
 tests/functional/test_cli_team.py
+tests/functional/test_context_sees_an_unborn_branch.py
+tests/functional/test_count_flags_reject_nonpositive.py
 tests/functional/test_everyday_loop.py
 tests/functional/test_integrity_enforce.py
 tests/functional/test_kind_conformance.py
 tests/functional/test_property_parsers.py
+tests/functional/test_recommend_because_is_true.py
+tests/functional/test_reports_match_reality.py
 tests/functional/test_run.py
 tests/functional/test_tap_signing.py
 tests/functional/test_workspace_scope.py
@@ -843,6 +853,7 @@ tests/unit/test_browse.py
 tests/unit/test_builtin.py
 tests/unit/test_capabilities.py
 tests/unit/test_catalog.py
+tests/unit/test_catalog_keyword_words.py
 tests/unit/test_catalogbundle.py
 tests/unit/test_chat.py
 tests/unit/test_check_anchors.py
@@ -863,6 +874,7 @@ tests/unit/test_complete_rc_block.py
 tests/unit/test_config.py
 tests/unit/test_content_dedupe.py
 tests/unit/test_content_identity.py
+tests/unit/test_count_flags_use_positive_int.py
 tests/unit/test_crash_redaction.py
 tests/unit/test_dedup_trust.py
 tests/unit/test_demo_index.py

{boost_skill_cli-1.2.111 → boost_skill_cli-1.2.112}/docs/commands.html

@@ -1200,7 +1200,7 @@
         </div>
         <div class="args-h">Options</div>
         <div class="args">
-          <div class="arg"><code>-s, --scope {project,global}</code><span>target scope (on/off default: global; others: project)</span></div>
+          <div class="arg"><code>-s, --scope {project,global}</code><span>target scope (on/off default: global; personas and status: both; others: project)</span></div>
           <div class="arg"><code>--modules MODULES</code><span>BMAD modules to install (default: bmm)</span></div>
           <div class="arg"><code>-y, --yes</code><span>skip confirmation prompts</span></div>
           <div class="arg"><code>--startup</code><span>enable the startup toggle right after install</span></div>

boost_skill_cli-1.2.112/docs/roadmap/items/because-that-was-not-the-reason.md

@@ -0,0 +1,54 @@
+---
+id: because-that-was-not-the-reason
+board: code
+section: health
+status: shipped
+category: Bug
+complexity: M
+impact: Med
+wow: 5
+note: A `.github/workflows/` directory made `boost recommend` suggest a pasta-recipe skill "because: ci"
+order: 316
+owner: fix/land-claims-fixes
+pr:
+title: Three commands that denied what was on the disk in front of them
+---
+Each of these is boost contradicting something the user can see, and each was confirmed by an
+independent verifier that tried to refute it first.
+
+<b><code>boost recommend</code> printed a reason that was not one.</b> Every row carries a
+<code>because: &lt;keyword&gt;</code> column — a causal claim about why this skill suits this
+project. It was scored on substrings, and the stack vocabulary is short words that live inside
+longer unrelated ones, so a project whose only signal was a <code>.github/workflows/</code>
+directory was told to install a pasta-recipe skill <i>because: ci</i> — matching the letters
+inside "recipes". The reported case was the mildest one. <code>rust</code> matched "trust", of
+which boost ships an entire command; <code>java</code> matched "javascript", so a JavaScript
+project was recommended Java skills; <code>go</code> matched "algorithms", "django" and "goals".
+False attribution was the common case, not the edge.
+
+The fix stays out of <code>catalog.search</code>, which is deliberately substring-based (a user
+typing <i>docker</i> wants <i>dockerfile</i> back) and is a scored engine in the eval baseline.
+Word matching is applied where the causal claim is actually made. A one-way suffix alias keeps
+<code>next</code> reaching <code>nextjs</code> and <code>go</code> reaching <code>golang</code>,
+while giving <code>java</code> no route back to <code>javascript</code>.
+
+<b><code>boost bmad personas</code> called seven installed personas "not installed".</b> It
+defaulted to the global scope, so after a project install it read the wrong directory and
+denied files that were sitting on disk — contradicting <code>boost bmad status</code> run a
+moment later in the same directory. Its own <code>--help</code> says the default should be
+project. Flipping it would only have moved the false statement to the global install, which is
+the more common one, so the command now reports <b>both</b> scopes when none is named — exactly
+what <code>bmad status</code> has always done, and a shape that cannot be wrong about either.
+
+<b><code>boost context</code> denied it was in a git repository while standing in one.</b>
+<code>git rev-parse</code> resolves HEAD to a <i>commit</i>, so it fails on a repo between
+<code>git init</code> and its first commit with the same exit code it gives outside a repo. The
+two states were indistinguishable, so <code>context status</code> reported "(not in a git
+repository)" and <code>context apply</code> declined to act — in a directory the user had just
+initialised. <code>git symbolic-ref</code> reads the ref HEAD points at without requiring it to
+exist yet, and still fails outside a repo, so the genuinely-not-a-repo answer is unchanged.
+
+Two further candidates in the same batch were <b>refuted</b> and left alone:
+<code>boost home</code>'s slot-level URL and <code>tap --dry-run</code>'s scope are both
+imprecise rather than false, and neither <code>--help</code> nor the command table promises what
+the finder assumed.

boost_skill_cli-1.2.112/docs/roadmap/items/count-flags-that-silently-invert.md

@@ -0,0 +1,45 @@
+---
+id: count-flags-that-silently-invert
+board: code
+section: internals
+status: shipped
+category: Bug
+complexity: S
+impact: Med
+wow: 4
+note: `serve --port 99999` reached socket.bind and exited 70 with a crash report
+order: 317
+owner: fix/land-claims-fixes
+pr:
+title: A scan that stops the bare-int count flag coming back
+---
+Six count flags accepting <code>0</code> and negatives were fixed one at a time, over two
+separate passes. Fixing them individually left nothing behind to stop the seventh, and two more
+had already appeared by the time this landed.
+
+<code>serve --port</code> is the shape <code>util.positive_int</code> does not cover: a port
+needs a <i>ceiling</i> as well as a floor. Without one an out-of-range number travelled all the
+way to <code>socket.bind</code>, which raises <code>OverflowError</code> — not an
+<code>OSError</code> boost frames — so a <b>typo</b> exited 70 and wrote a crash report
+inviting the reader to file a GitHub issue. New <code>util.port_number</code> bounds it to
+0-65535 at parse time, where the error is still about the thing the user typed.
+
+<b>0 is valid, and that is why this is not <code>positive_int</code> with a maximum.</b> The
+first draft rejected it and broke <code>TestServe</code>, which — like anything that wants a
+free port — starts the server with <code>--port 0</code>. A tidier bound would have turned a
+working idiom into a parse error; the control run against <code>main</code> is what caught it.
+
+<code>tap --jobs</code> was found by the scan rather than by anyone hitting it, and it fails
+the quiet way rather than the loud one: <code>registry.tap_jobs</code> ends in
+<code>max(1, min(requested, MAX_TAP_JOBS))</code>, so <code>--jobs 0</code> and
+<code>--jobs -5</code> both silently became <b>1</b>. That clamp is right for the env var and
+the default it also normalises; it is the wrong answer to an explicit flag, where the user asked
+for something boost cannot do and was given something else without being told. The upper clamp
+stays, and <code>--help</code> has always named it.
+
+<b>The durable half is the scan.</b> An AST pass walks every <code>add_argument</code> in the
+command layer and fails on any new bare <code>type=int</code>. One genuinely unbounded option
+(<code>--percent</code>, where 0 means "nobody") is exempt <i>with a recorded reason</i>, and a
+second test deletes an exemption once its flag is bounded — which is how this pass found that
+<code>--min</code> and <code>--timeout</code> had since moved to <code>score_int</code> and
+<code>positive_int</code>. The list cannot rot into a blanket suppression.

boost_skill_cli-1.2.112/docs/roadmap/items/lock-kept-links-it-had-just-removed.md

@@ -0,0 +1,31 @@
+---
+id: lock-kept-links-it-had-just-removed
+board: code
+section: health
+status: shipped
+category: Bug
+complexity: S
+impact: Low
+wow: 3
+note: `boost profile use` unlinked four agents and `boost list` kept naming all four
+order: 319
+owner: fix/land-claims-fixes
+pr:
+title: The lock kept advertising links it had just removed
+---
+A skill's <code>agents</code> field is defined as the links measured from disk.
+<code>boost quarantine</code> clears it when it removes them, and
+<code>quarantine --release</code> recomputes it — the pair that makes the field mean what it
+says.
+
+<code>store.sideline</code> did neither. <code>boost profile use</code> set a skill aside,
+deleted its symlinks, recorded <code>sidelined_by</code> so <code>doctor</code> and
+<code>sync</code> would stop fighting the switch — and left the old <code>agents</code> list
+standing. So <code>boost list --json</code> went on naming four agents for a skill none of them
+could see. The state was right and the report was wrong, which is the harder kind to notice:
+every command that <i>acts</i> on the sideline behaved correctly.
+
+<code>sideline</code> now empties the list and <code>unsideline</code> records what it relinked,
+which is exactly the <code>quarantine</code> / <code>--release</code> shape one function over.
+
+Separately, <code>boost taps</code> said "1 taps · 3 items".

boost_skill_cli-1.2.112/docs/roadmap/items/typos-reported-as-boost-bugs.md

@@ -0,0 +1,35 @@
+---
+id: typos-reported-as-boost-bugs
+board: code
+section: dx
+status: shipped
+category: Bug
+complexity: S
+impact: Med
+wow: 4
+note: `boost create --dir` answered a mistyped path with "file it at github.com/.../issues"
+order: 318
+owner: fix/land-claims-fixes
+pr:
+title: The last command that blamed boost for the user's typo
+---
+Naming a bad path to <code>boost create --dir</code> produced this:
+
+<code>Error: boost hit an unexpected error: NotADirectoryError: [Errno 20] Not a
+directory</code><br>
+<code>&nbsp;&nbsp;hint: a crash report was written to … or file it at
+https://github.com/jonnyeclectic/boost/issues</code>
+
+Exit 70, a crash report on disk, and an invitation to open a bug — for naming a file where a
+directory was wanted, or a directory boost cannot write.
+
+<b>boost already owned the right answer.</b> <code>boost import ./nope</code> replies
+<code>Error: no such directory: ./nope</code> with a hint and exit 1;
+<code>boost infer --path ./nope</code> replies <code>~/nope is not a directory</code>;
+<code>infer -o</code> and <code>tap</code> were brought to the same house style earlier. This
+was one command missing a house style, not a house style missing.
+
+One test in the first draft overreached and had to be corrected rather than the code:
+<code>create --dir</code> builds missing parent directories on purpose
+(<code>parents=True</code>), which is useful, not a defect. The bad-input cases are a
+<i>file</i> standing in the parent's place, and a parent that is not writable.