From fd11d08a89c23fd5eac21f4fd63de0a2cc01b603 Mon Sep 17 00:00:00 2001 From: DongHyeonka Date: Wed, 4 Nov 2026 22:08:25 +0900 Subject: [PATCH] =?UTF-8?q?fix(docs):=20=EC=B0=B8=EC=A1=B0=20=EA=B8=B0?= =?UTF-8?q?=EB=8A=A5=20=EC=A0=84=EC=9A=A9=20script=EB=A5=BC=20=EB=AC=B8?= =?UTF-8?q?=EC=84=9C=20=EA=B2=80=EC=82=AC=EA=B0=80=20=EC=9A=94=EA=B5=AC?= =?UTF-8?q?=ED=95=98=EC=A7=80=20=EC=95=8A=EA=B2=8C=20=EC=A0=81=EB=8A=94?= =?UTF-8?q?=EB=8B=A4?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 문제 test:sample-removal은 참조 기능을 지울 때 그 전용 script test:reference-feature도 package.json에서 지운다. 샘플을 지운 프로젝트도 같다. 그런데 docs/testing/taxonomy.md와 원장 두 행이 그 script를 백틱·명령 형태로 적어, 문서 검사가 "names package scripts that do not exist: test:reference-feature"로 실패했다(b6bfc9b snapshot의 드릴 실행). 고른 방법 - 참조 기능 경로와 같은 규칙(patterns.md 첫머리): 참조 기능이 가진 script는 백틱이나 `corepack pnpm` 없이 적고 "참조 기능과 함께 지워진다"를 붙인다. 위험·한계 - 템플릿에서도 문서 검사가 이 script 이름의 존재를 보지 않는다. 검증 - 샘플·SAMPLE_EXTRAS·fixture 전용 테스트를 지우고 test:reference-feature를 package.json에서 뺀 복사본(sim-sample-docs.sh)에서 verify:documentation PASS_SCOPED. 저장소에서도 PASS_SCOPED. Refs: docs/reviews/2026-11-03-maturity-review/14-template-product-docs.md 14-04 --- docs/operations/adapter-remediation-ledger.md | 4 ++-- docs/testing/taxonomy.md | 2 +- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/docs/operations/adapter-remediation-ledger.md b/docs/operations/adapter-remediation-ledger.md index 5e48aab7..78819d06 100644 --- a/docs/operations/adapter-remediation-ledger.md +++ b/docs/operations/adapter-remediation-ledger.md @@ -194,7 +194,7 @@ Captured after every correctness task landed. | `git diff --check` | 0 | clean | | `corepack pnpm test:component` | 0 | 126 passed | | `corepack pnpm test:integration` | 0 | 52 passed | -| `corepack pnpm test:reference-feature` | 0 | 26 passed | +| test:reference-feature (the reference sample's script) | 0 | 26 passed | | `corepack pnpm test:recipes` | 0 | 17 passed | | `corepack pnpm test:unit` | 1 | 1585 passed / 19 failed tests; the 19 are the unchanged pre-existing `ci-artifact-contract` sandbox failures | | `corepack pnpm check:registries` | 0 | 11 registries PASS | @@ -340,7 +340,7 @@ Run on the landed tree. Only what actually passed is claimed as passing. | `tests/unit` + `tests/integration`, no exclusions | — | 1643 passed / 1747; the 104 failures are the four environmental files below | | `corepack pnpm test:component` | 0 | 126 passed | | `corepack pnpm test:recipes` | 0 | 17 passed | -| `corepack pnpm test:reference-feature` | 0 | 26 passed | +| test:reference-feature (the reference sample's script) | 0 | 26 passed | ### Environmental failures, not claimed as green diff --git a/docs/testing/taxonomy.md b/docs/testing/taxonomy.md index 46e5d172..f3a199e9 100644 --- a/docs/testing/taxonomy.md +++ b/docs/testing/taxonomy.md @@ -18,7 +18,7 @@ Each gate is blocking in its declared scope. Failures are not downgraded with `test:all` is the normal product-development loop. It runs, in order, `test:runtime-schema`, `test:unit`, `test:contract`, `test:component`, -`test:integration`, `test:reference-feature`, `test:platform` (`tests/platform` +`test:integration`, test:reference-feature (removed with the reference sample), `test:platform` (`tests/platform` and `tests/architecture`), `check:release-coherence` and `test:recipes` (`package.json` `test:all`). It does not include `test:system`. CI-runner and supply-chain assurance has different host prerequisites and is invoked