Tighten validation and package metadata

[GsCommand]

Motivation

• Remove dead or duplicated implementation and meta-data that could mislead consumers or cause packaging omissions.
• Centralize strict JSON loading and duplicate-key detection to a single canonical loader to avoid drift and maintenance burden.
• Ensure publish-time metadata includes integrator guidance and scoped-package publish defaults without changing schema semantics or $id values.

Description

• Deleted tsconfig.json because the repo does not actively compile TypeScript and the include path endpoints/**/*.ts was a dead placeholder (file removed: tsconfig.json).
• Replaced ad-hoc JSON loading and inline duplicate-key detection with the canonical loader by importing loadJsonStrict and switching all loadJson calls to loadJsonStrict in scripts/validate-examples.mjs and scripts/validate-all.mjs, and removed the duplicated duplicate-key detection code (files modified: scripts/validate-examples.mjs, scripts/validate-all.mjs).
• Updated package distribution metadata to include INTEGRATOR.md in the files array and added publishConfig.access = "public" to package.json so scoped packages publish without extra flags (file modified: package.json).
• Added a concise authoritative note about schema identity and trust clarifying that https://commandlayer.org/... is the canonical namespace, the repository/package are the source of truth, and external resolution is a convenience (file modified: README.md).

Testing

• Ran the repository validation suite with npm run validate and it completed successfully with all schema, examples, and integrity checks passing.
• Ran npm pack --dry-run to confirm the published tarball contents include INTEGRATOR.md and the package layout is unchanged otherwise, and the dry-run completed successfully.
• Confirmation: automated validation still passes and no schema structure, $id values, or validation rules were altered.

---

Codex Task