feat: harness-name prevention gate + name-banlist intent (itd-74) - #1
Merged
Conversation
Two-layer guard against reintroducing banned names: - Public (CI-enforced): a harness/* banned-token family in the docs-currency lint (.abcd/docs-lint.json) — specific agent-harness names are blockers in user-facing content, with README now scanned alongside docs/ and a per-line <!-- docs-lint: allow --> escape hatch. A regression test loads the real config and asserts the family bites and respects the escape. - Private (local-only): a committed .githooks/pre-commit guard reads an untracked, gitignored banlist (.abcd/.work.local/) and refuses to stage matching content, so a name that must never appear in any public artefact is enforced without its literal string ever entering tracked content or CI config. itd-74 captures the generalisation (abcd manages both banlists; ahoy scaffolds them for any managed repo). This repo is the dogfood.
REPPL
added a commit
that referenced
this pull request
Jul 11, 2026
feat: harness-name prevention gate + name-banlist intent (itd-74)
This was referenced Jul 12, 2026
REPPL
added a commit
that referenced
this pull request
Jul 27, 2026
The registry is the itd-103 core: entries drawn only from this repo's own documented never-list, each carrying a command-position pattern over shell tokens, a blocker/warn tier mirroring the record-lint severity family, a safe successor, and a plain-language why — because the refusal itself is the lesson. Check returns allow / warn / block as values only; no stdout, no exit status. Fail-open-loud on a broken guard is the hook shim's job, so core only names the failure (ErrUnparsableCommand) and lets the caller decide. Matching is command-position only, so a hazard named inside a quoted argument never fires, while quoting is not a bypass and wrapper or environment prefixes do not hide the command. The admission gate test holds every bundled entry to its proof: each known-bad fixture fires at the declared tier, every known-good fixture fires nothing (100% true-negative floor), and known-good is at least 40% of the corpus. Known-good fixture #1 is this repo's own incident capture, the command a raw-regex guard would have refused. Assisted-by: Claude:claude-opus-5[1m]
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The deterministic guard so banned names can't creep back into published content — the generalised follow-up to the recent host-agnostic cleanup.
Two layers, split by sensitivity
Public (CI-enforced) — a
harness/*banned-token family in.abcd/docs-lint.json: specific agent-harness names are blockers in user-facing content.README.mdis now scanned alongsidedocs/; a per-line<!-- docs-lint: allow -->comment is the escape hatch. The.abcd/design record is deliberately not scanned (it records real integration decisions).Private (local-only) — a committed
.githooks/pre-commit(with no banned name in it) reads an untracked, gitignored banlist under.abcd/.work.local/and refuses to stage matching content. This is how a name that must never appear in any public artefact is enforced without its literal string ever entering tracked content or CI config — the case a public linter rule structurally cannot cover. No-op on machines without the banlist (fresh clones, CI).Tests / verification
TestDocsLintHarnessNameGateloads the real config and asserts the family flags a named harness at the right line and honours the allow-context — so deleting the family (or downgrading its severity) fails CI.build/vet/test/record-lint/docs lintall green; gofmt clean.itd-74
Draft intent capturing the generalisation: abcd manages both banlists as first-class config and
ahoyscaffolds them for any managed repo. This repo is the working prototype.Assisted-by: Claude