Document current unit sprite rework status

This commit is contained in:
2026-07-10 00:05:21 +09:00
parent 0e3f2592c3
commit b2d89f1c84

View File

@@ -0,0 +1,44 @@
# Unit Sprite Rework Progress Log
## 2026-07-10 Status Audit
- Runtime unit sprite rework is complete for the current manifest.
- Approved baseline units: `91`
- Pending approval units: `0`
- Queued rework units: `0`
- Source of truth: `docs/unit-sprite-rework-manifest.json`
- Generated queue: `docs/unit-sprite-batch-queue.md`
- Generated next steps: `docs/unit-sprite-next-steps.md`
- Workflow consistency: `docs/unit-sprite-workflow-consistency.md`
- Art gate: `docs/unit-sprite-art-quality-gate.md`
## Shu Infantry Resolution
- `unit-shu-infantry` is no longer pending on the old v7 candidate.
- The approved runtime baseline is `unit-shu-infantry` v8.
- Approval packet: `docs/unit-sprite-shu-infantry-v8-approval-packet.md`
- Source evidence: `docs/handpaint-batch2-shu-infantry-quality-restart-source-v8.png`
- Runtime sheets:
- `src/assets/images/units/unit-shu-infantry.png`
- `src/assets/images/units/unit-shu-infantry-actions.png`
- The v8 packet records browser verification, build verification, and the reason it superseded v7.
## Current Gate
- No current approval candidate is defined.
- No next unit queue is defined in the manifest.
- `scripts/check-unit-sprite-approval-gate.py --mode release` is the correct gate for sprite release checks in this state.
- `scripts/render-current-sprite-approval-board.py` is skipped until a new pending sample exists.
## Workspace Note
- The working tree still contains many untracked historical art review artifacts under `docs/`.
- These are review/evidence files, not automatically releasable runtime assets.
- Stage only the specific files for the current task; do not bulk-add the untracked art review workspace.
## Recommended Next Work
1. Move visual polish focus from unit sprites to remaining item/equipment icon and UI asset quality.
2. Build a small asset-quality inventory that lists runtime item/equipment images by file size, dimensions, and usage.
3. Pick the highest-impact low-quality item/equipment icon group and upgrade it with the same reviewable, one-batch workflow used for maps and sprites.
4. For any future sprite rework, first add a new `pendingApproval` candidate to `docs/unit-sprite-rework-manifest.json`, then regenerate the audit, boards, next steps, art gate, and workflow consistency docs.