no-mistakes(document): Docs: publish requirements opt-in, inherit key in port pages

Author: dmealing

docs/ports/csharp.md

@@ -114,7 +114,8 @@ A model published from another repository is declared under `dependencies` in
 reads both, at every rung of the source ladder, and never writes them: a snapshot that no longer
 matches the lock fails with `ERR_DEPENDENCY_SNAPSHOT_STALE`. The snapshot loads first, so your
 own metadata can `extends`, overlay or reference its nodes, but an imported node is not generated
-(and is not counted by the requirement gate) unless `scope.include` names its package. What C#
+unless `scope.include` names its package, and an imported requirement is not counted by the
+requirement gate unless `requirements.inherit` names it. What C#
 does and does not do is in
 [Metadata dependencies](../features/metadata-dependencies.md).
 
@@ -305,7 +306,8 @@ new SharedModelGenerator
 `<Version>` (from the project file, else the nearest `Directory.Build.props`). It writes nothing and
 names the option to change when the selection is empty, is not closed over `extends` and reference
 attributes, or needs vocabulary outside the library's. Give `OutDir` a directory that holds nothing
-else. `requirement.*` and `template.*` nodes are never published. `dotnet meta eject shared-model`
+else. `requirement.*` nodes are published only when `Requirements` is set (`requirements: true`, default
+off); `template.*` nodes are never published. `dotnet meta eject shared-model`
 copies the generator into your project; the artifact bytes stay in the package, because a copy that
 changed them would publish a model a consumer's sync refuses. The consumer runs the Node `meta deps
 sync`, which stays the only writer of the lock and the snapshot.

docs/ports/java.md

@@ -202,7 +202,8 @@ directory). `meta deps sync` (Node) is the only writer of the snapshot and `deps
 the Maven build reads them offline and refuses a stale or hand-edited snapshot with
 `ERR_DEPENDENCY_SNAPSHOT_STALE`. Your own entities can `extends` and reference the imported
 ones; the generators emit nothing for an imported object unless `scope.include` names its
-package, and a new top-level node declared into a package a dependency owns fails with
+package, an imported requirement counts toward the gate only when `requirements.inherit` names
+its package, and a new top-level node declared into a package a dependency owns fails with
 `ERR_DEPENDENCY_PACKAGE_NOT_OWNED`. Kotlin builds inherit all of this. See
 [`metadata-dependencies.md`](../features/metadata-dependencies.md).
 
@@ -802,7 +803,8 @@ Wire it like any generator:
 
 It writes the artifact and the manifest with the same bytes as the TypeScript `sharedModelFile()`:
 the shared corpus (`fixtures/shared-model-conformance/`) is the gate. The version comes from the
-module's `<version>` unless you pass `version`. Requirement and template nodes are never published.
+module's `<version>` unless you pass `version`. `requirement.*` nodes are published only when you pass
+`<requirements>true</requirements>` (default off); `template.*` nodes are never published.
 Moving the artifact into a registry, and recording a consumer's snapshot and lock, is the Node
 `meta deps sync`'s job; this generator only produces the files.