Skip to content

fix: harden public correctness before v0.1.2#1

Open
mireya-o wants to merge 1 commit into
mainfrom
fix/public-credibility-v0.1.2
Open

fix: harden public correctness before v0.1.2#1
mireya-o wants to merge 1 commit into
mainfrom
fix/public-credibility-v0.1.2

Conversation

@mireya-o

@mireya-o mireya-o commented Apr 8, 2026

Copy link
Copy Markdown
Owner

Summary

  • align the public runtime contract to Python 3.11+
  • fix deterministic grading for tool_error events
  • reject invalid diff comparisons when suite identity or case sets do not match
  • add targeted tests for the corrected blocking paths

Why

The public repo was still declaring Python 3.10+ while suite parsing requires stdlib tomllib in practice, and the blocking path needed stricter correctness before any real external validation.

Validation

  • ruff check .
  • pytest -q
  • fresh-clone README quickstart:
    • run exit = 0
    • diff exit = 0
  • fresh-clone golden path demo:
    • status = SUCCESS
    • expected pass/fail diff behavior observed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant