chore(mise): remove 13 phantom tools and a no-op [alias] block (#3)

## Context

`mise.toml` in this repo named **13 tools which do not exist in the mise
registry**, plus
an `[alias]` block that never did anything. The result was roughly **25
warning lines on
every shell entry**.

Introduced across the estate by `sweep2` on 2026-07-18: one file, copied
to 427 repos, 419
carrying all 13 phantom names. This repo is one of 56 that actually
**committed** the
broken file (most of the 419 copies exist only in uncommitted local
working trees, not on
any remote).

## Three faults

**1. Thirteen names that do not resolve.** Removed, grouped by reason:

| reason | names |
|---|---|
| already provided by a listed tool | `cargo` (rust), `gofmt` (go),
`pip` (python) |
| project deps, not system tools | `vitest`, `jest`, `pytest`, `isort` |
| base system binaries | `git`, `gnu-sed`, `gnu-grep`, `gnu-tar` |
| simply misnamed | `denojs` → `deno` |

`go-task` is **dropped, not renamed**. The bare name `task` does not
work either:
`mise registry` lists it as `aqua:go-task/task`, but `task@latest` still
fails to resolve.
Worth recording — *appearing in `mise registry` output is not sufficient
to conclude a name
resolves; check with `mise ls-remote`.* `just` is listed instead,
matching the estate's
Justfile convention.

**2. The `[alias]` block never ran.** mise's `[alias]` maps an alias to
a **tool plugin**;
it does not define tasks. `build = "cargo build --release || npm run
build || go build"`
was therefore dead, and mise separately warns `[alias]` is deprecated in
favour of
`[tool_alias]`. Not re-added as `[tasks]`.

## Verification

Controlled comparison on one machine, one shell:

```
warnings citing the FIXED file   : 0
errors  citing the FIXED file    : 0
warnings citing an UNFIXED copy  : 14
```

⚠️ **A caveat worth passing on:** an earlier version of this check
reported "0 warnings"
purely because mise had refused to parse the file — `Config files ...
are not trusted`.
An untrusted `mise.toml` is silently ignored, so *absence of warnings is
not evidence of
correctness unless the file is trusted first*. The numbers above were
taken after
`mise trust`.

## Acceptance criteria

- [x] Valid TOML
- [x] Zero mise warnings/errors attributable to this file (post-`mise
trust`)
- [x] No `[alias]` section
- [ ] Reviewer confirms dropping `go-task` is acceptable (nothing
in-repo invokes `task`)
- [ ] Reviewer adds this repo's actual language toolchain if `mise.toml`
should be doing
      more than it currently does — this PR only removes what was broken

## Note deliberately not actioned

Every tool is still pinned to `latest`, which is not reproducible and
sits awkwardly beside
the estate's SHA-pinning doctrine. Changing that is a judgement call per
repo, so it is
flagged here rather than made silently.

## Model tier

**Haiku/Sonnet** — one config file, no code paths, mechanical once the
registry facts are
established.

Co-authored-by: Claude Sonnet 5 <noreply@anthropic.com>

Author: hyperpolymath

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>`.
+# ---------------------------------------------------------------------------