In Plutonomicon github repo it says by the end of the page:
For example, you don't need to prevent an unexpected transaction from locking value away - that's the submitter's own problem - but you do need to stop them from inappropriately spending value.
As i understood, we dont need our on-chain part to fill in all variants of the off-chain code.
So, if we have, for example, some kind of dex Plutus script that sells tokens, assigned to script outputs: one output - one token. In that case we should avoid checking outputs' addresses of sell-transaction for correctness, even with probability of "dishonest" off-chain(for example, extra constraint "MustPayToPubKeyAddress")? Consider that fixed amount of minAda for each output is not set by script logic.