Status of deployment without parsing logs?

System

OD 6.2.1
Solaris

Wondering if it's possible, or if there's a mechanism in place (CLT or ENV variables, etc) to determine the status of the files in a completed deployment, without having to parse the logs to get that information. Status meaning the deployed/deleted/failed status for each file. I've skimmed the docs, but don't see anything.

The history behind this is that we still have an issue where sometimes files are being deployed as deletions, because OD is not seeing them in STAGING, when they should actually be in STAGING and should be deployed as regular content. This is wreaking havoc when it happens because as far as the deployment is concerned, it is a successful deployment - there's no indication that anything didn't work properly until the file is noticed as missing from the website. Not good. So while IW is pondering what's wrong (for 2 months now), we are having to have someone wake up in the middle of the night a couple times a week to verify that deployments scheduled at 2:00 am are actually working properly. There appears to be no solution on the horizon from IW, so we'd like to try and automate the detection of the problem by writing a DNR script that wakes up after a deployment, checks the status of each file, and if it deployed a deletion of a file, and that file exists in the workarea, send out a page to the on-call.

If anyone has any other ideas, I'd welcome them. I'd like to avoid having to parse the logs for this information (there are 4 logs with each production deployment), but if I have to I will. The reason I don't want to parse the logs is because I'd have to do it in shell script, and I don't really know shell script - we are not allowed to use perl here. Don't ask. Just don't.