Skip to content

fix(job-assessment): align pay range keys between schema and scorer - #24

Merged
darthrootbeer merged 1 commit into
mainfrom
fix/ja-pay-range-keys
Oct 1, 2026
Merged

darthrootbeer merged 1 commit into
mainfrom
fix/ja-pay-range-keys

Conversation

@darthrootbeer

Copy link
Copy Markdown
Owner

Context

The findings schema described pay tiers as low/high, but the scorer and the skill read min/max. A tier written exactly as the schema said made scoring exit with an error. Found by the WP-6 agent. Ticket: JBSR-099.

Changes

  • Schema tier keys are now min/max (2 lines, one file). Code, skill and fixtures were already right.
  • Two new tests: the schema and scorer agree on key names, and a schema-shaped pay range scores correctly through the scorer and its command line.

🤖 Generated with Claude Code

https://claude.ai/code/session_01XV3Ggh86cf2xwUyz28XaN6

  • Docs updated

The findings schema described pay tiers as low/high but the scorer and
the skill read min/max. Schema now says min/max. Adds a test that the
schema and scorer agree on key names and an end-to-end scoring test.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01XV3Ggh86cf2xwUyz28XaN6
@darthrootbeer
darthrootbeer merged commit 8c856d1 into main Oct 1, 2026
5 checks passed
@darthrootbeer
darthrootbeer deleted the fix/ja-pay-range-keys branch October 1, 2026 21:04
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