feat(migrate): actors, use cases and requirements are usages; use case diagrams draw their associations, includes, extends and refines as connections

[devin-ai-integration]

What and why

A migrated use case diagram was written as a view rendered asTextualNotation, so nothing it showed was drawn, and the lines it drew in v1 — actor associations, «Include», Extend, «Refine» — had no v2 member a tool can show as a line: they were actor usages inside a use case def, include use case members and dependency declarations between definitions. A connection is what tools draw, and a connection joins features, never definitions. A use case def plus a usage written beside it also showed up in a tool as two elements (two "Operator" actors on one diagram), and a trailing /* «include» */ comment as a note.

The migration now writes a use case model the way v2 users draw one:

• A UML Actor is a part usage and a UseCase a use case usage, each in its owning package, carrying what the def held (subject, includes, extension points, the migrated behavior). No part def/use case def and no inner actor parameters, so each v1 element is one v2 element.
• A «Requirement» is likewise a requirement <id> Name { doc … } usage, a nested requirement its subrequirement, a general one subset (requirement Safety :> Mass;). A «Satisfy»/«Verify» subsets it (satisfy requirement 'satisfy R' :> R;, or satisfy R; unnamed), a «DeriveReqt»'s connection def ends and a requirement-typed property subset it, and the document query engine reads a derivation def whose ends subset requirement usages. Requirement tables, matrices and «Requirement»-stereotype filters list the usages by name (Named) rather than WhereType(RequirementDefinition). An InstanceSpecification of a requirement is reported, as an individual cannot specialize a usage.
• Each actor association, «Include», Extend and «Refine» becomes a connection between the two usages, named by its kind ('Operator to Control Instrument', 'A includes B', 'A extends B', 'A refines B'), hosted by the nearest package holding both ends; a relationship its author named keeps the name and carries its kind (and an extend's condition) as doc. No trailing comments.
• A definition that is still a def (a block, action, …) gets one package-level usage only when a connection first names it; a named association's one usage is typed by its connection def (connection drives : Drives connect driver to vehicle;).
• Use case diagrams are rendered asInterconnectionDiagram over those usages and connections with their Cameo geometry; the renderer draws use case and requirement usages as nodes and an include as the connection's line, not a nested node.
• Classifier/Namespace/PackageableElement tables keep listing migrated actors, use cases and requirements by name; an Actor/UseCase table over a model without them lists the empty sequence.

Specification basis

SysML v2 textual notation: ConnectionUsage ends are feature references, so connections join usages; ConnectionDefinition is the v2 form of a KerML Association, so a named v1 Association maps to a connection def with its link as a connection usage. SatisfyRequirementUsage/VerificationCaseUsage objectives reference a requirement usage by subsetting. No row of docs/project/spec-compliance.md moves.

How it was verified

• go build ./..., go vet ./..., gofmt -l . (empty), go test ./..., the transformation census (-measure, -check) and scripts/changelog.py check pass locally.
• Goldens regenerated and reviewed: the changes are the usages and connections, requirement def → requirement, the :> satisfy/verify/derive forms, the Named requirement filters and the use case diagram views.
• New tests: TestUsagesOnlyForConnectedDefinitions, TestRequirementsAreUsages (nested, specializing, typed-property, refine, satisfy and instance cases), TestExecuteRelatedDerivationDefinitions over ends subsetting usages; relationship, table, document and layout tests updated to the new forms.
• A Cameo SysML v1 model with 4 use case diagrams (41 diagrams, 1124 elements): one part Operator;, all 4 use case diagrams render as graphs with every shown element positioned and every connector routed; the full output with the OpenSysML libraries inlined loads in the OMG pilot validator with 0 errors and 0 warnings.

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/dbff7ccc1454416fb497412e51cf5513
Open in Devin Desktop: https://nasa-jpl-demo.devinenterprise.com/desktop/session/dbff7ccc1454416fb497412e51cf5513?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