chore(sysml-import): full workspace compliance for generated .g.cs

[ottobolyos]

Summary

This chore PR reworks the SysML importer's Scriban templates and one
inheritance-tracking heuristic so a fresh regen against the pinned
build/sysml-model submodule (v2.7) produces .g.cs output that
passes every workspace rule that applies to hand-authored .cs
files.

Trigger: the generator was emitting spurious 8-space blank lines
between properties on Model-generated classes (checked-in files
had been hand-stripped to a single empty blank line, forbidden on
generated files). Several C# templates and one CuttingTools
inheritance seed had drifted from the SysML v2.7 shape at the same
time.

What this PR does

• chore(sysml-import): make generator emit compliant .g.cs output

  • Rewrites the property loop in Model.scriban so it emits a
    single blank line between properties and no stray 8-space
    blank line after each property.
  • Adds a trailing newline to every C#, XML, and JSON-cppagent
    template so rendered files end with a newline (POSIX, and
    matching hand-authored .cs convention).
  • Drops the Assets.CuttingTools.ToolingMeasurement seed that
    added Code to classOnlyNames. SysML v2.7 relocates Code
    from the parent Measurement class onto ToolingMeasurement,
    so the new marker no longer hides anything and was firing
    CS0109 under -p:TreatWarningsAsErrors=true.

• chore(common): regenerate .g.cs from v2.7 XMI with cleaned-up output

  • 745 files. Diff is mechanical: trailing newlines added,
    between-property spacing collapsed to a single blank line,
    and the ToolingMeasurement.Code property emitted without
    new.
  • Assets/CuttingTools/Measurement.g.cs drops its Code
    property and reworks its DescriptionText string to match the
    v2.7 XMI. This is a breaking API change on the base
    MTConnect.Assets.CuttingTools.Measurement type — downstream
    code that reads Measurement.Code needs to move to
    ToolingMeasurement.Code.

• chore(xml): regenerate .g.cs from v2.7 XMI with trailing newlines

  • 2 files. Trailing newline addition only; content unchanged.

Breaking?

Yes — one type: MTConnect.Assets.CuttingTools.Measurement
drops its Code property (the SysML v2.7 model relocates Code
to ToolingMeasurement). Consumers that read
Measurement.Code need to access ToolingMeasurement.Code
instead. Acceptable given the major-version window.

Notes

Nothing is hand-edited on any .g.cs file in this PR — every
change to a generated file is the output of running the SysML
importer with the corrected templates and inheritance seed.

---

Supersedes #216.

Dime review cycle 1

Retroactive backfill (2026-08-20). The 6-agent Ultrareview cycle ran on this PR and its findings landed atomically in commit fcec3039 (test(sysml-import): resolve base ref via fallback chain; fail-loud on CI) plus supporting template + migration-docs commits. Ledger reconstruction from commit history:

• [TEST] test-coverage-audit — generated .g.cs compliance + template semantics pinned via test(sysml-import): pin generated .g.cs compliance + template semantics (75abd0f) and template trailing-newline sweep pinned via test(sysml-import): pin template newline sweep + scriban render arms (3fd645b).
• [FINDING] code-review — generator-fidelity gap: base-ref resolution needed a fallback chain that fails loud on CI when neither the primary nor fallback resolution succeeds; fixed atomically in fcec303.
• [TEST] test-coverage-audit — scoping the generated-file compliance tests to PR-216's regeneration output landed in test(sysml-import): scope compliance tests to PR 216's swept file set (f8a63b2).
• [DOCS] documentation-audit — the Measurement.Code → ToolingMeasurement.Code relocation is a breaking API change on the major-version boundary and required an explicit migration note; added in docs(common): add v7 CuttingTools Measurement.Code relocation note (1ad7c21).
• [SIMPLIFY] simplification — the classOnlyNames seed for Assets.CuttingTools.ToolingMeasurement.Code was dropped in the main template commit (6bd1163) once the SysML v2.7 relocation made the new marker unnecessary; verified minimal shape.
• [FINDING:A08] security-audit — reviewed generator-output surface; no injection/deserialization vectors introduced by the template rewrite.
• [IMPROVE] improvement — no impact-ranked follow-ups surfaced beyond the fail-loud CI hardening already applied in fcec303.

(Zero unfixed findings — Ready-eligible.)

Depends on

• fix: clean every Release-pack warning and add multi-TFM CI gate #219 — infrastructure dep — warnings-clean base needed for own 0-warnings Completed verification
• chore: apply dotnet format baseline and add CI gate #230 — infrastructure dep — format-baseline needed for own 0-warnings Completed verification
• feat(common): add IConfiguration.VendorExtensions for XSD extension #223 — symbol + file dep: this PR regenerates ~770 .g.cs files after a template compliance sweep; the regen output for Configuration.g.cs / IConfiguration.g.cs must carry the partial marker feat(common): add IConfiguration.VendorExtensions for XSD extension #223 introduces via its TemplateRenderer.cs case-switch tweak, otherwise feat(common): add IConfiguration.VendorExtensions for XSD extension #223's hand-authored companion partials fail to compile.