docs(compliance): drop stale v2.6/v2.7 XMI byte-identical claim - #228
Draft
ottobolyos wants to merge 2 commits into
Draft
docs(compliance): drop stale v2.6/v2.7 XMI byte-identical claim#228ottobolyos wants to merge 2 commits into
ottobolyos wants to merge 2 commits into
Conversation
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 19, 2026
…entical (reconcile-cascade 20260819T134500Z)
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 19, 2026
…byte-identical claim
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 19, 2026
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 19, 2026
ottobolyos
force-pushed
the
docs/known-divergences-drop-v26-v27-byte-identical
branch
from
August 19, 2026 22:06
a1ed945 to
f0896bf
Compare
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 19, 2026
ottobolyos
force-pushed
the
docs/known-divergences-drop-v26-v27-byte-identical
branch
2 times, most recently
from
August 21, 2026 08:34
8f45b12 to
1f48880
Compare
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 21, 2026
…v27-byte-identical) at 1f48880
ottobolyos
force-pushed
the
docs/known-divergences-drop-v26-v27-byte-identical
branch
from
August 21, 2026 16:05
1f48880 to
026a156
Compare
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 21, 2026
…ical into integration/up-to-pr-228
ottobolyos
added a commit
to ottobolyos/mtconnect.net
that referenced
this pull request
Aug 21, 2026
…ical into integration/up-to-pr-228
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
The standard maintainer has corrected the byte-identical SysML XMI release issue. The documented claim is now stale and should be removed.
Change
Deleted the entire stale section (formerly lines 21–29):
## v2.6 SysML XMI byte-identical to v2.7No other sections or cross-references were modified.
Dime review cycle 1
Retroactive backfill (2026-08-20). The 6-agent Ultrareview cycle ran on this PR and surfaced a bug-class-atomic sibling-doc gap. Ledger reconstruction from commit history:
[DOCS]documentation-audit — inline cross-check confirmed Version26 and Version27 ARE distinguished at the type level in the code (AssociatedAssetIdDataItem,AssetAddedDataItem,CuttingTorchComponentall haveMinimumVersion => Version26;PinToolComponent,SwingDiameterDataItem,WaterHardnessDataItemall Version27). Original "treated as equivalent" claim was stale; primary section deletion landed indocs(compliance): drop stale v2.6/v2.7 byte-identical claim(fec1926).[FINDING]code-review — the byte-identical claim was cross-referenced from 2 sibling sites (docs/compliance/per-version-matrix.md,docs/cookbook/migrate-versions.md) that would have become stale after the primary section deletion; sibling atomic fix (bug-class-atomic rule) landed indocs(compliance): drop sibling byte-identical claims — atomic fix per...(f0896bf).[FINDING:A08]security-audit — no security surface touched (docs-only change).[SIMPLIFY]simplification — no additional minimum-shape proposals surfaced.[IMPROVE]improvement — no impact-ranked follow-ups surfaced.[TEST]test-coverage-audit — no test surface touched (docs-only change); no coverage FLOOR gap introduced.(Zero unfixed findings — Ready-eligible.)
Depends on