boost-skill-cli 1.2.46__tar.gz → 1.2.48__tar.gz

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/CLAUDE.md

@@ -435,6 +435,21 @@ of the three item kinds (see Non-obvious rules above); `core/store.py` owns
 install, uninstall and sync — copying into the canonical store, symlinking into
 each agent's skills dir, and updating the lock file.
 
+- **A tap pin lives in `config.json`, and `boost update` is what makes it real.**
+  `boost tap --at <sha>` used to check a commit out and record nothing, so the
+  next `boost update` reset the clone to the default branch — measured on a
+  two-commit fixture: tapped at `fb61736`, updated, `6206d22`. That silently
+  invalidates any shard imported for the old commit (stale vectors, still
+  present, no error), which is also the reason **search must never refresh taps
+  in the background**: `_hint_stale_taps` reads one mtime
+  (`paths.tap_refresh_marker`, stamped by `registry.update`) and prints one
+  line rather than fetching. `registry.update` skips a pinned tap; `--force`
+  moves it *and* drops the pin, because deciding to move a tap is deciding to
+  stop holding it still. After any tap actually moves, `pkg._resync_vectors`
+  asks the manifest whether a shard exists for the new commit — importing it
+  costs a download instead of an hour of CPU — and says plainly when one does
+  not.
+
 - **A published shard is only importable while three things match, and every
   mismatch is silent if waved through.** `core/shards.py` fetches
   `manifest.json` from a rolling `shards-latest` **prerelease** on this repo —

{boost_skill_cli-1.2.46/boost_skill_cli.egg-info → boost_skill_cli-1.2.48}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.46
+Version: 1.2.48
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0
@@ -188,6 +188,15 @@ the difference between semantic search being available and being reachable.
 
 Already tapped? `boost reindex --fetch-shards` does the download half alone,
 and `boost reindex --dense` embeds locally whatever has no published shard.
+
+Because vectors are keyed to a registry's commit, `quickstart` **pins** each tap
+it fetches vectors for, and `boost update` skips a pinned tap rather than moving
+it out from under them (`--force` moves it anyway and drops the pin). When a tap
+does move, boost checks whether a newer shard exists for the new commit and
+imports it; if none does, it says so instead of leaving stale vectors looking
+fresh. `boost search` never refreshes taps behind your back — it prints one line
+when they are more than two weeks old and leaves the fetching to
+`boost update --taps-only`.
 Every download is checked against the sha256 in the manifest and refused on a
 mismatch, and shards for a registry that has moved since publication are
 refused rather than merged — stale vectors would otherwise look fresh forever.

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/README.md

@@ -146,6 +146,15 @@ the difference between semantic search being available and being reachable.
 
 Already tapped? `boost reindex --fetch-shards` does the download half alone,
 and `boost reindex --dense` embeds locally whatever has no published shard.
+
+Because vectors are keyed to a registry's commit, `quickstart` **pins** each tap
+it fetches vectors for, and `boost update` skips a pinned tap rather than moving
+it out from under them (`--force` moves it anyway and drops the pin). When a tap
+does move, boost checks whether a newer shard exists for the new commit and
+imports it; if none does, it says so instead of leaving stale vectors looking
+fresh. `boost search` never refreshes taps behind your back — it prints one line
+when they are more than two weeks old and leaves the fetching to
+`boost update --taps-only`.
 Every download is checked against the sha256 in the manifest and refused on a
 mismatch, and shards for a registry that has moved since publication are
 refused rather than merged — stale vectors would otherwise look fresh forever.

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/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.46'
-__version_tuple__ = version_tuple = (1, 2, 46)
+__version__ = version = '1.2.48'
+__version_tuple__ = version_tuple = (1, 2, 48)
 
 __commit_id__ = commit_id = None

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_cli/commands/discovery.py

@@ -141,6 +141,9 @@ def cmd_search(argv):
             "no matches for %r" % query,
             "try `boost discover %s` to search all of GitHub" % query))
         _hint_semantic_search(engine)
