Add commons v1.1.0 schema surface

[GsCommand]

Motivation

• Implement Phase 1 of the Commons v1.1.0 migration by adding a self-contained, simplified Commons schema surface alongside existing v1.0.0 artifacts.
• Provide a flat, minimal request/receipt pair for each of the 10 canonical verbs and make the new schemas consumable from the package exports and docs.
• Prepare the package for publish/pin readiness while preserving historical artifacts and avoiding shared $ref usage in v1.1.0.

Description

• Added a new schemas/v1.1.0/commons folder containing 20 standalone schema files (request + receipt) for the verbs: analyze, classify, fetch, format, parse, summarize, clean, convert, describe, and explain, with requests following the specified verb/version/input/mode shape and receipts containing the tightened trust spine and conditional allOf rules.
• Exposed explicit named exports for every v1.1.0 request/receipt pair via a new index.js so consumers can import { analyzeRequestV110 } from "@commandlayer/commons".
• Updated package metadata to version: 1.1.0, added index.js to package files, added exports/main fields, updated manifest.json to point at schemas/v1.1.0, and left the new schemas_cid as PENDING for pinning during release.
• Updated docs and release notes by adding a CHANGELOG.md entry for 1.1.0, and extended README.md with a Commons v1.1.0 section and concrete example paths; also regenerated checksums.txt for the schemas/ tree.
• Adjusted validation scripts to scan schemas/ and relaxed AJV strictRequired for compilation of conditional receipt rules while keeping strict validation otherwise.

Testing

• Ran schema compilation and example validation with npm run validate (which runs node scripts/validate-all.mjs and node scripts/validate-examples.mjs), and all schemas and examples compiled/validated successfully.
• Regenerated checksums with npm run checksums:gen and verified checksums.txt was written successfully.
• Verified package consumability with node -e "import('./index.js').then(m => console.log(Object.keys(m).sort().join('\n')))" and confirmed expected exports are present.
• Performed a packaging dry-run with npm pack --dry-run to confirm package contents; no publish was performed and the pinned CID remains PENDING to be updated during the release/pin step.

---

Codex Task