claude-hdb
42c1f63c95
A bare host got two DIRTYs (the box-to-box drop 'MISSING', the host's Tailscale resolver) and a 'NOT fit to mint (or to drill)' verdict — and the very next drill run went 84/84 green from that exact state. Missing from a stack and never set up are different findings: the network, profile and ACL sections already knew this; the firewall and resolver sections now do too. FRESH (no boxnet) downgrades both to information — the VPN resolver is still named, as a fact about the host that setup-host pins around, not a fault in a stack that does not exist. The clean verdict on a fresh host now says what to actually do: run setup-host, or the drill, which sets the host up itself. Verified both paths live: standing stack → 'clean', post-teardown → 'fresh' with no DIRTYs. Also: the measured drill count is 84 (README said 83 — the box-info exposure check was a NOTE when last counted and is a PASS now). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
72 lines
4 KiB
Markdown
72 lines
4 KiB
Markdown
# Changelog
|
|
|
|
History before 0.5.0 lives in git and in [drill/RUNS.md](drill/RUNS.md),
|
|
which records not just what changed but what each drill run proved.
|
|
|
|
## 0.5.0 — 2026-07-15
|
|
|
|
The release the project was renamed in: the repo is `heavy-duty/box`, matching
|
|
the CLI it ships. Everything legacy-facing is honored forever — the
|
|
`user.claudebox=1` tag, the `.claudebox/` runbook folder, the old symlink the
|
|
installer retires — but nothing current carries the old name.
|
|
|
|
### Added
|
|
|
|
- **`codex` and `grok` templates** — OpenAI Codex CLI and xAI Grok CLI boxes,
|
|
creds-free like every template. The template mechanic (image + user +
|
|
resources, never a network or a `security.*` key) now has three tenants
|
|
beside `blank`, and the drill mints all of them cold.
|
|
- **`box expose <box> <port> [<host-port>]`** — a deliberate, loopback-only
|
|
door to a port inside a box, for seeing a dev server in your browser. The
|
|
listen side is always the host's `127.0.0.1` (no flag to widen it), the door
|
|
is per-port, `--list`/`--remove` manage it, and `box info` shows open
|
|
exposures — a box with a hole says so.
|
|
- **Inline resource overrides on `new`** — `--cpu <n> --memory <size>
|
|
--disk <size>` (#57). Resolution most-specific-first: flag > `BOX_CPU` /
|
|
`BOX_MEMORY` / `BOX_DISK` environment (the scripting form) > template
|
|
`box.env` > defaults. Values pass to Incus verbatim; resources are all a
|
|
flag can touch. `--from` refuses them — a clone carries its source's
|
|
resources.
|
|
- **Host lifecycle as verbs** — `box setup-host`, `box teardown-host`, and
|
|
`box migrate-host`, which re-homes pre-0.4.0 boxes onto the current stack
|
|
(`--box <n>` / `--all-boxes`, authed state preserved) and retires the legacy
|
|
bridge once empty (`--retire-legacy`).
|
|
- **The `.box/` recipe convention** — the agent-facing runbook folder a repo
|
|
can ship, renamed from `.claudebox/` (both spellings read).
|
|
|
|
### Fixed
|
|
|
|
- **VM mints no longer hang at GRUB** — Incus defaults VMs to Secure Boot on,
|
|
and a cloud image whose shim the host's OVMF doesn't trust dies with "bad
|
|
shim signature" forever. Boxes now launch with `security.secureboot=false`;
|
|
the VM boundary, not boot attestation, is the box threat model.
|
|
- **`box expose` actually delivers packets** — a trilogy of drill-found
|
|
absences: the NAT proxy needs the box's boxnet lease pinned as a static
|
|
`ipv4.address` (Incus resolves `connect=0.0.0.0` against device config, not
|
|
the lease); a loopback-sourced packet needs `route_localnet` plus a
|
|
masquerade on the bridge to leave the host and be answerable; and the box's
|
|
replies need a `ct state established,related` accept ahead of the host
|
|
firewall's input drop, which was eating them statelessly. Boxes still
|
|
cannot initiate toward the host — a box-originated SYN is a NEW flow.
|
|
- **Firewall rules now converge on upgrade** — `box-firewall.sh` rebuilds its
|
|
chains every run (add + flush + re-add) instead of skipping when they
|
|
exist, which had pinned every host to the rule set of the release that
|
|
first ran there.
|
|
- **Failed mints tell you why** — cloud-init failures print the box's own log
|
|
excerpts and leave the box up to inspect; a mint that never boots names the
|
|
likely cause (corrupt image, Secure Boot, GRUB hang) and ships a sanitized
|
|
console dump; the installer asserts it landed the ref it was asked for.
|
|
- **`grok` installs the binary it actually ships** — the installer was read,
|
|
not guessed at, and the CLI lands on the non-interactive PATH (same fix
|
|
class as codex).
|
|
|
|
### Changed
|
|
|
|
- **Debrand complete** — env vars, install dir, docs, template descriptions
|
|
and the README all say `box`; the install URL is
|
|
`heavy-duty/box` (GitHub redirects the old one, `BOX_REPO` overrides).
|
|
- **The drill grew from 47 to 84 checks** — the expose door opened, exercised
|
|
and shut (with the contract re-probed around it), every template minted
|
|
cold, a faithful pre-0.4.0 box re-homed through `migrate-host`, and the
|
|
inline resource flags asserted (including their precedence over the
|
|
environment).
|