Merge https://github.com/strata-org/Strata/pull/1076 and https://github.com/strata-org/Strata/pull/1077

[keyboardDrummer]

Create a branch that merges strata-org#1076 and strata-org#1077

[keyboardDrummer-bot]

I attempted to merge the two PR branches (disallow-transparent-statement-bodies from strata-org#1076 and issue-21-assign-variable-type from strata-org#1077) but there are 25 files with merge conflicts (65 conflict regions total).

The conflicts are non-trivial semantic conflicts — both PRs modify the same Laurel language infrastructure in overlapping ways. Key conflict areas include:

• Grammar definition (LaurelGrammar.lean) — both PRs added different grammar changes
• Type system (LaurelTypes.lean) — different implementations for call type computation (getCallType helper vs inline match)
• Assign target representation (EliminateValueReturns.lean, MapStmtExpr.lean) — PR Generalize multi-target assign so it supports intertwined declarations, local assignments and field assignments strata-org/Strata#1077 changed assign targets from Identifier to a new Variable type with Local/FieldAccess variants, while Various Laurel resolver improvements - including disallowing transparent procedures strata-org/Strata#1076 also modified these areas
• Compilation pipeline (LaurelCompilationPipeline.lean) — Generalize multi-target assign so it supports intertwined declarations, local assignments and field assignments strata-org/Strata#1077 added early-return logic for diagnostics
• HeapParameterization, InferHoleTypes, LiftImperativeExpressions, Resolution — extensive overlapping changes
• Python-to-Laurel translation (PythonToLaurel.lean, Specs/DDM.lean, Specs/Decls.lean) — 16 conflict regions
• Test files — 7 test/expected files with conflicts

Resolving these correctly requires understanding how the two feature sets interact (transparent body restrictions + multi-target assign generalization). I don't think I can resolve these reliably without introducing bugs.

Question: Would you prefer to:

1. Rebase one PR on top of the other in the upstream repo first, then I create the merged branch from the result?
2. Provide guidance on conflict resolution for specific files so I can attempt the merge?
3. Something else?

[keyboardDrummer]

Provide guidance on conflict resolution for specific files so I can attempt the merge?

This option

Compilation pipeline (LaurelCompilationPipeline.lean) — strata-org#1077 added early-return logic for diagnostics

You can keep the early return

different implementations for call type computation (getCallType helper vs inline match)

Keep the helper