fix: change strict exclusive logic to use inclusive bounds ge=0.0 le=1.0 according to reference successful project cad5793 Abhilater commited on Apr 8
fix: restore full 0.01-0.99 score range to satisfy strict variance bounds 173234e Abhilater commited on Apr 8
fix: eliminate floating-point boundary precision issues with safer margins b8b6191 Abhilater commited on Apr 7
fix: keep runtime values strictly inside the validated open interval ab008ab Abhilater commited on Apr 7
fix: eliminate inclusive 0/1 boundary values from schema and metadata 536e062 Abhilater commited on Apr 7
fix: update Pydantic models to enforce strict open interval (0, 1) boundaries d13baf2 Abhilater commited on Apr 7
fix: clamp scores to strictly (0,1) exclusive per validator requiremen 950ccf2 unverified PranjaySrivastava commited on Apr 7
fix: enforce strict (0, 1) bounds on all state fields in environment b1cecb7 Abhilater commited on Apr 7
fix: remove all numeric score-like values from breakdown dict - only string status fields 10f61e0 Abhilater commited on Apr 7
fix: make grader breakdown parser-safe for phase2 score validation 77064ed Abhilater commited on Apr 7
fix: remove reward values from structured output for validator compatibility 64d5c2f Abhilater commited on Apr 7
fix: widen score safety margin to avoid parser-side boundary rounding 64e3bb3 Abhilater commited on Apr 7
fix: remove stale inference results artifact and ignore generated output 113c506 Abhilater commited on Apr 7
fix: enforce strict (0,1) task scores for validator compatibility 5a2bd66 Abhilater commited on Apr 7
fix: use injected API_BASE_URL/API_KEY for llm proxy and separate env endpoint b9f1bad Abhilater commited on Apr 7
fix: emit strict [START]/[STEP]/[END] stdout logs for phase 2 parser 6a8f9d7 Abhilater commited on Apr 7
feat: add final inference results - perfect 1.0 scores on all tasks 84a9300 Abhilater commited on Apr 6
docs: comprehensive README with professional formatting and hackathon guidelines ea53858 Abhilater commited on Apr 6