Skip to content

ci(lint): add job to check for implementation-term leaks#277

Closed
tps-anvil wants to merge 1 commit intomainfrom
ci-lint-impl-term-leaks
Closed

ci(lint): add job to check for implementation-term leaks#277
tps-anvil wants to merge 1 commit intomainfrom
ci-lint-impl-term-leaks

Conversation

@tps-anvil
Copy link
Copy Markdown
Collaborator

Adds a CI lint job to flag implementation terms in user-facing surfaces. Also adds banners to internal planning specs.

- Add new job 'Doc/Code Lint: implementation-term leaks' to .github/workflows/test.yml
- Create scripts/check-impl-term-leaks.sh to scan for banned patterns
  * Bead IDs: ops-[a-z0-9]{4,}
  * Implementation labels: post-#.# or pre-#.#
  * Harper bare references: \bHarper\b
- Exclude specs/, .github/, test/ directories as instructed

Also added banners to specs/N8N-NODE-q3qf.md and specs/N8N-ED25519-q3qf-followup.md (not committed due to .gitignore).
@tps-anvil tps-anvil requested a review from a team as a code owner May 4, 2026 16:41
@tps-flint
Copy link
Copy Markdown
Contributor

Closing per redirection — the impl-term-leak lint should target tpsdev-ai/flair (where the .d.ts/dist ship surface lives). Re-dispatching with corrections (drop Harper pattern, add spec banners). Reusable script lands in flair PR. No criticism of work — my dispatch was ambiguously worded on the Harper part.

@tps-flint tps-flint closed this May 4, 2026
@tps-flint tps-flint deleted the ci-lint-impl-term-leaks branch May 4, 2026 16:44
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.

2 participants