Track remaining non-blocking follow-ups from merged PR reviews

[hjotha]

Source

While extracting actionable fixes from reviews on already-merged PRs, the concrete code issues were moved to #404, #405, #406 and addressed by PR #408. A few review notes are intentionally not part of that PR because they are either design cleanup, documentation-only, or need Studio Pro BSON evidence before changing writer behaviour.

Remaining follow-ups

• PR feat: support free microflow annotations #319: add a live bug-test/roundtrip fixture for free microflow annotations, and consider simplifying ActivityAnnotations.FreeAnnotation + FreeAnnotations into a single slice representation.
• PR fix: preserve microflow-call BSON field order #342: verify whether JavaActionCallAction has the same BSON field-order sensitivity as MicroflowCallAction by comparing against a Studio Pro-created sample before changing writer order.
• PR fix: write valid show-page parameter mappings #338: verify whether FormSettings.TitleOverride: nil is accepted by Studio Pro or should be serialized as a concrete embedded value, similar to the fixed Variable field.
• PR fix: write valid change-action item storage lists #374: document how the int32(2) storage-list marker for ChangeActionItem was verified, or add a small code comment if a Studio Pro-created MPR sample was used.
• PR fix: register import mapping result variable types #360: optional test cleanup for import mapping result type inference: initialise declaredVars in the helper and add a backend-unavailable negative case.

Notes

These are not known current correctness regressions. They are tracked separately so PR #408 stays focused on confirmed review follow-up fixes.

[github-actions]

Issue Triage

Summary:
The issue tracks remaining non‑blocking follow‑up tasks from earlier PR reviews (e.g., adding fixtures, verifying BSON field order, documenting verification steps, etc.).

Checklist of required information (based on issue type):

• This is a tracking/task issue, not a bug report or feature request, so the specific fields listed for bug reports or feature requests are not applicable.
• No missing information is needed for the purpose of this issue.

Feedback:
The issue looks complete for its intended use. Thank you for keeping the follow‑up work organized!

---

Automated triage via OpenRouter — workflow source