@propriety/court-calendar 1.0.128 → 1.0.131

package/.claude/agents/library-api-reviewer.md

@@ -0,0 +1,22 @@
+---
+name: library-api-reviewer
+description: Reviews changes to @propriety/court-calendar for public API compatibility — breaking prop changes, removed exports, peer dep violations. Invoke before opening a PR or publishing.
+---
+
+You are a library API compatibility reviewer for `@propriety/court-calendar`.
+
+Analyze the current diff or staged changes and identify:
+
+1. **Removed or renamed exports** — check `src/index.ts` for anything removed or renamed that consumers may depend on
+2. **Breaking prop changes** — removed props, changed types (stricter or different), new required props added to existing components
+3. **Peer dependency violations** — code that directly imports from `@mui/`, `@emotion/`, `react`, `react-dom` without accounting for them being peer deps (they must not be bundled)
+4. **Type regressions** — public TypeScript types that became more restrictive or were removed
+5. **Dexie schema changes** — any changes to IndexedDB stores in `src/` must handle version migrations
+6. **Context API surface** — changes to `ReferenceDataContext` shape affect all consumers of `useReferenceData()`
+
+Output a verdict:
+- **BREAKING** — consumers on the previous version will break on upgrade; needs a major version bump
+- **NON-BREAKING** — new features or additions only; minor version bump appropriate
+- **PATCH** — bug fixes with no API surface changes
+
+Include specifics: which files changed, what the impact is, and the recommended semver bump.

package/.claude/settings.json

@@ -0,0 +1,19 @@
+{
+  "hooks": {
+    "PostToolUse": [
+      {
+        "matcher": "Edit|Write",
+        "hooks": [
+          {
+            "type": "command",
+            "command": "node -e \"const i=JSON.parse(process.env.CLAUDE_TOOL_INPUT||'{}');const f=i.file_path||'';if((f.endsWith('.ts')||f.endsWith('.tsx'))&&!f.includes('dist/')){const cp=require('child_process');try{cp.execSync('npx biome format --write '+JSON.stringify(f),{stdio:'pipe',cwd:'c:/Users/Optiplex-BFHN/projects/court-calendar'})}catch(e){}}\""
+          },
+          {
+            "type": "command",
+            "command": "node -e \"const i=JSON.parse(process.env.CLAUDE_TOOL_INPUT||'{}');const f=i.file_path||'';if((f.endsWith('.ts')||f.endsWith('.tsx'))&&!f.includes('.test.')&&f.includes('src/')){const cp=require('child_process');try{cp.execSync('npx vitest run --related '+JSON.stringify(f),{stdio:'pipe',cwd:'c:/Users/Optiplex-BFHN/projects/court-calendar',timeout:30000})}catch(e){}}\""
+          }
+        ]
+      }
+    ]
+  }
+}

package/.claude/skills/gen-test/SKILL.md

@@ -0,0 +1,24 @@
+---
+name: gen-test
+description: Generate Vitest + React Testing Library tests for a court-calendar component or hook
+---
+
+Generate tests for the `@propriety/court-calendar` library targeting the file or subject passed as $ARGUMENTS.
+
+## Project Test Conventions
+- Test files live in `src/__tests__/` named `<subject>.test.ts(x)`
+- Shared fixtures: `src/__tests__/fixtures.ts` — read this first for reusable test data
+- Shared helpers: `src/__tests__/helpers/`
+- Hook test utilities: `src/__tests__/hooks/`
+- Vitest globals (`describe`, `it`, `expect`, `vi`) are auto-imported — no import needed
+- Use `renderHook` from `@testing-library/react` for custom hooks
+- Mock context modules: `vi.mock('@/context/ReferenceDataContext', () => ({ useReferenceData: vi.fn(() => ({ allUsers: [], allHearingOfficers: [], allMuniNames: [], isLoading: false })) }))`
+
+## Steps
+1. Read the target file to understand its props, return values, and side effects
+2. Read `src/__tests__/fixtures.ts` for available court case / event test data
+3. Scan `src/__tests__/helpers/` and `src/__tests__/hooks/` for setup utilities to reuse
+4. Write tests covering: happy path, edge cases, null/undefined inputs, and loading states
+5. Place output in `src/__tests__/<subject>.test.ts(x)`
+
+Target: $ARGUMENTS

package/.claude/skills/release-prep/SKILL.md

@@ -0,0 +1,18 @@
+---
+name: release-prep
+description: Prepare @propriety/court-calendar for npm publish — runs all checks, prompts for version bump, builds dist
+---
+
+Run the full release checklist for `@propriety/court-calendar`. Stop and report on first failure.
+
+## Steps (sequential — stop on failure)
+1. `npx tsc --noEmit` — type check must pass with zero errors
+2. `npx vitest run` — all tests must pass
+3. `npx biome check src/` — no lint or format violations
+4. Ask the user: **patch / minor / major** version bump? (default: patch)
+   - Update the `version` field in `package.json` accordingly
+5. `npm run build` — must succeed
+6. Verify `dist/index.mjs` and `dist/index.d.ts` exist and are non-empty
+7. Report: new version number, dist file sizes, ready to `npm publish`
+
+Bump type from $ARGUMENTS (default: patch if not provided).

package/CLAUDE.md

