django-spec-cli 0.4.0__tar.gz → 0.5.0__tar.gz

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/.github/workflows/release.yml

@@ -31,7 +31,7 @@ jobs:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
         with:
           fetch-depth: 0
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
       - name: Install

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/.github/workflows/tests.yml

@@ -20,7 +20,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
       - name: Install
@@ -37,7 +37,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
       - name: Install with docs group
@@ -54,7 +54,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
       # A floor is a claim about the *oldest* version that works, and a lockfile
@@ -171,7 +171,7 @@ jobs:
 
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: true
       - name: Install Python ${{ matrix.python-version }}

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/.github/workflows/upstream-drift.yml

@@ -43,14 +43,14 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
-      - uses: astral-sh/setup-uv@1c37ad07a6a961277cf70c0d37d6f313000f5884 # v10.3.0
+      - uses: astral-sh/setup-uv@07a047e608db84b3d8c06cd9a7c7dcc9c355c18e # v10.3.2
         with:
           enable-cache: false
 
       # One cell, not the matrix. The matrix answers "does this combination
       # work"; this answers "has an upstream moved under us", and the newest
       # supported Python is where a new release lands first.
-      - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7.0.0
+      - uses: actions/setup-python@6d4fd22b20465ccc0f7354476588e8df7c9ca0e0 # v7.1.0
         with:
           python-version: "3.14"
 

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/CHANGELOG.md

@@ -7,6 +7,37 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
+## [0.5.0] — 2026-11-08
+
+### Added
+- **A run stamps its transport: `"cli"`.** Every callable a `SpecCommand` run
+  reaches is now handed a `call_context` built by the kernel's
+  `build_call_context` and stamped last with `"cli"`, exported as
+  `CLI_TRANSPORT`, so a permission check, the Validator, a provider, the
+  service and the presenter read `call_transport(call_context) == "cli"` from
+  one dict. Before, the command handed `dispatch` none, and a callable reading
+  the key saw a missing one, which the kernel reads as an in-process caller.
+  The Validator's declaration the command reads for the options it parses is
+  asked under the stamped dict as well. `request`, `view`, `format` and
+  `action` are in the dict as `None`, which binds nothing different from a
+  missing key. The command line page says what a callable reads here.
+
+### Changed
+- **The floor on `django-service-specs` rises from 0.25.0 to 0.29.0**, the
+  release that adds `build_call_context` and removes the shared `Transport`
+  enum. A project on an older kernel stays on 0.4.x.
+
+## [0.4.1] — 2026-11-04
+
+### Added
+- **The command line page shows a spec the kernel refuses.** Its system-check
+  section now includes an example command, `drafts`, serving one spec that
+  declares a plain `Parameter` over a keyword with no default, and prints the
+  `django_spec_cli.W004` sentence it gets. The page's tests assert that
+  `manage.py check` reports exactly that warning for the example and that a
+  run of the spec raises the same sentence, so the page cannot drift from
+  what the check and the command say. No change to the package.
+
 ## [0.4.0] — 2026-11-04
 
 ### Added
@@ -124,7 +155,9 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
   `django-service-specs>=0.10.0`, the first kernel release with every name the
   command reads at its root.
 
-[Unreleased]: https://github.com/Artui/django-spec-cli/compare/v0.4.0...HEAD
+[Unreleased]: https://github.com/Artui/django-spec-cli/compare/v0.5.0...HEAD
+[0.5.0]: https://github.com/Artui/django-spec-cli/compare/v0.4.1...v0.5.0
+[0.4.1]: https://github.com/Artui/django-spec-cli/compare/v0.4.0...v0.4.1
 [0.4.0]: https://github.com/Artui/django-spec-cli/compare/v0.3.1...v0.4.0
 [0.3.1]: https://github.com/Artui/django-spec-cli/compare/v0.3.0...v0.3.1
 [0.3.0]: https://github.com/Artui/django-spec-cli/compare/v0.2.1...v0.3.0

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/CLAUDE.md

