Initial Argument-Risk-Engine MVP scaffold

[Spbd1]

Motivation

• Provide a local, taxonomy-first, evidence-grounded MVP for argument risk analysis that is runnable from a Chrome-first web dashboard.
• Offer a minimal, conservative analysis pipeline (claim extraction → lexical retrieval → deterministic classification → scoring → evidence/explanation) that surfaces review signals rather than automated judgement.
• Make the project easy to bootstrap and test locally with a one-command development flow and file-backed taxonomy/workbench workflows.

Description

• Added a full scaffold for the project including pyproject.toml, Makefile, README.md, docs, top-level package.json, docker-compose.yml, and example .env.example to describe setup and packaging.
• Implemented a FastAPI-style backend (backend/app) with API routes, schemas, and services for analysis, taxonomy, workbench, review, evaluation, settings, and reports, plus file-path helpers and simple logging.
• Implemented the analysis engine under engine/argument_risk_engine with taxonomy models and pack loader/saver, Excel importer/exporter, claim extraction, lexical retriever, deterministic classifier, scoring/calibration, evidence/explainer, evaluation runner, and report renderers.
• Added a lightweight frontend MVP under frontend/ (React/TSX structure, minimal dev/build scripts) and project scripts (scripts/dev.py, bootstrap.py, run_backend.py, run_frontend.py, seed_demo_data.py, import/export helpers) to support the one-command flow and local demo data seeding.

Testing

• Ran python -m pip install -e .[dev] successfully (editable install built with a local build backend to avoid external dependency failures).
• Compiled the code with python -m compileall backend engine tests and ran pytest, with the test suite passing (12 passed, 3 warnings).
• Built the frontend with the local stubbed build (cd frontend && npm run build) and confirmed the frontend dist was produced; npm install initially encountered a registry access error in this environment but a lightweight local frontend build path was exercised and succeeded.
• Exercised make test and ran timeout 8 python scripts/dev.py --install --run --open to confirm install, seeding, and server startup paths (the long-running dev servers were intentionally stopped by timeout after confirming startup prints).

---

Codex Task