fix(s31): pin numpy <2.3 — >=2.3 breaks the >=3.10 floor and mypy stub parsing

This commit is contained in:
Kjell Tore Guttormsen 2026-07-25 06:12:56 +02:00
commit 8a8c4f0fca
2 changed files with 9 additions and 150 deletions

View file

@ -19,7 +19,13 @@ dependencies = [
# PuLP 4.0 vil kreve `pip install pulp[cbc]` + COIN_CMD (Fase-migrasjonsnotat).
"mcp>=1.28.0", # tynn lokal-mappe MCP-server (Step 7) — GA (resolverte 1.28.0) per Step 1-beslutning
"pydantic>=2.11,<3", # IR/validering (B1) — eksplisitt pin til STABIL 2.x, aldri alpha
"numpy>=2.0,<3", # S3.1: brute-force cosine for the hybrid verdict retriever — MAF-free, offline (D-C)
# S3.1: brute-force cosine for the hybrid verdict retriever — MAF-free, offline (D-C).
# Upper bound is <2.3, NOT <3, and it is load-bearing twice over: numpy 2.3+ requires
# Python >=3.11 (2.4+ requires >=3.12), so a wider range silently contradicts this project's
# `requires-python = ">=3.10"`; and numpy 2.3+ stubs use PEP 695 `type` statements, which
# mypy refuses to parse under `python_version = 3.10` (python/mypy#18701) — breaking
# `uv run mypy src` outright. Raise both floors together or not at all.
"numpy>=2.0,<2.3",
"llm-ingestion-okf", # Door A ingest (§4§6) — the shared implementation of shared/ingest-spec.md; zero runtime deps, MAF-free (D7)
]