+        # Especially here: "no matches" is exactly the answer an out-of-date
+        # tap set produces, and the user has no other way to suspect it.
+        _hint_stale_taps()
         return 0
     # The CLI's long-standing wording for the BM25 engine differs from the label
     # rag/eval use ("BM25 full-content"), and both are load-bearing: the latter
@@ -180,6 +183,7 @@ def cmd_search(argv):
     if use_rag:
         _note_stem_expansions(query)
     _hint_semantic_search(engine)
+    _hint_stale_taps()
     return 0
 
 
@@ -200,6 +204,28 @@ def _note_stem_expansions(query: str) -> None:
         max(0, out.term_width() - 2)), "muted"))
 
 
+def _hint_stale_taps() -> None:
+    """Mention old tap clones. One `stat`, and never a network call.
+
+    Search deliberately does not refresh the taps themselves. A refresh is a
+    `git fetch` per tap — ~1.6 s each, minutes across a real install — so doing
+    it inline would turn a sub-second command into a wait, and doing it in the
+    background would mean unannounced network egress plus writes to the very
+    caches the search is reading. Worse, a tap's commit is load-bearing for
+    dense vectors, so a silent update would strand imported shards as stale.
+
+    So: say it, do not do it. The marker's mtime answers "how long ago" for the
+    price of one stat, and a machine that has never refreshed says nothing at
+    all rather than inventing an age.
+    """
+    age = registry.refresh_age_days()
+    if age is None or age < registry.STALE_TAPS_DAYS:
+        return
+    out.info(out.role(
+        "taps last refreshed %d days ago — `boost update --taps-only`"
+        % int(age), "muted"))
+
+
 def _hint_semantic_search(engine: str) -> None:
     """Say that a better engine exists, when BM25 answered alone.
 

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_cli/commands/pkg.py

@@ -31,6 +31,7 @@ from ..core import (
     lockfile,
     paths,
     projectlock,
+    rag,
     registry,
     resolve,
     scopes,
@@ -835,6 +836,48 @@ def _update_materialized(kind: str, installed: dict[str, dict], results) -> int:
     return n
 
 
+def _resync_vectors(moved: list[str]) -> None:
+    """Keep prebuilt vectors honest after the taps underneath them move.
+
+    A tap's commit is load-bearing for dense search: `dense.build` marks a tap
+    "reused" per commit and `import_shard` refuses a shard built for another
+    one. So an update that moves a tap leaves its vectors stale *but present* —
+    the failure mode that looks like nothing at all, and the reason auto-
+    updating taps in the background would quietly undo a shard import.
+
+    Two outcomes are worth the network: a newer shard exists for the commit the
+    tap just moved to, in which case importing it costs a download instead of
+    an hour of CPU; or one does not, in which case the honest thing is to say
+    the vectors are now stale and name the command that rebuilds them.
+    """
+    if not moved:
+        return
+    from ..core import dense, shards
+    if not dense.ready():
+        return                      # nothing embedded here to invalidate
+    try:
+        manifest = shards.fetch_manifest()
+    except BoostError:
+        # Offline, or no manifest published. The vectors are still stale, and
+        # saying so without the remedy we could not check for is enough.
+        out.info(out.role("prebuilt vectors for %d refreshed tap(s) are now "
+                          "stale — `boost reindex --dense` rebuilds them"
+                          % len(moved), "muted"))
+        return
+    commits = rag._tap_commits()
+    by_name = {t.name: commits.get(t.safe_name, "")
+               for t in registry.list_taps() if t.name in moved}
+    got = [r for r in shards.sync(list(by_name), by_name, manifest=manifest)
+           if r["status"] == "imported"]
+    if got:
+        out.ok("re-imported prebuilt vectors for %d tap(s)" % len(got))
+    left = len(moved) - len(got)
+    if left:
+        out.info(out.role("%d refreshed tap(s) have no matching shard yet — "
+                          "their vectors are stale until "
+                          "`boost reindex --dense`" % left, "muted"))
+
+
 def cmd_update(argv: list[str]) -> int:
     ap = cliparse.parser(prog="boost update",
                                  description="Sync taps or update installed skills")
@@ -849,14 +892,23 @@ def cmd_update(argv: list[str]) -> int:
     # sys.argv, so this makes the printed advice true rather than adding a path.
     ap.add_argument("-y", "--yes", action="store_true",
                     help="skip the confirmation prompt")
+    ap.add_argument("--force", action="store_true",
+                    help="move pinned taps too, clearing their pin")
     args = ap.parse_args(argv)
-    results, failures = registry.update(args.tap or None)
+    results, failures = registry.update(args.tap or None, force=args.force)
     if not results and not failures:
         out.info("no taps configured — start with `boost tap --defaults`")
         return 0
+    moved = []
     for tname, summary in results.items():
-        catalog.rebuild_tap(registry.get(tname))
+        if "skipped" not in summary:
+            catalog.rebuild_tap(registry.get(tname))
+        # "abc1234 → def5678" is a tap whose tree changed; "already up to date"
+        # and "pinned at ..." are not. Only the first invalidates vectors.
+        if "→" in summary:
+            moved.append(tname)
         out.ok("%s: %s" % (tname, summary))
+    _resync_vectors(moved)
     # Report the dead ones by name, after the successes, so a broken upstream
     # reads as one line of bad news rather than as the whole command failing.
     for tname, err in failures.items():

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_cli/commands/taps.py

@@ -226,7 +226,8 @@ def cmd_taps(argv) -> int:
         skills = catalog.load_tap(tap)
         total += len(skills)
         taps.append({"name": tap.name, "url": tap.url, "curated": tap.curated,
-                     "skills": len(skills), "updated": _tap_updated(tap)})
+                     "skills": len(skills), "updated": _tap_updated(tap),
+                     "pin": tap.pin})
     if args.json:
         print(json.dumps(taps, indent=2))
         return 0
@@ -234,7 +235,12 @@ def cmd_taps(argv) -> int:
         out.info("no taps configured")
         out.info(out.role("add the recommended registries with `boost tap --defaults`", "muted"))
         return 0
-    rows = [(t["name"], str(t["skills"]), t["updated"],
+    # A pinned tap reads as its commit rather than its date: the date of a
+    # clone held still is not what the user needs to know about it, and a tap
+    # that `boost update` deliberately skips should say why on the line the
+    # user is already reading.
+    rows = [(t["name"], str(t["skills"]),
+             "@%s" % str(t["pin"])[:7] if t["pin"] else t["updated"],
              "★" if t["curated"] else "", out.role(_tilde(t["url"]), "muted"))
             for t in taps]
     out.table(rows, headers=("NAME", "SKILLS", "UPDATED", "", "URL"))

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_cli/core/paths.py

@@ -103,6 +103,16 @@ def state_dir() -> Path:
     return boost_home() / "state"
 
 
+def tap_refresh_marker() -> Path:
+    """File whose mtime records when the taps were last refreshed.
+
+    An mtime rather than a JSON field: the only question asked of it is "how
+    long ago", on the search path, where one `stat` is affordable and parsing
+    anything is not.
+    """
+    return state_dir() / "last-tap-refresh"
+
+
 def snapshots_dir() -> Path:
     """Return the directory for ``snap-*`` store snapshot tarballs."""
     return state_dir() / "snapshots"

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_cli/core/registry.py

@@ -5,6 +5,7 @@ from __future__ import annotations
 
 import difflib
 import os
+import time
 from concurrent.futures import ThreadPoolExecutor
 from contextlib import suppress
 from dataclasses import dataclass
@@ -20,6 +21,12 @@ class Tap:
     name: str          # "anthropics/skills" or a short alias
     url: str           # https URL or local path
     curated: bool = False
+    #: A 40-character commit this tap is held at, or "" for "track the default
+    #: branch". A pin is durable *because it is recorded here*: `tap --at`
+    #: checked a commit out and nothing remembered, so the next `boost update`
+    #: moved the clone to HEAD — silently invalidating any prebuilt vectors
+    #: imported for that commit, which is the whole reason the pin exists.
+    pin: str = ""
 
     @property
     def safe_name(self) -> str:
@@ -131,7 +138,8 @@ def list_taps() -> list[Tap]:
     taps = config.get("taps", []) or []
     if not isinstance(taps, list):
         return []
-    return [Tap(name=t["name"], url=t.get("url", ""), curated=bool(t.get("curated")))
+    return [Tap(name=t["name"], url=t.get("url", ""),
+                curated=bool(t.get("curated")), pin=str(t.get("pin") or ""))
             for t in taps if isinstance(t, dict) and t.get("name")]
 
 
@@ -203,9 +211,12 @@ def add(spec: str, curated: bool = False, at: str | None = None) -> Tap:
             hint="add its key with `boost trust add <name> <key>`, "
                  "or relax `boost policy set require_signed_taps false`")
     cfg = config.load()
-    cfg.setdefault("taps", []).append(
-        {"name": name, "url": url, "curated": curated})
+    row = {"name": name, "url": url, "curated": curated}
+    if at:
+        row["pin"] = at
+    cfg.setdefault("taps", []).append(row)
     config.save(cfg)
+    tap.pin = at or ""
     return tap
 
 
@@ -336,8 +347,12 @@ def add_many(specs: list[str], curated: bool = False,
         cfg = config.load()
         rows = cfg.setdefault("taps", [])
         for r in fresh:
-            rows.append({"name": r["name"], "url": r["url"],
-                         "curated": curated})
+            row = {"name": r["name"], "url": r["url"], "curated": curated}
+            pin = pins.get(r["name"])
+            if pin:
+                row["pin"] = pin
+                r["tap"].pin = pin
+            rows.append(row)
         config.save(cfg)
     # First occurrence, not last: a dict comprehension over `specs` keeps the
     # LAST index for a repeated spec, which pushed the duplicate — and so its
@@ -352,6 +367,58 @@ def add_many(specs: list[str], curated: bool = False,
     return results
 
 
+#: How long a tap set may go unrefreshed before `boost search` mentions it.
+#: Two weeks rather than days: registries move slowly, and a hint that fires
+#: every other search is one users learn to read past.
+STALE_TAPS_DAYS = 14
+
+
+def mark_refreshed() -> None:
+    """Stamp "the taps were refreshed just now"; never fails a refresh."""
+    with suppress(OSError):
+        paths.ensure_dirs()
+        paths.tap_refresh_marker().write_text("", encoding="utf-8")
+
+
+def refresh_age_days() -> float | None:
+    """Days since the last tap refresh, or None when nothing has recorded one.
+
+    None is not zero and not infinity: on a machine that has never run
+    `boost update` there is nothing to report, and inventing an age would make
+    every fresh install nag about staleness on its first search.
+    """
+    marker = paths.tap_refresh_marker()
+    try:
+        age = time.time() - marker.stat().st_mtime
+    except OSError:
+        return None
+    return max(0.0, age / 86400.0)
+
+
+def pin(name: str, commit: str) -> Tap:
+    """Record `commit` as the tap's pin, so `update` leaves it alone."""
+    tap = get(name)
+    cfg = config.load()
+    for row in cfg.get("taps", []) or []:
+        if isinstance(row, dict) and row.get("name") == tap.name:
+            row["pin"] = commit
+    config.save(cfg)
+    tap.pin = commit
+    return tap
+
+
+def unpin(name: str) -> Tap:
+    """Drop a tap's pin so it tracks its default branch again."""
+    tap = get(name)
+    cfg = config.load()
+    for row in cfg.get("taps", []) or []:
+        if isinstance(row, dict) and row.get("name") == tap.name:
+            row.pop("pin", None)
+    config.save(cfg)
+    tap.pin = ""
+    return tap
+
+
 def remove(name: str) -> Tap:
     """Deregister a tap and delete its clone and cache file.
 
@@ -374,9 +441,14 @@ def remove(name: str) -> Tap:
 WHEEL_SCHEME = "builtin:"
 
 
-def update(name: str | None = None) -> tuple[dict, dict]:
+def update(name: str | None = None,
+           force: bool = False) -> tuple[dict, dict]:
     """git-pull one tap (or all). Returns ``({name: summary}, {name: error})``.
 
