capabilities · diagnostics
A repair loop should look like evidence, not prose
Use the compiler-only path repeatedly, carry structured source context into the repair, then escalate to vendor tooling only when the target environment needs to establish acceptance.
inner loop
2ot check --fast
Compiler analysis without vendor startup.
mapping
vendor aligned
Keep matching vendor diagnostics attributable.
repair input
structured context
Stable code, location and semantic context.
ILLUSTRATIVE REPAIR
From failing source to bounded repair
The useful payload is not just an error sentence. It is the diagnostic plus the source and semantic context needed to make the next edit falsifiable.
PS C:\automation> 2ot check --fast
E142 · type mismatch · Mixer.st:42:18
expected BOOL, found REAL
↳ source context
Enable := TankLevel;
↳ repair
Enable := TankLevel > 0.0;
✓ check clean · vendor build can follow
Fast first
Avoid IDE startup in the repeated repair loop.
Context stays structured
Keep code, location, source and semantic evidence separate.
Vendor remains authoritative
Run the exact target toolchain when that stronger claim matters.