feat(cli): delegate commands to gnd by default

[lutter]

Summary

• graph <cmd> now execs gnd <cmd> (the Rust @graphprotocol/gnd binary) by default.
• graph local stays on the TS path — gnd has no equivalent command.
• New graph dev oclif command shims to gnd dev so the command stays discoverable via graph --help in TS mode.
• Set GRAPH_CLI_IGNORE_GND=1 to force every command through the oclif/TS implementation. The test suite sets this
  automatically in tests/cli/globalSetup.ts.

Dispatch lives in bin/run.js; the spawn helper in src/command-helpers/gnd.ts is shared with src/commands/dev.ts.

Test plan

• ./bin/run.js --version reports the gnd version
• GRAPH_CLI_IGNORE_GND=1 ./bin/run.js --version reports the graph-cli version
• ./bin/run.js local --help shows the TS local help (with or without the env var)
• ./bin/run.js dev --watch actually starts gnd dev
• GRAPH_CLI_IGNORE_GND=1 ./bin/run.js dev --watch also starts gnd dev (via the oclif shim)
• pnpm test:cli passes (200/200)

[changeset-bot]

🦋 Changeset detected

Latest commit: ca825d4

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 1 package

Name	Type
@graphprotocol/graph-cli	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[cloudflare-workers-and-pages]

Deploying graph-tooling with    Cloudflare Pages

Latest commit:	ca825d4
Status:	✅  Deploy successful!
Preview URL:	https://1cf3a50e.graph-tooling.pages.dev
Branch Preview URL:	https://lutter-with-gnd.graph-tooling.pages.dev

View logs

[Copilot]

Pull request overview

Makes the Rust @graphprotocol/gnd binary the default executor for graph commands while keeping the TypeScript implementation reachable via an escape hatch. bin/run.js now delegates to gnd for everything except graph local, and an oclif dev shim is added so the command stays visible in TS-mode help. The deprecated TS-side graph node install (and its local-node helpers) are removed, since installation is now handled by depending on @graphprotocol/gnd directly. CLAUDE.md docs and a changeset are added; pnpm is bumped to v10.

Changes:

• Add @graphprotocol/gnd runtime dep and dispatch wrapper (bin/run.js, src/command-helpers/gnd.ts, src/commands/dev.ts), gated by GRAPH_CLI_IGNORE_GND (set in the test global setup).
• Delete src/commands/node.ts and src/command-helpers/local-node.ts (now superseded by the gnd npm package).
• Add monorepo/cli/ts CLAUDE.md docs, changeset entry, and bump root engines.pnpm to >=10 with packageManager: pnpm@10.17.1.

Reviewed changes

Copilot reviewed 11 out of 13 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
pnpm-lock.yaml	Lockfile updates for the new @graphprotocol/gnd package and unrelated drift.
packages/cli/package.json	Adds @graphprotocol/gnd dependency; leaves progress/decompress behind.
packages/cli/bin/run.js	New top-level dispatch that execs gnd unless command is local or env opt-out is set.
packages/cli/src/command-helpers/gnd.ts	Spawn helper that resolves and execs the gnd binary, forwarding stdio/signals.
packages/cli/src/commands/dev.ts	Oclif shim that always delegates to gnd dev.
packages/cli/src/commands/node.ts	Removed — replaced by gnd dependency.
packages/cli/src/command-helpers/local-node.ts	Removed — GitHub download/install logic no longer needed.
packages/cli/tests/cli/globalSetup.ts	Forces TS mode in tests via GRAPH_CLI_IGNORE_GND=1.
package.json	Bumps required pnpm to >=10 and pins packageManager.
CLAUDE.md / packages/cli/CLAUDE.md / packages/ts/CLAUDE.md	New high-level docs for the monorepo and each package.
.changeset/...dependencies.md	Records the new @graphprotocol/gnd dependency for changesets.

Files not reviewed (1)

• pnpm-lock.yaml: Language not supported

Comments suppressed due to low confidence (1)

packages/cli/src/command-helpers/gnd.ts:16

• process.kill(process.pid, signal) is used to "re-raise" the child's terminating signal in the parent. On Windows this throws for most signal names other than SIGTERM/SIGKILL/SIGINT/0, so if the child is killed by e.g. SIGHUP the parent will crash with an unhandled exception instead of exiting cleanly. Consider wrapping in a try/catch and falling back to process.exit(1) when re-raising fails, or only forwarding the small set of signals that are portable.

  child.on('exit', (code, signal) => {
    if (signal) {
      process.kill(process.pid, signal);
    } else {
      process.exit(code ?? 1);
    }
  });

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.