문제 config/ci/ungated-scripts.json의 check:feature-index 이유는 "--check는 로컬 사본이 오래됐다는 것만 알려 줄 수 있다"이다. 쓸모없다는 말로 읽혀 리뷰가 지울 후보로 올렸다. 실제로는 scripts/verify-extreme-scale.ts가 EXTREME_SCALE_GATES 첫 단계로 이 script를 부른다. 고른 방법 - 지우지 않는다. 이유 문구를 "로컬에서 생성 인덱스가 오래됐는지 확인, verify:extreme-scale(scripts/verify-extreme-scale.ts)의 첫 단계. 게이트는 인덱스를 먼저 다시 만들어서 얻는 것이 없다"로 고친다. - ungated-scripts 테스트가 EXTREME_SCALE_GATES에 이 script가 있고 이유가 verify:extreme-scale을 적는지 확인한다. verify:extreme-scale이 이 script를 그만 부르면 실패해서 다시 지울 후보가 된다. - 12-05의 나머지(script 4개 삭제, scan: 접두어 검사)는 98b9682가 했다. 버린 대안 - check:feature-index 삭제: verify-extreme-scale.ts의 단계 목록과 tests/scripts/verify-extreme-scale.test.ts를 같이 고쳐야 하고, 로컬에서 생성 인덱스가 오래됐는지 볼 방법이 없어진다. 위험·한계 - 게이트 명령은 바뀌지 않는다. CI 계약 기준선은 그대로다. 검증 - RED: 새 테스트 "names verify:extreme-scale as the user of check:feature-index"가 실패(expected 'The generated indexes (src/.generated…' to contain 'verify:extreme-scale'). - GREEN: ungated-scripts·ungated-tests·verify-extreme-scale 31/31 통과. - check:ci 세 단계를 pnpm 없이 직접 실행: generate-artifact-schemas --check PASS, check-ci-contract.ts PASS(27 gates), generate-ci-workflow --check PASS. 바꾼 테스트 eslint 통과. Refs: docs/reviews/2026-11-01-maturity-review/12-guardrails-ci.md 12-05
74 lines
5.0 KiB
JSON
74 lines
5.0 KiB
JSON
{
|
|
"schemaVersion": 1,
|
|
"entries": [
|
|
{
|
|
"script": "check:feature-index",
|
|
"reason": "Local check that the generated indexes (src/.generated/, not committed) are current, and the first step of verify:extreme-scale (scripts/verify-extreme-scale.ts), itself a local run. A gate gains nothing from it: every gate script regenerates the indexes first (generate-product-feature-index.ts)."
|
|
},
|
|
{
|
|
"script": "check:http-scenario-evidence",
|
|
"reason": "Run by scripts/run-http-scenario-evidence.ts, which is test:http-scenario-evidence in FE-GATE-007; that runner calls it by name after the scenario catalog."
|
|
},
|
|
{
|
|
"script": "check:http-scenario-evidence:fixture",
|
|
"reason": "Negative fixture run by scripts/run-http-scenario-evidence.ts (test:http-scenario-evidence, FE-GATE-007), which requires it to fail with TEST-EVIDENCE-EXECUTION-ID-MISSING."
|
|
},
|
|
{
|
|
"script": "check:remediation-ledger",
|
|
"reason": "Checks the prose ledger of the 2026-08-14 adapter re-review (docs/operations/adapter-remediation-ledger.md) against test-file markers and the file-transfer bundle budget. Later fixes removed those markers and the budget is re-set at integration, so the check reports stale claims at this commit. It is a history record run by hand, not a current contract; wiring it into a gate first needs the ledger or the markers brought up to date."
|
|
},
|
|
{
|
|
"script": "check:scale:baseline",
|
|
"reason": "Scale tier outside CI (scripts/scale/run-scale-profile.ts): it includes baseline-regression, which compares timings only on the CPU model that recorded config/scale/benchmark-baseline.json and reports incomplete elsewhere (review 11-03). Run it on that machine. The CPU-independent pr tier runs in FE-GATE-005."
|
|
},
|
|
{
|
|
"script": "check:scale:main",
|
|
"reason": "Scale tier outside CI (scripts/scale/run-scale-profile.ts): it includes baseline-regression, which compares timings only on the CPU model that recorded config/scale/benchmark-baseline.json and reports incomplete elsewhere (review 11-03). Run it on that machine. The CPU-independent pr tier runs in FE-GATE-005."
|
|
},
|
|
{
|
|
"script": "check:scale:nightly",
|
|
"reason": "Scale tier outside CI (scripts/scale/run-scale-profile.ts): it includes baseline-regression, which compares timings only on the CPU model that recorded config/scale/benchmark-baseline.json and reports incomplete elsewhere (review 11-03). Run it on that machine. The CPU-independent pr tier runs in FE-GATE-005."
|
|
},
|
|
{
|
|
"script": "check:scale:release",
|
|
"reason": "Scale tier outside CI (scripts/scale/run-scale-profile.ts): it includes baseline-regression, which compares timings only on the CPU model that recorded config/scale/benchmark-baseline.json and reports incomplete elsewhere (review 11-03). Run it on that machine. The CPU-independent pr tier runs in FE-GATE-005."
|
|
},
|
|
{
|
|
"script": "check:test-evidence",
|
|
"reason": "Local all-in-one run. CI splits it: check:test-evidence:browser (--skip-scenario-executions) in FE-GATE-008 after the browser suites, and the scenario part through test:http-scenario-evidence in FE-GATE-007."
|
|
},
|
|
{
|
|
"script": "check:test-evidence:source",
|
|
"reason": "--source-only is a subset of check:test-evidence:browser (FE-GATE-008), for a quick local run without browser results."
|
|
},
|
|
{
|
|
"script": "drill:runbooks",
|
|
"reason": "Local shortcut for all five drills. CI runs each drill as its own production gate (FE-GATE-021 to FE-GATE-025) through drill:runbook."
|
|
},
|
|
{
|
|
"script": "test:all",
|
|
"reason": "Local aggregate of suites the gates run one by one (FE-GATE-004 to FE-GATE-007). The removal checks in FE-GATE-020 run it inside their fixtures through scripts/lib/removal-fixture.ts, not through the package script graph."
|
|
},
|
|
{
|
|
"script": "test:e2e:dev",
|
|
"reason": "Runs tests/e2e against the Vite dev server (playwright.dev.config.ts) for local debugging. FE-GATE-008 runs the same specs against the production build (test:e2e)."
|
|
},
|
|
{
|
|
"script": "test:extreme-scale:focused",
|
|
"reason": "Part of verify:extreme-scale. All its paths run in FE-GATE-005 except tests/scale/global-local-independence.test.ts, which belongs to the main scale tier (see config/ci/ungated-tests.json)."
|
|
},
|
|
{
|
|
"script": "test:visual:update",
|
|
"reason": "Rewrites the visual snapshots; it is an update command, not a check. FE-GATE-008 runs test:visual."
|
|
},
|
|
{
|
|
"script": "verify:extreme-scale",
|
|
"reason": "Local aggregate of 24 scripts (scripts/verify-extreme-scale.ts). Its CPU-independent parts run in gates; the main, nightly and release scale tiers need the baseline CPU (see check:scale:main)."
|
|
},
|
|
{
|
|
"script": "verify:promotion",
|
|
"reason": "Re-verifies a promotion bundle archived by an earlier run (13-04, --archived) with provider trust keys and EXPECTED_PROMOTION_* inputs of that run. In CI the promotion job verifies the same bundle through scripts/stage-verified-promotion.ts before it uploads it."
|
|
}
|
|
]
|
|
}
|