root 3963b28b50 aibridge: fix glob_match — remove dead panic branch + add multi-* support
Iter 9 scrum flagged routing.rs with OffByOne + NullableConfusion risks
on the glob matcher. Two real bugs in one function:

1. The `else if parts.len() == 1` branch was dead AND panic-hazardous:
   split('*') on a string containing '*' always yields ≥2 parts, so
   the branch was unreachable — but if ever reached (via future
   caller or split-behavior change), `parts[1]` would index out of
   bounds and panic.

2. Multi-* patterns like `gpt-*-large*` fell through to exact-match
   because the `parts.len() == 2` branch only handled single-*. Result:
   a rule like `model_pattern: "gpt-*-oss-*"` would only match the
   literal string "gpt-*-oss-*", never an actual gpt-4-oss-120b.

Fix walks parts left-to-right: prefix check, suffix check, each
interior segment must appear in order. Cursor-advance logic ensures
a mid-segment that appears before cursor (duplicate prefix) can't
falsely match.

8 new tests cover: exact match, exact mismatch, leading/trailing/bare
wildcards, multi-* in-order, multi-* wrong-order (regression guard),
and the old panic-hazard case ("a*b*c" variants) as an explicit check.

Workspace warnings unchanged at 11.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-24 06:21:11 -05:00
2026-04-23 02:36:45 -05:00
2026-04-22 02:41:15 -05:00
2026-03-27 05:54:09 -05:00
2026-04-22 02:41:15 -05:00
Description
Rust-first object storage system
6.3 GiB
Languages
TypeScript 38.4%
Rust 35.8%
HTML 13.9%
Python 7.8%
Shell 2.1%
Other 2%