Extra Printing Options — Post-Implementation Specification

Delivered State

The printing format system now supports 15 sizes per category (card, label, breadcrumb): X_SMALL, SMALL, MEDIUM, LARGE, X_LARGE, and SPECIAL_01 through SPECIAL_10. CSV upload accepts both protobuf enum names and display-name aliases. Template configuration includes an active flag for future frontend filtering.

Deviations from Original Specification

D-01: Row count — 45 entries, not 48

The specification originally stated 48 entries (16 per category). The actual count is 45 (15 per category) because LARGE+QR was folded into SPECIAL_01 rather than retained as a separate row. The specification docs were corrected during implementation.

D-02: CSV alias mechanism — `valueAliases` in `ColumnDef`

The specification described alias resolution in ItemCsvUploadService.kt. The actual implementation adds valueAliases as a general-purpose feature of the ColumnDef configuration, resolved in Row.kt’s parseScalar ENUM branch. This is a broader, more reusable design than specified.

D-03: `ItemCsvUploadService` takes `MappingConfig` instead of separate maps

The specification showed headerAliases and valueAliases as separate constructor parameters. The implementation passes the MappingConfig object directly, which is cleaner and more stable.

D-04: Enum casing fix in alias resolution

The initial implementation lowercased the resolved value, which made findValueByName() a dead branch. This was caught in code review and fixed to preserve original casing for non-alias values while lowercasing only the alias lookup key.

Metrics

Metric	Value
Files changed (operations)	16
Lines added / removed	+494 / -58
New enum values	33 (11 per category)
New `pdf-templates.json` entries	33
New spreadsheet rows	33
New unit tests	4
Test files updated	6
Commits	2 (feat + fix)
PRs	2 (operations, documentation)
Tickets created	1 (frontend, management#850)

Acceptance Criteria Status

All 24 acceptance criteria from the goal file are addressed:

Spreadsheet (AC 1–4): Done
Backend (AC 5–14): Done (AC 13 coverage verified via koverVerify)
Frontend ticket (AC 15–20): Done (management#850)
System integration (AC 21–24): Pending deployment verification