@@ -21,6 +21,12 @@ here.**
 
 ### Fixed
 
+- **Python `verify --codegen` no longer passes while checking nothing.** With no
+  `--generators` it printed a note and exited 0. Since 1.0.4 there is no default suite, so a CI
+  step written before then regenerated nothing and passed over committed output (one adopter's
+  gate covered 159 generated files this way). It now fails when `--out` holds generated files
+  and nothing is selected, and still passes when there is no generated output. The config
+  schema and the C# `verify` help no longer mention a default suite.
 - **TypeScript `meta gen` regenerates output written outside the project root.** Since 1.0.5 such
   files (a monorepo target at `../shared/src/generated`, say) are not recorded, and the next run
   REFUSED every one whose content had changed, as "no record of generating this file", though
 
@@ -112,6 +112,10 @@ The tolerant tier's all-nullable mirror is named after the value object too: `<V
 - Models come from the `entity` generator's `<Name>.py`. A value object whose short name
   another top-level object shares — a second value object, or an entity — is now
   package-qualified (`AcmeAlphaNote.py`); before, both wrote the same module.
+- A field with a `default:` is typed as its plain type with that default (`user_id: str = ""`),
+  where the copy typed it `str | None = None`. Passing `None` to it now fails validation: a
+  caller that relied on `None` must pass a value, or the field must drop its `default:` so it
+  is optional. Found upgrading an adopter, whose tests caught one such call.
 - The request model no longer sets `extra="forbid"`, so a mistyped keyword argument is ignored
   rather than rejected. The model does carry the value object's declared validators
   (`validator.*`, `@maxLength`), which the copy did not, so construction enforces them.
 
@@ -108,7 +108,7 @@ public sealed record Options
         /// <c>--codegen</c> runs, the namespace is inferred from the committed output so a
         /// regen matches output generated with any namespace (avoids spurious drift).</summary>
         public bool NamespaceExplicit { get; init; }
-        /// <summary>Optional generator selection for the <c>--codegen</c> regen (else the default suite).</summary>
+        /// <summary>Generator selection for the <c>--codegen</c> regen. There is no default suite: name the ones <c>gen</c> ran.</summary>
         public IReadOnlyList<string>? Generators { get; init; }
         /// <summary>Template root for render-helper/template generators in the codegen regen.</summary>
         public string? TemplateRoot { get; init; }
 
@@ -1612,6 +1612,32 @@ def _diff_report(
     return 1
 
 
+
+def _no_generators_selected(out_dir: str) -> int:
+    """``verify --codegen`` with nothing selected: pass only if nothing would go unchecked.
+
+    There is no default suite (1.0.4), so with no ``--generators`` nothing is regenerated.
+    If ``out_dir`` already holds generated files, reporting success would be a false green
+    — a gate written before 1.0.4, relying on the default, silently stopped checking
+    anything. That is an error; an empty or absent ``out_dir`` is not.
+    """
+    committed = [p for p in Path(out_dir).rglob("*.py") if p.name != "__init__.py"] if Path(out_dir).is_dir() else []
+    if committed:
+        print(
+            f"error: verify --codegen: no generators selected, but {out_dir} holds "
+            f"{len(committed)} generated file(s) that would go unchecked. There is no "
+            "default suite: pass --generators <a,b,c> naming the same suite `gen` ran "
+            "(metaobjects gen --list is the catalog).",
+            file=sys.stderr,
+        )
+        return 1
+    print(
+        "verify --codegen: no generators selected and no generated output to check. "
+        "Pass --generators <a,b,c> naming the same suite `gen` ran "
+        "(metaobjects gen --list is the catalog).",
+    )
+    return 0
+
 def _verify_codegen(args: argparse.Namespace) -> int:
     """``verify --codegen`` — regenerate to a temp dir + diff vs committed ``--out``.
 
@@ -1676,12 +1702,7 @@ def _verify_codegen(args: argparse.Namespace) -> int:
                 print(f"  {msg}", file=sys.stderr)
             return 1
     elif not spec_gens:
-        print(
-            "verify --codegen: no generators selected, so there is no generated output "
-            "to check. Pass --generators <a,b,c> naming the same suite `gen` ran "
-            "(metaobjects gen --list is the catalog).",
-        )
-        return 0
+        return _no_generators_selected(args.out)
 
     with tempfile.TemporaryDirectory() as tmp:
         entities = _parse_entities(getattr(args, "entities", None))
@@ -1767,12 +1788,7 @@ def _verify_codegen_neutral_fallback(args: argparse.Namespace) -> int:
     # Same rule as _verify_codegen: the selection must be named, because there is no
     # default suite to regenerate and diff against.
     if not getattr(args, "generators", None):
-        print(
-            "verify --codegen: no generators selected, so there is no generated output "
-            "to check. Pass --generators <a,b,c> naming the same suite `gen` ran "
-            "(metaobjects gen --list is the catalog).",
-        )
-        return 0
+        return _no_generators_selected(args.out)
     selection, gen_errors = _resolve_generators(
         args.generators, GeneratorBuildContext(_template_root_for(args)))
     if gen_errors:
 
@@ -38,7 +38,7 @@
           "generators": {
             "type": "array",
             "items": { "type": "string" },
-            "description": "Stable generator names (see `metaobjects gen --list`). Omit to run the default suite."
+            "description": "Stable generator names (see `metaobjects gen --list`). Required: there is no default suite, so a target that names none generates nothing and `verify --codegen` checks nothing."
           },
           "entities": {
             "type": "array",
 
@@ -495,3 +495,22 @@ def test_prompts_and_templates_root_are_the_same_flag(tmp_path: Path) -> None:
     rc = main(["verify", "--codegen", "--generators", GEN_SUITE, str(root / "meta"), "--out", str(out),
                "--prompts", str(root / "no-such-dir")])
     assert rc != 0, "--prompts value was ignored — a missing dir still regenerated the spec files"
+
+
+# `verify --codegen` with no --generators used to print a note and exit 0. Since 1.0.4
+# there is no default suite, so a CI step written before then — naming no generators
+# because the default used to be implied — regenerated nothing and passed while the
+# committed output went unchecked (found upgrading an adopter: 159 generated files, gate
+# green). With committed generated output present and nothing selected, it now fails.
+def test_verify_without_generators_fails_when_committed_output_would_go_unchecked(tmp_path: Path) -> None:
+    meta_dir = _meta_dir(tmp_path)
+    out = tmp_path / "out"
+    assert main(["gen", "--generators", GEN_SUITE, meta_dir, "--out", str(out)]) == 0
+    assert main(["verify", meta_dir, "--out", str(out)]) != 0
+
+
+def test_verify_without_generators_still_passes_with_no_generated_output(tmp_path: Path) -> None:
+    meta_dir = _meta_dir(tmp_path)
+    out = tmp_path / "out"
+    out.mkdir()
+    assert main(["verify", meta_dir, "--out", str(out)]) == 0