mAi: #117 + #118 - t-paliad-285/-286 UPC dmgs+pi court followup (mig 133)

Adds the post-submission court phase to upc.dmgs.cfi and the appeal
route to upc.pi.cfi. The Verfahrensablauf timeline currently stops at
the last party submission (dmgs.rejoin / pi.order); without these rows
the interim conference / oral hearing / decision / appeal sub-tree
never renders, even though atlas's #96 spawn mechanism is in place.

Migration 133 (single slot, coordinated with knuth's #116 on 132):

Section A — UPC Damages tree end (#117):
- upc.dmgs.cfi.interim       court-set, R.105
- upc.dmgs.cfi.oral          court-set, R.118 / R.250
- upc.dmgs.cfi.decision      court-set, R.118 / R.144
- upc.dmgs.cfi.appeal_spawn  2mo, R.220.1(a) / R.224.1(a), spawn → upc.apl.merits

Section B — UPC PI appeal route (#118):
- upc.pi.cfi.appeal_spawn    2mo, R.220.1(a) / R.224.1(a), spawn → upc.apl.merits
  PI orders under R.211 dispose of the urgent question and ride the
  main 2-month track; the 15-day R.220.1(c) order track does not apply.

Same shape as mig 095 inf.appeal_spawn and the upc.inf.cfi
interim/oral/decision rows from mig 012. Court-set rows reuse the
shared interim-conference / oral-hearing / decision concepts.

Citations: docs/research-deadlines-completeness-2026-05-25.md §D + Tier 4 (R.144), docs/audit-upc-rop-deadlines-2026-05-08.md §D R.144 + §F R.220.1(a)/R.224.1(a). Per-row RoP citation in the migration header.

Idempotent INSERT NOT EXISTS guards per row + post-insert DO block that RAISEs EXCEPTION if any expected row is missing or the spawn shape (is_spawn / spawn_proceeding_type_id / parent_id) is wrong.

go build ./... clean, go test ./internal/... clean, bun run build clean.

internal/db/migrations/132_wave1_tier1_rule_additions.down.sql

@@ -1,76 +0,0 @@
--- Rollback of mig 132 (t-paliad-284 Wave 1 + m/paliad#116).
---
--- Reverses §0 (R.104/R.105 citation backfill) + §1..§11 (11 Tier 1
--- INSERTs) + §12 (T1.12 re-anchor of upc.pi.cfi.response).
---
--- Does NOT reverse §13b (Q6 archived-litigation cleanup) — those rows
--- were already in lifecycle_state='archived' before deletion and are not
--- surfaced by any product code path. Restoring them would require the
--- pre-mig-132 backup. Leaving them gone is the correct rollback choice;
--- emergency restore goes via mig 123 backup snapshot.
---
--- DOES restore §13a (re-add the deadline_rule_audit.rule_id FK) so the
--- audit-table schema returns to its pre-mig-132 shape on rollback. Any
--- orphan audit rows accumulated under mig 132 (rule_id pointing at
--- now-deleted rules) would block the FK re-add; the rollback DELETE
--- below removes them first.
-
-SELECT set_config(
-    'paliad.audit_reason',
-    'mig 132 down: rollback Wave 1 Tier 1 rule additions + R.105 citation backfill + T1.12 re-anchor (t-paliad-284 / m/paliad#116)',
-    true);
-
--- §12 down — un-re-anchor upc.pi.cfi.response back to its broken root state.
-UPDATE paliad.deadline_rules
-   SET parent_id    = NULL,
-       is_court_set = false,
-       rule_code    = NULL,
-       legal_source = NULL,
-       updated_at   = now()
- WHERE submission_code = 'upc.pi.cfi.response'
-   AND is_active = true
-   AND lifecycle_state = 'published'
-   AND is_court_set = true
-   AND rule_code = 'RoP.211.2';
-
--- §1..§11 down — delete the 11 Tier 1 INSERTs by submission_code.
-DELETE FROM paliad.deadline_rules
- WHERE submission_code IN (
-     'upc.inf.cfi.cmo_review',
-     'upc.inf.cfi.confidentiality_response',
-     'upc.apl.order.response_orders',   -- delete child first (FK to grounds_orders)
-     'upc.apl.order.grounds_orders',
-     'upc.inf.cfi.cons_orders',
-     'upc.inf.cfi.rectification',
-     'upc.pi.cfi.deficiency',
-     'upc.pi.cfi.merits_start',
-     'upc.inf.cfi.translation_request',
-     'upc.inf.cfi.interpreter_cost',
-     'upc.inf.cfi.translations_lodge'
- )
-   AND lifecycle_state = 'published';
-
--- §0 down — clear the R.104/R.105 citation on upc.inf.cfi.interim.
-UPDATE paliad.deadline_rules
-   SET rule_code    = NULL,
-       legal_source = NULL,
-       rule_codes   = NULL,
-       updated_at   = now()
- WHERE submission_code = 'upc.inf.cfi.interim'
-   AND is_active = true
-   AND lifecycle_state = 'published'
-   AND rule_code = 'RoP.104'
-   AND legal_source = 'UPC.RoP.104';
-
--- §13a down — re-add the deadline_rule_audit.rule_id FK with the
--- original ON DELETE CASCADE shape. Purge any orphan audit rows first
--- (audit entries pointing at rule_ids that no longer exist in
--- deadline_rules) so the FK re-add doesn't fail validation.
-DELETE FROM paliad.deadline_rule_audit a
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules dr WHERE dr.id = a.rule_id
- );
-
-ALTER TABLE paliad.deadline_rule_audit
-    ADD CONSTRAINT deadline_rule_audit_rule_id_fkey
-    FOREIGN KEY (rule_id) REFERENCES paliad.deadline_rules(id) ON DELETE CASCADE;

internal/db/migrations/132_wave1_tier1_rule_additions.up.sql

@@ -1,659 +0,0 @@
--- t-paliad-284 Wave 1 + m/paliad#116 — Tier 1 deadline-rule additions
--- (12 high-frequency procedural events) + UPC RoP R.104/R.105 Interim
--- Conference citation backfill + Q6 archived-litigation cleanup.
---
--- Source: docs/research-deadlines-completeness-2026-05-25.md
---   • §10 Tier 1 table (T1.1 .. T1.12)
---   • §3.1 missing-rules catalogue (per-rule statutory citations)
---   • §9.7 / Q6 (drop the _archived_litigation.* rows — m's design ack
---     locked in 2026-05-25)
---
--- m's report (2026-05-25 17:12) also explicitly named "Zwischenverfahren /
--- Interim Conference 105" as missing a rule citation. The audit does not
--- list R.105 as a Tier 1 item (the row upc.inf.cfi.interim already exists
--- as a court-set anchor), so the fix is to BACKFILL rule_code/legal_source
--- on that row rather than to insert a new rule. Done here as a separate
--- §0 section, with both RoP.104 (Aims of the interim conference) and
--- RoP.105 (Holding of the interim conference) cited via rule_codes[].
---
--- Wave 2 Slice A primitives (mig 128: working_days unit + combine_op +
--- timing='before' backward snap in deadline_calculator.go) are used by:
---   • T1.8  upc.pi.cfi.merits_start         — 31d OR 20wd, combine_op=max
---   • T1.9  upc.inf.cfi.translation_request — 1 month BEFORE oral hearing
---   • T1.10 upc.inf.cfi.interpreter_cost    — 2 weeks BEFORE oral hearing
--- Wave 2 Slice A landed mig 128 (`deadline_rules_unit_check`) — these
--- rules are no longer blocked.
---
--- Slot 132 reserved: 127 brunel Wave 0, 128 knuth W2-A, 129 demeter,
--- 130 atlas, 131 artemis → 132 this migration.
---
--- Idempotency:
---   • INSERTs guarded with `WHERE NOT EXISTS (... submission_code = ...)`
---     so re-applying matches zero rows on the second run.
---   • UPDATEs guarded with `WHERE` clauses that match the pre-fix row
---     state only (mig 095 convention).
---   • DELETE guarded by lifecycle_state='archived' AND prefix — repeats
---     match zero rows after first run.
---
--- audit_reason set_config is required at the top (mig 079 trigger on
--- paliad.deadline_rules raises EXCEPTION 'audit reason required' for
--- any INSERT / UPDATE / DELETE without it).
-
-SELECT set_config(
-    'paliad.audit_reason',
-    'mig 132: t-paliad-284 Wave 1 + m/paliad#116 — Tier 1 deadline-rule additions (12 rules) from curie''s audit §10 + UPC RoP R.104/105 Interim Conference citation backfill (m''s 2026-05-25 17:12 report) + Q6 archived-litigation cleanup (audit §9.7)',
-    true);
-
--- =============================================================================
--- §0  R.104/R.105 — Backfill citation on the existing Interim Conference row.
---     m's report flagged that `upc.inf.cfi.interim` (Zwischenverfahren) renders
---     with no rule reference at /admin/rules. The row exists as a court-set
---     anchor (duration=0, parent_id=NULL, primary_party='court'). The
---     governing UPC Rules of Procedure are:
---       • R.104 — Aims of the interim conference (the substantive rule)
---       • R.105 — Holding of the interim conference (procedural)
---     Both cited via the rule_codes[] array; rule_code/legal_source carry
---     the primary citation (R.104 — Aims).
--- =============================================================================
-UPDATE paliad.deadline_rules
-   SET rule_code    = 'RoP.104',
-       legal_source = 'UPC.RoP.104',
-       rule_codes   = ARRAY['RoP.104', 'RoP.105'],
-       updated_at   = now()
- WHERE submission_code = 'upc.inf.cfi.interim'
-   AND is_active = true
-   AND lifecycle_state = 'published'
-   AND rule_code IS NULL
-   AND legal_source IS NULL;
-
--- =============================================================================
--- §1  T1.1 upc.inf.cfi.cmo_review — Review of case-management order.
---     15 days from CMO service. UPC RoP R.333.2: "Any party adversely
---     affected by a case management order may within 15 days of service
---     of the order apply to the panel for a review." Routine in busy LDs
---     (Munich CMO traffic ~weekly). Anchor: the Interim Conference row,
---     which is where CMOs are typically issued.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 8,                                                          -- upc.inf.cfi
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.interim'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.cmo_review',
-       'Überprüfung Verfahrensanordnung',
-       'Review of Case-Management Order',
-       'both', 15, 'days', 'after', 'RoP.333.2', 'UPC.RoP.333.2',
-       'optional', false, 'published', true, 42,
-       'Frist 15 Tage ab Zustellung der Verfahrensanordnung (R.333.2). Jede beschwerte Partei kann beim Spruchkörper Überprüfung beantragen.',
-       '15-day period from service of the case-management order (R.333.2). Any adversely-affected party may apply to the panel for a review.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.cmo_review'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §2  T1.2 upc.inf.cfi.confidentiality_response — Response to opposing
---     party's confidentiality application. 14 days from receipt of the
---     opposing party's R.262.2 application: "Within 14 days of service
---     … the other party may lodge an Application to the contrary."
---     Trigger event 25 (paliad.trigger_events) maps 1:1 to this rule.
---     Daily occurrence in HLC infringement work. Anchor: Statement of
---     Claim row as proceeding root — actual trigger date supplied via
---     'Datum setzen' when the opp party files, since the confidentiality
---     app is not itself modelled as a deadline_rules row.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, trigger_event_id, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.soc'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.confidentiality_response',
-       'Erwiderung auf Vertraulichkeitsantrag',
-       'Response to Confidentiality Application',
-       'both', 14, 'days', 'after', 'RoP.262.2', 'UPC.RoP.262.2',
-       'optional', false, 'published', true, 8,
-       25,
-       'Frist 14 Tage ab Zustellung des Vertraulichkeitsantrags der Gegenseite (R.262.2). Datum bei Eingang des Antrags manuell setzen.',
-       '14-day period from service of the opposing party''s confidentiality application (R.262.2). Set trigger date manually on receipt of the application.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.confidentiality_response'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §3  T1.3 upc.apl.order.grounds_orders — Statement of Grounds on the
---     orders-track appeal. 15 days from service of the appealed
---     order/decision. UPC RoP R.224.2(b): "A Statement of grounds of
---     appeal shall be lodged … within 15 days of service of the
---     decision/order in cases referred to in Rule 220.1(c), Rule 220.2
---     and Rule 221.3." Existing upc.apl.order tree has the with_leave
---     notice but no separate grounds row — adding it.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 20,                                                         -- upc.apl.order
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.apl.order.order'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.apl.order.grounds_orders',
-       'Berufungsbegründung (Orders Track)',
-       'Statement of Grounds (Orders Track)',
-       'both', 15, 'days', 'after', 'RoP.224.2.b', 'UPC.RoP.224.2.b',
-       'mandatory', false, 'published', true, 2,
-       'Frist 15 Tage ab Zustellung der angegriffenen Anordnung/Entscheidung (R.224.2(b)).',
-       '15-day period from service of the appealed order/decision (R.224.2(b)).'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.apl.order.grounds_orders'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §4  T1.4 upc.apl.order.response_orders — Statement of Response on the
---     orders-track appeal. 15 days from service of the grounds. UPC RoP
---     R.235.2: "Within 15 days of service of grounds of appeal pursuant
---     to Rule 224.2(b), any other party … may lodge a Statement of
---     response." Parent: the grounds_orders row inserted in §3, looked
---     up by submission_code so this INSERT works either against a fresh
---     DB or a partially-applied state.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 20,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.apl.order.grounds_orders'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.apl.order.response_orders',
-       'Berufungserwiderung (Orders Track)',
-       'Statement of Response (Orders Track)',
-       'both', 15, 'days', 'after', 'RoP.235.2', 'UPC.RoP.235.2',
-       'optional', false, 'published', true, 3,
-       'Frist 15 Tage ab Zustellung der Berufungsbegründung (R.235.2).',
-       '15-day period from service of the Statement of grounds of appeal (R.235.2).'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.apl.order.response_orders'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §5  T1.5 upc.inf.cfi.cons_orders — Application for orders consequential
---     on validity. 2 months from service of the validity decision. UPC
---     RoP R.118.4: "The Court may, upon a reasoned request by one of
---     the parties, … give a decision granting consequential orders.
---     The application … shall be made within two months of service of
---     the decision …". Common after central-division revocation in
---     bifurcated UPC matters.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.decision'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.cons_orders',
-       'Antrag auf Folgeentscheidungen',
-       'Application for Consequential Orders',
-       'both', 2, 'months', 'after', 'RoP.118.4', 'UPC.RoP.118.4',
-       'optional', false, 'published', true, 60,
-       'Frist 2 Monate ab Zustellung der Validitätsentscheidung (R.118.4). Antrag auf Folgeentscheidungen (z.B. nach Zentralkammer-Nichtigerklärung).',
-       '2-month period from service of the validity decision (R.118.4). Application for orders consequential on validity (e.g. after central-division revocation).'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.cons_orders'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §6  T1.6 upc.inf.cfi.rectification — Application for rectification of a
---     decision/order. 1 month from delivery of the decision. UPC RoP
---     R.353: "Clerical mistakes, errors arising from any accidental
---     slip or omission and obvious errors in a decision or order of
---     the Court may be corrected by the Court of its own motion or on
---     the application of a party. The application shall be made within
---     one month of the decision or order being notified."
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.decision'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.rectification',
-       'Antrag auf Berichtigung',
-       'Application for Rectification',
-       'both', 1, 'months', 'after', 'RoP.353', 'UPC.RoP.353',
-       'optional', false, 'published', true, 70,
-       'Frist 1 Monat ab Zustellung der Entscheidung/Anordnung (R.353). Berichtigung von Schreib-, Rechen- oder ähnlichen Versehen.',
-       '1-month period from notification of the decision/order (R.353). Rectification of clerical mistakes, accidental slips or obvious errors.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.rectification'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §7  T1.7 upc.pi.cfi.deficiency — Cure of PI-application deficiency.
---     14 days from notification of the deficiency. UPC RoP R.207.6(a):
---     "The Registry shall as soon as practicable examine the
---     Application … and notify any deficiencies to the applicant. The
---     applicant shall be invited to correct the deficiencies … within
---     14 days." Failure to cure leads to deemed-withdrawal.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 10,                                                         -- upc.pi.cfi
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.pi.cfi.app'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.pi.cfi.deficiency',
-       'Mängelbeseitigung Antrag',
-       'Cure of Application Deficiency',
-       'claimant', 14, 'days', 'after', 'RoP.207.6.a', 'UPC.RoP.207.6.a',
-       'mandatory', false, 'published', true, 2,
-       'Frist 14 Tage ab Mängelmitteilung durch die Geschäftsstelle (R.207.6(a)). Bei Nichtbehebung gilt der Antrag als zurückgenommen.',
-       '14-day period from notification of deficiency by the Registry (R.207.6(a)). Failure to cure leads to deemed withdrawal of the application.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.pi.cfi.deficiency'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §8  T1.8 upc.pi.cfi.merits_start — Start proceedings on the merits.
---     31 calendar days OR 20 working days, whichever is the longer,
---     from grant of the PI. UPC RoP R.213.1 → R.198.1: "the applicant
---     shall start proceedings leading to a decision on the merits of
---     the case … within a period not exceeding 31 calendar days or
---     20 working days, whichever is the longer." Combine-max wiring
---     via Wave 2 Slice A primitives (mig 128: working_days unit +
---     combine_op). Failure to commence on time → PI lapses (R.213.2).
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit,
-     alt_duration_value, alt_duration_unit, alt_rule_code,
-     combine_op, timing, rule_code, legal_source, priority,
-     is_court_set, lifecycle_state, is_active, sequence_order,
-     deadline_notes, deadline_notes_en)
-SELECT 10,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.pi.cfi.order'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.pi.cfi.merits_start',
-       'Klage in der Hauptsache erheben',
-       'Start Proceedings on the Merits',
-       'claimant', 31, 'days',
-       20, 'working_days', 'RoP.198.1',
-       'max', 'after', 'RoP.213', 'UPC.RoP.213',
-       'mandatory', false, 'published', true, 3,
-       'Frist 31 Kalendertage ODER 20 Arbeitstage (jeweils das längere) ab Anordnung der einstweiligen Maßnahme (R.213 i.V.m. R.198.1). Bei Versäumnis erlischt die einstweilige Maßnahme.',
-       '31 calendar days OR 20 working days, whichever is the longer, from grant of the provisional measure (R.213 referring to R.198.1). Failure to commence within the period causes the provisional measure to lapse.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.pi.cfi.merits_start'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §9  T1.9 upc.inf.cfi.translation_request — Request for simultaneous
---     translation at the oral hearing. 1 month BEFORE the oral hearing.
---     UPC RoP R.109.1: "A party requiring simultaneous interpretation
---     of the oral hearing into a language other than the language of
---     proceedings shall, no later than one month before the date of
---     the oral hearing, lodge a request with the Court." timing='before'
---     uses the backward-snap path in deadline_calculator.go (mig 128).
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.oral'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.translation_request',
-       'Antrag auf Simultanübersetzung',
-       'Request for Simultaneous Translation',
-       'both', 1, 'months', 'before', 'RoP.109.1', 'UPC.RoP.109.1',
-       'optional', false, 'published', true, 45,
-       'Frist 1 Monat VOR der mündlichen Verhandlung (R.109.1). Antrag auf Simultanübersetzung in eine andere Sprache als die Verfahrenssprache.',
-       '1 month BEFORE the oral hearing (R.109.1). Request for simultaneous interpretation into a language other than the language of proceedings.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.translation_request'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §10 T1.10 upc.inf.cfi.interpreter_cost — Notification of interpreter
---     cost-bearing. 2 weeks BEFORE the oral hearing. UPC RoP R.109.4:
---     "Where … the party which made the request for interpretation is
---     not the party who has chosen the language of the proceedings,
---     the costs of the interpretation … shall be borne by the
---     requesting party, unless the Court orders otherwise. The party
---     shall be notified at least two weeks before the oral hearing."
---     timing='before' as in §9.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.oral'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.interpreter_cost',
-       'Mitteilung Dolmetscherkosten',
-       'Notification of Interpreter Costs',
-       'court', 2, 'weeks', 'before', 'RoP.109.4', 'UPC.RoP.109.4',
-       'mandatory', false, 'published', true, 46,
-       'Frist 2 Wochen VOR der mündlichen Verhandlung (R.109.4). Mitteilung, dass die antragstellende Partei die Dolmetscherkosten zu tragen hat.',
-       '2 weeks BEFORE the oral hearing (R.109.4). Notification to the requesting party that it shall bear the interpreter costs.'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.interpreter_cost'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §11 T1.11 upc.inf.cfi.translations_lodge — Lodging of translations on
---     judge-rapporteur order. 2 weeks AFTER the JR's order. UPC RoP
---     R.109.5: "If the judge-rapporteur orders, the parties shall lodge
---     a translation of any pleading or other document into the language
---     of the proceedings within two weeks." trigger_event_id=113 maps
---     to the JR translation order. Anchor: Interim Conference row, where
---     such JR orders are typically issued.
--- =============================================================================
-INSERT INTO paliad.deadline_rules
-    (proceeding_type_id, parent_id, submission_code, name, name_en,
-     primary_party, duration_value, duration_unit, timing, rule_code,
-     legal_source, priority, is_court_set, lifecycle_state, is_active,
-     sequence_order, trigger_event_id, deadline_notes, deadline_notes_en)
-SELECT 8,
-       (SELECT id FROM paliad.deadline_rules
-         WHERE submission_code = 'upc.inf.cfi.interim'
-           AND lifecycle_state = 'published' AND is_active = true
-         LIMIT 1),
-       'upc.inf.cfi.translations_lodge',
-       'Übersetzungen einreichen',
-       'Lodging of Translations',
-       'both', 2, 'weeks', 'after', 'RoP.109.5', 'UPC.RoP.109.5',
-       'mandatory', false, 'published', true, 47,
-       113,
-       'Frist 2 Wochen ab Anordnung des Berichterstatters, Übersetzungen einzureichen (R.109.5).',
-       '2-week period from the judge-rapporteur''s order to lodge translations (R.109.5).'
- WHERE NOT EXISTS (
-     SELECT 1 FROM paliad.deadline_rules
-      WHERE submission_code = 'upc.inf.cfi.translations_lodge'
-        AND lifecycle_state = 'published'
- );
-
--- =============================================================================
--- §12 T1.12 upc.pi.cfi.response — RE-ANCHOR of the existing PI Response
---     row. Currently broken: parent_id=NULL with is_court_set=false and
---     duration=0 makes the calculator treat this as a root anchor. UPC
---     RoP R.211.2 — judge sets the inter-partes hearing date and the
---     deadline for the response. Fix: set is_court_set=true and chain
---     parent_id on upc.pi.cfi.app (the proceeding root). Duration
---     remains 0 (court-set placeholder); the lawyer fills in the actual
---     date via 'Datum setzen'.
--- =============================================================================
-UPDATE paliad.deadline_rules
-   SET parent_id   = (SELECT id FROM paliad.deadline_rules
-                       WHERE submission_code = 'upc.pi.cfi.app'
-                         AND lifecycle_state = 'published'
-                         AND is_active = true
-                       LIMIT 1),
-       is_court_set = true,
-       rule_code    = 'RoP.211.2',
-       legal_source = 'UPC.RoP.211.2',
-       updated_at   = now()
- WHERE submission_code = 'upc.pi.cfi.response'
-   AND is_active = true
-   AND lifecycle_state = 'published'
-   AND parent_id IS NULL
-   AND is_court_set = false;
-
--- =============================================================================
--- §13a Pre-requisite for §13b — drop the deadline_rule_audit.rule_id FK.
---     The audit trigger (mig 079) tries to INSERT an audit row on AFTER
---     DELETE pointing at OLD.id, but the existing FK constraint
---     `deadline_rule_audit_rule_id_fkey` (FOREIGN KEY rule_id REFERENCES
---     paliad.deadline_rules(id) ON DELETE CASCADE) makes that INSERT fail
---     because by the time the trigger fires the parent row is gone. As a
---     result no DELETE on paliad.deadline_rules has ever succeeded in
---     production (`SELECT count(*) FROM paliad.deadline_rule_audit
---     WHERE action='delete'` returns 0). The trigger's DELETE branch was
---     dead code.
---
---     Standard audit-table design: the audit log is append-only history
---     and should NOT FK-constrain on the live entity table — before_json
---     captures the full row state at the time of the change, which is
---     all the audit trail needs. Dropping the FK fixes the latent bug
---     and unblocks legitimate cleanup work (here: §13b, plus any future
---     hard-delete migrations against deadline_rules).
---
---     Idempotent: DROP CONSTRAINT IF EXISTS no-ops on re-run.
--- =============================================================================
-ALTER TABLE paliad.deadline_rule_audit
-    DROP CONSTRAINT IF EXISTS deadline_rule_audit_rule_id_fkey;
-
--- =============================================================================
--- §13b Q6 cleanup — drop the _archived_litigation.* deadline rules.
---     40 rows at audit §9.7 flagged as obsolete Pipeline-A residue
---     (proceeding_type id=32 '_archived_litigation' — kept for FK
---     parity but the rules are no longer surfaced anywhere in the
---     product). m's Q6 design ack 2026-05-25 locked in their removal.
---     Idempotent: prefix + lifecycle_state='archived' match zero rows
---     after first run. The proceeding_type row itself is left in place
---     (referenced by historical deadline_rule_audit before_json blobs).
--- =============================================================================
-DELETE FROM paliad.deadline_rules
- WHERE submission_code LIKE '_archived_litigation.%' ESCAPE '\'
-   AND lifecycle_state = 'archived';
-
--- =============================================================================
--- Hard assertions. Each new/changed row must end up in its post-fix
--- shape. Re-running the migration is a no-op for the data but the
--- assertions still pass because they check the post-fix state.
--- =============================================================================
-DO $$
-DECLARE
-    v_count integer;
-BEGIN
-    -- §0 R.105 interim conference backfilled
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.interim'
-       AND is_active = true
-       AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.104'
-       AND legal_source = 'UPC.RoP.104'
-       AND 'RoP.105' = ANY(rule_codes);
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 §0: upc.inf.cfi.interim citation backfill not in post-fix shape (got % matches)', v_count;
-    END IF;
-
-    -- §1 T1.1 cmo_review present
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.cmo_review'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.333.2' AND duration_value = 15
-       AND duration_unit = 'days' AND timing = 'after';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.1: upc.inf.cfi.cmo_review missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §2 T1.2 confidentiality_response
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.confidentiality_response'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.262.2' AND duration_value = 14
-       AND duration_unit = 'days' AND trigger_event_id = 25;
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.2: upc.inf.cfi.confidentiality_response missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §3 T1.3 grounds_orders
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.apl.order.grounds_orders'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.224.2.b' AND duration_value = 15
-       AND duration_unit = 'days';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.3: upc.apl.order.grounds_orders missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §4 T1.4 response_orders chained on §3
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules dr
-      JOIN paliad.deadline_rules p ON p.id = dr.parent_id
-     WHERE dr.submission_code = 'upc.apl.order.response_orders'
-       AND dr.is_active = true AND dr.lifecycle_state = 'published'
-       AND dr.rule_code = 'RoP.235.2' AND dr.duration_value = 15
-       AND p.submission_code = 'upc.apl.order.grounds_orders';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.4: upc.apl.order.response_orders missing or wrong parent chain (got % matches)', v_count;
-    END IF;
-
-    -- §5 T1.5 cons_orders
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.cons_orders'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.118.4' AND duration_value = 2
-       AND duration_unit = 'months';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.5: upc.inf.cfi.cons_orders missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §6 T1.6 rectification
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.rectification'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.353' AND duration_value = 1
-       AND duration_unit = 'months';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.6: upc.inf.cfi.rectification missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §7 T1.7 pi.deficiency
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.pi.cfi.deficiency'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.207.6.a' AND duration_value = 14
-       AND duration_unit = 'days';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.7: upc.pi.cfi.deficiency missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §8 T1.8 pi.merits_start — combine-max wiring
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.pi.cfi.merits_start'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.213' AND duration_value = 31
-       AND duration_unit = 'days'
-       AND alt_duration_value = 20 AND alt_duration_unit = 'working_days'
-       AND alt_rule_code = 'RoP.198.1' AND combine_op = 'max';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.8: upc.pi.cfi.merits_start missing or wrong combine-max shape (got % matches)', v_count;
-    END IF;
-
-    -- §9 T1.9 translation_request — timing='before'
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.translation_request'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.109.1' AND duration_value = 1
-       AND duration_unit = 'months' AND timing = 'before';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.9: upc.inf.cfi.translation_request missing or wrong timing (got % matches)', v_count;
-    END IF;
-
-    -- §10 T1.10 interpreter_cost — timing='before'
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.interpreter_cost'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.109.4' AND duration_value = 2
-       AND duration_unit = 'weeks' AND timing = 'before';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.10: upc.inf.cfi.interpreter_cost missing or wrong timing (got % matches)', v_count;
-    END IF;
-
-    -- §11 T1.11 translations_lodge
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code = 'upc.inf.cfi.translations_lodge'
-       AND is_active = true AND lifecycle_state = 'published'
-       AND rule_code = 'RoP.109.5' AND duration_value = 2
-       AND duration_unit = 'weeks' AND trigger_event_id = 113;
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.11: upc.inf.cfi.translations_lodge missing or wrong shape (got % matches)', v_count;
-    END IF;
-
-    -- §12 T1.12 pi.response re-anchor
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules dr
-      JOIN paliad.deadline_rules p ON p.id = dr.parent_id
-     WHERE dr.submission_code = 'upc.pi.cfi.response'
-       AND dr.is_active = true AND dr.lifecycle_state = 'published'
-       AND dr.is_court_set = true
-       AND p.submission_code = 'upc.pi.cfi.app';
-    IF v_count <> 1 THEN
-        RAISE EXCEPTION 'mig 132 T1.12: upc.pi.cfi.response not re-anchored on app (got % matches)', v_count;
-    END IF;
-
-    -- §13 Q6 cleanup — no archived _archived_litigation rules left
-    SELECT count(*) INTO v_count
-      FROM paliad.deadline_rules
-     WHERE submission_code LIKE '_archived_litigation.%' ESCAPE '\'
-       AND lifecycle_state = 'archived';
-    IF v_count <> 0 THEN
-        RAISE EXCEPTION 'mig 132 §13: % archived _archived_litigation.* rules still present after cleanup', v_count;
-    END IF;
-END $$;

internal/db/migrations/133_upc_dmgs_pi_court_followup.down.sql

@@ -0,0 +1,33 @@
+-- Reverses mig 133. Removes the 5 new rules:
+--   * upc.dmgs.cfi.interim
+--   * upc.dmgs.cfi.oral
+--   * upc.dmgs.cfi.decision
+--   * upc.dmgs.cfi.appeal_spawn
+--   * upc.pi.cfi.appeal_spawn
+--
+-- The audit_reason is required by the mig 079 trigger for DELETE;
+-- set_config at top supplies it.
+--
+-- Idempotent — if a rule is already missing the DELETE matches zero
+-- rows and the audit log records nothing extra.
+
+SELECT set_config(
+    'paliad.audit_reason',
+    'mig 133 (down): revert UPC Damages tree-end rows and UPC PI appeal-spawn (t-paliad-285 / m/paliad#117 + t-paliad-286 / m/paliad#118)',
+    true);
+
+-- Delete the spawn rows first so the parent_id reference goes away
+-- before the parent decision row is removed.
+DELETE FROM paliad.deadline_rules
+ WHERE submission_code IN (
+        'upc.dmgs.cfi.appeal_spawn',
+        'upc.pi.cfi.appeal_spawn')
+   AND lifecycle_state = 'published';
+
+DELETE FROM paliad.deadline_rules
+ WHERE submission_code IN (
+        'upc.dmgs.cfi.interim',
+        'upc.dmgs.cfi.oral',
+        'upc.dmgs.cfi.decision')
+   AND proceeding_type_id = 17
+   AND lifecycle_state = 'published';

internal/db/migrations/133_upc_dmgs_pi_court_followup.up.sql

@@ -0,0 +1,405 @@
+-- t-paliad-285 (m/paliad#117) + t-paliad-286 (m/paliad#118) —
+-- post-submission court followup for UPC Damages and appeal route
+-- for UPC Provisional Measures.
+--
+-- m's 2026-05-25 report: the upc.dmgs.cfi proceeding stops at the
+-- last party submission (rejoin) — no interim conference, no oral
+-- hearing, no decision row, no appeal-spawn. The upc.pi.cfi
+-- proceeding has its decision row (`pi.order`) but no spawn into
+-- the appeal tree. Both gaps prevent the Verfahrensablauf timeline
+-- from rendering the court phase plus any downstream appeal sub-
+-- tree that atlas's #96 spawn-rendering mechanism is otherwise
+-- ready to surface.
+--
+-- Two sections in one migration (slot 133 — knuth on 132, paliadin
+-- coordinated):
+--
+--   A. UPC Damages tree-end rows (#117)
+--      A1  upc.dmgs.cfi.interim       UPC RoP R.105   court-set hearing
+--      A2  upc.dmgs.cfi.oral          UPC RoP R.118 / R.250  court-set hearing
+--      A3  upc.dmgs.cfi.decision      UPC RoP R.118 / R.144  court-set decision
+--      A4  upc.dmgs.cfi.appeal_spawn  UPC RoP R.220.1(a) / R.224.1(a)  2mo, spawn → upc.apl.merits (id=11)
+--
+--   B. UPC Provisional Measures appeal route (#118)
+--      B1  upc.pi.cfi.appeal_spawn    UPC RoP R.220.1(a) / R.224.1(a)  2mo, spawn → upc.apl.merits (id=11)
+--
+-- Source citations:
+--   * docs/research-deadlines-completeness-2026-05-25.md
+--       — §2.1 (upc.dmgs.cfi has only 4 rules: R.131.2 / R.137.2 / R.139)
+--       — §D Damages table (R.144 tree-end row missing — listed
+--         in Tier 4 as "cosmetic", upgraded to Tier-0 by m's
+--         report once the wider follow-up gap was understood)
+--   * docs/audit-upc-rop-deadlines-2026-05-08.md §D row R.144,
+--     §F R.220.1(a) / R.224.1(a) (verified verbatim in youpc DB
+--     under law_type=UPCRoP).
+--   * UPC Rules of Procedure (consolidated):
+--       R.105 — Interim conference (court fixes after written
+--         procedure closes; same structural shape as the inf
+--         interim conference, already modelled as `upc.inf.cfi.interim`).
+--       R.118 — Decision after oral hearing; general rule for
+--         deciding panels.
+--       R.250 — Determination of damages decision; damages-
+--         specific decision rule (chains R.144 indication →
+--         damages award).
+--       R.144 — Final decision on damages quantum (tree-end
+--         anchor for §A3).
+--       R.220.1(a) — Appeal lies from any final decision /
+--         decision disposing of the case at first instance.
+--         A PI order under R.211 disposes of the urgent question
+--         and is therefore appealable on the main 2-month track
+--         (not the 15-day order track of R.220.1(c), which covers
+--         case-management and procedural orders requiring leave).
+--         Curie's §F table confirms the main-track wiring for
+--         decisions on merits / disposing orders.
+--       R.224.1(a) — Statement of Appeal within 2 months of
+--         service of the final decision; the deadline-notes text
+--         mirrors mig 095's inf.appeal_spawn / rev.appeal_spawn.
+--       R.224.2(a) — Statement of grounds within 4 months
+--         (separate deadline in the spawned upc.apl.merits
+--         proceeding; already present as upc.apl.merits.grounds).
+--
+-- Shape decisions (mirroring mig 012 / mig 095 conventions):
+--   * Court-set rows (interim / oral / decision) carry
+--     primary_party='court', event_type='hearing'|'decision',
+--     duration_value=0, is_court_set=true, parent_id=NULL,
+--     concept_id reuses the shared concepts already wired for
+--     upc.inf.cfi (interim-conference / oral-hearing / decision).
+--   * Spawn rows carry primary_party='both', is_spawn=true,
+--     spawn_proceeding_type_id=11 (upc.apl.merits), spawn_label
+--     identical to the merits spawn already in production. The
+--     spawn row's parent_id is the spawning decision/order row
+--     (so the audit log carries the trigger link).
+--   * No condition_expr — m's F2.3 decision recorded in mig 095
+--     §3: "the appeal deadline should always be triggered by a
+--     decision … appeal is always a possibility." Visibility
+--     filtering on the frontend hides appeals on projects where
+--     no appeal is contemplated.
+--   * sequence_order numbering follows the inf convention
+--     (40=interim, 50=oral, 60=decision, 80=appeal_spawn) so the
+--     Verfahrensablauf timeline orders consistently across
+--     proceedings. For PI the existing pi.order sits at
+--     sequence_order=3; the appeal_spawn lands at 10 (clear of
+--     the writ phase, room for future court-phase rows).
+--
+-- Idempotency: every INSERT is gated by `WHERE NOT EXISTS (… same
+-- submission_code, proceeding_type_id, lifecycle_state)`. Re-apply
+-- against an already-migrated DB inserts zero rows and the audit
+-- log carries no duplicate entries.
+--
+-- audit_reason set_config required at the top — the mig 079 trigger
+-- on paliad.deadline_rules raises EXCEPTION 'audit reason required'
+-- on INSERT/UPDATE/DELETE without it.
+
+SELECT set_config(
+    'paliad.audit_reason',
+    'mig 133: t-paliad-285 / m/paliad#117 + t-paliad-286 / m/paliad#118 — UPC Damages tree-end rows (interim conference R.105, oral hearing R.118/R.250, decision R.118/R.144, appeal-spawn R.220.1(a)) and UPC Provisional Measures appeal-spawn R.220.1(a); see docs/research-deadlines-completeness-2026-05-25.md §D and docs/audit-upc-rop-deadlines-2026-05-08.md §D/§F',
+    true);
+
+-- =============================================================================
+-- A. UPC Damages — court-phase tree end (m/paliad#117)
+-- =============================================================================
+
+-- A1. upc.dmgs.cfi.interim — Interim conference (UPC RoP R.105).
+--     Court-set hearing fixed by the judge-rapporteur once the
+--     written procedure closes. Identical shape to
+--     upc.inf.cfi.interim; reuses the shared interim-conference
+--     concept node.
+INSERT INTO paliad.deadline_rules
+    (proceeding_type_id, parent_id, submission_code, name, name_en,
+     description, primary_party, event_type,
+     duration_value, duration_unit, timing,
+     rule_code, deadline_notes, deadline_notes_en, sequence_order,
+     is_spawn, spawn_proceeding_type_id, spawn_label,
+     is_active, legal_source, is_bilateral,
+     condition_expr, priority, is_court_set, lifecycle_state,
+     concept_id)
+SELECT
+    17,
+    NULL,
+    'upc.dmgs.cfi.interim',
+    'Zwischenverfahren',
+    'Interim Conference',
+    NULL,
+    'court',
+    'hearing',
+    0,
+    'months',
+    'after',
+    NULL,
+    'Termin vom Gericht bestimmt',
+    'Date set by the court',
+    40,
+    false,
+    NULL,
+    NULL,
+    true,
+    NULL,
+    false,
+    NULL,
+    'optional',
+    true,
+    'published',
+    'e5071152-d408-4455-b644-9e79d86fd538'
+WHERE NOT EXISTS (
+    SELECT 1 FROM paliad.deadline_rules
+     WHERE submission_code = 'upc.dmgs.cfi.interim'
+       AND proceeding_type_id = 17
+       AND lifecycle_state = 'published');
+
+-- A2. upc.dmgs.cfi.oral — Oral hearing (UPC RoP R.118 / R.250).
+--     Court-set hearing after the interim conference / close of
+--     written procedure. Same shape as upc.inf.cfi.oral; reuses
+--     the shared oral-hearing concept node.
+INSERT INTO paliad.deadline_rules
+    (proceeding_type_id, parent_id, submission_code, name, name_en,
+     description, primary_party, event_type,
+     duration_value, duration_unit, timing,
+     rule_code, deadline_notes, deadline_notes_en, sequence_order,
+     is_spawn, spawn_proceeding_type_id, spawn_label,
+     is_active, legal_source, is_bilateral,
+     condition_expr, priority, is_court_set, lifecycle_state,
+     concept_id)
+SELECT
+    17,
+    NULL,
+    'upc.dmgs.cfi.oral',
+    'Mündliche Verhandlung',
+    'Oral Hearing',
+    NULL,
+    'court',
+    'hearing',
+    0,
+    'months',
+    'after',
+    NULL,
+    NULL,
+    NULL,
+    50,
+    false,
+    NULL,
+    NULL,
+    true,
+    NULL,
+    false,
+    NULL,
+    'optional',
+    true,
+    'published',
+    'd6e5b793-dcf1-4d83-81ff-34f42dbb3693'
+WHERE NOT EXISTS (
+    SELECT 1 FROM paliad.deadline_rules
+     WHERE submission_code = 'upc.dmgs.cfi.oral'
+       AND proceeding_type_id = 17
+       AND lifecycle_state = 'published');
+
+-- A3. upc.dmgs.cfi.decision — Damages decision (UPC RoP R.118 /
+--     R.144 / R.250). Court-set decision delivered after oral
+--     hearing; closes the §3.1 audit gap (R.144 tree-end). Same
+--     shape as upc.inf.cfi.decision; reuses the shared decision
+--     concept node.
+INSERT INTO paliad.deadline_rules
+    (proceeding_type_id, parent_id, submission_code, name, name_en,
+     description, primary_party, event_type,
+     duration_value, duration_unit, timing,
+     rule_code, deadline_notes, deadline_notes_en, sequence_order,
+     is_spawn, spawn_proceeding_type_id, spawn_label,
+     is_active, legal_source, is_bilateral,
+     condition_expr, priority, is_court_set, lifecycle_state,
+     concept_id)
+SELECT
+    17,
+    NULL,
+    'upc.dmgs.cfi.decision',
+    'Entscheidung',
+    'Decision',
+    NULL,
+    'court',
+    'decision',
+    0,
+    'months',
+    'after',
+    NULL,
+    NULL,
+    NULL,
+    60,
+    false,
+    NULL,
+    NULL,
+    true,
+    NULL,
+    false,
+    NULL,
+    'optional',
+    true,
+    'published',
+    '472fc32d-cc4f-4aa4-8ace-e422031812de'
+WHERE NOT EXISTS (
+    SELECT 1 FROM paliad.deadline_rules
+     WHERE submission_code = 'upc.dmgs.cfi.decision'
+       AND proceeding_type_id = 17
+       AND lifecycle_state = 'published');
+
+-- A4. upc.dmgs.cfi.appeal_spawn — Appeal against damages decision
+--     (UPC RoP R.220.1(a), 2-month main track; grounds R.224.2(a)
+--     run as a separate deadline in the spawned upc.apl.merits
+--     proceeding). Parent points at the freshly-inserted
+--     upc.dmgs.cfi.decision; the SELECT subquery resolves it
+--     after A3 lands. Same shape as the mig 095 inf.appeal_spawn.
+INSERT INTO paliad.deadline_rules
+    (proceeding_type_id, parent_id, submission_code, name, name_en,
+     description, primary_party, event_type,
+     duration_value, duration_unit, timing,
+     rule_code, deadline_notes, deadline_notes_en, sequence_order,
+     is_spawn, spawn_proceeding_type_id, spawn_label,
+     is_active, legal_source, is_bilateral,
+     condition_expr, priority, is_court_set, lifecycle_state)
+SELECT
+    17,
+    (SELECT id FROM paliad.deadline_rules
+      WHERE submission_code = 'upc.dmgs.cfi.decision'
+        AND proceeding_type_id = 17
+        AND lifecycle_state = 'published'
+        AND is_active = true),
+    'upc.dmgs.cfi.appeal_spawn',
+    'Berufung gegen Schadensentscheidung',
+    'Appeal against damages decision',
+    'Berufung gegen die Entscheidung über die Schadensbemessung (R.118 / R.144). Statutarische Frist von 2 Monaten ab Zustellung der Entscheidung (R.224.1(a)); die Berufungsbegründung folgt mit 4 Monaten ab Zustellung (R.224.2(a), eigenständige Frist im Berufungsverfahren).',
+    'both',
+    'filing',
+    2,
+    'months',
+    'after',
+    'RoP.220.1.a',
+    'Innerhalb von 2 Monaten ab Zustellung der Schadensentscheidung Berufungsschrift einreichen (R.224.1(a)). Die Berufungsbegründung (R.224.2(a), 4 Monate) läuft als separate Frist im Berufungsverfahren.',
+    'Within 2 months of service of the damages decision lodge the Statement of appeal (R.224.1(a)). The Statement of grounds (R.224.2(a), 4 months) runs as an independent deadline in the appeal proceeding.',
+    80,
+    true,
+    11,
+    'Berufungsverfahren öffnen',
+    true,
+    'UPC.RoP.220.1',
+    false,
+    NULL,
+    'optional',
+    false,
+    'published'
+WHERE NOT EXISTS (
+    SELECT 1 FROM paliad.deadline_rules
+     WHERE submission_code = 'upc.dmgs.cfi.appeal_spawn'
+       AND proceeding_type_id = 17
+       AND lifecycle_state = 'published');
+
+-- =============================================================================
+-- B. UPC Provisional Measures — appeal route (m/paliad#118)
+-- =============================================================================
+
+-- B1. upc.pi.cfi.appeal_spawn — Appeal against PI order (UPC RoP
+--     R.220.1(a), 2-month main track). PI orders under R.211
+--     dispose of the urgent question and are appealable on the
+--     main 2-month track (R.220.1(a)/R.224.1(a)); the 15-day
+--     order track of R.220.1(c) is for case-management /
+--     procedural orders requiring leave and does not apply to
+--     PI dispositions. Parent points at the existing
+--     upc.pi.cfi.order (sequence_order=3) so the spawn fires
+--     once the order is anchored on a project's timeline.
+INSERT INTO paliad.deadline_rules
+    (proceeding_type_id, parent_id, submission_code, name, name_en,
+     description, primary_party, event_type,
+     duration_value, duration_unit, timing,
+     rule_code, deadline_notes, deadline_notes_en, sequence_order,
+     is_spawn, spawn_proceeding_type_id, spawn_label,
+     is_active, legal_source, is_bilateral,
+     condition_expr, priority, is_court_set, lifecycle_state)
+SELECT
+    10,
+    (SELECT id FROM paliad.deadline_rules
+      WHERE submission_code = 'upc.pi.cfi.order'
+        AND proceeding_type_id = 10
+        AND lifecycle_state = 'published'
+        AND is_active = true),
+    'upc.pi.cfi.appeal_spawn',
+    'Berufung gegen Anordnung',
+    'Appeal against PI order',
+    'Berufung gegen die einstweilige Anordnung nach R.211. Eine PI-Anordnung erledigt die einstweilige Streitfrage und wird wie eine Endentscheidung im Hauptverfahren behandelt: statutarische Frist von 2 Monaten ab Zustellung (R.224.1(a)); die Berufungsbegründung folgt mit 4 Monaten ab Zustellung (R.224.2(a), eigenständige Frist im Berufungsverfahren). Die 15-Tage-Spur nach R.220.1(c) / R.220.2 gilt für Verfahrensanordnungen mit Zulassung und ist hier nicht einschlägig.',
+    'both',
+    'filing',
+    2,
+    'months',
+    'after',
+    'RoP.220.1.a',
+    'Innerhalb von 2 Monaten ab Zustellung der PI-Anordnung Berufungsschrift einreichen (R.224.1(a)). Die Berufungsbegründung (R.224.2(a), 4 Monate) läuft als separate Frist im Berufungsverfahren.',
+    'Within 2 months of service of the PI order lodge the Statement of appeal (R.224.1(a)). The Statement of grounds (R.224.2(a), 4 months) runs as an independent deadline in the appeal proceeding.',
+    10,
+    true,
+    11,
+    'Berufungsverfahren öffnen',
+    true,
+    'UPC.RoP.220.1',
+    false,
+    NULL,
+    'optional',
+    false,
+    'published'
+WHERE NOT EXISTS (
+    SELECT 1 FROM paliad.deadline_rules
+     WHERE submission_code = 'upc.pi.cfi.appeal_spawn'
+       AND proceeding_type_id = 10
+       AND lifecycle_state = 'published');
+
+-- =============================================================================
+-- C. Post-insert verification — raise if any expected row is missing
+--    (matches the mig 095 / 127 convention; protects against a future
+--    re-shape of the table that silently drops one of the WHERE NOT
+--    EXISTS predicates).
+-- =============================================================================
+
+DO $$
+DECLARE
+    v_missing text;
+BEGIN
+    SELECT string_agg(expected, ', ' ORDER BY expected)
+      INTO v_missing
+      FROM (VALUES
+            ('upc.dmgs.cfi.interim'),
+            ('upc.dmgs.cfi.oral'),
+            ('upc.dmgs.cfi.decision'),
+            ('upc.dmgs.cfi.appeal_spawn'),
+            ('upc.pi.cfi.appeal_spawn')
+        ) AS t(expected)
+     WHERE NOT EXISTS (
+        SELECT 1 FROM paliad.deadline_rules dr
+         WHERE dr.submission_code = t.expected
+           AND dr.lifecycle_state = 'published'
+           AND dr.is_active = true);
+
+    IF v_missing IS NOT NULL THEN
+        RAISE EXCEPTION
+            'mig 133: expected published rules missing after insert: %', v_missing;
+    END IF;
+
+    IF NOT EXISTS (
+        SELECT 1 FROM paliad.deadline_rules dr
+         WHERE dr.submission_code = 'upc.dmgs.cfi.appeal_spawn'
+           AND dr.proceeding_type_id = 17
+           AND dr.spawn_proceeding_type_id = 11
+           AND dr.is_spawn = true
+           AND dr.parent_id IS NOT NULL
+           AND dr.lifecycle_state = 'published'
+    ) THEN
+        RAISE EXCEPTION
+            'mig 133: upc.dmgs.cfi.appeal_spawn shape check failed (expected is_spawn=true, spawn_proceeding_type_id=11, parent_id set)';
+    END IF;
+
+    IF NOT EXISTS (
+        SELECT 1 FROM paliad.deadline_rules dr
+         WHERE dr.submission_code = 'upc.pi.cfi.appeal_spawn'
+           AND dr.proceeding_type_id = 10
+           AND dr.spawn_proceeding_type_id = 11
+           AND dr.is_spawn = true
+           AND dr.parent_id IS NOT NULL
+           AND dr.lifecycle_state = 'published'
+    ) THEN
+        RAISE EXCEPTION
+            'mig 133: upc.pi.cfi.appeal_spawn shape check failed (expected is_spawn=true, spawn_proceeding_type_id=11, parent_id set)';
+    END IF;
+END $$;