Skip to content

🧪 Evals tests observe behavior instead of retired library fields - #83

Open
ebigunso wants to merge 3 commits into
feature/2026-09-29/evals-cleanup-binding-oncefrom
feature/2026-09-29/evals-cleanup-library-surfaces
Open

ebigunso wants to merge 3 commits into
feature/2026-09-29/evals-cleanup-binding-oncefrom
feature/2026-09-29/evals-cleanup-library-surfaces

Conversation

@ebigunso

Copy link
Copy Markdown
Owner

The evals test modules stop reading surfaces the library cleanup removes (evals value-audit cleanup Task_12).

  • Assertions that read the library's configured_object_types telemetry echo now check what they meant: the native candidate kinds actually returned. The hybrid check that Entity is excluded keeps its contract through the library's structured empty-scope error for an Entity-only request.
  • Test uses of CURRENT_SCHEMA_VERSION move to DEFAULT_SCHEMA_VERSION, the one constant the library keeps. The get_oxigraph_path reader already went with Task_8.

Two test modules; production bytes are identical. All four gates pass against both library c0ed9e21, before the cleanup, and library 9c885e14, the library value-audit cleanup's final tip: 372 tests, none excluded. This is the paired change the library cleanup plan names, so the two stacks can merge together. evals-reviewer APPROVED with no findings.

Stacked on #82.

🤖 Generated with Claude Code

…-binding-once' into feature/2026-09-29/evals-cleanup-library-surfaces
…-binding-once' into feature/2026-09-29/evals-cleanup-library-surfaces
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