Files
heros_web/docs/unit-sprite-next-steps.md

49 lines
1.8 KiB
Markdown

# Unit Sprite Next Steps
This file is generated by `scripts/write-unit-sprite-next-steps.py`.
## Current Gate
- Approved baseline units: 34
- Pending approval units: 0
- Queued rework units: 57
- Manifest: `docs/unit-sprite-rework-manifest.json`
- Audit: `docs/unit-sprite-rework-audit.json`
- Current approval board: not generated until the next pending sample.
- Batch inventory boards include old queued assets; use them for inventory/regression checks, not approval.
## Next Unit Queue
1. `unit-nanman-officer-warlord` - queued-rework, base `border-hits=64`, actions `border-hits=144`
2. `unit-nanman-shaman` - queued-rework, base `border-hits=32`, actions `border-hits=98`
3. `unit-nanman-shaman-ember` - queued-rework, base `border-hits=32`, actions `border-hits=98`
4. `unit-nanman-shaman-storm` - queued-rework, base `border-hits=32`, actions `border-hits=98`
## Commands Before Approval
```powershell
python scripts\audit-unit-sprite-sheets.py
python scripts\render-unit-sprite-review-boards.py
python scripts\render-current-sprite-approval-board.py
python scripts\check-unit-sprite-art-quality.py
python scripts\check-unit-sprite-approval-gate.py --mode sample
python scripts\write-unit-sprite-next-steps.py
python scripts\check-unit-sprite-workflow-consistency.py
```
## Commands After Approval
After user approval, promote the approved unit in `unit-sprite-rework-manifest.json`, regenerate outputs, and only then use the release gate.
```powershell
python scripts\audit-unit-sprite-sheets.py
python scripts\render-unit-sprite-review-boards.py
python scripts\check-unit-sprite-approval-gate.py --mode release
pnpm build
```
## First Task After Current Approval
- Start with `unit-nanman-officer-warlord`.
- Generate source art, assemble sheets, produce contact/GIF/before-after/scale/battle screenshots, then rerun the gates.