+    **A pinned tap is skipped** unless ``force``, which also clears the pin —
+    an update that silently moved a pinned clone is what made `tap --at` a
+    suggestion rather than a guarantee.
+
     **A named tap still raises.** ``boost update sometap`` is a request about
     that one tap, so its failure is the answer to the question asked.
 
@@ -395,6 +467,14 @@ def update(name: str | None = None) -> tuple[dict, dict]:
     results: dict = {}
     failures: dict = {}
     for tap in targets:
+        if tap.pin and not force:
+            # A pinned tap is held at one commit on purpose: prebuilt vectors
+            # are keyed to it, and moving the clone would make them stale while
+            # still present — the failure that looks like nothing at all. Not
+            # an error, because "update everything" over 400 taps should not
+            # fail because three are pinned.
+            results[tap.name] = "pinned at %s (skipped)" % tap.pin[:7]
+            continue
         try:
             if tap.url.startswith(WHEEL_SCHEME):
                 # boost's own tap arrives with the wheel, so there is no remote
@@ -414,6 +494,11 @@ def update(name: str | None = None) -> tuple[dict, dict]:
                 results[tap.name] = "cloned"
             else:
                 results[tap.name] = gitutil.pull(tap.path)
+                if tap.pin:
+                    # `--force` is a decision to stop holding this tap still,
+                    # so the pin goes with the move rather than silently
+                    # re-applying on the next run.
+                    unpin(tap.name)
         except BoostError as err:
             if name:
                 raise
