Implement phase 6 critical effect normalization

docs/critical_tables_db_model.md

@@ -145,6 +145,7 @@ Recommended canonical `effect_code` values:
 - `bleed_per_round`
 - `foe_penalty`
 - `attacker_bonus_next_round`
+- `power_point_modifier`
 - `initiative_gain`
 - `initiative_loss`
 - `drop_item`
@@ -169,6 +170,11 @@ Each effect should point to either:
 
 This lets you keep the raw text but still filter/query on effects.
 
+Current implementation note:
+
+- symbol-driven affixes are now normalized for both base results and conditional branch affixes
+- `value_expression` is used when the affix contains a formula instead of a flat integer, which is currently needed for `Mana` power-point adjustments such as `+(2d10-18)P`
+
 ## Why this works for your lookup
 
 Your lookup target is mostly:
@@ -258,8 +264,8 @@ Current import flow:
 1. Create `critical_table`, `critical_group`, `critical_column`, and `critical_roll_band` from each PDF's visible axes.
 2. Store each base cell in `critical_result` with base raw/description/affix text.
 3. Split explicit conditional branches into `critical_branch`.
-4. Return the base result plus ordered branches through the web critical lookup.
-5. Parse symbolic affixes into `critical_effect` in the next phase.
+4. Parse symbolic affixes for both the base result and any branch affix payloads into `critical_effect`.
+5. Return the base result plus ordered branches and parsed affix effects through the web critical lookup.
 6. Gradually enrich prose-derived effects such as death, blindness, paralysis, limb loss, initiative changes, and item breakage.
 7. Route image PDFs like `Void.pdf` through OCR before the same parser.