* feat(#2401): ground <automated> verify-command paths and inherit prior-phase commands Adds a deterministic resolvability probe over each PLAN.md <automated> verify command and surfaces the nearest prior phase's proven commands to the planner at every context window. - src/verify-command-grounding.cts: recognizer (not a shell interpreter) that grounds a leading cd <literal> chain and npm --prefix <literal>, and reports unresolvable rather than guessing. Never executes command text. - gsd-tools check verify-command-paths <N>: per-phase probe, wired into plan-phase.md before the plan-check pass. - init.plan-phase gains prior_verify_commands, ungated by context_window. - gsd-plan-checker: new Verify Command Path Resolvability dimension that reports the failing target and never prescribes a replacement. Also fixes first-match-wins prefix bucketing in scripts/lint-test-file-count.cjs (readdir order is not stable across platforms, so a module whose name extends another's with a hyphen bucketed differently on Linux than on macOS). Closes #2401 Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#2401): ground the canonical --prefix form, quoted paths, and absolute cd resets Independent review found three defects in the recognizer: - npm --prefix DIR run SCRIPT never reached the script-existence check, because the pattern required npm and run to be adjacent. That is the form the docs tell planners to prefer, so script_missing never fired for it. The prefix flag and its value are now stripped before matching. - --prefix captured with \S+, so a quoted path containing a space was truncated to a stray opening quote and reported as a missing directory - a false blocker, worse than the bug this feature fixes. The capture is now quote-aware. - A chained cd whose later segment was absolute concatenated instead of resetting, producing a nonsense path and another false blocker. The fold now resets on an absolute segment. Also replaces the bespoke phase-directory regex with the canonical phase-id helpers. Real phase directories are NN-slug, not phase-N-slug, so the prior-command harvest matched nothing outside its own fixtures and the planner-inheritance half of this feature was dead code. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * refactor(#2401): source task blocks from the canonical sectionizer The module carried its own copy of the <task>-block grammar - a fourth hand-rolled mirror of the one markdown-sectionizer owns. verify.cts keeps its copy only because it needs the type= attribute the canonical helper discards; this module never reads that attribute, so it can share the owner outright instead of adding a test around a copy. extractAutomatedCommands now takes task bodies from extractTaggedBlocks and the out-of-task remainder from stripTaggedBlocks. A task-grammar parity test pins the attributed task-name set against the canonical helper across six awkward task shapes. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(#2401): extract agent-file overflow to references and repair the property arbitrary The remote matrix run came back red with 19 failures, four root causes: - agents/gsd-plan-checker.md and agents/gsd-planner.md both blew the 49152 agent cap. Their bodies move to gsd-core/references/, leaving @-reference stubs, per the documented overflow pattern. - The new checker dimension invoked gsd_run before the canonical preamble that defines it. The call is deleted outright: plan-phase.md already runs the probe and hands the result in as {VERIFY_PATHS}, so the dimension consumes that rather than re-running anything. - fc.fullUnicodeString does not exist in fast-check 4.8.0. Replaced with fc.string({ unit: 'binary' }), which covers the same 0000-10FFFF range. - Three runtime-loaded files grew; acknowledged in the existing ack fragments that already own those bare filenames, since two ack sources may never name the same path. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * test(#2401): regenerate golden install-tree fixtures for the new references Adding two files under gsd-core/references/ changes what the installer emits into every runtime's tree, so all 19 golden install-parity fixtures went stale. Regenerated with npm run gen:install-tree; the delta is exactly the two new reference paths per runtime, no removals. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * chore(#2401): backfill changeset pr number to 3678 * fix(#2401): treat ~ as a home expansion only at the start of a path Windows CI caught this on both shards; the Linux-only remote matrix cannot see it. The dynamic-path refusal rejected ~ anywhere, and a GitHub Windows runner's tmpdir is an 8.3 short name - C:\Users\RUNNER~1\AppData\Local\Temp - so a valid absolute Windows path came back unresolvable/dynamic_path. This was a production bug, not a test artifact: any Windows user whose project path carries an 8.3 short name, or any literal ~, silently lost the probe entirely - every command degrading to unresolvable with no explanation. ~ is a home expansion only at the start of a path; elsewhere it is an ordinary literal. The check is now split: $, backtick, *, ? and newline stay refused anywhere (substitution and globs, and the glob characters are illegal in Windows path components regardless), while ~ is refused only leading, tolerating one leading quote since the check runs before quote stripping. The prior tests only caught this on Windows because only Windows puts a ~ in tmpdir. Four new tests pin it on every platform via a fixture directory literally named RUNNER~1. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> --------- Co-authored-by: sim <sim@local> Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
This commit is contained in:
Tom Boucher
@@ -1172,6 +1172,64 @@ Extract reusable patterns, anti-patterns, and architectural decisions from compl
|
||||
|
||||
---
|
||||
|
||||
### `gsd-tools check verify-command-paths`
|
||||
|
||||
Deterministic resolvability probe over a phase's `<automated>` verify commands (#2401). Run
|
||||
automatically by `/gsd-plan-phase` before the plan-check pass and handed to `gsd-plan-checker`;
|
||||
runnable by hand to see what the checker saw.
|
||||
|
||||
| Argument | Required | Description |
|
||||
|----------|----------|-------------|
|
||||
| `N` | **Yes** | Phase number whose `-PLAN.md` files are probed |
|
||||
|
||||
| Flag | Description |
|
||||
|------|-------------|
|
||||
| `--raw` | Emit the JSON payload with no surrounding prose |
|
||||
|
||||
**Prerequisites:** none — an unresolvable phase degrades to a JSON payload with `readError` set
|
||||
rather than failing.
|
||||
**Produces:** JSON on stdout. Nothing is written to disk.
|
||||
|
||||
**It never executes command text.** PLAN.md is LLM-authored, so the probe only resolves paths
|
||||
and stats directories; a `package.json` it finds is read for script *names* only.
|
||||
|
||||
It grounds exactly two forms — a leading `cd <literal>` chain and `npm --prefix <literal>` —
|
||||
and refuses to guess at anything else. `pushd`, `make -C`, `yarn --cwd`, `pnpm -C`, and
|
||||
`cargo --manifest-path` are not recognized today and report `unresolvable`.
|
||||
|
||||
Each row of `commands` carries `command`, `plan`, `task`, `status`, `severity`, `reason`,
|
||||
`form`, `rawTarget`, `target`, `manifest`, `script`, `sentinel`, and `base`. There is
|
||||
deliberately **no** `suggestion` field — the probe reports what failed to resolve and leaves
|
||||
the replacement to the planner.
|
||||
|
||||
| `status` | Meaning |
|
||||
|---|---|
|
||||
| `ok` | Target resolved (a `reason` may still carry an advisory — see below) |
|
||||
| `broken` | Target does not resolve, or holds no required manifest — **blocker** |
|
||||
| `unresolvable` | The path could not be grounded (variable, glob, substitution, `~`) — warning |
|
||||
| `pending_creation` | An earlier task in this phase creates the target — not a finding |
|
||||
| `not_applicable` | No `cd`/`--prefix` to resolve, or a Nyquist `MISSING …` sentinel |
|
||||
|
||||
| `reason` | `severity` | What it means |
|
||||
|---|---|---|
|
||||
| `missing_dir` | `blocker` | The resolved directory does not exist, or is not a directory |
|
||||
| `no_manifest` | `blocker` | The directory exists but holds no `package.json` / `Makefile` the command needs |
|
||||
| `dynamic_path` | `warning` | The path contains `$`, a backtick, `*`, `?`, or `~` — refused, not guessed |
|
||||
| `outside_root` | `warning` | A bare ancestor climb (`cd ../..`); the base differs under worktree execution |
|
||||
| `script_missing` | `warning` | `npm run <script>` names a script the manifest does not define — this phase may add it |
|
||||
| `manifest_unreadable` | `warning` | `package.json` is oversized, unparseable, or not a JSON object |
|
||||
| `null` | `none` | Nothing to report |
|
||||
|
||||
A non-empty `readError` means the probe **could not look** — distinct from finding nothing.
|
||||
|
||||
```bash
|
||||
gsd-tools check verify-command-paths 3 --raw # probe phase 3's verify commands
|
||||
```
|
||||
|
||||
See [Resolve verify-command path findings](how-to/resolve-verify-command-path-findings.md).
|
||||
|
||||
---
|
||||
|
||||
## Workstream Management
|
||||
|
||||
### `/gsd-workstreams`
|
||||
|
||||
@@ -3414,3 +3414,29 @@ The load-bearing wire is the `plan-phase` lift into `must_haves.prohibitions`, s
|
||||
- A `STATE.md` with no `### Quick Tasks Completed` section at all is a normal, silent no-op for the reset step — the section is created lazily by `/gsd-quick`, not present in the project template.
|
||||
|
||||
See [Archiving quick tasks](how-to/handle-quick-and-fast-tasks.md#archiving-quick-tasks) for the full walkthrough.
|
||||
|
||||
---
|
||||
|
||||
### 161. Verify-Command Path Grounding
|
||||
|
||||
**Command:** `/gsd-plan-phase` (automatic), `gsd-tools check verify-command-paths <N>` (#2401)
|
||||
|
||||
**Behavior:** A planner authoring a per-task `<automated>` verify command has no line of sight to whether the path it just wrote actually resolves, and `gsd-plan-checker` had no deterministic way to check — so it hand-reasoned the filesystem and, in the motivating case, prescribed two successively-wrong replacement paths (the second citing a `package.json` that did not exist). Two changes close that:
|
||||
|
||||
1. **Prior-command inheritance.** The nearest prior phase's `<automated>` commands are surfaced to the planner as `prior_verify_commands`, **at every context window**. Cross-phase enrichment was previously gated on `context_window >= 500000`; at 200k the planner re-invented the command and got it wrong. This payload is a handful of one-liners, so it is never gated.
|
||||
2. **A deterministic probe.** `gsd-tools check verify-command-paths <N>` resolves each `<automated>` command's target directory and reports whether it exists and holds the manifest the command needs. `/gsd-plan-phase` runs it before the plan-check pass and hands the JSON to the checker, which acts on `severity` instead of guessing.
|
||||
|
||||
**It never executes command text.** PLAN.md is model-authored, so running it from the checker would be arbitrary code execution — and would trigger the real lint/build as a side effect. The probe only resolves paths and stats directories; a `package.json` it finds is read for script names only.
|
||||
|
||||
**Why a recognizer, not a shell parser.** Interpreting shell would mean maintaining a bad shell. Exactly two forms are grounded — a leading `cd <literal>` chain and `npm --prefix <literal>` — and any path carrying a variable, glob, substitution, or `~` returns `unresolvable`, which is a warning and never a blocker. The parser's incompleteness is the specification: it degrades to "cannot prove" rather than growing features. Refusing to guess is the fix, not a limitation of it.
|
||||
|
||||
**It reports, it never prescribes.** The payload carries the target that failed and what was missing; there is deliberately no `suggestion` field. Choosing the replacement is the planner's job — and the planner now has the prior phase's proven command to reach for.
|
||||
|
||||
**Not findings:** a target an earlier task in this phase creates (`pending_creation`), a command with no `cd`/`--prefix` at all, and the Nyquist `MISSING — Wave 0 …` sentinel, which Dimension 8 owns.
|
||||
|
||||
**Known limits:**
|
||||
- Only `cd <literal>` and `npm --prefix <literal>` are recognized. `pushd`, `make -C`, `yarn --cwd`, `pnpm -C`, and `cargo --manifest-path` report `unresolvable`.
|
||||
- Verdicts are relative to the *checker's* project root. Under parallel worktree execution the executor's root differs, so a bare ancestor climb (`cd ../..`) is reported `outside_root` as a warning rather than asserted about.
|
||||
- `script_missing` is advisory only — this phase may be adding the script — so a genuinely mistyped npm script still reaches the executor.
|
||||
|
||||
See [Resolve verify-command path findings](how-to/resolve-verify-command-path-findings.md) and [`gsd-tools check verify-command-paths`](COMMANDS.md#gsd-tools-check-verify-command-paths).
|
||||
|
||||
@@ -262,6 +262,7 @@
|
||||
"planner-reviews.md",
|
||||
"planner-revision.md",
|
||||
"planner-source-audit.md",
|
||||
"planner-verify-command-grounding.md",
|
||||
"planning-config.md",
|
||||
"prohibition-probe.md",
|
||||
"project-skills-discovery.md",
|
||||
@@ -298,6 +299,7 @@
|
||||
"verification-patterns.md",
|
||||
"verifier-phase-gates.md",
|
||||
"verifier-wiring-patterns.md",
|
||||
"verify-command-path-resolvability.md",
|
||||
"verify-mvp-mode.md",
|
||||
"workstream-flag.md",
|
||||
"worktree-branch-check.md",
|
||||
@@ -516,6 +518,7 @@
|
||||
"vendor/re2js.cjs",
|
||||
"verification-command-router.cjs",
|
||||
"verification.cjs",
|
||||
"verify-command-grounding.cjs",
|
||||
"verify-command-router.cjs",
|
||||
"verify.cjs",
|
||||
"workflow-fragments.cjs",
|
||||
|
||||
@@ -328,6 +328,7 @@ Full roster at `gsd-core/references/*.md`. References are shared knowledge docum
|
||||
| `research-documentation-lookup.md` | Shared documentation-lookup protocol (Context7 MCP + guarded CLI fallback) injected into all researcher agents. |
|
||||
| `research-philosophy.md` | Shared research philosophy (training-as-hypothesis, honest reporting, investigation-not-confirmation) injected into researcher agents. |
|
||||
| `research-verification-protocol.md` | Shared research verification protocol (4 pitfalls + pre-submission checklist) injected into researcher agents. |
|
||||
| `verify-command-path-resolvability.md` | Verify Command Path Resolvability dimension (#2401) loaded by `gsd-plan-checker`: how to consume the `{VERIFY_PATHS}` probe result (never re-run or hand-reason the filesystem), the severity/reason table, and report-never-prescribe rules. |
|
||||
|
||||
### Workflow References
|
||||
|
||||
@@ -416,6 +417,7 @@ The `gsd-planner` agent is decomposed into a core agent plus reference modules t
|
||||
| `planner-graphify-auto-update.md` | How `load_graph_context` surfaces `.last-build-status.json` auto-update state (running / failed / stale head) alongside the existing staleness annotation. Opt-in via `graphify.auto_update` (#3347). |
|
||||
| `planner-interface-context.md` | Interface context rules for executors — how to extract key interfaces/types/exports from existing code and document new interfaces that downstream plans will consume. |
|
||||
| `planner-load-graph-context.md` | Planner's load_graph_context step: knowledge-graph freshness + dependency-context query via the gsd_run launcher (extracted from gsd-planner.md). |
|
||||
| `planner-verify-command-grounding.md` | Verify Command Grounding rules (#2401): inherit `prior_verify_commands` verbatim when the story repeats, prefer `npm --prefix <dir> run <script>` over `cd <dir> && npm run <script>`, and ground every authored path. |
|
||||
| `skeleton-template.md` | SKELETON.md template emitted for new-project Walking Skeleton (Phase 1 + `--mvp`). |
|
||||
| `user-story-template.md` | User story format for MVP planning — "As a / I want to / So that" structured fields. |
|
||||
| `specless-probe-fallback.md` | Spec-less probe fallback protocol — gate (toggle + per-section absence via the shared `spec-section` helper), the deterministic edge probe (mirrors spec-phase 5.5), the in-planner prohibition recall, and the `must_haves` authoring lift; consumed by plan-phase step 7.95 when a phase SPEC omits `## Edge Coverage` / `## Prohibitions` (ADR-857 Phase 6). |
|
||||
@@ -616,6 +618,7 @@ Full listing: `gsd-core/bin/lib/*.cjs`.
|
||||
| `validate.cjs` | Pure phase variant normalization helpers (`phaseVariants`, `buildRoadmapPhaseVariants`, `buildNotStartedPhaseVariants`) used by `verify.cjs` for W006/W007 checks; no I/O, no async |
|
||||
| `verification-command-router.cjs` | Thin CJS subcommand router adapter for `gsd-tools verification` |
|
||||
| `verification.cjs` | Verification-status routing — consolidates pass/gaps_found/human_needed status from phase verifier-emitted VERIFICATION.md frontmatter (#651) |
|
||||
| `verify-command-grounding.cjs` | Verify-command path-resolvability probe (#2401) — pure `extractAutomatedCommands` (`<automated>` blocks + owning task, ReDoS-safe), `resolveVerifyCommandTarget` (grounds a leading `cd <literal>` chain or `npm --prefix <literal>` against the project root; three-state `ok`/`broken`/`unresolvable` plus `not_applicable`/`pending_creation`), `probePhaseVerifyCommands` (per-phase report backing `gsd-tools check verify-command-paths`), and `harvestPriorVerifyCommands` (nearest prior phase's commands, surfaced to the planner ungated by `context_window`). Never executes command text — PLAN.md is model-authored — and never prescribes a replacement path. Compiled from `src/verify-command-grounding.cts` |
|
||||
| `verify-command-router.cjs` | Thin CJS subcommand router adapter for `gsd-tools verify` |
|
||||
| `verify.cjs` | Plan structure, phase completeness, reference, commit validation |
|
||||
| `workflow-fragments.cjs` | In-file `<!-- gsd:section id= when= -->` marker parser/composer for GSD workflow markdown (ADR-1671, #2930) — `parseWorkflowSections` (fence/HTML-comment-aware document partition into explicit/gap sections, fail-closed on malformed/unclosed/nested/duplicate markers or an unknown `when=`), `toFragments` (maps sections to `context-composer.cjs` `verbatim` fragments — non-lossy by construction), and `renderFragments`/`composeWorkflow` (compose-within-budget then join, run BEFORE per-runtime converters so a marker attribute never reaches a path-rewrite regex). `WHEN_VOCABULARY` is a frozen 4-atom applicability set (`always`, `flag:--wave`, `state:gap-closure-phase`, `state:has-prior-phases`); widening it is an ADR amendment, not an organic edit. Compiled from `src/workflow-fragments.cts` |
|
||||
|
||||
@@ -24,6 +24,7 @@ Language versions: [English](README.md) · [Português (pt-BR)](pt-BR/README.md)
|
||||
- [Resolve edge-coverage findings](how-to/resolve-edge-coverage-findings.md) — turn the spec phase's surfaced domain-boundary edges into covered, dismissed, or backstopped spec decisions
|
||||
- [Resolve prohibition findings](how-to/resolve-prohibition-findings.md) — turn the spec phase's surfaced must-NOT constraints into resolved, dismissed, or deferred spec decisions
|
||||
- [Resolve an unreachable-workflow finding](how-to/resolve-unreachable-workflow-findings.md) — wire or fully sweep a shipped workflow that no command, agent, or skill references
|
||||
- [Resolve verify-command path findings](how-to/resolve-verify-command-path-findings.md) — fix an `<automated>` verify command whose target directory does not resolve from the executor's cwd
|
||||
- [Resolve a contract-drift finding](how-to/resolve-contract-drift-findings.md) — bring an agent's completion contract, read-tag gate, or deleted-file test reference back into agreement with the registry
|
||||
- [Resolve unreachable-guard findings](how-to/resolve-unreachable-guard-findings.md) — fix shell guards whose fallback arm cannot run, and tell "nothing to report" apart from "could not look"
|
||||
- [Resolve an ESLint glob-coverage finding](how-to/resolve-eslint-coverage-findings.md) — bring a source file that matches no lint rule under coverage, or record a reasoned exemption
|
||||
|
||||
105
docs/how-to/resolve-verify-command-path-findings.md
Normal file
105
docs/how-to/resolve-verify-command-path-findings.md
Normal file
@@ -0,0 +1,105 @@
|
||||
# Resolve verify-command path findings
|
||||
|
||||
`/gsd-plan-phase` runs a deterministic probe over every `<automated>` verify command in a
|
||||
phase's plans before the plan-check pass. When a command's target directory does not resolve,
|
||||
the plan checker reports it and planning does not pass. This page is what to do with that
|
||||
report.
|
||||
|
||||
The probe answers one narrow question — *can this command's target directory be grounded from
|
||||
the executor's cwd?* — and it answers it without ever running the command.
|
||||
|
||||
## When you will see this
|
||||
|
||||
`/gsd-plan-phase N` returns `## ISSUES FOUND` with a blocker like:
|
||||
|
||||
```
|
||||
Verify Command Path Resolvability — BLOCKER
|
||||
Plan 02-PLAN.md, task "lint and build the frontend"
|
||||
Command: cd ../../frontend && npm run lint && npm run build
|
||||
rawTarget: ../../frontend
|
||||
target: /Users/you/code/frontend
|
||||
reason: missing_dir
|
||||
```
|
||||
|
||||
## Fix it in three steps
|
||||
|
||||
### 1. Read the prior phase's proven command first
|
||||
|
||||
The planner is handed `prior_verify_commands` — the `<automated>` commands from the nearest
|
||||
prior phase that had any — at **every** context window. If a previous phase already lints or
|
||||
builds the same tree, that command resolved in a real run. Reuse it verbatim.
|
||||
|
||||
```bash
|
||||
gsd-tools query init.plan-phase N --pick prior_verify_commands
|
||||
```
|
||||
|
||||
If that returns commands, the fix is usually a copy-paste, not a new path.
|
||||
|
||||
### 2. Ground the path yourself if there is nothing to inherit
|
||||
|
||||
Check the target the probe reported:
|
||||
|
||||
```bash
|
||||
ls -d <target>
|
||||
ls <target>/package.json
|
||||
```
|
||||
|
||||
Two forms are recognized. Prefer the second:
|
||||
|
||||
| Form | When it breaks |
|
||||
|---|---|
|
||||
| `cd <dir> && npm run <script>` | Depends on the executor's cwd; a relative climb resolves differently inside a worktree |
|
||||
| `npm --prefix <dir> run <script>` | Independent of cwd — **prefer this** |
|
||||
|
||||
Rewrite the plan's `<automated>` block, then re-run `/gsd-plan-phase N`.
|
||||
|
||||
### 3. Re-run the probe by hand to confirm
|
||||
|
||||
```bash
|
||||
gsd-tools check verify-command-paths N --raw
|
||||
```
|
||||
|
||||
Every row should be `severity: none`, or carry a warning you have consciously accepted.
|
||||
|
||||
## Reading the report
|
||||
|
||||
Act on `severity`, not on `status` — a row can be `status: ok` and still carry an advisory.
|
||||
|
||||
| `reason` | `severity` | What to do |
|
||||
|---|---|---|
|
||||
| `missing_dir` | blocker | The directory is not there. Fix the path, or have an earlier task create it. |
|
||||
| `no_manifest` | blocker | The directory exists but has no `package.json` / `Makefile`. You are almost certainly one level off — this is the #2401 case. |
|
||||
| `script_missing` | warning | The manifest has no such script. Fine if this phase adds it; otherwise a typo. |
|
||||
| `dynamic_path` | warning | The path uses a variable, glob, substitution, or `~`. The probe refuses to guess. Replace it with a literal if you can. |
|
||||
| `outside_root` | warning | A bare ancestor climb (`cd ../..`). Under parallel worktree execution the base differs, so this cannot be checked. Anchor it instead. |
|
||||
| `manifest_unreadable` | warning | `package.json` is unparseable, not a JSON object, or over 512 KB. Fix the manifest. |
|
||||
|
||||
## When the report says nothing
|
||||
|
||||
**An empty report is not automatically a clean bill of health.** Tell the two apart:
|
||||
|
||||
| What you see | What it means |
|
||||
|---|---|
|
||||
| `commands: []`, `readError: null` | The phase's plans contain no `<automated>` blocks to probe. |
|
||||
| `commands: [...]`, every `severity: none` | Every command's target resolved. This is the clean case. |
|
||||
| `readError` is a non-empty string | The probe **could not look** — the phase directory or a plan file was unreadable. Not a pass. |
|
||||
| `status: not_applicable` rows | Those commands have no `cd` or `--prefix` to resolve; they run at the project root. |
|
||||
| `status: pending_creation` rows | An earlier task in this phase creates that directory. Correct and expected on a greenfield phase. |
|
||||
|
||||
## What the probe deliberately will not do
|
||||
|
||||
- **It will not run your command.** PLAN.md is model-authored text; executing it from the
|
||||
checker would be arbitrary code execution, and would trigger the real lint/build as a side
|
||||
effect.
|
||||
- **It will not suggest a replacement path.** Prescribing one is exactly the failure that
|
||||
motivated this check — the checker previously guessed twice and was wrong both times, the
|
||||
second time citing a `package.json` that did not exist.
|
||||
- **It does not recognize every launcher.** `pushd`, `make -C`, `yarn --cwd`, `pnpm -C`, and
|
||||
`cargo --manifest-path` report `unresolvable` rather than being half-parsed. Refusing to
|
||||
guess is the design.
|
||||
|
||||
## Related
|
||||
|
||||
- [Verify Command Path Resolvability](../COMMANDS.md#gsd-tools-check-verify-command-paths) — the command reference
|
||||
- [Resolve edge-coverage findings](resolve-edge-coverage-findings.md)
|
||||
- [Resolve prohibition findings](resolve-prohibition-findings.md)
|
||||
Reference in New Issue
Block a user