Skip to content

Run 1 Bug Fixes — Implementation Summary

Date: 2026-04-07 → 2026-04-10 Repositories: operations, arda-frontend-app, documentation Plan: run-1-bug-fixes/project-plan.md Exit gate: plan/run-1-bug-fixes/validate-exit.sh Phase doc: phase-1-bug-fixes/verification.md

All seven tracker tasks completed. Exit criteria passed (unit + integration + frontend smoke).

Three customer-reported defects resolved:

  • #815 / #816 — Card notes mapping leaked order history into the printed notes field when KanbanCard.notes was null or blank. Fix collapses the fallback chain to an empty string, so cards without notes print with a blank notes area.
  • #595 — No way to reset a card from PRINTED back to NOT_PRINTED. Added an UNMARK event type, a printEventRoute() helper, a POST /kanban-card/{eId}/event/unmark endpoint, and a frontend dropdown action gated on PRINTED status.
  • B-2 verification — Confirmed ItemPrinter correctly maps Item.notes to the Documint notes field for labels and breadcrumbs; no code change required.
  • Separate printEventRoute() helper instead of generalising eventRoute(). The two helpers return different state-change payload types (KanbanCardStateChange vs KanbanCardPrintStateChange); a generic was rejected as larger than the surface change warranted. See implementation-log § T-1.4.
  • Empty-string fallback for card notes rather than null, matching SAC::PRINT::FR-0016 and the Documint template’s expectation that the field is always present.
  • Unmark UI placed in the existing card row dropdown rather than as a new action button, to avoid an extra cell in the cards table.
  • make build in operations — green (unit tests + coverage).
  • Frontend regression suite (Jest + Playwright smoke) — green.
  • API tests for unmark deferred to Run 4 because card test data was not available locally.
  • operations#163 (merge 7a81c9c), portions covering phase 1.
  • arda-frontend-app#741 (merge b878516), unmark UI and notes-related fixes.

Copyright: (c) Arda Systems 2025-2026, All rights reserved