REPL: SET key = value listed in HELP but not implemented (scaffolding only)

[retran]

Description

The HELP output documents set key = value; under "Other" commands. The full execution path exists:

• ast.SetStmt (ast_query.go:434-440)
• execSet() handler (cmd_misc.go:41-48) stores key=value in ctx.Settings
• register_stubs.go:390-392 registers the handler
• repl.go:338 recognizes set prefix as complete statement
• repl.go:800 provides tab completion for SET

However, no grammar production creates ast.SetStmt. The grammar's setStatement only handles microflow-level SET $Variable = expression. The utilityStatement rule has no SET alternative.

Steps to Reproduce

mxcli -c "SET format = json"
# Parse error: mismatched input 'SET'

Expected

SET format = json should store the setting and print confirmation as documented.

Root Cause

Grammar gap — utilityStatement in MDLParser.g4 needs a session-level SET rule (distinct from microflow setStatement).

Affected Files

• mdl/grammar/MDLParser.g4 — needs session-level SET rule in utilityStatement
• mdl/visitor/visitor_query.go — needs visitor to construct ast.SetStmt

[github-actions]

Issue Triage

Summary:
The SET key = value command is documented and has implementation code, but the grammar lacks a production for it, causing a parse error when the command is used.

Checklist of required bug‑report information

Required info	Present?	Details
mxcli version	❌	Not mentioned
Mendix version	❌	Not mentioned
Scenario (what the user was trying to do)	✅	Running mxcli -c \"SET format = json\"
Expected output	✅	Command should store the setting and print a confirmation
Experienced output	✅	Parse error: “mismatched input 'SET'”
AI bug report (mxcli diag --bundle or session log)	❌	Not provided

What’s missing:
Please add the output of mxcli --version (or commit/build info), the Mendix version of the project you’re working with, and, if possible, a diagnostic bundle (mxcli diag --bundle) or at least the session log showing the error. This will help us reproduce and fix the issue quickly.

Thank you for reporting the problem!

---

Automated triage via OpenRouter — workflow source

[retran]

Reclassification: This is scaffolding/enhancement, not a bug. The Settings map is written but never read by any code — no behavior changes based on SET values. No defined keys exist (format, default module are not referenced anywhere). This was likely a placeholder added during REPL development. The HELP text should either be removed or the feature completed.