김경종
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Step 2: regression-thresholds
|
|
|
|
## Read First
|
|
- /AGENTS.md
|
|
- /PLAN.md
|
|
- /PROGRESS.md
|
|
- /docs/HARNESS.md
|
|
- /docs/IMPLEMENTATION_PLAN.md
|
|
- /docs/PRD.md
|
|
- /phases/7-mvp-quality-hardening/step1.md
|
|
|
|
## Task
|
|
Define MVP regression thresholds for the sample corpus.
|
|
|
|
Thresholds should distinguish mandatory fast validation from slower/manual quality checks.
|
|
|
|
## Sprint Contract
|
|
- Done means: MVP pass/fail criteria are encoded in tests or documented commands and tied to sample metadata traits.
|
|
- Hard thresholds: mandatory validation remains runnable on the local machine; slow tests are opt-in; failed quality areas are not masked.
|
|
- Files owned: `tests/`, `scripts/`, sample metadata updates if needed, `PROGRESS.md`, phase index.
|
|
- Dependencies: Quality metrics report.
|
|
|
|
## Acceptance Criteria
|
|
```powershell
|
|
python scripts\validate_workspace.py
|
|
.\venv\python.exe -m pytest tests
|
|
```
|
|
|
|
## Verification
|
|
1. Run the acceptance commands.
|
|
2. Confirm slow tests are documented separately if needed.
|
|
3. Update `PROGRESS.md` and this phase index.
|
|
|
|
## Do Not
|
|
- Do not make local validation unusably slow.
|
|
- Do not turn all failures into warnings.
|
|
- Do not remove sample coverage for Korean paths or formulas.
|