Ishaan Jaffer c009f4f18f fix(tag_regex): address greptile review - security docs, strict-mode enforcement, validation order ... - Strengthen security note in tag_routing.md: explicitly state User-Agent is client-supplied and can be set to any value; frame tag_regex as a traffic classification hint, not an access-control mechanism - Move tag_regex startup validation before _add_deployment() so an invalid pattern never leaves partial router state - Enforce match_any=False strict-tag policy: when a deployment has both tags and tag_regex and the strict tag check fails, skip the regex fallback rather than silently bypassing the operator's intent - Extract per-deployment match logic into _match_deployment() helper to keep get_deployments_for_tag() readable - Add two new tests: strict-mode blocks regex fallback, regex-only deployment still matches under match_any=False		2026-03-13 20:18:36 -07:00
..
my-website	fix(tag_regex): address greptile review - security docs, strict-mode enforcement, validation order	2026-03-13 20:18:36 -07:00