feat(operations): bind schemas and diagnostics

[jmagar]

Stack

Position	Branch	Base	Purpose
1	feat/product-family-architecture	main	Product-family architecture (#257)
2	feat/operations-foundation	architecture branch	Neutral operation foundation (#260)
3	feat/operations-semantic-parity	foundation branch	Donor legacy semantics (#261)
4	feat/operations-canonical-classification	semantic branch	Canonical operation classifications (#262)
5	feat/operations-schema-diagnostics	classification branch	Versioned schema identities and stable diagnostics

Summary

• add validated SchemaId and DiagnosticCode contract types with constructor and Serde validation
• derive deterministic parameter/result IDs as schema.operations.<operation>.<parameters|result>.vN
• add parameter schema, result schema, and declared diagnostic-code sets to OperationSpec
• reject operation specs whose schema IDs do not match their operation name/version
• make runtime Diagnostic carry the typed stable code
• extend all 59 generated operation classifications with versioned schema IDs and stable diagnostic vocabularies
• declare 735 operation/code relationships across 33 unique diagnostic codes
• align operation-contract.schema.json with the exact Rust OperationSpec wire shape
• add and validate a dedicated Draft 2020-12 schema for the canonical Synapse classification bundle
• correct stale target-kind and retry names in the normative model documentation

Validation

• cargo fmt --all --check
• 55 unit tests passed
• both digest-bound 59-operation integration tests passed
• canonical classification SHA-256: d7ebb3bfba204301...
• canonical fixture validated against both Draft 2020-12 schemas
• strict all-feature Clippy passed
• rustdoc with warnings denied passed
• unrelated external consumer compile passed
• architecture check passed: 37 packages, 85 internal edges
• full xtask suite passed: 206 tests
• docs manifest/checksums current: 127 files
• git diff --check

Next slice

Define concrete closed parameter/result schemas and map the stable diagnostic vocabulary into CLI exit codes, REST statuses, MCP error data, and operation events.