@@ -139,7 +139,7 @@ configured and enforced. isort order is stdlib, third party, first party.
 | --- | --- | --- |
 | Python | 3.10 | 3.10 through 3.14 |
 | Django | 4.2 | 4.2, 5.0, 5.1, 5.2, 6.0, 6.1 |
-| django-service-specs | 0.25.0 | the newest release, and the floor in the `floor` job |
+| django-service-specs | 0.29.0 | the newest release, and the floor in the `floor` job |
 
 The Python and Django floors are the kernel's, and cannot sit below them.
 

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: django-spec-cli
-Version: 0.4.0
+Version: 0.5.0
 Summary: Run a django-service-specs registry from manage.py: one subcommand per spec, options generated from its parameters, exit codes for every refusal.
 Project-URL: Homepage, https://github.com/Artui/django-spec-cli
 Project-URL: Repository, https://github.com/Artui/django-spec-cli
@@ -30,7 +30,7 @@ Classifier: Programming Language :: Python :: 3.13
 Classifier: Programming Language :: Python :: 3.14
 Classifier: Topic :: Software Development :: Libraries :: Python Modules
 Requires-Python: >=3.10
-Requires-Dist: django-service-specs>=0.25.0
+Requires-Dist: django-service-specs>=0.29.0
 Requires-Dist: django>=4.2
 Description-Content-Type: text/markdown
 
@@ -61,7 +61,7 @@ the import path, the system check ids and the setting key are this package's.
 pip install django-spec-cli
 ```
 
-Python 3.10 or later, Django 4.2 or later, and `django-service-specs` 0.25.0 or
+Python 3.10 or later, Django 4.2 or later, and `django-service-specs` 0.29.0 or
 later, which it installs.
 
 ## Quickstart

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/README.md

@@ -25,7 +25,7 @@ the import path, the system check ids and the setting key are this package's.
 pip install django-spec-cli
 ```
 
-Python 3.10 or later, Django 4.2 or later, and `django-service-specs` 0.25.0 or
+Python 3.10 or later, Django 4.2 or later, and `django-service-specs` 0.29.0 or
 later, which it installs.
 
 ## Quickstart

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/django_spec_cli/__init__.py

@@ -11,11 +11,13 @@ from django_spec_cli.render.render_table import render_table
 from django_spec_cli.render.wants_table import wants_table
 from django_spec_cli.report.unguarded_message import unguarded_message
 from django_spec_cli.spec_command import SpecCommand
+from django_spec_cli.types.cli_transport import CLI_TRANSPORT
 from django_spec_cli.types.exit_code import ExitCode
 from django_spec_cli.version import __version__
 
 __all__ = [
     "__version__",
+    "CLI_TRANSPORT",
     "ExitCode",
     "ParameterDescriptor",
     "SpecCommand",

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/django_spec_cli/spec_command.py

@@ -26,6 +26,7 @@ from django_service_specs import (
     ServiceSpec,
     ServiceValidationError,
     SpecRegistry,
+    build_call_context,
     check_seeds,
     coerce_flat,
     dispatch,
@@ -46,6 +47,7 @@ from django_spec_cli.render.render_result import render_result
 from django_spec_cli.render.wants_table import wants_table
 from django_spec_cli.report.unguarded_message import unguarded_message
 from django_spec_cli.report.utils import refused_message
+from django_spec_cli.types.cli_transport import CLI_TRANSPORT
 from django_spec_cli.types.exit_code import ExitCode
 
 _OWN_OPTIONS = frozenset({"--as-user", "--json", "--table"})
@@ -173,7 +175,7 @@ class SpecCommand(BaseCommand):
                 )
             self._entries[name] = entry
             spec = kernel_spec(entry.spec)
-            parameters = _sendable(spec, self.pool_seeds)
+            parameters = _sendable(spec, self.pool_seeds, _call_context())
             summary = _summary(spec, entry.name)
             subparser = subparsers.add_parser(
                 name,
@@ -256,7 +258,11 @@ class SpecCommand(BaseCommand):
                 refused_message(entry.name, self._command_label, error)
             ) from error
         spec = kernel_spec(entry.spec)
-        parameters = spec.parameters()
+        # One dict for the whole run, built ahead of the first callable it
+        # asks: the declaration read here, then every stage ``dispatch`` runs,
+        # so a callable reading ``transport`` sees ``cli`` from either.
+        call_context = _call_context()
+        parameters = spec.parameters(call_context=call_context)
         raw = parsed_arguments(argparse.Namespace(**options), parameters)
         # Read before the run, not after it: a setting that names no format
         # raises, and raising once a write has committed reports a failure for
@@ -282,6 +288,7 @@ class SpecCommand(BaseCommand):
                 principal=principal,
                 arguments=coerce_flat(parameters, raw),
                 pool_seeds=self.pool_seeds,
+                call_context=call_context,
             )
         except (DispatchError, ServiceError) as error:
             raise CommandError(_message(error), returncode=int(exit_code_for(error))) from error
