fix(agent-context): the audit checklist carried the same JVM-only clause, a fourth time

`67b1937e0` corrected three surfaces that said the names generator is opt-in only on the
JVM. `references/capability-checklist.md` is the fourth and was missed: "on the JVM an
un-wired names generator is the finding first" — which reads, to an agent auditing a
TypeScript estate, as confirmation that there is nothing to check.

Same correction: on TypeScript and the JVM the generator list in the config IS the
complete list, so an existing project emits no names artifact and the un-wired generator
is the finding FIRST. C# and Python have a real default suite and get it by upgrading.

Regenerated the five conformance mirrors.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01At3v6M6uqECZ2Sb5eUv6YY

Author: dmealing

agent-context/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when

fixtures/agent-context-conformance/java-kotlin-react-tanstack/expected/.claude/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when

fixtures/agent-context-conformance/java-react/expected/.claude/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when

fixtures/agent-context-conformance/python/expected/.claude/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when

fixtures/agent-context-conformance/ts-react-tanstack/expected/.claude/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when

fixtures/agent-context-conformance/ts-requirements/expected/.claude/skills/metaobjects-audit/references/capability-checklist.md

@@ -70,8 +70,11 @@ classify it (using the classification scheme in `SKILL.md`) and route the cutove
   name spelled as a literal outside its declaration — raw SQL, a hand-written repository, a
   migration script, a body-to-column map (drift signature 11). Every port emits a per-object
   names artifact from the declaration, so a literal is a second source of truth even when it
-  agrees with the naming strategy today. A typed ORM handle in its place is correct; on the
-  JVM an un-wired names generator is the finding first.
+  agrees with the naming strategy today. A typed ORM handle in its place is correct. **Check
+  the artifact is emitted at all before scoring the literals: on TypeScript and the JVM the
+  generator list in the config IS the complete list, so an existing project emits none and the
+  un-wired generator is the finding FIRST** (C# and Python have a real default suite and get it
+  by upgrading).
 - **`@kind` = `view` / `materializedView`** — hunt hand-written SQL views where an authored
   read-only source belongs. Apply the **view-necessity test** (SKILL.md, drift signature 8): a
   hand-written `CREATE VIEW` (or read-only SQL mirroring a read model) is a CODEGEN CANDIDATE when