Add support triage budget policy evidence

[taditya1997]

Summary

• add a support-triage workload with 15 labelled SaaS support tickets
• add a cross-provider support-triage ladder, pricing, budget caps, and judge policy under proofs/config/support_triage/
• record p4 journal details so README evidence includes the ordered event trace
• document measured cost/resolution trade-off, break-even rate, trace id, adversarial budget refusal, and reproduced floor results

Verification

• uv run pytest -q -> 280 passed, 1 warning in 54.79s
• uv run ruff check . -> All checks passed
• p1 support_triage -> ALL CHECKS PASSED
• p2 support_triage -> ALL CHECKS PASSED
• p3 support_triage -> ALL CHECKS PASSED
• p4 support_triage -> ALL CHECKS PASSED
• p6 support_triage -> ALL CHECKS PASSED
• p7 support_triage -> ALL CHECKS PASSED

Note: local gateway http://127.0.0.1:8112 was unavailable, so the README labels the proof evidence as offline. The controller, ledger, graph, refusal path, and trace export still use the real implementation.