When a vendor's setup prompt conflicts with the project's spec, ship both behind one config value
A pasted vendor integration prompt asked for the vendor's hosted paywall UI, while the project's spec and standing instructions required a custom paywall that was already built. Rather than replace the spec'd screen or ignore the request, the hosted UI went in as a thin wrapper view selected by a single config value, defaulting to the spec'd screen, plus a debug launch argument to preview the hosted one without editing config. That kept the work unblocked, let the person choose with a one-word answer after seeing both, and made the later switch a config change. Once they chose, the decision went into the project's instructions file with the date, what the alternative was, and a note not to switch without asking, so a later session does not reopen it. Note that hosted paywalls render a vendor placeholder until one is designed in the dashboard, so check that before recommending the switch.