devstuff 2.2.1__py3-none-any.whl → 2.3.0__py3-none-any.whl

dev_setup/catalog.py

@@ -14,6 +14,9 @@ BUNDLED_CATALOG = "tools.yaml"
 
 VERSION = 1
 VALID_KEY = re.compile(r"^[a-z0-9][a-z0-9_-]*$")
+# Fields that only mean anything to `uv tool install`, and the types that accept them.
+UV_ONLY_FIELDS = ("uv_with", "uv_executables_from", "uv_python")
+UV_TYPES = ("pip", "uvx")
 SUPPORTED_FIELDS = {
     "name",
     "description",
@@ -26,6 +29,9 @@ SUPPORTED_FIELDS = {
     "requires",
     "npm_name",
     "pip_name",
+    "uv_with",
+    "uv_executables_from",
+    "uv_python",
     "apt_packages",
     "git_url",
     "git_install_cmd",
@@ -89,6 +95,22 @@ def validate_catalog(raw: Any, *, source: Path | str = "<catalog>") -> dict[str,
         item.setdefault("category", "custom")
         item.setdefault("type", "unknown")
 
+        for field in UV_ONLY_FIELDS:
+            if field not in item:
+                continue
+            if item["type"] not in UV_TYPES:
+                types = "/".join(UV_TYPES)
+                raise CatalogError(
+                    f"{source}: tool {key!r} sets {field!r}, which is only valid on "
+                    f"type {types} (got {item['type']!r})"
+                )
+            value = item[field]
+            if field == "uv_python":
+                if not isinstance(value, str):
+                    raise CatalogError(f"{source}: tool {key!r} {field} must be a string")
+            elif not isinstance(value, list) or not all(isinstance(v, str) for v in value):
+                raise CatalogError(f"{source}: tool {key!r} {field} must be a list of strings")
+
         requires = item.get("requires")
         if requires is None:
             if item["type"] == "npm":

dev_setup/commands/add_cmd.py

@@ -61,6 +61,20 @@ def add_cmd() -> None:
     elif install_type == "uvx":
         kwargs["pip_name"] = ui.text_input("PyPI package name:", default=key, required=True)
         kwargs["check_cmd"] = ui.text_input("Command to check if installed:", default=key)
+        # All optional. Empty answers must not write empty keys into the user catalog.
+        exes = ui.text_input(
+            "Also expose executables from (space-separated packages, blank for none):"
+        )
+        if exes:
+            kwargs["uv_executables_from"] = exes.split()
+        extra = ui.text_input(
+            "Extra packages to install alongside it (space-separated, blank for none):"
+        )
+        if extra:
+            kwargs["uv_with"] = extra.split()
+        py = ui.text_input("Pin to a Python version (e.g. 3.12, blank for uv's default):")
+        if py:
+            kwargs["uv_python"] = py
 
     elif install_type == "apt":
         kwargs["apt_packages"] = ui.text_input(

dev_setup/functions.yaml

@@ -238,3 +238,101 @@ functions:
         saml2aws login --force
       fi
     docs_url: https://github.com/Versent/saml2aws
+
+  which-ansible:
+    name: Which Ansible
+    description: Show which ansible a directory will actually use — the project's uv venv or the global one
+    category: validation
+    type: script
+    params:
+      - name: path
+        description: Directory to inspect (default the current one)
+        required: false
+        default: "."
+    docs_url: https://docs.astral.sh/uv/guides/projects/
+    script: |
+      # No `set -e`: reporting "this project has no ansible" is a successful answer,
+      # not a failure, and -e would turn a stray non-zero probe into a red banner.
+      # Non-zero is reserved for "could not perform the lookup" (see whats-on-port).
+      set -uo pipefail
+
+      if ! command -v uv >/dev/null 2>&1; then
+        echo "uv is not installed, so there is nothing to inspect." >&2
+        echo "Install it with: devstuff install uv" >&2
+        exit 1
+      fi
+
+      start="${path:-.}"
+      if [ ! -d "$start" ]; then
+        echo "Not a directory: $start" >&2
+        exit 1
+      fi
+      start="$(cd "$start" && pwd)"
+
+      # Walk up for a uv project root, the same way uv itself does.
+      root=""
+      dir="$start"
+      while [ -n "$dir" ]; do
+        if [ -f "$dir/pyproject.toml" ] || [ -f "$dir/uv.lock" ]; then
+          root="$dir"
+          break
+        fi
+        [ "$dir" = "/" ] && break
+        dir="$(dirname "$dir")"
+      done
+
+      global="$(command -v ansible-playbook 2>/dev/null || true)"
+
+      if [ -z "$root" ]; then
+        echo "No uv project above $start (no pyproject.toml or uv.lock)."
+        if [ -n "$global" ]; then
+          echo "ansible-playbook here is the global one: $global"
+        else
+          echo "No ansible-playbook on PATH either — install one with: devstuff install ansible"
+        fi
+        exit 0
+      fi
+
+      echo "uv project root: $root"
+
+      declared=""
+      for f in "$root/uv.lock" "$root/pyproject.toml"; do
+        [ -f "$f" ] || continue
+        if grep -qiE '(^|[^-a-z])ansible(-core)?([^-a-z]|$)' "$f" 2>/dev/null; then
+          declared="$f"
+          break
+        fi
+      done
+
+      venv_ansible="$root/.venv/bin/ansible-playbook"
+      if [ -x "$venv_ansible" ]; then
+        echo "Project ansible:  $venv_ansible"
+        echo "                  $("$venv_ansible" --version 2>/dev/null | head -1)"
+        echo
+        echo "Inside this project, run ansible through uv so it uses that one:"
+        echo "    uv run ansible-playbook <playbook.yml>"
+        # `[ -n "$x" ] && echo ...` as the last statement of a branch would make the
+        # whole script exit 1 whenever the test is false — a correct answer reported
+        # as a failure. Use a full `if`.
+        if [ -n "$global" ]; then
+          echo "(A bare 'ansible-playbook' would use $global instead.)"
+        fi
+      elif [ -n "$declared" ]; then
+        echo "Declared in:      $declared"
+        echo "But .venv has no ansible-playbook yet — create it with:"
+        echo "    uv sync"
+        if [ -n "$global" ]; then
+          echo "Until then a bare 'ansible-playbook' uses the global $global."
+        fi
+      else
+        echo "This project does not declare ansible."
+        if [ -n "$global" ]; then
+          echo "ansible-playbook here is the global one: $global"
+        else
+          echo "No ansible-playbook on PATH — install one with: devstuff install ansible"
+        fi
+      fi
+
+      # Belt and braces for the rule above: every path that got far enough to print
+      # an answer is a success, whatever the last command happened to return.
+      exit 0

dev_setup/generic.py

@@ -95,6 +95,12 @@ class GenericTool(Tool):
     version_cmd: str = ""
     npm_name: str = ""
     pip_name: str = ""
+    # uvx/pip only. `uv tool install` exposes console scripts of the *requested*
+    # package alone, so a package whose entry points live in a dependency (ansible's
+    # live in ansible-core) needs uv_executables_from or it installs nothing usable.
+    uv_with: list | None = None
+    uv_executables_from: list | None = None
+    uv_python: str = ""
     git_url: str = ""
     git_install_cmd: str = ""
     git_remove_cmd: str = ""
@@ -113,6 +119,12 @@ class GenericTool(Tool):
             self.name = self.key
         if self.requires is None:
             self.requires = list(AUTO_REQUIRES.get(self.install_type, []))
+        # Normalise to lists so the installer can iterate without None checks. Both
+        # stay falsy when unset, so to_dict() still omits them.
+        if self.uv_with is None:
+            self.uv_with = []
+        if self.uv_executables_from is None:
+            self.uv_executables_from = []
 
     @classmethod
     def from_dict(cls, data: dict, key: str) -> GenericTool:
@@ -214,6 +226,22 @@ def _install_npm(tool: GenericTool) -> None:
         _run(["bash", "-lc", f"{_npm_init()} && npm install -g {shlex.quote(tool.npm_name)}"])
 
 
+def _uv_install_flags(tool: GenericTool) -> list[str]:
+    """Catalog uv_* fields as `uv tool install` flags.
+
+    uv records all of these in the tool's uv-receipt.toml and re-applies them on
+    `uv tool upgrade`, so they only need passing at install time.
+    """
+    flags: list[str] = []
+    if tool.uv_python:
+        flags += ["--python", tool.uv_python]
+    for pkg in tool.uv_with or []:
+        flags += ["--with", pkg]
+    for pkg in tool.uv_executables_from or []:
+        flags += ["--with-executables-from", pkg]
+    return flags
+
+
 def _install_uvx(tool: GenericTool) -> None:
     if not tool.pip_name:
         raise RuntimeError("pip_name not set")
@@ -224,7 +252,7 @@ def _install_uvx(tool: GenericTool) -> None:
             "Install it first: devstuff install uv"
         )
     with verbose.step(f"Installing {tool.name} via uvx..."):
-        _run([uv, "tool", "install", tool.pip_name])
+        _run([uv, "tool", "install"] + _uv_install_flags(tool) + [tool.pip_name])
 
 
 def _install_git(tool: GenericTool) -> None:
@@ -284,9 +312,30 @@ def _update_uvx(tool: GenericTool, version: str | None) -> None:
             "uv is required to update uvx packages. "
             "Install it first: devstuff install uv"
         )
-    target = f"{tool.pip_name}=={version}" if version else tool.pip_name
-    with verbose.step(f"Updating {tool.name} via uv tool upgrade..."):
-        _run([uv, "tool", "upgrade", target])
+    # Both paths go through `uv tool install`, not `uv tool upgrade`.
+    #
+    # `uv tool upgrade` takes a tool *name*, not a requirement, so the pinned form
+    # ("pkg==1.2.3") was read as the whole name and always failed. And it is a no-op
+    # on an already-pinned tool ("Nothing to upgrade"), which would leave a user who
+    # ever pinned with no way back to latest through devstuff. `install pkg@latest`
+    # re-resolves *and* clears the pin in one call — measured against uv 0.11.21.
+    #
+    # Passing the uv_* flags on every update is deliberate: this writes a fresh
+    # receipt, and re-deriving from the catalog means a newly added uv_with or
+    # uv_executables_from takes effect on update rather than only on reinstall.
+    target = f"{tool.pip_name}=={version}" if version else f"{tool.pip_name}@latest"
+    cmd = [uv, "tool", "install", "--force"] + _uv_install_flags(tool) + [target]
+
+    if version:
+        from dev_setup import ui
+        ui.warn(
+            f"Pinning {tool.name} to {version}. It stays there until the next "
+            f"'devstuff update {tool.key}' without --version, which moves it back "
+            f"to the latest release."
+        )
+
+    with verbose.step(f"Updating {tool.name} via uv tool install..."):
+        _run(cmd)
 
 
 def _update_apt(tool: GenericTool, version: str | None) -> None:
@@ -500,6 +549,12 @@ def _remove_npm(tool: GenericTool) -> None:
 
 
 def _remove_uvx(tool: GenericTool) -> None:
+    # An explicit remove_script wins, mirroring _remove_apt. Without this, a tool that
+    # shares a pip_name with another entry (ansible-vault shares ansible's) would
+    # uninstall the whole shared tool environment out from under it.
+    if tool.remove_script:
+        _run_bash_script(tool.remove_script)
+        return
     uv = shutil.which("uv")
     if not uv:
         raise RuntimeError(

dev_setup/tools.yaml

@@ -4,23 +4,29 @@ tools:
     name: Ansible
     description: Automation engine for configuration management and app deployment
     category: tools
-    type: apt
+    type: uvx
     check_cmd: ansible
-    apt_packages: ansible
+    pip_name: ansible
+    # The `ansible` distribution is the collections bundle and declares no console
+    # scripts of its own — `ansible`, `ansible-playbook`, `ansible-vault` and the rest
+    # are entry points of its ansible-core dependency, and `uv tool install` only
+    # exposes the requested package's scripts. Without this, the install "succeeds"
+    # and puts a single unusable `ansible-community` on PATH. Do not swap this for
+    # pip_name: ansible-core — that drops the bundled collections.
+    uv_executables_from:
+      - ansible-core
     help_cmd: ansible --help
     docs_url: https://docs.ansible.com/
-    remove_script: |
-      set -euo pipefail
-      sudo apt-get remove -y ansible
-      sudo apt-get autoremove -y
 
   ansible-vault:
     name: Ansible Vault
     description: Encrypt and manage secrets within Ansible projects (bundled with Ansible)
     category: tools
-    type: apt
+    type: uvx
     check_cmd: ansible-vault
-    apt_packages: ansible
+    pip_name: ansible
+    uv_executables_from:
+      - ansible-core
     help_cmd: ansible-vault --help
     docs_url: https://docs.ansible.com/ansible/latest/vault_guide/index.html
     requires:
@@ -525,6 +531,50 @@ tools:
       sudo apt-get remove -y 'php8.4*'
       sudo apt-get autoremove -y
 
+  python:
+    name: Python (uv-managed)
+    description: CPython provisioned by uv, installed as the default python/python3
+    category: languages
+    type: bash
+    # Every Linux host already has a python3, so "is python3 on PATH" would report
+    # this installed before it ever ran. Ask uv where its interpreters live and
+    # require the default shim to resolve *inside* that directory. `test -x` rather
+    # than `test -e` because a leftover shim pointing at an uninstalled version is a
+    # dangling symlink — readlink still prints a matching path, but it is not usable.
+    # The `test -n "$d"` guard is load-bearing: with uv absent, "$d" is empty and the
+    # case pattern would collapse to "/*", which matches every absolute path.
+    check_cmd: |
+      bin="${UV_PYTHON_BIN_DIR:-$HOME/.local/bin}"; d="$(uv python dir 2>/dev/null)"; test -n "$d" || exit 1; case "$(readlink -f "$bin/python3" 2>/dev/null)" in "$d"/*) test -x "$bin/python3";; *) exit 1;; esac
+    help_cmd: uv python list
+    docs_url: https://docs.astral.sh/uv/guides/install-python/
+    requires:
+      - uv
+    install_script: |
+      set -euo pipefail
+      uv python install --default
+      bin="${UV_PYTHON_BIN_DIR:-$HOME/.local/bin}"
+      echo
+      echo "'python' and 'python3' in $bin now resolve to uv's CPython."
+      echo "Since uv puts $bin early on PATH, that is what your shell will pick."
+      echo "The system interpreter at /usr/bin/python3 is untouched, and anything"
+      echo "with an explicit /usr/bin/python3 shebang keeps using it."
+    remove_script: |
+      set -euo pipefail
+      bin="${UV_PYTHON_BIN_DIR:-$HOME/.local/bin}"
+      target="$(readlink -f "$bin/python3" 2>/dev/null || true)"
+      if [ -z "$target" ] || [ ! -x "$target" ]; then
+        echo "No uv-managed default python3 found in $bin — nothing to remove."
+        exit 0
+      fi
+      # Uninstall only the version the default shim points at. `uv python uninstall
+      # --all` would also take out managed interpreters that existing `uv tool`
+      # environments were built against, breaking tools this command was not asked
+      # to touch.
+      version="$("$target" -c 'import sys; print("%d.%d.%d" % sys.version_info[:3])')"
+      uv python uninstall "$version"
+      echo "Removed uv-managed Python $version and its python/python3 shims."
+      echo "Other uv-managed versions and /usr/bin/python3 were left alone."
+
   pre-commit:
     name: pre-commit
     description: Git hook manager for automated code quality checks

{devstuff-2.2.1.dist-info → devstuff-2.3.0.dist-info}/METADATA

@@ -1,6 +1,6 @@
-Metadata-Version: 2.4
+Metadata-Version: 2.5
 Name: devstuff
-Version: 2.2.1
+Version: 2.3.0
 Summary: Development environment setup CLI for Linux
 Project-URL: Repository, https://github.com/thesawdawg/dev-setup-py
 Author-email: Sawyer <sawyerksu@gmail.com>
@@ -287,7 +287,7 @@ How "update" is performed depends on the package's install `type`:
 | Type | Latest | Specific version |
 |------|--------|-------------------|
 | `npm` | `npm install -g <pkg>@latest` | `npm install -g <pkg>@<version>` |
-| `pip` / `uvx` | `uv tool upgrade <pkg>` | `uv tool upgrade <pkg>==<version>` |
+| `pip` / `uvx` | `uv tool install --force <pkg>@latest` | `uv tool install --force <pkg>==<version>` |
 | `apt` | `apt-get install --only-upgrade` | `apt-get install <pkg>=<version>` (single package only) |
 | `git` | `git pull` (+ re-run `git_install_cmd`) | not supported — repos are cloned shallow (`--depth=1`) |
 | `script` / `bash` | Re-runs the install script | not supported — no version parameter to inject |
@@ -296,6 +296,17 @@ For `script`/`bash` packages, "update" is a full reinstall (the same script that
 `sudo` runs again), since there's no narrower update mechanism available. `devstuff update` asks
 for confirmation before doing this.
 
+`pip`/`uvx` packages go through `uv tool install` rather than `uv tool upgrade` in **both**
+columns. `uv tool upgrade` takes a tool *name*, so it cannot accept `<pkg>==<version>` at all, and
+it is a no-op on a tool that was previously pinned — using it for the "latest" column would mean
+pinning a package once left no way to move it again. `<pkg>@latest` re-resolves and clears any
+existing pin in one step. Pinning warns that the pin holds until the next `devstuff update`
+without `--version`.
+
+Any `uv_with` / `uv_executables_from` / `uv_python` fields on the package are re-applied on every
+update, so adding one to your catalog takes effect on the next update rather than needing a
+reinstall.
+
 ---
 
 ### `configure`
@@ -1132,6 +1143,7 @@ ones tools already have — for now, custom functions are hand-edited YAML at
 | `whats-on-port` | network | script | Find which process is listening on a port | `port`, `protocol` (optional: `tcp`/`udp`/`all`) |
 | `acc-check` | web-dev | script | Run the pi coding agent's `/dogfood` skill against a web URL | `url`, `instruction` (optional) |
 | `aws-saml-reauth` | web-dev | script | Reauthorize the AWS CLI via `saml2aws login --force` | `profile` (optional) |
+| `which-ansible` | validation | script | Show which ansible a directory will actually use — the project's uv venv or the global one | `path` (optional) |
 
 #### `whats-on-port`
 
@@ -1163,6 +1175,32 @@ so a missing `ss` names the apt package instead of surfacing "command not found"
 
 ---
 
+#### `which-ansible`
+
+```bash
+devstuff run which-ansible              # the current directory
+devstuff run which-ansible ~/infra      # somewhere else
+```
+
+Answers "if I type `ansible-playbook` here, which one runs?" — the project's own uv venv, or the
+global tool install. It walks up for a `pyproject.toml`/`uv.lock` the way uv does, then reports
+whichever applies:
+
+- a synced project venv, plus the `uv run ansible-playbook` invocation that uses it (and what a
+  bare `ansible-playbook` would pick instead);
+- ansible declared but not synced yet, pointing at `uv sync`;
+- no ansible in the project, or no project at all, naming the global one.
+
+Every one of those is a success and exits 0 — including "this project has no ansible", which is
+an answer, not a failure. Non-zero is reserved for not being able to look at all (no uv, or a
+path that isn't a directory).
+
+It exists because devstuff's ansible and a uv-managed ansible repo are now the *same shape* — both
+a uv-created venv — so the question stopped being "which tool is broken" and became "which
+environment am I in". See `docs/specs/uv-backbone/` for why the global one moved off apt.
+
+---
+
 ## Built-in packages
 
 ### Core
@@ -1182,13 +1220,18 @@ Optional utilities you may want on some machines.
 | Key | Name | Description | Help |
 |-----|------|-------------|------|
 | `ansible` | Ansible | Automation engine for configuration management and app deployment (`devstuff configure ansible`) | `ansible --help` |
+| `ansible-vault` | Ansible Vault | Encrypt and manage secrets within Ansible projects (bundled with Ansible) | `ansible-vault --help` |
 | `aws` | AWS CLI | Amazon Web Services CLI v2 | `aws help` |
 | `bat` | bat | cat replacement with syntax highlighting and git integration (`devstuff configure bat`) | `bat --help` |
 | `commitizen` | Commitizen | Conventional-commit prompt, semantic version bumping, and changelog generation (`devstuff configure commitizen`) | `cz --help` |
-| `eza` | eza | Modern ls replacement with git status, icons, and tree view | `eza --help` |
 | `gh` | GitHub CLI | GitHub's official CLI | `gh --help` |
+| `git-lfs` | Git LFS | Git extension for versioning large files | `git lfs --help` |
 | `htop` | htop | Interactive process and resource monitor | `man htop` |
+| `homebrew` | Homebrew | Package manager for Linux (and macOS) | `brew --help` |
+| `ipython` | IPython | Enhanced interactive Python shell with rich tab completion and magic commands | `ipython --help` |
 | `lazygit` | lazygit | TUI git client for fast, keyboard-driven git workflows (`devstuff configure lazygit`) | `lazygit --help` |
+| `llm-checker` | llm-checker | Check LLM compatibility with your hardware | `llm-checker --help` |
+| `lmstudio` | LM Studio | Run large language models locally with a GUI | `lms --help` |
 | `mkcert` | mkcert | Zero-config local HTTPS certificates | `mkcert --help` |
 | `nerd-font` | JetBrainsMono Nerd Font | Patched font supplying the icons Starship and other CLI tools draw | `fc-list \| grep -i "nerd font"` |
 | `ollama` | Ollama | Run large language models locally | `ollama --help` |
@@ -1205,6 +1248,7 @@ Optional utilities you may want on some machines.
 |-----|------|-------------|------|
 | `go` | Go | Go programming language toolchain | `go help` |
 | `java` | Java 21 (OpenJDK) | OpenJDK 21 LTS - JDK and JRE | `java --help` |
+| `python` | Python (uv-managed) | CPython provisioned by uv, installed as the default `python`/`python3` | `uv python list` |
 | `ruby` | Ruby (rbenv) | Ruby via rbenv version manager + ruby-build | `ruby --version` |
 
 ---
@@ -1247,7 +1291,10 @@ tools:
 | `docs_url` | no | URL opened by `devstuff docs <key>` |
 | `requires` | no | List of package keys that must already be installed |
 | `npm_name` | npm | npm package name |
-| `pip_name` | pip | PyPI package name |
+| `pip_name` | pip | PyPI package name. Extras work as-is: `pip_name: "ansible-lint[lock]"` |
+| `uv_with` | no (pip/uvx) | Extra packages installed into the tool's environment (`uv tool install --with`) |
+| `uv_executables_from` | no (pip/uvx) | Also expose console scripts from these packages (`--with-executables-from`). Needed when a package's entry points live in a dependency |
+| `uv_python` | no (pip/uvx) | Pin the tool environment's Python (`--python`), e.g. `"3.12"` |
 | `apt_packages` | apt | Space-separated list of apt packages |
 | `git_url` | git | Repository URL to clone |
 | `git_install_cmd` | git | Bash command run inside the cloned repo after clone |
@@ -1256,7 +1303,21 @@ tools:
 | `install_script` | bash | Full bash script to run on install |
 | `remove_script` | bash | Full bash script to run on remove |
 
-Unknown fields fail validation. `requires` defaults to `["nvm"]` for `npm` tools and `["uv"]` for `pip`/`uvx` tools unless explicitly set.
+Unknown fields fail validation — including the three `uv_*` fields on any type other than `pip`/`uvx`. `requires` defaults to `["nvm"]` for `npm` tools and `["uv"]` for `pip`/`uvx` tools unless explicitly set.
+
+`uv_executables_from` is worth understanding before you skip it: `uv tool install` exposes the console scripts of the *requested* package only. The `ansible` distribution is a collections bundle that declares none of its own — `ansible`, `ansible-playbook` and `ansible-vault` are all entry points of its `ansible-core` dependency — so without this field the install reports success and puts a single unusable `ansible-community` on `PATH`:
+
+```yaml
+version: 1
+tools:
+  ansible:
+    name: Ansible
+    type: uvx
+    check_cmd: ansible
+    pip_name: ansible
+    uv_executables_from:
+      - ansible-core
+```
 
 ### Examples
 

{devstuff-2.2.1.dist-info → devstuff-2.3.0.dist-info}/RECORD

@@ -3,17 +3,17 @@ dev_setup/__main__.py,sha256=w-Vnqe3bgAw_UNlPywPkbOqoFKcEk2H2S79wrQjXvU4,102
 dev_setup/agent_tools.schema.json,sha256=veXnih00xW4w9yK3ruWz-npUrCnJmcQpQdFvfcu7v_I,4928
 dev_setup/agent_tools.yaml,sha256=56E70B1W7hBqjGhYhhCAGzFQvi1nUZ04cnNiqZlMjyY,4506
 dev_setup/base.py,sha256=j2EQ5gzeGgtveWQN_BgbLcZianMENJ7PQy8EQ9J9MPE,1946
-dev_setup/catalog.py,sha256=YST_dpTpIh08aLz1FBziywtKX_zFfhlU5fr56hgf0mA,5514
+dev_setup/catalog.py,sha256=PrimTBUYoh8cW9QYhXUxP8qSMeK51kzQjUoPEGD9EBw,6530
 dev_setup/cli.py,sha256=Y_RbHkexTAIQN4neDQ3buo6vmtTMNdXrsYsmY0X_Om8,2976
 dev_setup/doctor.py,sha256=JliUAgmiW2HVCWHhT76PIXTBekNXXrc0VfDMaOeLBWY,15918
 dev_setup/function_runner.py,sha256=08F6jvB9-oOyE5ivYtRjnL16JTGsfRnkpvkjSVrJhsM,6957
 dev_setup/functions.schema.json,sha256=VVdpH3xWsdbtqw47S1QqpBcs4O9wd3XZ_s0Q3sGwv0Q,6220
-dev_setup/functions.yaml,sha256=IZbdIsfRkQEvgYOjEtBMYxD-TRdqKCsoF1siWTHEYtE,9173
+dev_setup/functions.yaml,sha256=MYeBgR6mkpJZDcoSW88lCIfrtayvJViY8BZxjxedM7o,12734
 dev_setup/functions_catalog.py,sha256=YgR2hY9HM1iol1AZcF-_j02EXCP9U4P3e_5eWes9KH0,7116
 dev_setup/functions_registry.py,sha256=YSl-VgNXPf0hj4WgReg-pZUj4fAjFlwvC165dgon_BE,3682
-dev_setup/generic.py,sha256=S-5kHtvXM2xVmlJ4siZvwbaQFnkodZbuaCcvc4_1yDI,25788
+dev_setup/generic.py,sha256=Tr7YAkS_SXjExJpyNw3palDuaiNn1TcAoeZ0wHdXIeM,28424
 dev_setup/registry.py,sha256=8lrk6EXCCWk1WNeNnCGLTJ-v8rpCs7-TLYtVXgiuxnA,2243
-dev_setup/tools.yaml,sha256=3r8XV3UBJqO6WWrFlVBJ2BQ_c7r6zk0zpkrNyVXJolI,27562
+dev_setup/tools.yaml,sha256=5etktWY2tRAm7l4CG34wspdw9M-zipuhhvmJHg5ufJQ,30431
 dev_setup/ui.py,sha256=Z5nNZV8MN8tAjo1ZWq7-QPZYkPKQKuM7JbmGtiuKTqM,3806
 dev_setup/verbose.py,sha256=N3U9JAYOvFwdd8DT6W7Pqq6RCIUfbcQnPsm0O1TnvQY,5003
 dev_setup/agent/__init__.py,sha256=znrgxUCr_y0Qp-f41S6EaTv-hoTYwoZ9mOMLVge-IJg,226
@@ -32,7 +32,7 @@ dev_setup/agent/session.py,sha256=KxBBbFFvO5bBbDJ6H94O7tgtrQ2i5kGq6EsXCHaDvPo,11
 dev_setup/agent/transcript.py,sha256=hJQuSLriAe5hvnD3SCMqOWduuYtblyhmqzZQ3jDco1Y,1868
 dev_setup/agent/wizard.py,sha256=p0vHiJ-palTMoL6p7zQscL01laBFKw9f5HHY1yemZ4w,4056
 dev_setup/commands/__init__.py,sha256=47DEQpj8HBSa-_TImW-5JCeuQeRkm5NMpJWZG3hSuFU,0
-dev_setup/commands/add_cmd.py,sha256=rBdPoY6DiMLz26MewXE-lobepOYhe-55bA8GP4hrx9w,11666
+dev_setup/commands/add_cmd.py,sha256=dqgagwBDkeK47RTnIREf0PlXjfLHQpxjdQ0kHJqLqDE,12290
 dev_setup/commands/agent_cmd.py,sha256=TtsCzNVXgwxS2ACFLFl6ibnjoohEQWXgM2rfWkBnKk0,5128
 dev_setup/commands/catalog_cmd.py,sha256=dz_0UfZy3v622sbJ4AWiNftZr6yYtsjaBQw1z7UF4Lk,1002
 dev_setup/commands/configure_cmd.py,sha256=-6UQhrcdEpf6AecDfGq7otq2G4rqdeRPjJUV1lze2Zg,3738
@@ -90,7 +90,7 @@ dev_setup/configure/starship/model.py,sha256=HNkIj69DqBQFAq0VTHqPLNZT2DuBZSfF-5y
 dev_setup/configure/starship/preview.py,sha256=ZaNhNA3AeHHtPnMqrJbB9XVVXDFbH1R36jm8xyYdt2U,6145
 dev_setup/configure/starship/render.py,sha256=gDE0hbGZ9oDCR1VAZQRDm5EFYviMjj0-eSmr1EnZfn8,10262
 dev_setup/configure/starship/wizard.py,sha256=BmWl-U6ttF79gepDhCv8UxT8ZDIMe1SWnhSkA1iIrGQ,15498
-devstuff-2.2.1.dist-info/METADATA,sha256=QLY5Y0oqXNKDKuGz7uCso5sWbXNCyE927_czjOKC_Pg,68408
-devstuff-2.2.1.dist-info/WHEEL,sha256=lCkmxWfQsSc9CfIClYeavTdQeEX2toPqufh9gI35EQA,87
-devstuff-2.2.1.dist-info/entry_points.txt,sha256=48ITy9ENdXDFrTHwAyVPUpq1MDmgFqcOisOo5mAR6OQ,53
-devstuff-2.2.1.dist-info/RECORD,,
+devstuff-2.3.0.dist-info/METADATA,sha256=GN8skkw5mqOAce6_TDbHMk7SFX5EUiPQAL8w0O7Chek,72225
+devstuff-2.3.0.dist-info/WHEEL,sha256=zOwg4jB6zX2kU910N-cMawjivD6tO8NEWvE12je1bVk,87
+devstuff-2.3.0.dist-info/entry_points.txt,sha256=48ITy9ENdXDFrTHwAyVPUpq1MDmgFqcOisOo5mAR6OQ,53
+devstuff-2.3.0.dist-info/RECORD,,

{devstuff-2.2.1.dist-info → devstuff-2.3.0.dist-info}/WHEEL

@@ -1,4 +1,4 @@
 Wheel-Version: 1.0
-Generator: hatchling 1.31.0
+Generator: hatchling 1.32.0
 Root-Is-Purelib: true
 Tag: py3-none-any