Align package validation with v1.1.0 package boundary

[GsCommand]

Motivation

• The package files/exports expectations in scripts/validate-all.mjs still assumed the older, broader surface which caused schema validation failures like package files surface drift after package.json was narrowed to the v1.1.0-only release surface.

Description

• Update scripts/validate-all.mjs to expect the exact v1.1.0 package files list: schemas/v1.1.0/, examples/v1.1.0/, manifest.json, checksums.txt, README.md, LICENSE, and index.js by replacing the previous surface check with EXPECTED_PACKAGE_FILES.
• Replace the partial exports assertions with a deep equality check against the exact v1.1.0 export map EXPECTED_PACKAGE_EXPORTS, which includes ., ./manifest.json, ./checksums.txt, ./schemas/v1.1.0/*, and ./examples/v1.1.0/*.
• Keep existing schema validation logic and version handling unchanged, and remove the unused CANONICAL_PACKAGE_SURFACE import from the script.

Testing

• Ran npm run validate which invokes the full validation flow and the command completed successfully with all steps passing (schemas, examples, integrity, and pack validations).
• Running node scripts/validate-all.mjs directly also returned successful validation for the v1.1.0 package boundary.

---

Codex Task