docs: add FAQ and JSON-LD schema

[cloudsealed]

Add FAQ section covering: what the lib does, vs ML.NET alone, .NET version, zero-allocation meaning, ASP.NET Core integration example.

Add JSON-LD FAQPage schema for LLM/search discoverability.

[github-actions]

🏗️ predictive-ml-core — architecture risk audit

Analysis of 4 system(s) for Acme complete. Overall score (weighted by criticality): 67/100. 4 finding(s), 4 recommendation(s).

Overall score	Systems	Findings
67/100	4	4

Findings

System	Severity	Title
checkout-api	HIGH	Single point of failure: checkout-api	System 'checkout-api' (criticality CRITICAL, type API) declares no redundancy. Assumption: the input schema exposes no redundancy field, so a single instance is assumed (worst case).
orders-db	CRITICAL	Single point of failure: orders-db	System 'orders-db' (criticality CRITICAL, type DATABASE) declares no redundancy. Assumption: the input schema exposes no redundancy field, so a single instance is assumed (worst case).
orders-db	MEDIUM	Scalability gap: orders-db	Insufficient scalability signal for 'orders-db' (no historicalMetrics — conditional risk, labeled as unknown risk).
payment-gateway	HIGH	Single point of failure: payment-gateway	System 'payment-gateway' (criticality HIGH, type THIRD_PARTY_SERVICE) declares no redundancy. Assumption: the input schema exposes no redundancy field, so a single instance is assumed (worst case).

Top recommendations

• Implement redundancy (checkout-api) — effort MEDIUM
• Implement redundancy (orders-db) — effort HIGH
• Improve scalability (orders-db) — effort MEDIUM
• Implement redundancy (payment-gateway) — effort MEDIUM

Generated by Predictive-ML-Core — deterministic, auditable rule scoring, method in METHODOLOGY.md.