MC-4415

Elmar request (Telegram, 2026-05-29): update the May fuel burn numbers and update/regenerate the fuel impact report. He normally does this on Lucienne; QV numbers must be refreshed using the Windows PC on the work network. Context already found: - Current report artifacts: `/home/lucienne/workspace/PKA/reports/fuel-impact-2026-05-27.html` and methodology `.md`. - Relevant plan from previous iteration: `/home/lucienne/workspace/PKA/docs/plans/2026-05-27-fuel-impact-may-third-column.md`. - Fuel-impact workflow/source: PKA `.claude/skills/fuel-impact-report/build_report.py` (single-file report builder; load the repo/project skill/runbook before edits). - QV export/project note: `/home/lucienne/workspace/PKA/Vault/memory/auto/lucienne/project_qlikview_exports_repo.md`. - May projection memory: `/home/lucienne/workspace/PKA/Vault/memory/auto/lucienne/project_fuel_impact_actuals_projection.md`. - Latest methodology states QV fuel-burn is used for May fuel volume via activity × intensity. Update this now with the current May QV export/actuals. Access verified by controller before ticket creation: - Windows PC SSH reachable: `ssh 'elmar conradie'@100.118.210.89` returned host `DESKTOP-601MKF8`. - Use this Windows PC for QV/work-network access; if Lucienne/Mac Dropbox/OneDrive is needed, use the documented Mac remote-dispatch path from AGENTS. Expected work: 1. Refresh the QV Fuel Burn Detail export for May/current month from the Windows PC on the work network. Find/execute the existing QlikView export workflow where possible; do not invent numbers. 2. Copy/update the canonical fuel-burn workbook used by the report, normally `Fuel Burn 2026.xlsx` under Safair Reporting Data / Fuel Burn, keeping a dated backup of the previous file. 3. Re-read the current May dashboard/FinDash/B4i inputs needed by `fuel-impact-report`. 4. Regenerate the fuel impact HTML + methodology report with May numbers updated. If May is still not closed in FinDash, label the non-closed values clearly as projection/MTD and do not present them as GL actuals. 5. Verify report math against source rows: QV fuel volume/intensity, revenue, fuel R/L, fuel cost, PBT/scenario outputs, and May labels. 6. Produce a concise handoff for Elmar with: - what QV export/date was used, - old vs new May fuel-burn/fuel-volume numbers, - updated report link through MC markdown/report viewer where appropriate, - caveats about actual vs projection. Quality gates: - If code/report-builder changes are needed, use the mandatory single-session dev-loop before edits/commit. - Preserve March/April actuals and existing recovery ratio logic unless source data has genuinely changed. - No Apr→May recovery percentage; May relief/projection caveat remains. - Run the report builder cleanly and inspect the generated HTML/methodology for May labels. - Commit/push any repo changes and attach/link generated artifacts if they are part of PKA repo workflow. Expected check-in: today after QV export attempt; if Windows/QV automation blocks, report exact blocker and what manual action is needed.