no-mistakes(document): Docs for 1.1.2 agent-context and C# scoping updated; Python seam corrected

Author: dmealing

agent-context/skills/metaobjects-codegen/SKILL.md

@@ -125,7 +125,7 @@ without typechecking, so a wrong accessor runs silently.
 - **Which objects.** The runner hands you every object — entities, value objects,
   projections and abstract bases. Filter: abstract bases only contribute fields to what
   `extends` them. To scope a generator that ships with the tool to some objects, use the
-  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter()` method; the
+  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter=` argument; the
   table in `references/owning-generators.md`), never emit everything and delete files by name.
 - **Resolving accessors, always (ADR-0039).** `fields()`, `attr()`, `isRequired`,
   `resolvedIsArray()` see what a field or object inherits through `extends`; the `own*()`

agent-context/skills/metaobjects-codegen/references/owning-generators.md

@@ -51,7 +51,7 @@ adopt the surface you decided against.
 |---|---|
 | **TypeScript** | the generator's `filter: (obj) => boolean` |
 | **C#** | `new EntityGenerator { Include = o => ... }` on the entry in `codegen/Generators.cs` (also on `db-context`, `routes`, `filter-allowlist`, `names`, `callable`); for any other generator, wrap it and hand it a narrowed `GenContext` (`ctx.Narrow(...)`), or eject and edit. `references/csharp.md`, "Scoping a generator to some objects". Never emit everything and delete files by name afterwards |
-| **Python** | the owned generator's `filter(self, obj)` method |
+| **Python** | the `filter=` argument on the generator factory (a callable of the object), e.g. `trace_helper_generator(filter=...)` |
 | **Java / Kotlin** | the entry's `<args>` in the pom where the generator offers one; otherwise `mvn metaobjects:eject` the generator and edit its object selection |
 
 Every port gets a reference generator's source the same way — its `eject` command — and

fixtures/agent-context-conformance/java-kotlin-react-tanstack/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -125,7 +125,7 @@ without typechecking, so a wrong accessor runs silently.
 - **Which objects.** The runner hands you every object — entities, value objects,
   projections and abstract bases. Filter: abstract bases only contribute fields to what
   `extends` them. To scope a generator that ships with the tool to some objects, use the
-  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter()` method; the
+  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter=` argument; the
   table in `references/owning-generators.md`), never emit everything and delete files by name.
 - **Resolving accessors, always (ADR-0039).** `fields()`, `attr()`, `isRequired`,
   `resolvedIsArray()` see what a field or object inherits through `extends`; the `own*()`

fixtures/agent-context-conformance/java-kotlin-react-tanstack/expected/.claude/skills/metaobjects-codegen/references/owning-generators.md

@@ -51,7 +51,7 @@ adopt the surface you decided against.
 |---|---|
 | **TypeScript** | the generator's `filter: (obj) => boolean` |
 | **C#** | `new EntityGenerator { Include = o => ... }` on the entry in `codegen/Generators.cs` (also on `db-context`, `routes`, `filter-allowlist`, `names`, `callable`); for any other generator, wrap it and hand it a narrowed `GenContext` (`ctx.Narrow(...)`), or eject and edit. `references/csharp.md`, "Scoping a generator to some objects". Never emit everything and delete files by name afterwards |
-| **Python** | the owned generator's `filter(self, obj)` method |
+| **Python** | the `filter=` argument on the generator factory (a callable of the object), e.g. `trace_helper_generator(filter=...)` |
 | **Java / Kotlin** | the entry's `<args>` in the pom where the generator offers one; otherwise `mvn metaobjects:eject` the generator and edit its object selection |
 
 Every port gets a reference generator's source the same way — its `eject` command — and

fixtures/agent-context-conformance/java-react/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -125,7 +125,7 @@ without typechecking, so a wrong accessor runs silently.
 - **Which objects.** The runner hands you every object — entities, value objects,
   projections and abstract bases. Filter: abstract bases only contribute fields to what
   `extends` them. To scope a generator that ships with the tool to some objects, use the
-  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter()` method; the
+  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter=` argument; the
   table in `references/owning-generators.md`), never emit everything and delete files by name.
 - **Resolving accessors, always (ADR-0039).** `fields()`, `attr()`, `isRequired`,
   `resolvedIsArray()` see what a field or object inherits through `extends`; the `own*()`

fixtures/agent-context-conformance/java-react/expected/.claude/skills/metaobjects-codegen/references/owning-generators.md

