Revised drawings land as revisions, not duplicates

Revisions are where document control usually goes wrong, and it tends to surface late. This release is mostly about that.

What's new

• Upload a revision and have it read as one. Plenty of drawings carry their revision only in the filename, or only in the title block a scan can't reach. PlanOps now reads the revision out of the name where the drawing itself doesn't give one up, so the file arrives carrying a revision either way.
• Stop a revised drawing being filed as a duplicate. Where no revision could be established, a new file with a familiar reference was marked as a duplicate of the drawing it actually supersedes, which took it out of the default view. That now needs positive evidence the two files are genuinely the same, so the revision stays visible.
• Get the comparison on a bulk upload. When a revision is detected during a multi-file upload, it's now linked to the drawing it supersedes. The revision history shows the full chain and the side-by-side comparison runs, where before it reported that there was nothing earlier to compare against.
• Keep a subcontractor's RAMS as a project document. Files submitted through a RAMS or schedule upload page are now filed into the project's documents every time, whatever the project's wider ingestion policy says. The review, the operative sign-off and the acceptance record all point at the same file.
• Keep marked-up files with the RAMS. Assessment reports and marked-up copies sent out with a review decision now appear against the RAMS itself, rather than living only in the email that carried them. At handover the evidence sits where someone will look for it.
• Build a dashboard by describing it. Ask the assistant for a chart, or a whole dashboard page, and it drafts it against your real project data, checks the fields it has chosen actually work before anything is saved, and shows you the result. You approve what gets added.
• Smaller things. Linking a document to an item no longer overwrites a link someone else added at the same moment, so two people tidying the same package don't undo each other.

Why it matters

A revision that gets filed as a duplicate doesn't announce itself. The drawing office sends P02, the system keeps showing P01, and nobody finds out until someone builds to the wrong sheet or the final account is disputed. Reading the revision off the name, refusing to call two files the same without evidence, and linking each issue to the one before it are all the same job: making sure the latest thing you have is the thing you see.