Exhaustively red-team resolution logic with compiling fixtures

Finding subtle compiler/resolver bugs that only manifest across language boundaries and import patterns

• · per-language lenses (Rust, Python, PHP, Go, C#, Java, C++, Ruby, TS, JS, Swift, Kotlin, Scala, Lua)
• · per-scenario lenses (14 import/resolution patterns)

• · proven bugs array {id, artifact, construct, fixture, probe_cmd, as_is, fix_needed}
• · updated docs/findings reflecting confirmed-new cases

• · cargo/rustc/python/go/csharp/etc (per-language compilers)
• · recad binary (resolution tool)
• · git

• · recad dev binary built
• · per-language toolchains available
• · special_names_findings.html and subscription_resolution design readable

• · Fixture doesn't actually compile (false positive)
• · Recad behavior not as claimed by probe
• · Finding already covered (not new)
• · Race in concurrent compilations/probes

• · 6-phase Build → Seed → Red-team → Verify → Edit → Deploy
• · 30+ cycles of red-teaming (not a one-pass audit)
• · COMPILING fixtures validate construct genuinely reproduces
• · Per-language and per-scenario lenses exhaustively cover space