How to auto generate documentation from report packages?

[abaltins]

I am writing some scripts to automate various documentation output tasks.
I have developed some RTF Templates and am using model documents and report packages to assemble my content – works great!
Now I want to automate the creation of my reports.  I am currently heading down the road of creating a report specification for each of my outputs and then running Project.RunReport() to create the report.
The problem that I have is that the ReportSpecifications’ DocumentOptions tag (xml) contains the attribute for the sourceguid of the package to report on (i.e. my report package) and when I provide that value to RunReport(), the document generator treats my report package like just another package and ignores the templates specified by the model documents.
Also I noticed that the document generator dialog is slightly different if you choose to Generate Documentation of a report package vs any other type of package/element:  1st input field is Master Document vs Element (respectively)
Any thoughts or suggestions?

[Spool]

I think I have the same problem here:

I want to update my <<report specification>> element by script, like RunReport(...). This command should replace or add the generated report as a LinkedDocument to the element.
By hand, this is performed by clicking on the element.

Best regards
T.Frank