If the .bug-script doesn't ask any questions (ie is completely non-interactive - which I think is the case), calling the script from the apport hook via an apport_utils command and include its output as one field in the report seems reasonable.
If the .bug-script doesn't ask any questions (ie is completely non-interactive - which I think is the case), calling the script from the apport hook via an apport_utils command and include its output as one field in the report seems reasonable.