@@ -0,0 +1,41 @@
+# court-calendar
+
+Published npm package: `@propriety/court-calendar` — a React component library built with Vite in library mode.
+
+## Commands
+
+```bash
+npm run build                        # tsc -b && vite build → dist/
+npx vitest run                       # run all tests
+npx biome format --write <file>      # format a file
+npx biome check src/                 # lint entire src
+```
+
+## Architecture
+
+- **Entry**: `src/index.ts` → exports `CCalendar` component from `src/_components/CCalendar.tsx`
+- **Path alias**: `@/` resolves to `./src/`
+- **Build output**: `dist/index.mjs` (ES module) + `dist/index.d.ts` (types)
+- **Peer deps** (not bundled): React, react-dom, MUI 5, Emotion — `vite.config.ts` externalizes these
+
+## Key Pattern: ReferenceDataContext
+
+Reference data (users, hearing officers, municipalities) is fetched once in `ReferenceDataProvider` (wrapped inside `CCalendar`) and consumed via `useReferenceData()` in child components. Do **not** fetch this data at the module level or use top-level await.
+
+Context is at `src/context/ReferenceDataContext.tsx` and provides: `allUsers`, `allHearingOfficers`, `allMuniNames`, `getTownshipName`, `getCountyName`, `isLoading`.
+
+## Runtime Config
+
+`import.meta.env` values are baked in at **library build time**, not consumer runtime. Pass runtime config (API keys, endpoints) as React props and thread them through context — never read env vars in library code.
+
+## Component Props
+
+`CCalendar` accepts:
+- `apiKey` — runtime API key (passed through context, not env var)
+- `activeUser` — the currently logged-in user object
+
+## Tooling
+
+- **Formatter/Linter**: Biome — not Prettier or ESLint
+- **Tests**: Vitest + @testing-library/react. Files: `src/__tests__/`, fixtures: `src/__tests__/fixtures.ts`
+- **Pre-commit**: Husky runs on commit — run `npx biome format --write` before staging

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

@@ -1,3 +1,3 @@
-export default function NoticeFileLink({ fileKey }: {
-    fileKey: string | null;
+export default function NoticeFileLink({ fileKeys }: {
+    fileKeys: string[] | null;
 }): import("react/jsx-runtime").JSX.Element;

package/dist/_components/Modal/DateEdit/CreateEditCase.d.ts

@@ -7,5 +7,7 @@ declare const CreateEditCase: import('react').NamedExoticComponent<{
     setEditedCases: (cases: Case[]) => void;
     modalMode: ModalMode;
     activeUser: number;
+    pendingNoticeFiles: File[];
+    setPendingNoticeFiles: (files: File[]) => void;
 }>;
 export default CreateEditCase;

package/dist/helpers/api/courtDates.d.ts

@@ -1,7 +1,8 @@
 import { DateType, CourtDate, DateEditLog } from '../../types';
 export declare function getAllDates(apiKey: string, type?: DateType): Promise<Array<CourtDate>>;
-export declare function updateCourtDate(courtDateId: number, updatedData: Partial<CourtDate>, apiKey: string, courtCases?: string[], user?: number, type?: DateType, skipMotion?: boolean): Promise<boolean>;
+export declare function updateCourtDate(courtDateId: number, updatedData: Partial<CourtDate>, apiKey: string, courtCases?: string[], user?: number, type?: DateType, skipMotion?: boolean, noticeFiles?: File[]): Promise<boolean>;
+export declare function getCourtDate(courtDateId: number, apiKey: string, type?: DateType): Promise<CourtDate | null>;
 export declare function deleteCourtDate(courtDateId: number, apiKey: string, type?: DateType): Promise<boolean>;
-export declare function createCourtDate(courtDate: Date, muniCode: string, apiKey: string, courtCases?: string[], hearingTime?: string, multipleDates?: Date[], type?: DateType): Promise<number | null>;
+export declare function createCourtDate(courtDate: Date, muniCode: string, apiKey: string, courtCases?: string[], hearingTime?: string, multipleDates?: Date[], type?: DateType, noticeFiles?: File[]): Promise<number | null>;
 export declare function snoozeUploadDeadline(courtDateId: number, apiKey: string): Promise<boolean>;
 export declare function getDateEditLogs(courtDateId: number, apiKey: string, type?: DateType): Promise<DateEditLog | null>;

package/dist/hooks/UseModalActions.d.ts

@@ -21,7 +21,7 @@ import { ModalMode } from '../_components/Modal/types';
  * - `handleViewUpdateChair`             – Optimistically updates a first/second chair in view mode.
  * - `handleSelectedCasesAdjournmentChange` – Updates the adjournment date for a set of cases.
  */
-export declare function useModalActions({ modalMode, selectedCourtDate, selectedCases, editedData, editedCases, setEditedData, setIsOpen, }: {
+export declare function useModalActions({ modalMode, selectedCourtDate, selectedCases, editedData, editedCases, setEditedData, setIsOpen, pendingNoticeFiles, }: {
     modalMode: ModalMode;
     selectedCourtDate: CourtDate | null;
     selectedCases: Case[];
@@ -29,6 +29,7 @@ export declare function useModalActions({ modalMode, selectedCourtDate, selected
     editedCases: Case[];
     setEditedData: (data: CourtDate) => void;
     setIsOpen: (isOpen: boolean) => void;
+    pendingNoticeFiles?: File[];
 }): {
     handleSave: () => Promise<boolean>;
     handleDelete: () => Promise<void>;