@propriety/court-calendar 1.0.180 → 1.0.182

package/.vscode/extensions.json

@@ -20,7 +20,7 @@
     "dbaeumer.vscode-eslint",
     "inferrinizzard.prettier-sql-vscode",
 
-    // --- Python stack (lives in ../adminAPI, ../Utility-API, ../pdfOcr) ---
+    // --- Python stack (lives in ../adminAPI, ../court-calendar-api, ../ocr) ---
     "ms-python.python",
     "ms-python.vscode-pylance",
     "ms-python.debugpy",

package/dist/helpers/cases.d.ts

@@ -3,7 +3,7 @@ export declare function isCaseSettled(c: Case, isVillage: boolean): boolean;
 /**
  * The case is waiting on a hearing officer's decision.
  *
- * `D` is written by Utility-API's nightly `set_past_cases_to_awaiting_decision` job, which
+ * `D` is written by court-calendar-api's nightly `set_past_cases_to_awaiting_decision` job, which
  * stamps every hearing that has passed with no determination recorded. It is not a settled
  * action, so none of the case-level filters can retire one — hence `showOutForDecision`.
  *

package/dist/types.d.ts

@@ -223,7 +223,7 @@ export interface AdjournmentEntry {
     /**
      * Holds the originating CourtDateID, not a date, despite the name. The adjournment
      * flows store the court date here so rows can be related back to it — see
-     * `get_adjournment_dates_by_court_date` in Utility-API. Don't "fix" this.
+     * `get_adjournment_dates_by_court_date` in court-calendar-api. Don't "fix" this.
      */
     HearingDate: number | null;
     FirstChair: number | null;

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@propriety/court-calendar",
   "private": false,
-  "version": "1.0.180",
+  "version": "1.0.182",
   "type": "module",
   "main": "dist/index.js",
   "module": "./dist/index.mjs",

package/src/__tests__/filtering.test.ts

@@ -564,7 +564,7 @@ describe('filterCourtDates — past negotiations', () => {
 
 // ─── filterCourtDates — out for decision (showOutForDecision) ─────────────────
 //
-// 'D' is written by Utility-API's nightly job on every past hearing with no determination
+// 'D' is written by court-calendar-api's nightly job on every past hearing with no determination
 // recorded. It is not a settled action, so nothing else on this pipeline can retire one.
 // DEFAULT_FILTER_CTX sets showOutForDecision TRUE suite-wide, so every test here states it.
 

package/src/helpers/cases.ts

@@ -20,7 +20,7 @@ export function isCaseSettled(c: Case, isVillage: boolean): boolean {
 /**
  * The case is waiting on a hearing officer's decision.
  *
- * `D` is written by Utility-API's nightly `set_past_cases_to_awaiting_decision` job, which
+ * `D` is written by court-calendar-api's nightly `set_past_cases_to_awaiting_decision` job, which
  * stamps every hearing that has passed with no determination recorded. It is not a settled
  * action, so none of the case-level filters can retire one — hence `showOutForDecision`.
  *

package/src/helpers/filtering.ts

@@ -90,7 +90,7 @@ export function filterCourtDates(
             return lastDay >= negCutoff;
         })
         // A date whose remaining cases are all waiting on a hearing officer's decision is
-        // waiting on the court, not on us. Utility-API's nightly job stamps 'D' on every
+        // waiting on the court, not on us. court-calendar-api's nightly job stamps 'D' on every
         // hearing that has passed with nothing recorded, and 'D' is not a settled action, so
         // the case-level filters above can never retire one — the same shape of problem that
         // `showPastNegotiations` solves for negotiations.

package/src/types.ts

@@ -271,7 +271,7 @@ export interface AdjournmentEntry {
     /**
      * Holds the originating CourtDateID, not a date, despite the name. The adjournment
      * flows store the court date here so rows can be related back to it — see
-     * `get_adjournment_dates_by_court_date` in Utility-API. Don't "fix" this.
+     * `get_adjournment_dates_by_court_date` in court-calendar-api. Don't "fix" this.
      */
     HearingDate: number | null;
     FirstChair: number | null;