From a45c942ac860f7479bde84d07691b4247e3c76b5 Mon Sep 17 00:00:00 2001 From: Juniper Bevensee Date: Tue, 20 Oct 2026 17:57:49 +1300 Subject: [PATCH] fix(sanitize): don't flag the shared gate's own public location 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) --- sanitize.config.json | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/sanitize.config.json b/sanitize.config.json index 6595b9c..4005382 100644 --- a/sanitize.config.json +++ b/sanitize.config.json @@ -26,7 +26,8 @@ "do_not_flag_examples": [ "generic methodology (\"how to structure a handoff\", \"how to grade a source\")", "tool, API, library, or product names", - "well-known public reference material used illustratively" + "well-known public reference material used illustratively", + "the public location of the shared sanitization gate or other public infrastructure this package depends on (e.g. the cyborg-garden/swarm-map repository that hosts the gate and the tag it is pinned to)" ], "model": "moonshotai/kimi-k3" },