Dental

In app/Services/PlanfactService.php at around line 2645, inside parseQuoteDental(), the Deductible Period switch handles unusual values like a single "c" or "ccalendar year". The single-character "c" match is too permissive.

Please:
1. Show me the switch.
2. Replace the single-character "c" case with explicit case-insensitive matching for "calendar year" only.
3. Add a default branch that logs a warning when an unexpected value is encountered, instead of silently mapping unknown strings.
4. Show me the proposed change.

In app/Services/PlanfactService.php at lines 2656–2676, inside parseQuoteDental(), the Rollover Amount is written to two field formats simultaneously:
- inNetwork{1,2}RolloverMaximum (legacy)
- inNetwork{1,2}RolloverVer2 + Type (new)

Comments in the source suggest the dual-write was a reversible migration safety net.

Please:
1. Show me the current dual-write.
2. Search the codebase (form templates, presentation rendering, exports, any Excel job) for which format is actually consumed.
3. If only Ver2 is consumed, recommend removing the legacy write here. If both are still used somewhere, document why with a comment.
4. Don't change anything yet — show the audit results first.

In app/Services/PlanfactService.php at lines 2997–3034, inside parseQuoteDental(), the Cleanings frequency regex matches "N per [period]" but only covers 6 specific period strings (calendar year, plan year, 6 Months, etc.).

Common phrasings like "every 12 months", "twice annually", "2 per benefit year" may silently fail to match.

Please:
1. Show me the current regex / switch.
2. Recommend a more flexible matcher that handles "every N months", "N per [period]", "twice/three times per [period]" — or a fallback path that captures the raw string and flags it for review.
3. Show me the proposed change.

In app/Services/PlanfactService.php at lines 2555–2557, inside parseQuoteDental(), Excess Responsibility is set unconditionally:
- in-network: "None"
- out-of-network: "Yes"

Not read from Plan Facts.

Please:
1. Show me the assignment.
2. Add a 2-line code comment explaining why these are hardcoded (because dental balance-billing rules are standard and don't need per-plan extraction).
3. No behavior change.

In app/Services/PlanfactService.php at lines 2875–2900, inside parseQuoteDental(), waiting period handling distinguishes:
- field absent → skip entirely (no value set on Quote)
- field present with empty / zero value → Type = "None"

The first case might mask incomplete Plan Facts responses.

Please:
1. Show me the current logic.
2. Recommend either:
   (a) treat absent same as zero (always set Type = "None" if no value), or
   (b) log a warning when the field is absent so we know if Plan Facts ever sends incomplete data.
3. Don't change yet — recommend.