/**
 * graphTool — branch coverage for the spec-handler paths the primary
 * tool-register suite doesn't reach: the `--resolution` choices declaration
 * (+ the `fast` path), the graph-shard-worker handler, catalog-export's
 * incremental + changed-file advisory branch, the error handler on a pipeline
 * throw, and the contributeScope / collectDashboardData hooks.
 *
 * Since release 2.11.0 Phase 5 graph mounts via `commandSpecs`; we drive each
 * spec's handler directly (the host invokes it post-parse), threading
 * positionals on the parsed-opts object under `_args`. `--resolution` is now
 * validated declaratively (`choices: ['exact','fast']`) by the host's mount
 * layer — its rejection of an out-of-set value is covered in
 * `cli/src/__tests__/mount-command-spec.test.ts`; here we assert the spec
 * DECLARES the choices (the source of truth) and that the `fast` value flows
 * through.
 */
export {};
//# sourceMappingURL=tool-branches.test.d.ts.map