Expand compatibility matrix coverage across indicators and fixtures

[TDamiao]

Goal

Broaden compatibility coverage across more indicators and fixtures to strengthen the trust layer for future releases.

Why

Current policy and gates are solid, but coverage is concentrated on a subset. Expanding breadth reduces blind spots.

Implementation prompt

Extend compat vectors/scripts to include additional indicators prioritized by usage and implementation risk.

Add:

• More fixtures (trending, mean-reverting, high-volatility, gap-heavy)
• More indicator outputs in compat-current.json
• Policy entries (scripts/compat-policy.json) with explicit burn-in/tolerance per added indicator

Keep blocking/non-blocking reference behavior consistent with current model.

Scope

• Maintain deterministic export/compare workflow
• Preserve release gate clarity in CI logs
• Update README compatibility matrix accordingly

Acceptance criteria

• Compatibility checks cover the expanded indicator set
• Tolerance and burn-in are explicitly documented per new indicator
• CI output remains readable and actionable
• No silent skips for blocking refs

Test plan

• Run technicalindicators and python refs comparisons in CI
• Add regression tests to ensure policy and exported vectors stay in sync
• Verify one failure case produces clear diagnostics

[TDamiao]

Tracked by v0.4 master gate: #21.