@@ -421,4 +506,9 @@ def update(name: str | None = None) -> tuple[dict, dict]:
             # says; git's own first line already carries the URL or path. See
             # gitutil._git_error for why that line is now the one we show.
             failures[tap.name] = err.message
+    if results:
+        # Stamped on any successful sweep, including one where every tap was
+        # already current: "refreshed" is about having asked, not about having
+        # found something.
+        mark_refreshed()
     return results, failures

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48/boost_skill_cli.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: boost-skill-cli
-Version: 1.2.46
+Version: 1.2.48
 Summary: boost — Homebrew for AI coding skills
 Author: Jonathan Reyes
 License-Expression: Apache-2.0
@@ -188,6 +188,15 @@ the difference between semantic search being available and being reachable.
 
 Already tapped? `boost reindex --fetch-shards` does the download half alone,
 and `boost reindex --dense` embeds locally whatever has no published shard.
+
+Because vectors are keyed to a registry's commit, `quickstart` **pins** each tap
+it fetches vectors for, and `boost update` skips a pinned tap rather than moving
+it out from under them (`--force` moves it anyway and drops the pin). When a tap
+does move, boost checks whether a newer shard exists for the new commit and
+imports it; if none does, it says so instead of leaving stale vectors looking
+fresh. `boost search` never refreshes taps behind your back — it prints one line
+when they are more than two weeks old and leaves the fetching to
+`boost update --taps-only`.
 Every download is checked against the sha256 in the manifest and refused on a
 mismatch, and shards for a registry that has moved since publication are
 refused rather than merged — stale vectors would otherwise look fresh forever.

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/boost_skill_cli.egg-info/SOURCES.txt