@@ -304,7 +311,20 @@ class SpecCommand(BaseCommand):
             self.stdout.write(unguarded_message(unguarded, label))
 
 
-def _sendable(spec: ServiceSpec | SelectorSpec, pool_seeds: PoolSeeds) -> Parameters:
+def _call_context() -> dict[str, Any]:
+    """A new context for the command's own reads and one run, stamped ``cli``.
+
+    ``request`` and ``view`` are there as ``None``, since a command line has
+    neither: the kernel hands a callable declaring either ``None`` for a
+    ``None`` entry exactly as for a missing one, so no binding changes.
+    ``format`` and ``action`` are no pool names and are never bound.
+    """
+    return build_call_context(CLI_TRANSPORT)
+
+
+def _sendable(
+    spec: ServiceSpec | SelectorSpec, pool_seeds: PoolSeeds, call_context: dict[str, Any]
+) -> Parameters:
     """What a caller may send, as the kernel's caller schema reads it: required only where dispatch demands it.
 
     The parameters ``spec_caller_input_schema`` offers under the command's
@@ -327,7 +347,7 @@ def _sendable(spec: ServiceSpec | SelectorSpec, pool_seeds: PoolSeeds) -> Parame
     return Parameters.of(
         *(
             param if param.name in required else replace(param, required=False)
-            for param in spec.parameters()
+            for param in spec.parameters(call_context=call_context)
             if param.name in schema["properties"]
         )
     )

django_spec_cli-0.5.0/django_spec_cli/types/__init__.py

@@ -0,0 +1,9 @@
+"""Value types: the exit status a command's run ends with, and the transport name it stamps."""
+
+from django_spec_cli.types.cli_transport import CLI_TRANSPORT
+from django_spec_cli.types.exit_code import ExitCode
+
+__all__ = [
+    "CLI_TRANSPORT",
+    "ExitCode",
+]

django_spec_cli-0.5.0/django_spec_cli/types/cli_transport.py

@@ -0,0 +1,13 @@
+"""``CLI_TRANSPORT`` - the transport name a ``SpecCommand`` stamps on every call's context."""
+
+from __future__ import annotations
+
+from typing import Final
+
+CLI_TRANSPORT: Final = "cli"
+"""What a ``SpecCommand`` stamps under the kernel's ``TRANSPORT_KEY``: the plain string ``"cli"``.
+
+A callable reads it with the kernel's ``call_transport``, or compares
+``call_context["transport"] == "cli"`` with nothing imported. This package owns
+the string and the kernel lists no transports; it is a public contract, so it
+never changes."""

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/django_spec_cli/version.py

@@ -2,6 +2,6 @@
 
 from __future__ import annotations
 
