Path Editing, Improve Mathblock Output

[guardian-automation]

Follow-on to #6326 ("Path Editing, Improve Mathblock Input" — closed, shipped in 3.7.0), which added direct pathname editing for MathBlock INPUT variables. That work only covered inputs; this story extends the same path-based editing capability to MathBlock OUTPUT variables.

Description

When working with the mathblock and adding OUTPUT variables, I want to be able to directly edit the pathname, so that they can be quickly updated and I can avoid using the click-through tree navigation / selection tool when I already know the path name or just need to make a small edit.

Acceptance Criteria

• Output variable path name is editable
• Pressing '.' character brings up autocomplete menu
• Display validation error if pathname does not exist (but allow invalid entries to be saved)

Reference (completed inputs work): #6326

[FloatingPegasus]

Would the team consider this existing backlog item for a funded community contribution? I reviewed the current develop sources; I have not implemented or run tests yet.

In math-editor-dialog.component.html, inputs use onPathChange/onPathBlur plus suggestions, while outputs still use the onOutputLink picker. Simply reusing those handlers for outputs would be insufficient: _updateFieldWarning calls getField('input', ...), and _computePathSuggestions falls back to inputSchemaFieldMap.

Proposed scope: make the output path editable, resolve suggestions and warnings against the output schema (including the existing input-schema fallback when no separate output schema is configured), retain the field picker, and preserve unknown paths on save with a visible warning. Add regression coverage for differing input/output schemas, dot-triggered suggestions, unknown-path save/reopen, clearing paths, and readonly behavior.

I estimate 2–3 engineering days after scope approval and propose US$750, subject to your assigned bounty value. The program document currently lists 2025 deadlines: is this item eligible for a current cash bounty, and is a cash receiving method available for an India-based contributor? Please confirm the current acceptance/payment terms and whether someone is already implementing it before I start. If you need a separate [BOUNTY PROPOSAL] issue under the program workflow, I can create one linked to this item rather than duplicate the feature request now.

Kanishq Sharma