김경종
38 lines
1.2 KiB
Markdown
38 lines
1.2 KiB
Markdown
# Step 3: mvp-fix-sweep
|
|
|
|
## Read First
|
|
- /AGENTS.md
|
|
- /PLAN.md
|
|
- /PROGRESS.md
|
|
- /docs/HARNESS.md
|
|
- /docs/IMPLEMENTATION_PLAN.md
|
|
- /docs/PRD.md
|
|
- /phases/7-mvp-quality-hardening/step2.md
|
|
|
|
## Task
|
|
Run a focused MVP stabilization pass based on failing quality metrics and sample smoke tests.
|
|
|
|
This step should fix only defects revealed by prior acceptance criteria and should avoid feature expansion.
|
|
|
|
## Sprint Contract
|
|
- Done means: MVP fast validation and selected sample smoke conversions pass with documented residual risks.
|
|
- Hard thresholds: fixes are test-backed; no new primary parser is introduced; out-of-scope UI/API/LLM features remain out of scope.
|
|
- Files owned: failing modules and tests identified by prior phase output, `PROGRESS.md`, phase index.
|
|
- Dependencies: Regression thresholds and quality reports.
|
|
|
|
## Acceptance Criteria
|
|
```powershell
|
|
python scripts\validate_workspace.py
|
|
.\venv\python.exe -m pytest tests
|
|
```
|
|
|
|
## Verification
|
|
1. Run the acceptance commands.
|
|
2. Record remaining quality risks in `PROGRESS.md`.
|
|
3. Update this phase index.
|
|
|
|
## Do Not
|
|
- Do not use this as a broad refactor step.
|
|
- Do not add new major features.
|
|
- Do not bypass failed quality gates without recording a blocker.
|