2 Commits

Author	SHA1	Message	Date
mAi	cd5f752a0e	feat(litigationplanner): scenarios — paliad.scenarios jsonb table + Catalog API + engine adapter (Slice D, t-paliad-306, m/paliad#124 §5) ... A scenario is a named composition of existing proceedings + flags + per-card choices + anchor dates. Users compose, they don't author — spec references existing rules by submission_code; never creates new rules. Per m's 2026-05-26 AskUserQuestion picks (doc commit 6e58595): Q1 composition: primary + spawned (v1); multi-proceeding peer compose is the v2 goal (spec.proceedings[] array) Q2 scope: per-project + abstract (project_id NULL = abstract) Q3 trigger: per-anchor overrides over one base date Q4 storage: NEW paliad.scenarios table with jsonb spec (NOT a project_event_choices column extension) Migration 145 — additive only. Pre-flight coordination check: - On-disk max: 138 (Berufung backfill, just merged). - Live DB tracker: 106 (significantly behind — many migs pending deploy). - curie's #93 B.2-B.6 migs not pushed yet — reserved 139-143 + 144 as buffer; claimed 145 as the safe minimum that won't collide. - paliad.scenarios has audit_reason NOT applicable (no audit trigger on the table); updated_at trigger added on the table itself. - paliad.projects gains active_scenario_id uuid NULL FK with ON DELETE SET NULL (mig 134 lesson — no updated_at clauses on proceeding_types-style assumptions). Schema: paliad.scenarios ( id uuid pk, project_id uuid NULL FK → projects(id) ON DELETE CASCADE, name text NOT NULL CHECK char_length > 0, description text NULL, spec jsonb NOT NULL CHECK jsonb_typeof = 'object', created_by uuid NULL FK → users(id) ON DELETE SET NULL, created_at + updated_at timestamptz, UNIQUE NULLS NOT DISTINCT (project_id, created_by, name) ); paliad.projects.active_scenario_id uuid NULL FK; RLS: project-scoped → can_see_project; abstract → created_by = auth.uid(); Trigger: scenarios_touch_updated_at_trg. pkg/litigationplanner additions: - Scenario struct (db + json tags) - ScenarioSpec / ScenarioProceeding / ScenarioCardChoice — parsed view of the jsonb (version-1 today, v2 multi-peer-ready) - ParseSpec(raw) + ScenarioSpec.PrimaryProceeding() + CalcOptionsFromSpec() - ScenarioFilter + Catalog.LoadScenarios + Catalog.MatchScenario - CalculateFromScenario(scenario, catalog, holidays, courts) — high- level engine entry: parses spec → builds CalcOptions → delegates to Calculate - Sentinel errors: ErrUnknownScenario, ErrInvalidScenario, ErrScenarioNoPrimary paliadCatalog impl: - LoadScenarios with progressively-built WHERE clauses (project-id filter, abstract-for-user filter, or all) - MatchScenario by id — returns ErrUnknownScenario on not-found - Services connection bypasses RLS; ScenarioService enforces visibility at the application layer (mirrors EventChoiceService pattern from t-paliad-265) SnapshotCatalog impl (embedded/upc): - LoadScenarios returns empty slice (no scenarios in the snapshot) - MatchScenario returns ErrUnknownScenario internal/services/scenario_service.go: - Create / Get / ListForProject / ListAbstractForUser / Patch / SetActive / Delete with visibility checks - validateSpec checks version, base_trigger_date format, every proceedings[*].code resolves to an active paliad.proceeding_types row, every appeal_target is valid, every anchor_overrides date parses, every role ∈ {primary, peer} - SetActive validates the scenario belongs to the requested project (a scenario from a different project can't be active here) - Returns ErrScenarioNotVisible for failed visibility checks REST endpoints (registered in handlers.go): GET /api/scenarios?project=<id> — list project's GET /api/scenarios?abstract=true — list user's abstract GET /api/scenarios/{id} — one POST /api/scenarios — create PATCH /api/scenarios/{id} — partial update DELETE /api/scenarios/{id} — remove PUT /api/projects/{id}/active-scenario — set / clear active Handler error mapping: - ErrUnknownScenario / ErrScenarioNotVisible → 404 - ErrInvalidInput / ErrInvalidScenario / ErrScenarioNoPrimary → 400 - everything else → 500 Tests: - pkg/litigationplanner/scenarios_test.go: ParseSpec roundtrip (well-formed + unknown version + malformed json), PrimaryProceeding zero/multi/single, CalcOptionsFromSpec full unpack, trigger_date_override path, no-base-trigger safety check. 8 cases total, all DB-free. Wired in cmd/server/main.go alongside EventChoice — same pattern, nil-safe when DATABASE_URL is unset (handlers 503 in that mode). Acceptance: - go build ./... clean - go test ./... all green (incl. new scenarios tests) - Pre-flight audit confirmed mig 145 number is safe vs curie's pending B.2-B.6 range	2026-05-26 17:48:56 +02:00
mAi	ce28ea972e	feat(litigationplanner): embedded UPC snapshot + generator (Slice C, m/paliad#124 §19) ... Lays the foundation for youpc.org's cross-repo integration: an in-package UPC subset of paliad's deadline corpus, embedded as JSON, that any consumer can use to run the litigationplanner engine without DB access. Generator (cmd/gen-upc-snapshot): - Reads paliad's live DB (DATABASE_URL), applies pending migrations to match schema HEAD, SELECTs the UPC subset (proceeding_types WHERE jurisdiction='UPC' AND is_active=true, deadline_rules WHERE lifecycle_state='published' AND is_active=true on those proceedings, referenced trigger_events, DE+UPC holidays, UPC courts). - Writes pretty-printed JSON to pkg/litigationplanner/embedded/upc/{proceeding_types, rules, trigger_events, holidays, courts, meta}.json. - Idempotent — same DB state → same output (modulo meta.generated_at + auto-versioned suffix). - Date-stamped versioning (YYYY-MM-DD-N) with same-day suffix bump. - Operator runbook in cmd/gen-upc-snapshot/README.md. Embedded subpackage (pkg/litigationplanner/embedded/upc/): - embed.go — //go:embed *.json + LoadMeta() - snapshot.go — SnapshotCatalog (full lp.Catalog impl: LoadProceeding / LoadProceedingByID / LoadRuleByID / LoadRuleByCode / LoadRulesByTriggerEvent / LoadTriggerEventsByIDs / LookupEvents); O(1) map lookups; LookupEvents linear over the < 100-row UPC corpus. - holidays.go — SnapshotHolidayCalendar implementing lp.HolidayCalendar (IsNonWorkingDay / Adjust* with structured AdjustmentReason). - courts.go — SnapshotCourtRegistry implementing lp.CourtRegistry. - Compile-time assertions (_ lp.X = (*Snapshot*)(nil)) catch interface drift. Wire-up for consumers: cat, _ := upc.NewCatalog() hc, _ := upc.NewHolidayCalendar() cr, _ := upc.NewCourtRegistry() timeline, _ := lp.Calculate(ctx, "upc.inf.cfi", "2026-05-26", lp.CalcOptions{}, cat, hc, cr) Tests (snapshot_test.go, all DB-free): - meta parses cleanly, non-zero counts - LoadProceeding(upc.inf.cfi) returns expected proc + rules - LoadProceeding(unknown) returns ErrUnknownProceedingType - LookupEvents(Jurisdiction:UPC, all-following) covers corpus - LookupEvents(party=defendant, next) scopes anchors correctly - engine end-to-end via lp.Calculate against the embedded snapshot - holiday calendar (weekends, DE closures, UPC vacation block) - court registry (empty courtID fallback, known + unknown court) Placeholder data shipped (2 proceedings, 2 rules, 5 holidays, 2 courts) so tests run without a live DB. Operator regenerates against prod via `make snapshot-upc` once migrations 134 (B1) and 135 (B3) have landed on prod — see cmd/gen-upc-snapshot/README.md for the runbook. The placeholder's meta.version is suffixed `-placeholder` to make the regeneration delta obvious. Makefile target: make snapshot-upc — wraps the generator + reruns the snapshot tests Design (§19 of docs/design-litigation-planner-2026-05-26.md): - Embedding format: go:embed JSON (diff-friendly, no compile coupling) - Generator entry: cmd/gen-upc-snapshot/main.go (idiomatic Go cmd path) - Versioning: meta.json carries semver + generated_at + paliad_commit - Regeneration: manual via Make target or `go generate`; no CI cron in v1 - Out of scope: snapshot signing, DE/EPA/DPMA snapshots, snapshot diff tooling Acceptance: - go build clean, go test all green (incl. 6 new tests in pkg/litigationplanner/embedded/upc, all DB-free) - SnapshotCatalog passes the compile-time lp.Catalog assertion - Generator binary builds + runs (Idempotence verified by re-running against the same source data)	2026-05-26 15:11:07 +02:00