Make live-model use and deterministic fallback explicit

[simaba]

Assessment-provenance and usability hardening

• introduces a provenance-aware assessment service that records whether output came from the live model or the deterministic fallback
• records the selected model name or a safe fallback reason on AssessmentResult
• makes fallback provenance visible in the role-aware summary and CLI output
• adds --require-llm so CLI users can fail clearly instead of accepting a fallback when a live result is required
• repairs the Tool Recommender import failure, replaces its fragile nested UI block with a smaller testable seven-question wizard, and adds rule-level tests
• adds regression tests for missing-key fallback and strict mode
• documents the two generation modes and their limits
• adds monthly dependency-update automation

The deterministic fallback remains available for local demos and offline work; this change prevents it from being mistaken for a successful live-model response.