CONFIG_SCHEMA_POINTER

const CONFIG_SCHEMA_POINTER: "https://gauntsloth.app/schema/v2/gsloth-config.schema.json" = 'https://gauntsloth.app/schema/v2/gsloth-config.schema.json'

Defined in: _worktrees/docs-release/gaunt-sloth/packages/core/src/constants.ts:39

$schema pointer written into a generated .gsloth.config.json (GS2-1) so editors offer autocomplete + validation. The hosted, major-pinned URL is used rather than a relative node_modules path because the relative path only resolves when @gaunt-sloth/core sits in a node_modules beside the config, which is NOT the case for a globally-installed CLI (npm i -g): the schema lands in the global prefix, not next to the user’s project config, so a relative pointer would silently fail to resolve. A hosted URL resolves for every install mode (global, npx, local, or a hand-written config with nothing installed) and is the standard convention editors fetch + cache.

The channel is major-pinned (/schema/v2/…, not latest or alpha) so a config never revalidates against a future major it was not written for. The hosted copy is kept in sync with this package’s generated schema by the deploy runbook in websites/gauntsloth-site/schema/README.md (interim, hand-run) and, in time, PLAT-9’s automated release step. The schema still ships inside the package (files: ["./schema/*"]) as an offline artifact and golden-snapshot source of truth; it is just no longer what the pointer references.