Skip to content

agent: CI scans release binaries for test-seam names - #161

Merged
jaredLunde merged 1 commit into
mainfrom
jared/release-seam-scan
Oct 7, 2026
Merged

jaredLunde merged 1 commit into
mainfrom
jared/release-seam-scan

Conversation

@jaredLunde

Copy link
Copy Markdown
Contributor

Split out of #159: only the release-binary seam scan.

  • CI's build (release) job runs mise check:release-seams after mise build:rs:release. It greps every top-level release binary for the BEYOND_AI_AGENT_TEST_ prefix and fails on any hit, so a test seam can't ship however the source spells it (concat!, a // inside a string literal).
  • tests/release_seams.rs remains the fast source-level warning and pins the scanner: it must fail on the debug build (which carries the seams) and on a concat!-assembled name, and pass a clean file.

#159's audit verified this half correct. The restore-window half of #159 is dropped (narrow MCP Events webhook edge case; current behaviour on main is acceptable).

🤖 Generated with Claude Code

https://claude.ai/code/session_01JimHGjsfk2Ktm5GxyZJKKk

The authority on "no test seam ships" is now the artifact itself: CI's
`build (release)` job runs `mise check:release-seams`, which greps every
top-level release binary for the BEYOND_AI_AGENT_TEST_ prefix and fails on
any hit. tests/release_seams.rs stays as the fast source-level warning and
pins the scanner (it must fail on the debug build and on a concat!-built
name). Split out of #159; its restore-window half is dropped.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01JimHGjsfk2Ktm5GxyZJKKk
@jaredLunde
jaredLunde enabled auto-merge (squash) October 7, 2026 15:03
@jaredLunde
jaredLunde merged commit 63ffc76 into main Oct 7, 2026
21 checks passed
@jaredLunde
jaredLunde deleted the jared/release-seam-scan branch October 7, 2026 15:06
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