Files
msd-core/tests/fixtures/representative/api-coverage-detector
Jakub Zych a9a7a328e6 refactor: hard-fork GSD -> MSD (Make Software Done)
Mechanical rename produced by scripts/msd-rename.cjs: gsd/Gsd/GSD -> msd/Msd/MSD
across contents and paths, upstream package/repo coordinates -> @golem15/msd-core
and golem15com/msd-core. Deep links into upstream history, sibling upstream
packages, the GSD-2 import feature, CHANGELOG.md and .changeset/ are kept as-is.

Hand edits on top: MSD block-letter banner and logos, LICENSE copyright line,
package/plugin identity, regenerated lockfile, install-tree fixtures, derived
registries and benchmark baseline; migration checksum baseline re-locked
(MSD keeps its own install state, so no install had applied the old sums);
sort-order and regex-escaped expectations in tests adjusted.
2026-10-06 01:47:40 +02:00
..

API-coverage detector fixtures (#2365)

Verbatim reproduction lines from #2365, each used as a PLAN.md body and driven through check api-coverage.verify-pre <phaseDir> — the real blocking gate, not detectApiIntegration() called in isolation.

  • nextjs-route-path.txt — a first-party Next.js route path read as an external API signal because / is a word boundary.
  • unrelated-verb-noun.txt — a verb and a noun on the same line, unrelated clauses, no compound relation.
  • threat-model-prose.txt — a threat-model table cell describing a LOCAL interface, misread as a third-party service name.
  • non-integration-assertion.txt — a line that explicitly states no new integration was added, misread as evidence of one.

The first three currently detected: true; the gate expects false for all four (see MANIFEST.json's expectedDetected/currentBuggyOutput fields). non-integration-assertion.txt already returns detected: false in isolation, so it's asserted directly. The other three are asserted against their currentBuggyOutput in tests/representative-corpus.test.cjs — a characterization of today's known-broken behavior, not a todo (see tests/fixtures/representative/README.md for why todo doesn't work with this repo's test-runner) — until #2365 lands.