-__version__: str = "0.4.0"
+__version__: str = "0.5.0"
 
 __all__ = ["__version__"]

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/docs/examples/commands.py

@@ -1,4 +1,6 @@
-"""A registry served as a management command, and a command that looks its user up by username.
+"""A registry served as a management command, a command that looks its user up by username, a
+command whose service reads the transport it is called over, and a command serving a spec the
+kernel refuses as declared.
 
 ``tests/docs/test_commands_examples.py`` runs every command line
 ``docs/index.md`` shows through this module's ``Command``, from argv as
@@ -30,6 +32,7 @@ from django_service_specs import (
     ServiceSpec,
     SpecRegistry,
     Unrestricted,
+    call_transport,
 )
 
 from django_spec_cli import SpecCommand
@@ -137,3 +140,49 @@ class ByUsername(SpecCommand):
 
 
 # --8<-- [end:by_username]
+
+
+# --8<-- [start:refused]
+def retitle(*, title: str) -> str:
+    return title
+
+
+drafts = SpecRegistry()
+drafts.register(
+    "retitle",
+    ServiceSpec(
+        service=retitle,
+        permissions=[IsSignedIn()],
+        # Optional, as a Parameter is unless it says otherwise, over a keyword
+        # with no default: a call leaving it out could not run, so the kernel's
+        # check_seeds refuses the spec, and manage.py check reports it as
+        # django_spec_cli.W004.
+        reads=Parameters.of(Parameter("title", "string")),
+    ),
+)
+
+
+# yourapp/management/commands/drafts.py
+class Drafts(SpecCommand):
+    registry = drafts
+
+
+# --8<-- [end:refused]
+
+
+# --8<-- [start:transport]
+def where(*, call_context: Any) -> str:
+    """The transport this call came over, as its context says."""
+    return call_transport(call_context) or "in-process"
+
+
+where_registry = SpecRegistry()
+where_registry.register("where", ServiceSpec(service=where, permissions=[IsSignedIn()]))
+
+
+# yourapp/management/commands/where.py
+class Where(SpecCommand):
+    registry = where_registry
+
+
+# --8<-- [end:transport]

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/docs/index.md

