Spaces:
Sleeping
Sleeping
Commit History
-
0.6.3: CI ui-build — npm install instead of npm ci
The CI workflow's ui-build job used `npm ci` with a `cache-dependency-path: ui/package-lock.json`, but we don't ship a lock file (matching the HF Docker build, which also uses `npm install`). The job would fail on every push until a lock was committed. Switch to `npm install --no-audit --no-fund` to match the Docker stage's install step. This trades reproducibility (same versions on every run) for parity with the HF build — the Docker image is what actually deploys, so CI should validate the same install path. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>37d7dce -
Initial scaffold: HCC-MEAT Coder v0.1.0
End-to-end runnable pipeline with rule-based baselines in place of ML components, a FastAPI backend serving a React three-panel UI, and a 10-case regression suite guarding the invariants from AGENT_BRIEF.md §3 (faithfulness, negation/family-history filtering, hierarchy trumping, transparent risk). Deterministic components (real, tested): - E — HCC crosswalk + trumping over CMS-HCC v28 seed tables - H — over-coding (RADV) risk heuristic with named components + reasons - I — faithfulness verifier (substring guarantee + NLI hook) Baseline / swappable components: - A segmenter, B dictionary NER, C negation, D exact/alias linker, F rule-based MEAT extractor, G identity calibrator Infra: uv-driven pyproject, ruff + pytest + pre-commit, GH Actions CI for Python and UI, multi-stage Dockerfile for the HF Docker Space, typer CLIs for pipeline (`hcc-meat`) and evaluation (`hcc-meat-eval`). Reference data in data/reference/ uses PLACEHOLDER RAF weights; hydrate via scripts/fetch_cms_hcc_v28.…c6cfe5f
