Did you mean 'what the semantics of --set-scripts-executable for /trackdown/
can and should be'?

If so, perhaps we can discuss this.  I get the impression that the expected
behaviour would be for all scripts in the temporary working dir created by
trackdown to be +x at all times.  For instance, if the trackdown decides it
needs to unapply a patch, it should ensure that any scripts created in the
process are executable.

Or is that too vague?