Answer
On Apps10, the actual client runtime deployed to end users is packaged as client.war inside WebLogic, visible under ifs_home\instance\<instance>\client.war. To have customization changes actually picked up and redeployed, make the relevant changes under <ifs_home>\<repository>\client\runtime first, then run a Reconfiguration — that's what deploys the updated files into WebLogic as a refreshed client.war; f1mage itself runs automatically as part of the installer/reconfiguration process rather than needing to be run manually as a separate step. One important gotcha: during Reconfiguration, the installer skips regenerating client.war entirely if it doesn't detect any actual change on a specific client-signing-related radio-button screen. To force it to regenerate regardless, deliberately change that radio-button selection, click Next, then go back to the previous screen and switch it back to whatever the original setting was — that's enough of a detected change to make the installer regenerate client.war, even though the final setting ends up unchanged.