Image processing failure in production despite local success

The goal is to reproduce the production image‑processing failure while preserving the working local configuration, focusing on the [GFX] processor_path setting and its interaction with the web‑server user’s environment.

Constraints include the unknown availability of ImageMagick or GraphicsMagick binaries for the www‑data user, possible open_basedir or disable_functions restrictions, and the version‑dependent fallback to GD that does not cover all operations such as GIFBUILDER text rendering.

Uncertainty remains about which specific image operations trigger the failure, how TYPO3 determines the fallback path, and what context‑aware overrides can be applied without hard‑coding binary paths.

• Which image operations require ImageMagick/GraphicsMagick and therefore fail under the GD fallback?
• How can the exact binary path and execute permissions used by the production web‑server user be verified?
• What ApplicationContext‑based configuration strategy can reliably override [GFX][processor_path] across environments?