@propriety/court-calendar 1.0.154 → 1.0.155

package/dist/__tests__/DateHistory.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/__tests__/helpers/motionWindow.test.d.ts

@@ -0,0 +1 @@
+export {};

package/dist/_components/Modal/DateDetails/DateHistory.d.ts

@@ -1,8 +1,14 @@
 import { HistoryEntry } from '../../../helpers/dateHistory';
 /**
- * Compact, newest-first trail of everything that has moved this court date — reschedules
- * and bulk case adjournments. Renders nothing when there is no history, so unchanged court
- * dates keep their header exactly as it was.
+ * The trail of everything that has moved this court date.
+ *
+ * Reschedules render as one left-to-right path — `Feb 23 → Mar 23 → Aug 5` — rather than
+ * one chip per log row, so the order reads the way the arrows point and a date shared by
+ * two consecutive moves is only printed once. Bulk case adjournments are a different kind
+ * of event (they move cases off this date, not the date itself) and keep their own row.
+ *
+ * Renders nothing when there is no history, so unchanged court dates keep their header
+ * exactly as it was.
  */
 export default function DateHistory({ entries, align, }: {
     entries: HistoryEntry[];

package/dist/_components/Modal/DateDetails/MotionToPreclude.d.ts

@@ -0,0 +1,22 @@
+import { AdjournmentEntry, Case, CourtDate } from '../../../types';
+export interface MotionToast {
+    severity: 'success' | 'error' | 'info';
+    text: string;
+}
+/**
+ * The Motion to Preclude panel: window status and the two actions.
+ *
+ * Both buttons render for every SCAR date rather than appearing only when usable. The
+ * window is a few weeks out of a court date's months-long life, and when the controls were
+ * hidden outside it nobody discovered the feature existed — so they stay put and explain
+ * themselves through the status line and their tooltips.
+ *
+ * Callers gate on `isScarDate`: negotiation and collections dates never carry a motion.
+ */
+export default function MotionToPreclude({ courtDate, township, adjournments, cases, onNotify, }: {
+    courtDate: CourtDate;
+    township: string;
+    adjournments?: AdjournmentEntry[];
+    cases?: Pick<Case, 'AdjournedDate'>[];
+    onNotify: (toast: MotionToast) => void;
+}): import("react/jsx-runtime").JSX.Element;

package/dist/helpers/dateHistory.d.ts

@@ -31,6 +31,8 @@ export declare function parseHistoryDate(value: Date | string | null | undefined
  * than a meaningless "User 420".
  */
 export declare function resolveUserName(updatedBy: number | string | null | undefined, allUsers: Record<number, User>): string;
+/** Same calendar day, ignoring the time component the edit log carries. */
+export declare function isSameDay(a: Date | null, b: Date | null): boolean;
 /**
  * Merge the court date's reschedule trail with its case adjournments into one
  * time-ordered list, newest first.
@@ -40,6 +42,31 @@ export declare function resolveUserName(updatedBy: number | string | null | unde
  * be 20 identical chips — CourtDateID 296 is exactly that shape in production.
  */
 export declare function buildDateHistory(courtDateHistory: DateEditItem[], adjournments: AdjournmentEntry[], allUsers: Record<number, User>): HistoryEntry[];
+/** One date the court date has sat on, as a stop along the reschedule trail. */
+export interface TrailNode {
+    /** Stable React key. */
+    key: string;
+    date: Date | null;
+    /** The reschedule that landed on this date. Null on the stop a run starts from. */
+    entry: HistoryEntry | null;
+    /** False when this stop does not continue the one before it — the log has a hole. */
+    connected: boolean;
+}
+/**
+ * Flatten the reschedule entries into the ordered path of dates this court date has
+ * actually sat on, oldest first.
+ *
+ * Consecutive log rows chain: a row's `OldValue` is the previous row's `NewValue`. So
+ * three separate "A → B", "B → C", "C → D" chips are really one path, A → B → C → D.
+ * Rendering the path instead of the edges drops the repeated endpoints and puts the
+ * events in reading order, which the newest-first chip list could not do.
+ *
+ * When a row's origin does not match the previous stop the trail has a hole — rows are
+ * only written for edits made through the app, so a direct DB change leaves no row. That
+ * stop is marked `connected: false` so the UI can show a break rather than imply a move
+ * that never happened.
+ */
+export declare function buildRescheduleTrail(entries: HistoryEntry[]): TrailNode[];
 /**
  * The adjournment rows belonging to a single case.
  *

package/dist/helpers/formatter.d.ts

@@ -1,4 +1,11 @@
 import { Evidence } from '../types';
+/**
+ * MM/DD/YYYY for display, or "-" when there is no date.
+ *
+ * Routed through `parseLocalDate` so a date-only string keeps its calendar day: `new
+ * Date("2026-08-14")` is UTC midnight, which renders as 08/13 in any US timezone.
+ */
+export declare function formatDisplayDate(date: Date | string | null | undefined): string;
 export declare function formatDateForAPI(date: Date): string;
 export declare function formatDateTimeForAPI(date: Date, hearingTime?: string): string;
 export declare function to24Hour(time: string): string;

package/dist/helpers/motionWindow.d.ts

@@ -0,0 +1,60 @@
+import { AdjournmentEntry, Case, CourtDate } from '../types';
+/**
+ * Where a court date sits relative to its Motion to Preclude upload window.
+ *
+ * The window runs from `MotionDate` — the *first* day a motion can be uploaded, which the
+ * backend computes as four business days before the hearing — through the hearing itself.
+ * It is not a countdown to a deadline: `MotionDate` opens the window, the hearing closes it.
+ */
+export type MotionWindowState = 'no-motion-date' | 'skipped' | 'not-yet-open' | 'open' | 'closed';
+export interface MotionWindow {
+    state: MotionWindowState;
+    /** A draft PDF can be produced for review. Never files anything. */
+    canDownload: boolean;
+    /** The motion can be uploaded to NYSCEF right now. */
+    canUpload: boolean;
+    /** First day uploading is possible — the court date's MotionDate. */
+    opensOn: Date | null;
+    /** Last day uploading is possible — the hearing, pushed out by any adjournment. */
+    closesOn: Date | null;
+    /** Last *scheduled* hearing day: CourtDate, or the final entry of MultipleDates. */
+    hearingOn: Date | null;
+    /** Set only when an adjournment moved the hearing past `hearingOn`, else null. */
+    adjournedTo: Date | null;
+}
+/**
+ * Midnight-local for any shape the API hands back, without mutating the input.
+ *
+ * Date-only strings must not go through `new Date(s)` — that reads "2026-08-14" as UTC
+ * midnight, which is the 13th anywhere west of Greenwich. Every comparison in this module
+ * is day-granular, so one bad parse is a whole day of wrong answer.
+ */
+export declare function startOfDay(value: Date | string | null | undefined): Date | null;
+/**
+ * Resolves the Motion to Preclude upload window for a court date.
+ *
+ * The close boundary is the *effective* hearing day, which is the latest of:
+ *   - `CourtDate`
+ *   - every entry in `MultipleDates` (a multi-day hearing is not over until its last day)
+ *   - every adjourned-to date belonging to this court date
+ *
+ * Taking the maximum across adjournments is deliberate. Adjournments are per case, so a
+ * date can be part-adjourned; as long as one case still has a hearing ahead of it the
+ * motion is live. Which cases actually get a motion is the backend's call —
+ * `_get_active_indices_for_motion` filters them server-side — so gating the button on the
+ * most permissive boundary avoids the frontend refusing an upload the backend would accept.
+ *
+ * @param courtDate    The selected date. Non-SCAR dates never carry a motion; callers gate
+ *                     on `isScarDate` before rendering the control at all.
+ * @param adjournments Rows from `GET /court-dates/{id}` — already scoped to this date, but
+ *                     re-checked here because `AdjournmentEntry.HearingDate` holds the
+ *                     originating CourtDateID (yes, an id in a field named for a date).
+ * @param cases        The date's cases; `AdjournedDate` is a second, independent record of
+ *                     the same adjournment and covers a detail fetch that has not landed.
+ * @param today        Injectable for tests. Defaults to now.
+ */
+export declare function computeMotionWindow(courtDate: CourtDate | null | undefined, { adjournments, cases, today, }?: {
+    adjournments?: AdjournmentEntry[];
+    cases?: Pick<Case, 'AdjournedDate'>[];
+    today?: Date;
+}): MotionWindow;