Skip to content

fix(sanitize): don't flag the shared gate's own public location - #4

Merged
juniperbevensee merged 1 commit into
mainfrom
fix/gate-location-not-a-particular
Oct 20, 2026
Merged

juniperbevensee merged 1 commit into
mainfrom
fix/gate-location-not-a-particular

Conversation

@juniperbevensee

Copy link
Copy Markdown
Collaborator

What

  • sanitize.config.json: one do_not_flag_examples entry covering the public location of the shared sanitization gate (cyborg-garden/swarm-map) and other public infrastructure a package depends on.

Why

#3's gate run flagged SETUP.md for naming cyborg-garden/swarm-map, which every package built from this template must name to pin the gate. It is public infrastructure, not a particular, so every new package would hit the same false flag.

🤖 Generated with Claude Code

Every package copied from this template names cyborg-garden/swarm-map
when it pins the shared gate, and the semantic layer read that as a
particular. It is public infrastructure, not an engagement detail.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
@juniperbevensee
juniperbevensee merged commit d801af0 into main Oct 20, 2026
1 check passed
@juniperbevensee
juniperbevensee deleted the fix/gate-location-not-a-particular branch October 20, 2026 05:03
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