feat(pssm): bind entry, do and effect parameters from the accepted event and return a behavior's outputs

[devin-ai-integration]

What and why

Builds on #486, now on develop. The classifier's behavior parameter and operation result constructs were "no translation" refusals: UML binds an entry/exit/do behavior's parameters from the triggering event occurrence's data (PSSM §8.5, CallEventOccurrence/SignalEventOccurrence), and a call event's operation returns whatever the triggered behavior produces; SysML v2 has a spelling for each, but the emitter did not carry it. This PR adds the spellings so the referee can run these tests instead of refusing them, and pins where the spelling does not hold.

Per construct:

Construct	Verdict	Reading
Behavior parameter — entry, do, transition effect	translated	A v2 accept binds the payload on the transition (SysML v2 §7.18.3, accept actions §7.17.8). The accepting transition's effect stores the payload or the operation's arguments in machine attributes (trigger_<Signal>, trigger_<op>_<param>), and the target state's entry/do action declares its parameters bound to them: entry action : S_entry { inout log = log; in p1 = trigger_op_p1; }. Same values, same run-to-completion step, no extra trace unit. An effect that is itself the parameterised behavior reads the accept's parameters directly. Data-less paths (completion, accept without payload) that reach such a behavior stay refused, since UML then has no data to bind.
Behavior parameter — exit	refused (behavior parameter <state>)	UML runs the exit before the leaving transition's effect, which is the first place a v2 spelling can read the accepted data; a candidate that stores the data before the exit would need to run before the transition fires, an extra observable unit the admitted traces do not have. Recorded as a refusal in the alignment note.
Operation result	translated	The behavior producing the value becomes an action def with out parameters (out output : String / out 'return' : Boolean), its return an assignment; the runtime's call path from #486 returns the outputs to the synchronous caller after the step.
Tester trace	translated in #486; here the driver's ordering is exercised by the returning cases
Standalone machine	translated in #486; Standalone 003 now runs

Emitter additions the traces needed, read from the model rather than hard-coded: operation in parameters on call triggers, Util::Tracing::formatParameterValue, ToString, or/xor/not, and qualified library names for packaged behaviors.

PSSM buckets

52 pass / 13 fail / 37 not-expressible / 1 differs-by-design (after #486) → 56 / 13 / 33 / 1. Every movement is adjudicated in docs/project/pssm-referee.md ("Moves"):

Test	Movement	Adjudication
Event 019 D	not-expressible → pass	T2's effect return "output" spelled with out output; the one admitted trace reached and nothing else
Event 019 E	not-expressible → pass	or(left, right) arguments carried into the two regions' entries; both admitted orders reached and nothing else
Deferred 007	not-expressible → pass	deferred op(p1) dispatched from S2, T4_effect with in p/out 'return'; the one admitted trace reached
Standalone 003	not-expressible → pass	same machine as Event 019 E, standalone
Event 017 B, Event 019 B, Event 019 C	stay not-expressible, reason shrank	entries, do and effects bind; each has an exit reading the leaving transition's data
Standalone 002	stays not-expressible	exit point ExitPoint1; entry point EntryPoint1; behavior parameter S2 — first two byte-identical
Entry 002 F	stays not-expressible	entry point EntryPoint1; local transition T1.1; local transition T1.2 — byte-identical

The classification pinned by TestSuiteClassification moves 35 standard / 31 extension / 37 not-expressible → 38 / 32 / 33. No fail moved.

Runtime changes

None. The runtime's call-result path is #486's; this PR touches tools/referee/pssm/ and the records only.

Unresolved

• An exit behavior with parameters stays a refusal (Event 017 B, 019 B, 019 C, Standalone 002), with the reading above.
• Same-named operations are told apart by identity throughout (tester call, sameEvent, one set of carried attributes per overload, trigger_bump_1_count / trigger_bump_2_flag). Two whose input names cover each other — bump(in count : Integer) and bump(in count : Boolean) — have one accept bump(count) spelling between them, so a trigger naming either is refused (TestParametersOverloadsWithOneSpellingRefused); no suite test has the shape.
• A do activity with out parameters, a behavior reached by several triggers or by events of different shapes, and a signal with several attributes stay refused with precise reasons (TestParametersRefusals).

Specification basis

PSSM ptc/18-11-06 §8.5 (event occurrences binding a triggered behavior's parameters; the caller of a synchronous call event resumed with the outputs after the run-to-completion step); SysML v2 §7.18.3 (transition accept and its payload), §7.17.8 (accept actions), §7.17.2 (action parameters), KerML StatePerformances.kerml and TransitionPerformances.kerml. No row of docs/project/spec-compliance.md moves — no runtime rule changed. The alignment note (docs/internals/design/precise-semantics-alignment.md) gains the input → emitted-v2 spelling for each construct so the translation can be re-implemented from the record.

How it was verified

New tests: tools/referee/pssm/parameters_test.go (signal and operation-argument binding, rebinding per occurrence, do-activity inputs, operation outputs, and the refusal cases), driver tests in run_test.go (TestDriveTesterTraceAfterCallReturns, TestTracerMakesEachCallOnce), TestParametersUnnamedReturnIsRead (an operation and entry whose UML return parameter is unnamed, read as return throughout), and TestSuiteNoTranslationReasons pinning the remaining reasons per test.

All gates pass:

go build ./... && go vet ./... && gofmt -l .                      # clean, gofmt prints nothing
go test ./...                                                     # ok
go test -C tools ./... && go vet -C tools ./...                   # ok
OPENSYSML_REQUIRE_PSSM_SUITE=1 go test -C tools ./referee/pssm/... # ok
go run -C tools ./cmd/pssm-referee -check                         # 56 pass / 13 fail / 33 not-expressible / 1 differs-by-design, baseline reproduces
OPENSYSML_REQUIRE_TRAINING_CORPUS=1 OPENSYSML_REQUIRE_PILOT_CORPORA=1 go test -count=1 ./tests/corpus  # ok
make lint && make docs-check                                      # ok
python3 scripts/changelog.py check && python3 scripts/check-doc-ids.py  # ok
go run -C tools ./cmd/doc-counts -check                           # already current

Referee checks by hand: -json output byte-identical under -jobs 1, -jobs 8 twice, and no data race under -race; -check rejects a mutated count and a mutated provenance digest (provenance first) with exit 1; -update is reproducible; an absent suite is a skip (exit 0) unless OPENSYSML_REQUIRE_PSSM_SUITE=1; a wrong checksum is refused; a hand-broken trace separator fails -check on the first test and the front end rejects a hand-broken emitted type; -keep writes 70 models (38 standard + 32 extension); a flipped construct disposition fails TestSuiteClassification.

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

[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]

Devin Review found 2 new potential issues.