Release v4.65.0

Added

• A named validation rule on a command can carry an implementation block with ordered hint lines and, optionally, the rule's file or tagged code fence. A rule with only hints, or an empty block, records pending implementation intent. (part of #307)
• Pending rules are valid source but report PLAY0268 when bound. A rule whose implementation is attached binds exactly as before, and adding, editing or reordering its hints does not change the executable model, requirement identity or content hash. (part of #307)
• Both compilers, the Monaco and VS Code editors, MCP inventories and typed authoring understand the new block, and workspace edits and refactorings keep each pending rule's obligation with its rule or refuse the edit. (part of #307)

Changed

• implementation blocks are rejected on concept rules, built-in property rules and whole-command require/validate bodies, with matching diagnostics in both compilers and the editors. Files without implementation blocks parse, print and serialize as before. (part of #307)