@@ -27,7 +27,7 @@ pip install django-spec-cli
 ```
 
 It installs [`django-service-specs`](https://artui.github.io/django-service-specs/), the kernel whose specs it serves,
-from 0.25.0, on Python 3.10 and Django 4.2 or later. The command line was the
+from 0.29.0, on Python 3.10 and Django 4.2 or later. The command line was the
 kernel's `commands/` subpackage, and moved here so the kernel carries no
 transport.
 
@@ -264,6 +264,23 @@ with the same sentence, raised as `ImproperlyConfigured` (exit code 1,
 with a traceback) before `--as-user` is looked up, even when the options sent
 would let it run. The command's other specs are unaffected.
 
+A `Parameter` is optional unless it says `required=True`, so a read declared
+plainly over a keyword with no default is one such declaration:
+
+```python
+--8<--
+docs/examples/commands.py:refused
+--8<--
+```
+
+`manage.py check` reports it as `django_spec_cli.W004`, and
+`manage.py drafts retitle --as-user 1 --title Final` is refused with the same
+sentence:
+
+```text
+'retitle' in manage.py drafts cannot run as declared, and a run of it is refused: ServiceSpec.service requires the keyword(s) ['title'], declared as optional reads that nothing else fills, so a call leaving one out is refused as missing. Declare the read required, or give the keyword a default.
+```
+
 All three are warnings, so a spec nobody runs never stops `migrate`, and
 `SILENCED_SYSTEM_CHECKS` silences one by id. Silencing `W004` hides the report
 and does not let the spec run.
@@ -275,10 +292,50 @@ listing only `"django_service_specs"` gets no check for a command. List
 A `SpecCommand` keeps Django's system checks on, so on the command line the
 report is printed to stderr before every run of every command. The runs on
 this page are shown without it; in a project listing the app, each would be
-preceded by the warning for `whoami`. `call_command` skips
+preceded by the warnings for `whoami` and `retitle`. `call_command` skips
 system checks for every command but `check`, so a command run through it
 does not print them.
 
+## What a callable reads here
+
+Every callable a run reaches is handed one `call_context`, built by the
+kernel's
+[`build_call_context`][django_service_specs.types.build_call_context.build_call_context]
+and stamped last with this package's transport name, the plain string `"cli"`,
+exported as `django_spec_cli.CLI_TRANSPORT`. Read it with the kernel's
+[`call_transport`][django_service_specs.types.call_transport.call_transport],
+or compare `call_context["transport"] == "cli"` with nothing imported:
+
+```python
+--8<--
+docs/examples/commands.py:transport
+--8<--
+```
+
+- **One dict per run.** The command builds it ahead of everything it asks of
+  a spec and hands the same object to the declaration it reads for the
+  options it parses, then to `dispatch`, so a permission check, the
+  Validator's `parameters()` and `validate()`, a provider, the service and the
+  presenter all read `"cli"` from one dict.
+- **The standard entries are there as `None`.** `request`, `view`, `format`
+  and `action` are keys of the dict with no value, since a command line has
+  none. The kernel hands a callable declaring `request` or `view` `None` for
+  such an entry, as it does for a missing one, and `format` and `action` are
+  never bound by name, so a spec written for HTTP runs here as it did.
+- **`--help` is read under a dict too.** The command builds a stamped dict of
+  its own for each spec to describe a Validator's fields for the parser. The
+  kernel's schema and seed checks that decide which options are offered are
+  asked outside a call, as they are by every transport, and read no stamp. So
+  the option names come from a transport-blind declaration: a field a
+  Validator declares only when `call_transport(call_context) == "cli"` is
+  never offered, and if it is required, every run is refused for it.
+  Declare such a field for every transport, or not at all.
+- **Seams.** The value is not configurable: a subclass cannot change what a
+  run stamps. What a subclass can supply is `resolve_as_user`, who the run is
+  made as, and `pool_seeds`, which adds a keyword to the pool every callable
+  may declare, so an entry a project needs in every call is a seed rather
+  than a key of the dict.
+
 ## What it does not do
 
 - **No payload file.** Arguments are options; an object or a list of rows has

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/docs/reference.md

@@ -60,3 +60,4 @@ Registered by `DjangoSpecCliConfig`, so a project gets them by listing
 ## Types
 
 ::: django_spec_cli.types.exit_code.ExitCode
+::: django_spec_cli.types.cli_transport.CLI_TRANSPORT

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/pyproject.toml

@@ -48,8 +48,9 @@ dependencies = [
     # ``PermissionCheckDenied`` in ``REFUSALS``, which
     # ``tests/test_exit_code_for.py`` decides by name. Below 0.11.0 the kernel
     # also still shipped its own copy of the command and registered its own
-    # ``W001`` and ``W003``.
-    "django-service-specs>=0.25.0",
+    # ``W001`` and ``W003``. 0.29.0 adds ``build_call_context``, which the
+    # command builds the context it stamps ``cli`` on through.
+    "django-service-specs>=0.29.0",
 ]
 
 [project.urls]
@@ -149,7 +150,7 @@ skip-magic-trailing-comma = false
 root = ["./django_spec_cli"]
 
 [tool.bumpversion]
-current_version = "0.4.0"
+current_version = "0.5.0"
 allow_dirty = false
 commit = false
 tag = false

{django_spec_cli-0.4.0 → django_spec_cli-0.5.0}/tests/docs/test_commands_examples.py

@@ -7,6 +7,10 @@
 shows them - must be the lines printed under it, and its exit status the
 number an ``echo $?`` after it shows. So the page cannot show an option, an
 output or an exit code the command does not have.
+
+The sentence the page prints for the example's ``Drafts``, whose spec the
+kernel refuses, must be the ``django_spec_cli.W004`` the system check reports
+and the refusal a run of the spec raises.
 """
 
 from __future__ import annotations
@@ -18,10 +22,13 @@ from pathlib import Path
 from typing import Any
 
 import pytest
+from django.core.checks import Warning
+from django.core.exceptions import ImproperlyConfigured
 from django.core.management import call_command
 from django.core.management.base import CommandError
 from django_service_specs import UnguardedReason, UnguardedSpec
 
+from django_spec_cli.checks import check_unguarded_specs
 from django_spec_cli.report.unguarded_message import unguarded_message
 from docs.examples import commands
 from tests.dispatch_app.models import Note
@@ -30,6 +37,7 @@ pytestmark = [pytest.mark.django_db, pytest.mark.usefixtures("keep_the_test_conn
 
 PAGE = Path(__file__).resolve().parents[2] / "docs" / "index.md"
 PROMPT = "$ python manage.py notes "
+RETITLE_ARGV = "retitle --as-user 1 --title Final"
 
 
 def _runs() -> list[tuple[str, list[str], int]]:
@@ -112,7 +120,62 @@ def test_the_username_lookup_runs_as_the_user_it_names() -> None:
     assert (caught.value.returncode, str(caught.value)) == (5, "No user named 'nobody'.")
 
 
+def _refused_line() -> str:
+    """The line the page prints for the W004 example: the one opening with its spec and command.
+
+    Found by that opening rather than by its block, so another ``text`` block
+    on the page leaves it alone, and a page no longer printing it fails here.
+    """
+    (line,) = [
+        line
+        for line in PAGE.read_text().splitlines()
+        if line.startswith("'retitle' in manage.py drafts ")
+    ]
+    return line
+
+
+def test_the_refused_spec_is_reported_as_w004_with_the_page_s_sentence(
+    monkeypatch: pytest.MonkeyPatch,
+) -> None:
+    # The examples are no installed app, so the walk is pointed at the one
+    # command; it would otherwise never load it, and no other test's check
+    # sees this command.
+    monkeypatch.setattr("django_spec_cli.checks.get_commands", lambda: {"drafts": "yourapp"})
+    monkeypatch.setattr(
+        "django_spec_cli.checks.load_command_class", lambda app_name, name: commands.Drafts()
+    )
+    assert check_unguarded_specs(None) == [
+        Warning(
+            _refused_line(),
+            hint=(
+                "Change the declaration as the message says. Until then a run of the spec "
+                "is refused, whether or not django_spec_cli.W004 is silenced."
+            ),
+            obj=commands.Drafts,
+            id="django_spec_cli.W004",
+        )
+    ]
+
+
+@pytest.mark.usefixtures("world")
+def test_a_run_of_the_refused_spec_raises_the_page_s_sentence() -> None:
+    # The run the page names, which sends every option the spec declares, and
+    # is still refused.
+    assert f"`manage.py drafts {RETITLE_ARGV}`" in PAGE.read_text()
+    command = commands.Drafts()
+    with pytest.raises(ImproperlyConfigured) as caught:
+        command.run_from_argv(["manage.py", "drafts", "--skip-checks", *shlex.split(RETITLE_ARGV)])
+    assert str(caught.value) == _refused_line()
+
+
 @pytest.mark.usefixtures("world")
 def test_whoami_is_the_user_named(capsys: pytest.CaptureFixture[str]) -> None:
     assert _run_from_argv("whoami --as-user 1") == 0
     assert capsys.readouterr().out == '"ada"\n'
+
+
+@pytest.mark.usefixtures("world")
+def test_the_transport_example_reads_cli() -> None:
+    out = io.StringIO()
+    call_command(commands.Where(), "where", "--as-user", "1", stdout=out)
+    assert out.getvalue() == '"cli"\n'