sneak d4df9701f6 Drop the lint-guard shell scanner, keep the Dockerfile.lint checks (closes #121) ...

Four reviews found successive ways a shell script could run the host
linter that the hand-written scanner in cmd/vaultik/lintdocker_test.go
did not see. A shell parser cannot be complete, and it is the
machinery-over-fix the workflow rejects. The tree is already right:
script/lint is the only lint entry point and runs golangci-lint only
inside the container; keeping it so is a review matter.

Remove TestNoHostLintPathRemains and every helper and helper-test that
served only it. Keep the plain Dockerfile.lint assertions: pinned image,
config verify before run, and the per-run epoch reaching both steps.
Correct the TODO.md sentence that claimed a test proves no host lint.

Model: opus-4-8

2026-09-21 18:03:15 +00:00

..

vaultik

Drop the lint-guard shell scanner, keep the Dockerfile.lint checks (closes #121)

2026-09-21 18:03:15 +00:00