fix(doctor): a fresh host is not a dirty one #62
No reviewers
Labels
No labels
blocked
blocker:ci-red
blocker:conflict
blocker:drill-pending
blocker:unrequested
bug
claimed
documentation
enhancement
epic
merge-next
needs-triage
ready
release
scope:cli
scope:drill
scope:host
scope:installer
scope:templates
scope:tiers
stale
state:addressing
state:bots-reviewing
state:building
state:needs-human
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: heavy-duty/box#62
Loading…
Reference in a new issue
No description provided.
Delete branch "fix/doctor-fresh-host"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
From the green run's preamble: the doctor gave a bare host two DIRTYs (box-to-box drop "MISSING — boxes can reach each other", the host's Tailscale resolver) and declared it "NOT fit to mint boxes (or to drill)" — then the drill went 84/84 green from that exact state.
Missing from a stack and never set up are different findings. The network/profile/ACL sections already knew this ("does not exist — a fresh host"); the firewall and resolver sections now do too:
FRESH(no boxnet) downgrades both to information. The VPN resolver is still named — it's a real fact about the host — but as "noted, not a fault: setup-host pins around it", not a DIRTY.fresh — run box setup-host (or the drill — it sets the host up itself)instead of implying the host is ready to mint.Verified both paths live on a real stack: standing stack →
clean, post-teardown →freshwith zero DIRTYs.Rider: 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); README and CHANGELOG updated to match the green run.
🤖 Generated with Claude Code