@@ -599,6 +599,7 @@ tests/functional/test_cli_pane_width.py
 tests/functional/test_cli_pkg.py
 tests/functional/test_cli_quality.py
 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_everyday_loop.py
@@ -786,6 +787,7 @@ tests/unit/test_store.py
 tests/unit/test_store_materialize.py
 tests/unit/test_sync_blocked_links.py
 tests/unit/test_sync_repairs_gutted_skill.py
+tests/unit/test_tap_pins.py
 tests/unit/test_token_parity.py
 tests/unit/test_toolchain_lock.py
 tests/unit/test_trustaudit.py

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/adapters.html

@@ -353,7 +353,7 @@ python3 -m venv /tmp/crew &amp;&amp; /tmp/crew/bin/pip install <span class="s">"
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/carousel.html

@@ -387,7 +387,7 @@
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/chat.html

@@ -198,7 +198,7 @@ boost chat -k 3 --no-sources "review my diff"</pre>
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/commands.html

@@ -104,7 +104,7 @@
       <a class="cmd-link" href="#cmd-install" data-search="install install a skill from a tap registry  --force --path p --agent a --scope {user,project} --local --global --dry-run --no-deps --no-mcp name">install</a>
       <a class="cmd-link" href="#cmd-uninstall" data-search="uninstall remove an installed skill, rule, workflow, or config  --local -y, --yes name">uninstall</a>
       <a class="cmd-link" href="#cmd-sync" data-search="sync reconcile installed skills &amp; symlinks against the lock file  --diff --prune --json">sync</a>
