no-mistakes(document): Document @collectionName implementedIn and pluralizer

Author: dmealing

docs/CONFORMANCE.md

@@ -148,6 +148,9 @@ canonical (`fixtures/registry-conformance/expected-registry.json`).
   - `view.image`, and its `@accept`, `@aspectRatio`, `@maxBytes`, `@maxEdge`, `@store`
 - *Implemented in Java only* (`implementedIn: ["java"]`): `object.* @object` (ADR-0001), the
   native class an object binds to. Java's runtime acts on it; Java's own behaviour is unchanged.
+- *Implemented in C# only* (`implementedIn: ["csharp"]`): `object.* @collectionName`, the
+  collection name the generated DbSet takes. Every port registers it and reads the `naming.collections`
+  key that names the default pluralizer; C# codegen does not apply that pluralizer yet.
 - *Loads strictly in every port.* Each port registers the `metaobjects-ui-web` provider
   (`view.textarea @rows`, the `view.image` attrs) and `@object` / `@objectAdapter` on
   `object.*`, loads all three fixtures strictly, and emits `implementedIn` in its manifest, which

docs/features/migrations/physical-naming.md

@@ -62,9 +62,10 @@ and is `pascal` otherwise:
 
 Table rules register the same way (`namingStrategies.tables`, `RegisterTables`, `registerTables`,
 `register_table_naming_rule`) and name a source with no physical name; the entity-name fallback
-is still made plural after the rule. Pluralizers register the same way (`registerPluralizer`, `RegisterPluralizer`,
-`registerPluralizer`, `register_pluralizer`): an object name in, in its declared casing, its
-collection name out. `standard` is the cross-port plural and `none` keeps the name as it is. A built-in name cannot be replaced. Register the same
+is still made plural after the rule. Pluralizers register the same way (`registerPluralizer`,
+`RegisterPluralizer`, `registerPluralizer`, `register_pluralizer`): an object name in, in its
+declared casing, its collection name out. `standard` is the cross-port plural and `none` keeps the
+name as it is. A built-in name cannot be replaced. Register the same
 strategy in every port that reads the database, because each port resolves the names itself.
 Every port looks a strategy up by name each time it applies one, so registering again under the
 same name replaces it for everything that runs afterwards. A test that registers its own calls

fixtures/registry-conformance/README.md

@@ -257,7 +257,8 @@ still fails everywhere.
   generic `view.*` controls (`checkbox`, `date`, `dropdown`, `hidden`, `hotlink`, `image`,
   `month`, `number`, `password`, `radio`, `text`, `textarea`, `web`) and their attrs
   (`view.textarea @rows`, `view.image @accept/@aspectRatio/@maxBytes/@maxEdge/@store`) are
-  `["typescript"]`; `object.* @object` (ADR-0001) is `["java"]`. They used to be carved out
+  `["typescript"]`; `object.* @object` (ADR-0001) is `["java"]`; `object.* @collectionName` is
+  `["csharp"]`. They used to be carved out
   as `PRESENTATION_ONLY` / `NATIVE_BINDING`; both reasons are retired. The parity gaps are
   listed in `docs/CONFORMANCE.md`, "Split coverage".
 - **Kind 2 — language-specific by nature.** The attr carries `"ports": [...]`: