A parameter shouldn't be called "Reserved"

Rare host (Orion) doesn't list parameters with such a name, the issue is that it then generates automation for another parameter, leading to much confusion.

But "Reserved0" works.

Start by reproducing the issue with the Rare host Orion using a parameter named "Reserved", then compare it with "Reserved0". Trace the parameter-name handling and automation generation paths to identify why the bare name maps to another parameter. Done means "Reserved" is handled without generating automation for a different parameter, while the existing "Reserved0" behavior remains intact.

Written by the indexing model from the issue text.