Skip to content

fix(blacksmith): tailscale/headscale is a network credential; time out on the slowest healthy run - #54

Open
jtomaszewski wants to merge 1 commit into
mainfrom
fix/blacksmith-network-cred
Open

fix(blacksmith): tailscale/headscale is a network credential; time out on the slowest healthy run#54
jtomaszewski wants to merge 1 commit into
mainfrom
fix/blacksmith-network-cred

Conversation

@jtomaszewski

@jtomaszewski jtomaszewski commented Sep 9, 2026

Copy link
Copy Markdown
Contributor

Two corrections from the skill's first real run on a client repo.

  • inventory.sh — a job that joins a LAN via tailscale/github-action with a headscale pre-auth key was suggested for migration; the network-credential regex only knew WireGuard/OpenVPN. Added tailscale, headscale, TS_AUTHKEY. The skill text names the case too.
  • Timeout rule — "1.5 × the slowest run" anchored on a 56-minute cache-restore stall, i.e. the pathology being removed. Now "the slowest healthy run".

plugin.json 1.7.0 → 1.7.1. shellcheck and bash -n clean.

🤖 Generated with Claude Code


View with [code]smith Autofix with [code]smith
Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.

…tial; time out on the slowest healthy run

First real run of the skill on a client repo. The inventory suggested migrating a
nightly that joins the client's LAN through a headscale pre-auth key — the regex only
knew WireGuard. A tailscale/headscale join is the same thing: a network-scoped
credential that should keep originating where it does today.

The timeout rule also said "1.5 × the slowest run", which on that repo was a 56-minute
cache-restore stall — the exact thing the migration removes. The slowest *healthy* run
is the right anchor.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant