[devin-ai-integration]

What and why

The pinned OMG pilot validator (tag 2026-08) found two conformance gaps on develop.

1. Body members accepted in bodies whose grammar doesn't allow them. frame inside a view (examples/views-demo.sysml:176, examples/self-model/views.sysml:197) parsed cleanly, even under -strict. I compared OpenSysML and the pilot on every body-specific member across view / view def / viewpoint / viewpoint def / rendering / rendering def bodies (222 fixtures) and found three more gaps of the same kind. Each now follows the project's existing classification:

Member	Grammar home	Now
frame concern c : C; / frame c;	RequirementBodyItem (requirement, concern, viewpoint)	parser error elsewhere, via ownedMembers like subject/stakeholder/render
filter …;	PackageBodyElement, view and view def bodies	parser error elsewhere (new bodyPackage context for packages and the file root)
accept … action node	ActionBodyItem (action, calc, case bodies)	parser error elsewhere, like send/assign; state bodies are unchanged
one-name then t;	ActionBodyItem, plus the state body's target transition	nonstandard-notation outside action/state bodies (warning by default, error under -strict), extending the existing target-succession check; if g then t; / else t; there were already parser errors

Viewpoint frames (views-demo.sysml:135, self-model/views.sysml:9) are valid and stay clean.

Supersedes develop's warning for frame in view and view def bodies. Develop reported such a frame as nonstandard-notation (a warning by default, an error under -strict). It is now a parser error in every mode, coded framed-concern-membership-owning-type, because FramedConcernMember appears only in RequirementBodyItem. The notation check that issued the warning is removed, so a frame gets exactly one diagnostic. A misplaced filter is coded element-filter-membership-owning-type; both codes are in docs/reference/diagnostics.md. Develop's %view rule, which evaluates each viewpoint concern directly against the view's exposed elements, matches this PR's and is kept as is.

%view. Develop has since landed the same conformance rule (each concern the satisfied viewpoint frames is evaluated directly against the elements the view exposes; no view-local re-framing is required, since valid SysML can't write it). This PR takes develop's implementation, tests and example edits, and adds one test for an untyped frame concern mass; in a viewpoint.

2. Extension libraries marked standard. DiagramLayout, IdentityMetadata, MigrationMetadata and SysMLValidation are non-normative OpenSysML extensions, but were declared standard library package. They are now library package. What this changes:

• Element ids: no change. Normative UUIDs come from the library tier (Kernel/Systems/Domain), not from isStandard, and the OpenSysML Libraries tier never had them.
• RDF export: these four packages no longer export sysml:isStandard true (false flags aren't written).
• stdlib.snapshot: regenerated (make stdlib-snapshot).
• Library-version recognition: a user copy is matched on its library/standard keywords, so a copy now has to be written library package to stand in for the bundled file.
• Docs: pages that quote these declarations are updated.

Specification basis

• SysML v2 pilot grammar SysML.xtext (tag 2026-08): ViewBodyItem, ViewDefinitionBodyItem, RequirementBodyItem (FramedConcernMember), PackageBodyElement (ElementFilterMember), ActionBodyItem (AcceptNode, TargetSuccessionMember).
• KerML 1.0 LibraryPackage::isStandard: only for standard / normative model libraries.
• docs/project/spec-compliance.md: the view-conformance row text is updated; its status is unchanged (⚠️ Approximate, tool-defined verdict rules).

How it was verified

Pilot results, before → after:

Input	Before	After
examples/self-model + OpenSysML Libraries	2 syntax errors (views.sysml:197), 4 "should not be marked as standard" warnings	0 errors (the 46 existing bound-feature/duplicate-name warnings in document.sysml are unchanged)
examples/views-demo.sysml + OpenSysML Libraries	2 syntax errors (:176), 4 warnings	0 errors, 0 warnings
OpenSysML Libraries alone	0 errors, 4 warnings	0 errors, 0 warnings

• Fixture comparison: across all 222 body × member cases plus extra accept / if…then / else cases, every case the pilot rejects as a syntax error is now an error from us under -strict. The remaining mismatches are cases where both sides already report non-syntax errors.
• Pilot rejection oracle: new cases g82–g85 (frame in view / view def bodies, filter outside a package or view, accept outside an action body) and x12 (target succession outside an action body), all rejected by both. Baseline is now 328 cases: 319 rejected by both, 0 pilot-only, 9 ours-only (develop: 323 / 314).
• Pilot differential: re-recorded on current develop; identical to develop's baseline (397 files, 358 fully agreeing, 93 pilot-only rows), since develop's own example edits already removed the invalid view frames.
• Corpus gates: pilot-corpora, training-examples and corpus round-trip gates pass with no movement; nothing was re-baselined.
• Full checks: go build ./..., go vet ./..., gofmt -l . (empty), go test ./..., go test -C tools ./..., make docs-check, make stdlib-snapshot-check, make self-model, make docs-counts, man-check and changelog check all pass.
• Fixtures moved to valid bodies: test fixtures that relied on the over-accepted forms were checked as pilot-invalid first, then moved into valid bodies (goldens regenerated): tests/export/testdata/convert/imported_references.sysml (filter in a part def), accept_payload_test.go, event_feature_test.go and runtime/signal_test.go (accept in a part def).

Checklist

• make test and make lint pass locally
• Tests added or updated for the change
• Documentation extended where it already covers the surface (see CONTRIBUTING.md)
• Changelog entry added as changes/unreleased/<slug>.<section>.md, not as an edit to CHANGELOG.md
• baselines regenerated and make docs-counts run if a gate count moved (compliance rows need nothing: the census is counted at docs build)
• No internal work-item labels (waves, slices, F4, K5) in the body, docs, or changelog

Link to Devin session: https://nasa-jpl-demo.devinenterprise.com/sessions/2c39248a684e49a4af9bd168ba90484e
Open in Devin Desktop: https://nasa-jpl-demo.devinenterprise.com/desktop/session/2c39248a684e49a4af9bd168ba90484e?variant=devin
Requested by: @HuiJun

[devin-ai-integration]

I'll fix CI failures and address comments from users with write access. I'll skip comments containing "(aside)".

• Disable automatic comment, CI, and merge conflict monitoring

[devin-ai-integration]

End-to-end testing of the CLI, REPL and pilot on ef0f402 (later commits changed only the changelog): all checks passed.

Concern evaluation	Default vs. strict notation

Misplaced members and clean controls	RDF before and after

• Strict validation: views-demo.sysml and examples/self-model report no errors. A misplaced frame, filter or accept gives exactly one error at the member, the same in default and strict mode, and the declarations after it still parse. Valid controls in requirement, concern, viewpoint, package, view, action, calc, case and state bodies are clean.
• Notation: then y; in a view body is a warning by default and an error under strict; the same line in an action body is silent. if/else there remain parser errors, and the pilot rejects them too.
• %view: Lander heavyDescender and Robot heavyMockup violate their mass conditions. A custom model gives a violated concern that names the failing element, a concern that holds, an unevaluable concern with no condition, and a conforming view that exposes only light elements.
• Pilot: the extension libraries report 0 errors and 0 warnings. With self-model and views-demo added: 0 errors (the 46 existing self-model warnings are unchanged). The pilot rejects the invalid fixtures and accepts the controls.
• RDF: IdentityMetadata is exported as a LibraryPackage with no isStandard (false flags aren't written); the old declaration exported by the same binary gives isStandard true.

[devin-ai-integration]

Note

Newer findings are available below. Devin Review posted a newer report on this PR, in addition to the findings presented here.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no bugs or issues to report.

[devin-ai-integration]

This branch now conflicts with develop. Conflicting files, and the merged PRs that changed them:

• .agents/skills/testing-pilot-corpora-gate/SKILL.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• .agents/skills/testing-pilot-differential/SKILL.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• .agents/skills/testing-pilot-execution-referee/SKILL.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• .agents/skills/testing-pilot-xpect/SKILL.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• README.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897, feat(view): add a D2 rendering form across every surface #887, feat(install): add install.sh and install.ps1 for every supported platform #907)
• docs/internals/architecture.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• docs/project/pilot-differential-baseline.json (fix(runtime): explore every order of unordered statements in calc, constraint and case bodies #864, fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897)
• docs/project/pilot-differential.md (fix(resolve): treat same-named members of non-conforming metaclasses as distinguishable #897, fix(parser): accept only a literal or a feature reference as a multiplicity bound #891)
• docs/project/pilot-rejection-baseline.json (fix(parser): accept only a literal or a feature reference as a multiplicity bound #891)

To resolve: merge current develop into this branch with an ordinary merge commit (no rebase or force-push).
Don't hand-merge generated files: regenerate docs/project/pilot-differential-baseline.json with go run -C tools ./cmd/pilot-diff -update after the merge.
Regenerate docs/project/pilot-rejection-baseline.json with go run -C tools ./cmd/pilot-reject as described in docs/project/pilot-rejection.md, and the pilot figures quoted in README.md, docs/internals/architecture.md and the testing skills with make docs-counts.

Planned merge order for the view and docs PRs: #889 → #881 → #871 → #882 → #884 → #885 → #886. Each needs these files regenerated again after the one before it merges.

Re-run the full gate (go build ./..., go vet ./..., gofmt -l ., make lint, make docs-check, go test ./...) and wait for green CI before marking ready.

[devin-ai-integration]

Hold on pushes: please don't push to this branch, including develop merges or empty commits to retrigger CI, until a maintainer says the CI runners are free. Prepare the conflict resolution locally and push it then.

[devin-ai-integration]

The push pause is lifted for this PR, for one push after the work below.

Merge origin/develop (2f92d69) into this branch. 20 files conflict.

Source files: resolve by hand.

• internal/semantic/semantics/conformance.go (3 hunks)
• conformance_test.go (11)
• internal/check/passes/nonstandard_notation.go (4)
• internal/frontend/repl/view_test.go (2)
• examples/views-demo.sysml (1)

Generated files: do not hand-merge. Take develop's side, then regenerate:

• internal/workspace/libs/stdlib.snapshot: make stdlib-snapshot
• docs/project/pilot-differential-baseline.json: ./scripts/download-pilot-sysml-validator.sh && ./scripts/download-pilot-kerml-validator.sh && go run -C tools ./cmd/pilot-diff -record
• docs/project/pilot-rejection-baseline.json: ./scripts/download-pilot-reject-validators.sh && go run -C tools ./cmd/pilot-reject -update

Every row that moves in those two baselines must be adjudicated in pilot-differential.md or pilot-rejection.md, not just recorded. Both files also conflict, with 6 and 5 hunks.

Prose: README.md (4 hunks), docs/project/spec-compliance.md, docs/internals/architecture.md, docs/guide/04-repl.md and six .agents/skills/*/SKILL.md files.

Before pushing, run the full gate and confirm it passes:

• go build ./..., go vet ./..., gofmt -l . (must print nothing) and go test ./...
• go test ./tests/corpus with OPENSYSML_REQUIRE_PILOT_CORPORA=1 OPENSYSML_REQUIRE_TRAINING_CORPUS=1
• make docs-counts
• make docs

Push once, without force-pushing.