@@ -51,7 +51,7 @@ adopt the surface you decided against.
 |---|---|
 | **TypeScript** | the generator's `filter: (obj) => boolean` |
 | **C#** | `new EntityGenerator { Include = o => ... }` on the entry in `codegen/Generators.cs` (also on `db-context`, `routes`, `filter-allowlist`, `names`, `callable`); for any other generator, wrap it and hand it a narrowed `GenContext` (`ctx.Narrow(...)`), or eject and edit. `references/csharp.md`, "Scoping a generator to some objects". Never emit everything and delete files by name afterwards |
-| **Python** | the owned generator's `filter(self, obj)` method |
+| **Python** | the `filter=` argument on the generator factory (a callable of the object), e.g. `trace_helper_generator(filter=...)` |
 | **Java / Kotlin** | the entry's `<args>` in the pom where the generator offers one; otherwise `mvn metaobjects:eject` the generator and edit its object selection |
 
 Every port gets a reference generator's source the same way — its `eject` command — and

fixtures/agent-context-conformance/python/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -125,7 +125,7 @@ without typechecking, so a wrong accessor runs silently.
 - **Which objects.** The runner hands you every object — entities, value objects,
   projections and abstract bases. Filter: abstract bases only contribute fields to what
   `extends` them. To scope a generator that ships with the tool to some objects, use the
-  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter()` method; the
+  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter=` argument; the
   table in `references/owning-generators.md`), never emit everything and delete files by name.
 - **Resolving accessors, always (ADR-0039).** `fields()`, `attr()`, `isRequired`,
   `resolvedIsArray()` see what a field or object inherits through `extends`; the `own*()`

fixtures/agent-context-conformance/python/expected/.claude/skills/metaobjects-codegen/references/owning-generators.md

@@ -51,7 +51,7 @@ adopt the surface you decided against.
 |---|---|
 | **TypeScript** | the generator's `filter: (obj) => boolean` |
 | **C#** | `new EntityGenerator { Include = o => ... }` on the entry in `codegen/Generators.cs` (also on `db-context`, `routes`, `filter-allowlist`, `names`, `callable`); for any other generator, wrap it and hand it a narrowed `GenContext` (`ctx.Narrow(...)`), or eject and edit. `references/csharp.md`, "Scoping a generator to some objects". Never emit everything and delete files by name afterwards |
-| **Python** | the owned generator's `filter(self, obj)` method |
+| **Python** | the `filter=` argument on the generator factory (a callable of the object), e.g. `trace_helper_generator(filter=...)` |
 | **Java / Kotlin** | the entry's `<args>` in the pom where the generator offers one; otherwise `mvn metaobjects:eject` the generator and edit its object selection |
 
 Every port gets a reference generator's source the same way — its `eject` command — and

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-codegen/SKILL.md

@@ -125,7 +125,7 @@ without typechecking, so a wrong accessor runs silently.
 - **Which objects.** The runner hands you every object — entities, value objects,
   projections and abstract bases. Filter: abstract bases only contribute fields to what
   `extends` them. To scope a generator that ships with the tool to some objects, use the
-  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter()` method; the
+  port's own idiom (a TypeScript `filter`, a C# `Include`, a Python `filter=` argument; the
   table in `references/owning-generators.md`), never emit everything and delete files by name.
 - **Resolving accessors, always (ADR-0039).** `fields()`, `attr()`, `isRequired`,
   `resolvedIsArray()` see what a field or object inherits through `extends`; the `own*()`

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-codegen/references/owning-generators.md

@@ -51,7 +51,7 @@ adopt the surface you decided against.
 |---|---|
 | **TypeScript** | the generator's `filter: (obj) => boolean` |
 | **C#** | `new EntityGenerator { Include = o => ... }` on the entry in `codegen/Generators.cs` (also on `db-context`, `routes`, `filter-allowlist`, `names`, `callable`); for any other generator, wrap it and hand it a narrowed `GenContext` (`ctx.Narrow(...)`), or eject and edit. `references/csharp.md`, "Scoping a generator to some objects". Never emit everything and delete files by name afterwards |
-| **Python** | the owned generator's `filter(self, obj)` method |
+| **Python** | the `filter=` argument on the generator factory (a callable of the object), e.g. `trace_helper_generator(filter=...)` |
 | **Java / Kotlin** | the entry's `<args>` in the pom where the generator offers one; otherwise `mvn metaobjects:eject` the generator and edit its object selection |
 
 Every port gets a reference generator's source the same way — its `eject` command — and