Refactor codebase into feature modules

[ocularminds]

Summary

• reorganize the Python API into feature-owned decision, demo, policy, and risk modules
• introduce explicit service, data-source, repository, and skill contracts
• move web behavior into feature folders with shared UI components and typed API infrastructure
• standardize authored module and test filenames to PascalCase and application identifiers to camelCase
• keep FastAPI routes, JSON field names, decision rules, risk scoring, and Next.js URLs unchanged
• update runtime entrypoints and documentation for the new module paths

Why

The previous implementation concentrated API composition, scoring, data generation, and page behavior in large procedural files. The new boundaries give each module one reason to change, encapsulate mutable state and external resources, and make feature ownership explicit without changing product behavior.

Impact

There are no intended API or UI behavior changes. Existing snake_case transport fields remain mapped at the API boundary, and framework-required filenames remain intact.

Validation

• ruff check passed
• ruff format --check passed
• 22 backend tests passed
• OpenAPI transport contract verified
• CLI smoke test passed
• ESLint passed
• TypeScript and production Next.js build passed