- Shipped
- September 11, 2026 at 3:06 AM UTC
- Author
- Kamo
- Commit
- 5a67394
The one way to change a file the document editor cannot open - a PDF above all, which is what most templates are. POST **************** takes the new file, scans it for malware and content-addresses it exactly as a first upload, and hands the change to **************** (kamo-shared-library 6d0523e8): the document keeps its id, name, shares, binders and template layer, and its category's versioning mode decides what is kept of what it held - a new version under Automatic, the working copy moving under Manual, an overwrite under Disabled. The PDF rendition and page thumbnails are made for the new bytes by the same pipeline an upload runs. EDIT_DOCUMENTS, not CREATE_DOCUMENTS: nothing new is created. The category's extension policy applies **************** is public for this), and the type is read from the bytes - a new version may be a different format, and the name's extension follows it. Refused for an EXECUTED legal package - the signed record HR issued to a member, which nobody gives a new version, not even its subject - through IssuedArtifactLookup, a read-only local repository over the shared assignment entity; and for the per-party mortgage collections, which the generic imaging endpoints never touch. esign.repos is now scanned here, because a version of a template records its layer's design version.