-      <a class="cmd-link" href="#cmd-update" data-search="update sync taps or update installed skills  --taps-only -y, --yes tap">update</a>
+      <a class="cmd-link" href="#cmd-update" data-search="update sync taps or update installed skills  --taps-only -y, --yes --force tap">update</a>
       <a class="cmd-link" href="#cmd-reinstall" data-search="reinstall reinstall a skill or all skills (force) reinstall an installed skill, rule or workflow (force) --all name">reinstall</a>
       <a class="cmd-link" href="#cmd-bundle" data-search="bundle export/install skill sets via a boostfile  {dump,install} file">bundle</a>
       <a class="cmd-link" href="#cmd-import" data-search="import import skills from a github url or local path  --name n --all --agent a url_or_path">import</a>
@@ -257,10 +257,10 @@
           <div class="arg"><code>--json</code><span>machine-readable output</span></div>
         </div>
       </section>
-      <section class="cmd" id="cmd-update" data-search="update sync taps or update installed skills  --taps-only -y, --yes tap">
+      <section class="cmd" id="cmd-update" data-search="update sync taps or update installed skills  --taps-only -y, --yes --force tap">
         <h3><span class="cname">update</span><span class="gtag">pkg</span></h3>
         <p class="summary">Sync taps or update installed skills</p>
-        <pre class="syn">boost update [--taps-only] [--yes] [TAP]</pre>
+        <pre class="syn">boost update [--taps-only] [--yes] [--force] [TAP]</pre>
         <div class="args-h">Arguments</div>
         <div class="args">
           <div class="arg"><code>TAP</code><span>refresh only this tap</span></div>
@@ -269,6 +269,7 @@
         <div class="args">
           <div class="arg"><code>--taps-only</code><span>refresh tap clones &amp; catalogs without touching skills</span></div>
           <div class="arg"><code>-y, --yes</code><span>skip the confirmation prompt</span></div>
+          <div class="arg"><code>--force</code><span>move pinned taps too, clearing their pin</span></div>
         </div>
       </section>
       <section class="cmd" id="cmd-reinstall" data-search="reinstall reinstall a skill or all skills (force) reinstall an installed skill, rule or workflow (force) --all name">
@@ -1254,7 +1255,7 @@
 </div>
 
 <footer>
-  <p class="foot-brand"><b>boost</b> &mdash; a package manager for AI coding skills</p>
+  <p class="foot-brand"><b>boost</b> &mdash; a package manager for AI skills</p>
   <p class="foot-note">Install with <code>pip install boost-skill-cli</code> &middot; requires Python 3.12+ and <code>git</code></p>
   <nav class="foot-links" aria-label="Documentation">
     <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/demo.html

