Thanks – yes, I found that scripts in Queued status end up working their way out after application refreshes (and I currently have no scripts in “Queued” status).

Well, incorporate has a strict definition on the Agile side.  You may want to visit your “Modify” privileges for items at specific criteria (using $CURRENTREV and $LATESTREV logic, for instance) to satisfy your business needs.  Just take away user’s modify privileges for the Attachments table.

There is an EVENT HISTORY database table that might be of some use, though I’d admit that I haven’t tried it. 
Perhaps you can also utilize the CHANGE HISTORY or ITEM HISTORY tables as well, if you were interested in regularly tapping into an event occurrence at some point in an object’s history (essentially an SQL query off of the History tab for all objects per your requirements). 
I’ve never tried getting the monitor file by SDK, though.

True, stortip brought up some good answers.  I’d say:
1/2: As few as possible but more importantly, the right people per the process you write out and define in your SOP.  Bare minimum is an requirements owner and a requirements user, which often times for a product change means the Design Engineer (doc owner) and Manufacturing Engineer (user).  Sometimes regulatory/quality gets put in there too.  You can have any number depending on your business maturity and need.
3: Cycle time depends too – consider breaking that number up though to be more specific when looking at metrics.  For instance if you had a Risk Level 1 type Change, what’s the normal time it take for that to be released?  What’s your Post-Release/Implementation phase cycle time?  What is the typical user signoff time?  There’s no such thing as an industry standard for target cycle time.  Quicker is better, but make sure it’s done correctly.

Thank you Karthik and Antonio.
It looks like I eventually got it. Antonio is partially incorrect as the way to set a list value to Inactive because rather it is quite similar to how you would add a new list value.
Borrowing from what Karthik wrote, I experimented and got this to finally work, though I didn’t see your last comment until just now. 

IAgileList listchildren = list.getValues()
IAgileList[] arr =(IAgileList[]) listchildren.getChildren();

arr.each{ listentry ->
   if (value == “Neptune”) {
   listentry.setObsolete(true)  }

listchildren.addChild(listentry) }

list.setValues(listchildren)

Oh, I am referring to inactivate a specific list value. I was already able to inactivate an entire list, but am struggling to inactivate a particular list value via API. 
For instance, say I was going to inactivate a list value called “Neptune”, found in the adminList, how would I go about doing that?  I’ve had little success even after following the API user guide.

Namely, this does not work:
IAdminList list = listLib.getAdminList(“Selection List for 28760”)
IAgileList listchildren = list.getValues()
listchildren.addChild(“Neptune”)
listchildren.setObsolete(true)

I’d still give it a permanent object number if it’s non-interchangeable.  That way you always have a record of it.  
If not, use a deviation because you are talking about a temporary departure from the product baseline.

This is the on the Parts, not through the Change Order user interface tab.
So just go to Parts class user interface tab in the Java Client for BOM attributes and reorder the columns there as you need. That’ll update the BOM and redlined BOM tables for what you see on Change Order affected items.

You can also try the “Personalize” filter and formatting criteria on the top right corner of the BOM (but below the affected items table).

We did figure out, just for anyone’s knowledge, that when Agile goes through the ECO/MCO release process, it conducts a BOM Explosion report (use Oracle SQL) to update the BOM object numbers (i.e., BOM serial number entries).  We were releasing MCOs and ECOs with 20+ BOM levels.  Because this took over 15 minute for us, weblogic failed.

I’m afraid that received the same error message: “Cant support nested workflow search criteria grouping.”

Odd, huh?  There’s no documentation on how to do this in the API guide.

And to think that this advanced search works just fine but recreating the same thing as an IQuery does not.