The pre-window config reader is a deliberate YAML subset (two-space keys,
four-space `- ` items), so any other valid indentation silently disabled
both launch keys — the app just started with no heap ceiling and no way to
tell. And the argv scan read `--name=value` only, so `--js-flags
--max-old-space-size=4096` lost the value and registered a bogus
`max-old-space-size` switch, letting config.yaml's ceiling replace the
launcher's instead of merging with it.
- one warning naming the supported shape when a `desktop:` block mentions
either key and nothing parses; a block with no mention stays silent.
- argv pairs a bare `--name` with a following non-flag token, and
`--js-flags` with whatever follows it (its value is dash-prefixed).
- website/docs/user-guide/desktop.md documents the supported indentation
next to the snippet, plus the warning users will see.
5dd70d7cb6