Docs/CI: update references to renamed Makefile targets

Author: PierreSenellart

.github/pull_request_template.md

@@ -25,7 +25,7 @@ Tick the rows that apply to this PR.
 
 **Studio (Python / JS / CSS under `studio/`)**
 
-- [ ] `make studio-test` passes locally (chains `ruff check` and runs the unit + Playwright e2e suite under `studio/tests/`)
+- [ ] `make test-studio` passes locally (chains `ruff check` and runs the unit + Playwright e2e suite under `studio/tests/`)
 - [ ] New tests for the changed behaviour live in `studio/tests/` (pytest unit) or `studio/tests/e2e/` (Playwright smoke)
 
 **Documentation (`doc/`, applies to both components)**

.github/workflows/build_and_test.yml

@@ -78,7 +78,7 @@ jobs:
       - uses: ./.github/actions/install-knowledge-compilers
       - run: make -j$(nproc) && make tdkc && make provsql_migrate_mmap && make install
       - name: KCMCP protocol conformance (tdkc)
-        run: make kcmcp-tdkc-test
+        run: make test-kcmcp
       - run: echo "shared_preload_libraries = 'provsql'" >> /etc/postgresql/${{ matrix.pg }}/test/postgresql.conf
       - run: service postgresql restart
       - run: pg_isready -t 30

.github/workflows/macos.yml

@@ -75,7 +75,7 @@ jobs:
           fetch-depth: 0
       - run: make -j$(sysctl -n hw.ncpu) && make tdkc && make provsql_migrate_mmap && make install
       - name: KCMCP protocol conformance (tdkc)
-        run: make kcmcp-tdkc-test
+        run: make test-kcmcp
       # pg_isready does a single connection attempt; the -t flag is the
       # connection timeout, not a retry duration.  When the cluster is
       # mid-startup or in recovery, pg_isready returns 1 immediately.

.github/workflows/wasm.yml

@@ -9,7 +9,7 @@ name: in-process store smoke
 #
 # The full browser/PGlite build (a matched pglite.wasm + provsql.so), its
 # headless Node smoke test, and the Playwright browser e2e are reproduced
-# locally with `make wasm` / `make playground-test` (wasm/build-wasm.sh) rather
+# locally with `make wasm` / `make test-playground` (wasm/build-wasm.sh) rather
 # than in CI: that build is heavy, was only ever opt-in (never auto-triggered),
 # and the local script is the single source of truth.
 

.github/workflows/wsl.yml

@@ -79,7 +79,7 @@ jobs:
           fetch-depth: 0
       - run: make -j$(nproc) && make tdkc && make provsql_migrate_mmap && make install
       - name: KCMCP protocol conformance (tdkc)
-        run: make kcmcp-tdkc-test
+        run: make test-kcmcp
       - run: echo "shared_preload_libraries = 'provsql'" >> /etc/postgresql/*/*/postgresql.conf
       - run: service postgresql restart
       - run: perl -i -pe 's/\r//g unless /\\set ECHO none/' test/expected/*.out

CONTRIBUTING.md

@@ -88,10 +88,10 @@ studio/.venv/bin/playwright install --with-deps chromium
 
 # Run lint + the unit suite + the Playwright e2e smoke (against the
 # extension already installed on your local PostgreSQL).
-make studio-test
+make test-studio
 ```
 
-`make studio-test` chains `ruff check .` before `pytest tests`, so
+`make test-studio` chains `ruff check .` before `pytest tests`, so
 the same lint that gates CI also gates the local target. The
 release pipeline is documented in the [build-system
 chapter](https://provsql.org/docs/dev/build-system.html#studio-releases).
@@ -142,7 +142,7 @@ checker can validate them.
      Playwright smoke under `studio/tests/e2e/` that exercises
      the changed behaviour.
 3. Ensure the relevant local test target passes: `make test` for
-   extension changes, `make studio-test` for Studio changes (or
+   extension changes, `make test-studio` for Studio changes (or
    both if the change crosses the boundary).
 4. If your change touches the documentation, run `make docs` and
    confirm the coherence checker (`check-doc-links.py`) reports

doc/source/dev/build-system.rst

@@ -12,7 +12,9 @@ ProvSQL uses two Makefiles:
 
 - ``Makefile`` (top-level) -- user-facing targets: ``make``,
   ``make test``, ``make docs``, ``make website``, ``make deploy``.
-  This file delegates to ``Makefile.internal`` for the actual build.
+  ``make help`` prints the full grouped target menu. This file
+  delegates to ``Makefile.internal`` for the actual build (a mistyped
+  target is forwarded there and errors, rather than in the wrapper).
 
 - ``Makefile.internal`` -- the real build file, based on
   PostgreSQL's **PGXS** (PostgreSQL Extension Building Infrastructure).

doc/source/dev/kc-server-protocol.rst

@@ -37,7 +37,7 @@ any server that exists today.
    the protocol; ProvSQL itself keeps tree decomposition in process rather
    than talking to it over a socket.  ``test/kcmcp/conformance.py`` drives it
    through a handshake, ``compile``/``wmc`` requests, ``PING``/``PONG``, and
-   error cases (``make kcmcp-tdkc-test``).
+   error cases (``make test-kcmcp``).
 
 
 Design goals

doc/source/dev/playground.rst

@@ -180,13 +180,13 @@ Build, test, deploy
   artifacts from ``wasm/``: the matched PGlite dist and
   ``provsql.tar.gz``). ``make playground`` reuses the in-place artifacts;
   ``make wasm`` and the first build pass ``--pglite``/``--provsql``.
-* **Test**: ``make playground-test`` runs ``studio/tests/web/``, a
+* **Test**: ``make test-playground`` runs ``studio/tests/web/``, a
   headless-Chromium Playwright suite (JSPI is on by default in current
   Chromium) driving the real frontend + Python backend against the in-page
   PGlite. It covers boot, the query → circuit → semiring path, the ``/api``
   surface, database switching, Reset, deep links, sub-path portability, and
   a fully off-line boot. The browser build and this e2e run locally only (via
-  ``make wasm`` / ``make playground-test``), not in CI; the per-PR
+  ``make wasm`` / ``make test-playground``), not in CI; the per-PR
   ``.github/workflows/wasm.yml`` job covers just the cheaper in-process-store
   single-session smoke.
 * **Deploy** with ``make deploy-playground`` (rsync to

doc/source/dev/studio.rst

@@ -408,7 +408,7 @@ not override the ``--search-path provsql_test`` we pass at
 startup) and drives the live UI through a ``chromium`` instance.
 
 Both suites live under the same ``pytest`` invocation: ``make
-studio-test`` from the repo root runs ``ruff check`` first, then
+test-studio`` from the repo root runs ``ruff check`` first, then
 ``pytest tests`` (which walks both directories). For
 finer-grained runs, ``pytest tests --ignore=tests/e2e`` skips the
 chromium tax.