@@ -266,7 +266,7 @@
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/design-roadmap.html

@@ -578,7 +578,7 @@ hidden hot-path cost hiding behind the one this card measured.</p>
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.9+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/eval.html

@@ -578,7 +578,7 @@
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/index.html

@@ -4,8 +4,8 @@
 <meta charset="utf-8">
 <link rel="icon" href="data:image/svg+xml,%3Csvg xmlns='http://www.w3.org/2000/svg' viewBox='0 0 100 100'%3E%3Crect width='100' height='100' rx='20' fill='%2307080f'/%3E%3Ctext x='50' y='70' font-size='58' font-family='monospace' font-weight='bold' fill='%2340cbe3' text-anchor='middle'%3E%E2%9C%A6%3C/text%3E%3C/svg%3E">
 <meta name="viewport" content="width=device-width, initial-scale=1">
-<meta name="description" content="boost is a package manager for AI coding skills — find, install, and govern the SKILL.md, rule, and workflow files that Claude Code, Cursor, and Windsurf run on, wired into every agent in one pass.">
-<title>boost — Homebrew for AI coding skills</title>
+<meta name="description" content="boost is a package manager for AI skills — find, install, and govern the SKILL.md, rule, and workflow files that Claude Code, Cursor, and Windsurf run on, wired into every agent in one pass.">
+<title>boost — Homebrew for AI skills</title>
 <!-- Canonical Aurora tokens + primitives (single source of truth). The
      inline block below carries ONLY page-specific layout, and wins ties
      by coming later in the cascade. -->
@@ -561,10 +561,10 @@
   <!-- ================= HERO ================= -->
   <div class="wrap hero">
     <span class="badge">AI Skill Package Manager · on PyPI</span>
-    <h1><span class="grad">Homebrew</span> for AI coding skills.</h1>
+    <h1><span class="grad">Homebrew</span> for AI skills.</h1>
     <p class="lede">
       Boost is a command-line package manager that <b>searches, installs, and
-      manages AI coding skills</b> from GitHub-hosted registries — then wires
+      manages AI skills</b> from GitHub-hosted registries — then wires
       them into <b>Claude Code, Windsurf, Cursor and Gemini CLI</b> at once. One command
       replaces the copy-paste-and-pray dance of setting up AI agent skills by hand.
     </p>
@@ -600,7 +600,7 @@
     <div class="wrap">
       <span class="eyebrow">The Concept</span>
       <h2 class="sec-title">What is a “skill” — and why manage them?</h2>
-      <p class="sec-sub">AI coding agents get better when you give them reusable knowledge.
+      <p class="sec-sub">AI agents get better when you give them reusable knowledge.
         Boost makes that knowledge installable.</p>
 
       <div class="concept-grid">
@@ -1019,7 +1019,7 @@ pipx inject boost-skill-cli <span class="yv">"boost-skill-cli[rag]"</span>
      offer it as "footer" in the landmark list. -->
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a aria-current="page" href="#top">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/langchain.html

@@ -566,7 +566,7 @@ builder.<span class="fn">add_edge</span>(<span class="s">"skills"</span>, <span
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/mcp-hub.html

@@ -757,7 +757,7 @@ REGISTRY.register(
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.12+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>

{boost_skill_cli-1.2.46 → boost_skill_cli-1.2.48}/docs/roadmap.html

@@ -12339,7 +12339,7 @@ bytes a structurally-correct JSON response never emits.</p>
 
 <footer>
   <div class="wrap">
-    <p class="foot-brand"><b>boost</b> — a package manager for AI coding skills</p>
+    <p class="foot-brand"><b>boost</b> — a package manager for AI skills</p>
     <p class="foot-note">Install with <code>pip install boost-skill-cli</code> · requires Python 3.9+ and <code>git</code></p>
     <nav class="foot-links" aria-label="Documentation">
       <a href="index.html">Guide</a>