Compiler-enforced backend boundary between executor and sdk/mpr

[ako]

Problem

The PR checklist includes: "No sdk/mpr write imports in executor." This rule exists because executor handlers must route through the backend interface (mdl/backend/), never calling the MPR writer directly. Today this is enforced only in code review. An AI code generator that bypasses the backend produces code that compiles but violates the architecture — the mistake ships unless a reviewer catches it.

Proposed solution

Convert this checklist rule into a compiler or linter error so violations are caught before review.

Option A — Go internal/ package: Move MPR write types into sdk/mpr/internal/writer/. Go's visibility rules prevent any package outside sdk/mpr/ from importing it.

Design note: mdl/backend/mpr/ (the legitimate consumer) lives under mdl/, not sdk/mpr/, so the internal/ mechanism would also block it. This requires either restructuring the package layout or using Option B.

Option B — Linting rule: Add a depguard or gomodguard rule to CI that flags any import of specific sdk/mpr write symbols from mdl/executor/. Enforced at CI, not compile time, but achieves the same practical effect.

Implementation steps

1. Decide on Option A (package restructure) or Option B (linting rule)
2. For Option A: move write-path types into sdk/mpr/internal/writer/, update mdl/backend/mpr/ imports, verify compile
3. For Option B: configure depguard in .golangci.yml with a deny rule on write imports in mdl/executor/, add to make lint
4. Verify the rule catches a deliberate violation in a test branch

Expected outcome

Any code in mdl/executor/ that imports sdk/mpr write types fails at compile time (Option A) or CI lint (Option B). The architecture is self-enforcing.

See proposal: docs/11-proposals/PROPOSAL_agentic_architecture_improvements.md (Change 5)

[github-actions]

Issue Triage

Summary:
The issue proposes adding a compile‑time or lint‑time rule to prevent mdl/executor/ code from directly importing sdk/mpr write types, thereby enforcing the backend boundary automatically.

Checklist for feature request

Required info	Present?	Notes
Use case – why the feature is needed, what problem it solves	✅	Described as preventing architecture violations that slip through code review.
Proposed syntax or behavior (if applicable)	✅	Two options outlined: Go internal/ package restructuring or a depguard/gomodguard lint rule.
Mendix version relevance (if version‑specific)	❓	Not mentioned; please clarify if this change is specific to certain Mendix versions or applies universally.

Next step:
Could you let us know whether this feature is intended to work across all Mendix versions supported by mxcli, or if it is tied to a particular version range? Once we have that detail, the issue will be complete. Thank you for the clear proposal!

---

Automated triage via OpenRouter — workflow source