feat: harden local runtime and verification

This commit is contained in:
Joseph Magly
2026-08-23 11:16:10 -04:00
parent b0da692ea0
commit ad883cef0b
14 changed files with 602 additions and 58 deletions
+24 -2
View File
@@ -76,10 +76,32 @@ CUDA_TORCH_VERSION="$(.venv/bin/python -c \
UV_TORCH_BACKEND=cu130 uv pip install --python .venv/bin/python \
--reinstall-package torch "torch==$CUDA_TORCH_VERSION"
uv pip check --python .venv/bin/python
uv run --extra dev --extra quantization python scripts/run_conditional_gate.py cuda-runtime
uv run --extra dev --extra quantization python scripts/run_conditional_gate.py bitsandbytes-runtime
.venv/bin/python scripts/run_conditional_gate.py cuda-runtime
.venv/bin/python scripts/run_conditional_gate.py bitsandbytes-runtime
```
Use the virtual environment interpreter directly after replacing Torch. A subsequent
`uv run` or `uv sync` without the CUDA override may restore the portable CPU wheel
from the lock. The agentic developer installer automates this ordering and performs
a real CUDA tensor probe; see `installer/setup.dev.manifest.yaml`.
## Quality-verifier coherence semantics
The built-in VERIFY stage does not treat length and vocabulary diversity as
coherence. Each fixed factual prompt has deterministic semantic anchors, and the
scorer rejects strong repetition and recognizable corpus contamination such as
scraped Q&A profile/answer fragments. This is intentionally local and deterministic:
release verification does not call another model or a network judge. Perplexity and
extended capability checks remain separate measurements.
On Linux workstations that also install cuDNN system-wide, the dynamic loader can
mix a host sublibrary with PyTorch's bundled cuDNN and raise
`CUDNN_STATUS_SUBLIBRARY_VERSION_MISMATCH`. The local launcher sets
`OBLITERATUS_DISABLE_CUDNN=1`, keeping causal convolutions and attention on
PyTorch's other CUDA kernels rather than moving the model to the CPU. Installer
verification runs actual causal `conv1d` and SDPA operations, not only a generic
CUDA allocation, so this failure is caught before a model pipeline begins.
Jetson CUDA support is tracked separately from this generic x64 CUDA lane. The
mandatory `Linux ARM64 preflight` uses GitHub's hosted `ubuntu-24.04-arm` runner
to prove locked CPU packaging, imports, CLI startup, and Jetson tooling contracts.