docs(contract): lock eval-spec identity

[jeremylongshore]

What changed

• records the canonical EvalSpec identity and the planned SkillEvalSpec profile boundary
• states that J-Rig's skill-shaped document must be adapted before shared evidence or rollout use
• adds the repo-local contract identity application document and indexes it
• corrects the kernel README and CLAUDE version references from 0.9.0 to the shipped 0.10.0
• records the documentation change in the Unreleased changelog

Why

The kernel is already at @intentsolutions/core@0.10.0, but its docs still reported 0.9.0. More importantly, J-Rig currently calls its skill-specific schema EvalSpec, while the kernel exports a different canonical EvalSpec. This PR makes the boundary explicit before the adapter work lands, preventing a second unrelated source of truth.

Tracking

• Plan: IEP-EVAL-EVOLUTION-001
• Refs bead: bd_000-projects-htjt.1
• Parent repo epic: bd_000-projects-htjt.10
• Branch: feat/iec-E10-eval-substrate-contracts
• Commit: de41909

Validation

• targeted Prettier check on changed files
• pnpm run check:version-lockstep
• pnpm run lint
• pnpm run typecheck
• pnpm run test — 49 files, 1,412 passed, 1 skipped
• pnpm run build
• pre-commit escape-scan and boundaries passed

The repo-wide pnpm run check reaches format:check but is currently blocked by pre-existing ignored python/.mypy_cache files being included in the repository-wide Prettier sweep; no changed source file is implicated.

[jeremylongshore]

Maintenance update: rebased feat/iec-E10-eval-substrate-contracts onto current origin/main and force-with-lease pushed. New head: 068d4cd (the contract/docs diff is unchanged). Existing validation evidence remains: version lockstep, lint, typecheck, tests (49 files / 1,412 passed, 1 skipped), build, boundary checks, and escape-scan passed; repo-wide format check remains subject to the documented pre-existing ignored python/.mypy_cache issue.

[jeremylongshore]

Follow-up pushed as 084c6bc: added the established platform term rollout to the Vale acceptance vocabulary. This removes the diff-specific advisory Vale findings from the new contract-identity document; the commit hook boundary check passed and CI has been re-triggered.

[jeremylongshore]

Verification update: PR #84 is clean with all reported checks green after 084c6bc.

• Contract identity is explicit: core EvalSpec remains canonical; J-Rig uses SkillEvalSpec.
• Current package and Python distribution are version-locked at 0.10.0.
• CI version-lockstep, authoring/codegen parity, boundary, prose-anchor, lint, typecheck, test, build, and CodeQL lanes are green.
• The dependent J-Rig contract branch has now also removed its diff-specific Vale spelling finding in commit 45160cc.

This satisfies the core-side acceptance for bead bd_000-projects-htjt.1; the PR remains draft until the coordinated stack is ready.