no-mistakes(document): Fixed stale template-header overwrite claims in three docs and one stale audit-axis reference; ADRs, CHANGELOG and JVM docs already matched the change.

Author: dmealing

agent-context/skills/metaobjects-audit/references/surface-review-axes.md

@@ -141,8 +141,7 @@ The full hunt for each axis of Phase 1b (Partial / Deep path). Each axis runs in
   taxonomy impurity (entity over read-only primary source; read model that should be
   `object.projection`; `value` carrying identity/source, ADR-0028); copy-pasted base-field
   blocks — or the same-named field re-declared across objects (drift signature 10) — instead of
-  abstract + `extends`; `@`-prefixed YAML keys (ADR-0006); relative refs
-  in committed canonical JSON (ADR-0032); DB-type-as-logical-subtype (ADR-0013); per-port
+  abstract + `extends`; `@`-prefixed YAML keys (ADR-0006); DB-type-as-logical-subtype (ADR-0013); per-port
   migration engine where schema is Node-`meta`-owned (ADR-0015).
 
 - [ ] **H2. Wrong native type — `field.<x>` + `@dbColumnType` that hides the real type

docs/features/codegen-concepts.md

@@ -282,11 +282,10 @@ Python, `TemplateRoot` in C#; default `prompts/` when it exists, else `templates
 `perEntity`/`perPackage`/`perModel` and `format` (when present) one of the
 registered escaper formats; a `target` field is **rejected** (the CLI ports have no
 output-target concept). The same neutral data dict, output-pattern grammar, and
-conformance corpus apply, so a spec renders byte-identically across ports. (Because
-a template's output flows through the standard write path — which refuses to
-overwrite a file lacking the `@generated` marker — a regenerable template must emit
-that header in its own body. The JVM's `TemplateScopeGenerator` writes directly and
-carries no such obligation.)
+conformance corpus apply, so a spec renders byte-identically across ports. The standard
+write path decides from the hash manifest, not the header (section 7), so a template need
+not emit the `@generated` marker. The JVM's `TemplateScopeGenerator` writes directly and
+keeps no manifest record.)
 
 **The spec is declared, never discovered.** Through 1.0 both CLI ports also read a
 `--template-spec` flag or a project-root `template-spec.json` on their own. Since 1.1.0 a spec

docs/ports/csharp.md

@@ -586,8 +586,9 @@ Each spec entry derives the neutral template data dict for its scope
 `--out`, or under its own `OutDir` when it sets one, and are gated byte-identical against the
 shared `fixtures/template-codegen-conformance/` corpus. A `target` field is rejected (C# has no
 output-target concept); a missing spec file, a bad template ref or a wrong `TemplateRoot`
-surfaces as a clean error, not a stack trace. For output to be regenerable, the **template**
-must emit the `@generated` header itself (the write path refuses to overwrite files lacking it).
+surfaces as a clean error, not a stack trace. The write path decides from the committed hash
+manifest, not the `@generated` header, so the template need not emit one (see
+[codegen-concepts](../features/codegen-concepts.md#7-safety-never-clobbering-hand-edits)).
 
 ## Angular 18 frontend
 

docs/ports/python.md

@@ -523,9 +523,9 @@ The named generators run after the target's `generators`, into the same `outDir`
 are gated byte-identical against the shared `fixtures/template-codegen-conformance/`
 corpus. Output is format-agnostic (text/markdown/csv/json/xml/html), so the template-spec
 pass emits no `__init__.py` into its tree. A `target` field inside the spec is rejected (the
-spec's target is the one that declares it); for output to be regenerable, the **template**
-must emit the `@generated` header itself (the write path refuses to overwrite files lacking
-it).
+spec's target is the one that declares it). The write path decides from the committed hash
+manifest, not the `@generated` header, so the template need not emit one (see
+[codegen-concepts](../features/codegen-concepts.md#7-safety-never-clobbering-hand-edits)).
 
 ### Universal browser-client hookup (React / Angular 18)