feat(cashier): carry forward yesterday's denomination count into Day Open, warn on a mismatch

The Day Open form's note/coin table started at zero even though the
branch's own closing count from the day before was already on record --
whoever opened the day had to re-key numbers that were already known.
It now auto-fills from that closing count, flags any row a manual edit
moves away from it, and shows a live Tallied/Short/Excess comparison
against it -- so a short or excess opening count is visible before the
day is opened, not discovered later. A reason is required once a mismatch
exists, matching the new backend enforcement.

Also fixes the register table's date chip wrapping onto two lines when
the column narrows.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

src/app/cashier/cashier.service.ts

@@ -229,17 +229,20 @@ export class CashierService {
     return this.http.get('/branchday/close-preview', { params });
   }
 
+  /** openingDifferenceReason is required when the opening figure differs from yesterday's closing. */
   openBranchDay(
     businessDate: string,
     openingCash?: number,
     officeId?: number,
-    denominations?: { denominationId: number; denominationValue: number; count: number }[]
+    denominations?: { denominationId: number; denominationValue: number; count: number }[],
+    openingDifferenceReason?: string
   ): Observable<any> {
     return this.http.post('/branchday/open', {
       businessDate,
       openingCash: openingCash != null ? String(openingCash) : null,
       officeId: officeId ?? null,
       denominations: denominations?.length ? denominations : null,
+      openingDifferenceReason: openingDifferenceReason ?? null,
       locale: 'en'
     });
   }