task-h.5.3
This commit is contained in:
@@ -207,13 +207,28 @@ Current:
|
||||
|
||||
- payment, warranty, delivery, and extra topic sections now flow through the dynamic `topic` / `data_topic` engine on page 2 instead of fixed placeholder fields
|
||||
- approval signature placeholders now resolve through the H.3 signature strategy and `crm_job_title` position lookup
|
||||
- `quotation_price_data` is now the canonical runtime table input for the price row, while active template JSON still embeds nested `{quotation_price}` and `{currency}` cells inside that table field
|
||||
|
||||
Future:
|
||||
|
||||
- keep validating pagination and closing-block placement against production designer expectations for large topic sets
|
||||
- add fixture-backed end-to-end PDF generation verification in CI once a stable runtime path is available
|
||||
- remove nested price-table placeholders in a controlled template revision once design change windows allow it
|
||||
- decide whether static template field `line` should remain a tolerated designer-only artifact or be normalized in future audits
|
||||
|
||||
### Template version remap operations
|
||||
|
||||
Current:
|
||||
|
||||
- template version remap is now handled by `npm run seed:pdf-template-version`, not by the base foundation seed
|
||||
- active `1.1` mappings intentionally preserve historical `1.0` versions for snapshot integrity
|
||||
|
||||
Future:
|
||||
|
||||
- decide whether template version promotion needs an operator-facing review/approve workflow
|
||||
- add artifacting or changelog snapshots for template-schema diffs before activation
|
||||
- decide whether the remap command should write a persistent audit history table instead of JSON-only artifacts
|
||||
|
||||
## After Task I
|
||||
|
||||
### Storage provider production rollout
|
||||
|
||||
Reference in New Issue
Block a user