diff --git a/mise.toml b/mise.toml
index 6dd983f..e66c9f5 100644
--- a/mise.toml
+++ b/mise.toml
@@ -1,3 +1,8 @@
+# Every tool name below was checked against `mise registry` AND resolved with
+# `mise ls-remote` before being written. The previous version of this file named
+# 13 tools that do not exist in the registry, so mise emitted ~25 lines of
+# warnings on every shell entry while installing none of them.
+
 [tools]
 # Language runtimes
 node = "latest"
@@ -7,20 +12,16 @@ go = "latest"
 zig = "latest"
 java = "latest"
 bun = "latest"
-denojs = "latest"
+deno = "latest"   # was `denojs` — not a registry name
 
-# Package managers
+# Package managers / task runner
 npm = "latest"
 yarn = "latest"
 pnpm = "latest"
-pip = "latest"
-cargo = "latest"
-go-task = "latest"
+just = "latest"   # the estate's task runner (Justfile)
 
-# Formatting & Linting
-gofmt = "latest"
+# Formatting & linting
 black = "latest"
-isort = "latest"
 ruff = "latest"
 prettier = "latest"
 shfmt = "latest"
@@ -31,27 +32,53 @@ cmake = "latest"
 make = "latest"
 ninja = "latest"
 
-# Shell tools
-git = "latest"
-gnu-sed = "latest"
-gnu-tar = "latest"
-gnu-grep = "latest"
-
-# Testing
-vitest = "latest"
-pytest = "latest"
-jest = "latest"
+# ---------------------------------------------------------------------------
+# REMOVED — none of these resolve in the mise registry, so they installed
+# nothing and only produced warnings. Grouped by why they were wrong:
+#
+#   Already provided by a tool that IS listed above:
+#     cargo   -> ships with `rust`
+#     gofmt   -> ships with `go`
+#     pip     -> ships with `python`
+#
+#   Project-level dependencies, not system tools. These belong in
+#   package.json / pyproject.toml / mix.exs, not in a toolchain manager:
+#     vitest, jest, pytest, isort
+#
+#   Base system binaries that mise should not be shadowing on Linux:
+#     git, gnu-sed, gnu-grep, gnu-tar
+#   (If a GNU-vs-BSD coreutils difference ever actually bites on macOS, add
+#   `coreutils`, which does exist in the registry, rather than these names.)
+#
+#   Task runner that never installed:
+#     go-task -> not a registry name. NB the bare name `task` does not work
+#     either: `mise registry` LISTS it as `aqua:go-task/task`, but resolving
+#     `task@latest` still fails. Appearing in `mise registry` output is NOT
+#     sufficient to conclude a name resolves — check with `mise ls-remote`.
+#     `just` is listed above instead.
+# ---------------------------------------------------------------------------
 
 [env]
-# Common environment variables
 NODE_ENV = "development"
 PYTHONDONTWRITEBYTECODE = "1"
 PYTHONUNBUFFERED = "1"
 
-# Task runner alias
-[alias]
-task = "go-task"
-build = "cargo build --release || npm run build || go build"
-test = "cargo test || npm test || go test ./..."
-lint = "ruff check . || prettier --check . || black --check ."
-fmt = "ruff format . || prettier --write . || black ."
+# ---------------------------------------------------------------------------
+# REMOVED — an `[alias]` section holding what were clearly meant to be tasks:
+#
+#     [alias]
+#     task  = "go-task"
+#     build = "cargo build --release || npm run build || go build"
+#     test  = "cargo test || npm test || go test ./..."
+#     lint  = "ruff check . || prettier --check . || black --check ."
+#     fmt   = "ruff format . || prettier --write . || black ."
+#
+# mise's `[alias]` maps an alias to a TOOL PLUGIN — it does not define tasks,
+# so none of these ever ran. mise also warns that `[alias]` is deprecated in
+# favour of `[tool_alias]`.
+#
+# They are not re-added as `[tasks]`: the estate drives builds through the
+# Justfile, and a second task runner sharing the verbs `build`/`test`/`lint`/
+# `fmt` — one of which silently falls through `||` chains into a different
+# language's build — is worse than one. Use `just <recipe>`.
+# ---------------------------------------------------------------------------