Skip to content

fix(security): keep boundary guard self-clean - #198

Merged
allenwoods merged 1 commit into
v0.1-dev/hackforgerfrom
security/public-boundary-self-scan
Jul 10, 2026
Merged

fix(security): keep boundary guard self-clean#198
allenwoods merged 1 commit into
v0.1-dev/hackforgerfrom
security/public-boundary-self-scan

Conversation

@allenwoods

Copy link
Copy Markdown
Contributor

Summary

Prevent the boundary guard and its tests from matching their own fixture literals.

  • replace one explanatory literal with neutral wording;
  • construct sensitive test fixtures at runtime, as the existing tests already do elsewhere;
  • keep every positive/negative assertion and checker behavior unchanged.

Verification

  • 53 complete boundary tests passed;
  • both guard source files pass targeted content scanning;
  • independent static review found no P0/P1/P2 and confirmed the runtime fixture bytes are unchanged;
  • git diff --check passed.

Guard update exception

This is a dedicated two-file guard update. Its branch was pushed with the required audited --no-verify exception. The trusted guard-integrity step is expected to reject it until an explicit security-admin merge. Reinstall the immutable hook after merge.

@allenwoods
allenwoods requested a review from a team as a code owner July 10, 2026 08:15
@allenwoods
allenwoods merged commit b87b90f into v0.1-dev/hackforger Jul 10, 2026
3 of 6 checks passed
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