nthlayer-core 3.0.2__tar.gz → 4.0.0__tar.gz

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: nthlayer-core
-Version: 3.0.2
+Version: 4.0.0
 Summary: NthLayer core — reliability-critical verdict store, case management, and HTTP API
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
-Requires-Dist: nthlayer-common<6.0.0,>=5.3.0
+Requires-Dist: nthlayer-common<6.0.0,>=5.3.1
 Requires-Dist: starlette>=0.40
 Requires-Dist: uvicorn>=0.30
 Requires-Dist: httpx>=0.27
@@ -23,9 +23,13 @@ Requires-Dist: ruff>=0.8; extra == "dev"
 
 ```bash
 pip install nthlayer-core
-nthlayer serve --host 0.0.0.0 --port 8000
+nthlayer-core serve --host 0.0.0.0 --port 8000
 ```
 
+The console script was `nthlayer` before 4.0.0; it was renamed to `nthlayer-core` because nthlayer-generate owns `nthlayer` (opensrm-dww5).
+
+**Upgrading from 3.x:** if nthlayer-generate is installed in the same environment, reinstall it after upgrading core, because the 3.x core package owned the `nthlayer` script file and the upgrade removes it: `pip install --force-reinstall --no-deps nthlayer-generate` (or `uv pip install --reinstall-package nthlayer-generate nthlayer-generate`).
+
 ## What it is
 
 `nthlayer-core` is the single source of truth for the NthLayer runtime. It owns the SQLite store, exposes an HTTP API, and is the only component that touches the database. Tier 2 workers ([`nthlayer-workers`](https://github.com/rsionnach/nthlayer-workers)) and the Tier 3 operator TUI ([`nthlayer-bench`](https://github.com/rsionnach/nthlayer-bench)) talk to core exclusively over HTTP — never directly to SQLite.
@@ -101,8 +105,8 @@ WAL mode + `PRAGMA synchronous=NORMAL` + `busy_timeout=5000`. Thread-local conne
 ## CLI
 
 ```bash
-nthlayer serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
-nthlayer -V                                       # print version
+nthlayer-core serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
+nthlayer-core -V                                    # print version
 ```
 
 ## NthLayer ecosystem

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/README.md

@@ -4,9 +4,13 @@
 
 ```bash
 pip install nthlayer-core
-nthlayer serve --host 0.0.0.0 --port 8000
+nthlayer-core serve --host 0.0.0.0 --port 8000
 ```
 
+The console script was `nthlayer` before 4.0.0; it was renamed to `nthlayer-core` because nthlayer-generate owns `nthlayer` (opensrm-dww5).
+
+**Upgrading from 3.x:** if nthlayer-generate is installed in the same environment, reinstall it after upgrading core, because the 3.x core package owned the `nthlayer` script file and the upgrade removes it: `pip install --force-reinstall --no-deps nthlayer-generate` (or `uv pip install --reinstall-package nthlayer-generate nthlayer-generate`).
+
 ## What it is
 
 `nthlayer-core` is the single source of truth for the NthLayer runtime. It owns the SQLite store, exposes an HTTP API, and is the only component that touches the database. Tier 2 workers ([`nthlayer-workers`](https://github.com/rsionnach/nthlayer-workers)) and the Tier 3 operator TUI ([`nthlayer-bench`](https://github.com/rsionnach/nthlayer-bench)) talk to core exclusively over HTTP — never directly to SQLite.
@@ -82,8 +86,8 @@ WAL mode + `PRAGMA synchronous=NORMAL` + `busy_timeout=5000`. Thread-local conne
 ## CLI
 
 ```bash
-nthlayer serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
-nthlayer -V                                       # print version
+nthlayer-core serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
+nthlayer-core -V                                    # print version
 ```
 
 ## NthLayer ecosystem

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "nthlayer-core"
-version = "3.0.2"
+version = "4.0.0"
 description = "NthLayer core — reliability-critical verdict store, case management, and HTTP API"
 readme = "README.md"
 requires-python = ">=3.11"
@@ -20,17 +20,19 @@ dependencies = [
     # every threshold entry [opensrm-7zpz]; catalogue.manifest_to_dict
     # serialises each threshold via threshold_to_v2_entry, common's validated
     # emitter of the v2 spec.judgment_threshold entry, never a hand-copy.
-    # WHY 5.3.0 (opensrm-pnmv): the version this repo is now built and tested
+    # WHY 5.3.1 (opensrm-dww5): the version this repo is now built and tested
     # against (rule 10: the floor is the installed sibling). Bump it on
     # every nthlayer-common minor release: the floor guard fails until you do.
-    "nthlayer-common>=5.3.0,<6.0.0",
+    # Raised to 5.3.1 (a patch) because its opensrm/v1 rejection names a
+    # command that runs in a co-install.
+    "nthlayer-common>=5.3.1,<6.0.0",
     "starlette>=0.40",
     "uvicorn>=0.30",
     "httpx>=0.27",
 ]
 
 [project.scripts]
-nthlayer = "nthlayer_core.cli:main"
+nthlayer-core = "nthlayer_core.cli:main"
 
 [project.optional-dependencies]
 dev = [

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/src/nthlayer_core/cli.py

@@ -9,7 +9,7 @@ def build_parser() -> argparse.ArgumentParser:
     """Build the CLI parser. Exposed so tests can introspect the surface
     without running ``main``'s side effects (see
     ``tests/test_deploying_doc_parity.py``)."""
-    parser = argparse.ArgumentParser(description="NthLayer core")
+    parser = argparse.ArgumentParser(prog="nthlayer-core", description="NthLayer core")
     parser.add_argument("-V", "--version", action="version", version=f"%(prog)s {__version__}")
     sub = parser.add_subparsers(dest="command")
 

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/src/nthlayer_core.egg-info/PKG-INFO

@@ -1,10 +1,10 @@
 Metadata-Version: 2.4
 Name: nthlayer-core
-Version: 3.0.2
+Version: 4.0.0
 Summary: NthLayer core — reliability-critical verdict store, case management, and HTTP API
 Requires-Python: >=3.11
 Description-Content-Type: text/markdown
-Requires-Dist: nthlayer-common<6.0.0,>=5.3.0
+Requires-Dist: nthlayer-common<6.0.0,>=5.3.1
 Requires-Dist: starlette>=0.40
 Requires-Dist: uvicorn>=0.30
 Requires-Dist: httpx>=0.27
@@ -23,9 +23,13 @@ Requires-Dist: ruff>=0.8; extra == "dev"
 
 ```bash
 pip install nthlayer-core
-nthlayer serve --host 0.0.0.0 --port 8000
+nthlayer-core serve --host 0.0.0.0 --port 8000
 ```
 
+The console script was `nthlayer` before 4.0.0; it was renamed to `nthlayer-core` because nthlayer-generate owns `nthlayer` (opensrm-dww5).
+
+**Upgrading from 3.x:** if nthlayer-generate is installed in the same environment, reinstall it after upgrading core, because the 3.x core package owned the `nthlayer` script file and the upgrade removes it: `pip install --force-reinstall --no-deps nthlayer-generate` (or `uv pip install --reinstall-package nthlayer-generate nthlayer-generate`).
+
 ## What it is
 
 `nthlayer-core` is the single source of truth for the NthLayer runtime. It owns the SQLite store, exposes an HTTP API, and is the only component that touches the database. Tier 2 workers ([`nthlayer-workers`](https://github.com/rsionnach/nthlayer-workers)) and the Tier 3 operator TUI ([`nthlayer-bench`](https://github.com/rsionnach/nthlayer-bench)) talk to core exclusively over HTTP — never directly to SQLite.
@@ -101,8 +105,8 @@ WAL mode + `PRAGMA synchronous=NORMAL` + `busy_timeout=5000`. Thread-local conne
 ## CLI
 
 ```bash
-nthlayer serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
-nthlayer -V                                       # print version
+nthlayer-core serve [--host 0.0.0.0] [--port 8000]   # start the HTTP server
+nthlayer-core -V                                    # print version
 ```
 
 ## NthLayer ecosystem

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/src/nthlayer_core.egg-info/SOURCES.txt

@@ -24,6 +24,7 @@ tests/test_api_heartbeats.py
 tests/test_api_manifests.py
 tests/test_api_overrides.py
 tests/test_api_suppressions.py
+tests/test_console_script_name.py
 tests/test_dependency_declarations.py
 tests/test_deploying_doc_parity.py
 tests/test_health.py

nthlayer_core-4.0.0/src/nthlayer_core.egg-info/entry_points.txt

@@ -0,0 +1,2 @@
+[console_scripts]
+nthlayer-core = nthlayer_core.cli:main

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/src/nthlayer_core.egg-info/requires.txt

@@ -1,4 +1,4 @@
-nthlayer-common<6.0.0,>=5.3.0
+nthlayer-common<6.0.0,>=5.3.1
 starlette>=0.40
 uvicorn>=0.30
 httpx>=0.27

nthlayer_core-4.0.0/tests/test_console_script_name.py

@@ -0,0 +1,126 @@
+"""The console script is ``nthlayer-core``, never ``nthlayer``.
+
+nthlayer-generate owns ``nthlayer``. Both packages registering it made the
+installed one depend on install order, so core declares only ``nthlayer-core``
+(symmetric naming: PyPI name = repo = script). Bead: opensrm-dww5.
+"""
+from __future__ import annotations
+
+import pathlib
+import re
+import tomllib
+
+import pytest
+
+from nthlayer_core.cli import build_parser
+
+REPO_ROOT = pathlib.Path(__file__).resolve().parent.parent
+
+# Lines containing any of these are exempt from the guard: they name the old
+# script on purpose (the rename note and the 3.x upgrade note). Keep in sync
+# with those notes in README.md and docs/deploying.md.
+RENAME_NOTE_MARKERS = ("before 4.0.0", "Upgrading from 3.x")
+
+# Legitimate mentions of the bare name that are NOT the console script: the
+# `nthlayer` meta-package on PyPI. Matched by line substring, not by weakening
+# the regex.
+ALLOWED_LINE_SUBSTRINGS = ("front door + meta-package",)
+
+# The bare word `nthlayer` (not preceded by a word char, `/`, `.` or `-`) in a
+# stale-invocation position: followed by a subcommand/flag (`serve`,
+# `--version`, `-V`, `--help`), a version number (`nthlayer 1.7.0` output), a
+# backtick, `:`, `→`, or end of line. So it ignores nthlayer-core,
+# nthlayer-generate, nthlayer_core, NTHLAYER_*, /var/lib/nthlayer/, nthlayer.io.
+STALE_SCRIPT_RE = re.compile(
+    r"(?<![\w/.-])nthlayer"
+    r"(?=\s+(?:serve\b|--version|-V\b|--help|\d+\.\d+)|\s*$|`|:|\s*→)",
+    re.MULTILINE,
+)
+
+
+def _scripts() -> dict[str, str]:
+    data = tomllib.loads((REPO_ROOT / "pyproject.toml").read_text(encoding="utf-8"))
+    return data["project"]["scripts"]
+
+
+def test_pyproject_declares_nthlayer_core_script() -> None:
+    assert _scripts().get("nthlayer-core") == "nthlayer_core.cli:main"
+
+
+def test_pyproject_does_not_declare_nthlayer_script() -> None:
+    assert "nthlayer" not in _scripts(), (
+        "core must not register `nthlayer`; nthlayer-generate owns it"
+    )
+
+
+def test_parser_prog_is_nthlayer_core() -> None:
+    assert build_parser().prog == "nthlayer-core"
+
+
+@pytest.mark.parametrize(
+    "text",
+    [
+        "nthlayer serve --port 8000",
+        "nthlayer --version",
+        "nthlayer -V",
+        "nthlayer --help",
+        "nthlayer 1.7.0",
+        "run nthlayer",
+        "see nthlayer:",
+        "the `nthlayer` script",
+        "nthlayer \u2192 nthlayer_core.cli:main",
+    ],
+)
+def test_stale_script_regex_matches(text: str) -> None:
+    assert STALE_SCRIPT_RE.search(text), text
+
+
+@pytest.mark.parametrize(
+    "text",
+    [
+        "nthlayer-core serve",
+        "nthlayer-generate build",
+        "import nthlayer_core",
+        "nthlayer-common>=1.5.0",
+        "NTHLAYER_STORE_PATH=/x",
+        "/var/lib/nthlayer/data",
+        "https://nthlayer.io/docs",
+        "nthlayer.db-wal",
+        "pip install nthlayer-core",
+        "nthlayer-core --version",
+        # `-` in the lookbehind: a hyphenated prefix is another name, not
+        # the bare script (e.g. a `foo-nthlayer` binary or path segment).
+        "foo-nthlayer serve",
+    ],
+)
+def test_stale_script_regex_ignores(text: str) -> None:
+    assert not STALE_SCRIPT_RE.search(text), text
+
+
+# Top-level docs that tell a reader how to run core. CHANGELOG.md is excluded:
+# it is a historical record and names the old script on purpose.
+_ROOT_DOCS = ("README.md", "AGENTS.md", "CONTRIBUTING.md", "CLAUDE.md")
+
+
+def _doc_paths() -> list[pathlib.Path]:
+    return [
+        *(REPO_ROOT / name for name in _ROOT_DOCS),
+        *sorted((REPO_ROOT / "docs").glob("*.md")),
+    ]
+
+
+def test_docs_exist_so_guard_is_not_vacuous() -> None:
+    names = {p.name for p in _doc_paths()}
+    assert {*_ROOT_DOCS, "deploying.md", "architecture.md"} <= names
+
+
+@pytest.mark.parametrize("path", _doc_paths(), ids=lambda p: p.name)
+def test_docs_invoke_nthlayer_core_not_nthlayer(path: pathlib.Path) -> None:
+    lines = [
+        ln
+        for ln in path.read_text(encoding="utf-8").splitlines()
+        if not any(m in ln for m in RENAME_NOTE_MARKERS)
+        and not any(a in ln for a in ALLOWED_LINE_SUBSTRINGS)
+    ]
+    bare = STALE_SCRIPT_RE.findall("\n".join(lines))
+    assert not bare, f"{path.name} still names the old script: {bare}"

{nthlayer_core-3.0.2 → nthlayer_core-4.0.0}/tests/test_deploying_doc_parity.py

@@ -109,7 +109,7 @@ def test_cli_subsection_matches_argparse() -> None:
     (plus any subparsers) so the test sees exactly what users see.
 
     Pins both *flag* parity and *subcommand-name* parity — a new top-level
-    subcommand (e.g. ``nthlayer migrate``) added to cli.py without a
+    subcommand (e.g. ``nthlayer-core migrate``) added to cli.py without a
     matching mention in the deploying.md CLI section fails this test.
     """
     section = _doc_section("### CLI")
@@ -144,7 +144,7 @@ def test_cli_subsection_matches_argparse() -> None:
 
     # Subcommand-name parity: each subcommand registered with the parser
     # must appear verbatim in the CLI section (typically inside a code
-    # block like ``nthlayer serve``). Catches "new subcommand added,
+    # block like ``nthlayer-core serve``). Catches "new subcommand added,
     # nobody updated the docs."
     missing_subcommands = {sc for sc in src_subcommands if sc not in section}
     assert not missing_subcommands, (

nthlayer_core-3.0.2/src/nthlayer_core.egg-info/entry_points.txt

@@ -1,2 +0,0 @@
-[console_scripts]
-nthlayer = nthlayer_core.cli:main