Add v1.1.0 commons example tree and validation support

[GsCommand]

Motivation

• Provide a complete examples/v1.1.0/commons example tree that mirrors the v1.0.0 per-verb layout while using the new v1.1.0 schemas and the simplified flat request shape.
• Regenerate every v1.1.0 example from the authoritative schemas under schemas/v1.1.0/commons/ so examples are schema-accurate and judge-friendly.
• Make the repository validation tooling aware of both legacy v1.0.0 examples and the new v1.1.0 json/ + ts/ layout so CI and local validation work end-to-end.

Description

• Added a full examples/v1.1.0/commons tree for all ten verbs with json/valid, json/invalid, ts/valid, and ts/invalid subfolders and ~120 example files that follow the v1.0.0 naming/style patterns but use v1.1.0 schema shapes.
• Each JSON request example uses the new flat request shape (verb, version, input, optional mode) and each receipt uses the v1.1.0 receipt surface (status, timestamp, agent, request_hash, optional result_hash, optional result_cid, summary/error, signature) to match schemas exactly.
• Updated scripts/validate-examples.mjs to validate both v1.0.0 (legacy valid/invalid) and v1.1.0 (new json/valid/json/invalid) examples by preloading schemas from both schemas/v1.0.0 and schemas/v1.1.0 and checking against the correct schema IDs.
• Updated manifest.json and README.md to point to the new examples/v1.1.0 roots and to show the new json/ + ts/ structure; retained all v1.0.0 examples untouched.

Testing

• Ran node --check scripts/validate-examples.mjs which passed with no script syntax errors.
• Ran npm run validate:examples which validated both v1.0.0 and v1.1.0 examples and completed successfully.
• Ran npm run validate:schemas which compiled all schemas and reported ✅ All 45 schemas compiled successfully. with no failures.

---

Codex Task