refactor: remove vendored binaries and raw assets from repo

README.md

@@ -25,6 +25,9 @@ The service needs:
 - MicroDicom files
 - writable temp storage
 
+Large runtime assets are intentionally not stored in git.
+Use the setup scripts in `scripts/` to stage local copies in ignored directories.
+
 ## Setup
 Before running the service, make sure the VM has:
 - Go installed, if you are building on that machine
@@ -33,6 +36,27 @@ Before running the service, make sure the VM has:
 - network access to PACS, the patient API, and the CD publisher
 - a writable temp directory
 
+Stage local runtime assets if needed:
+
+```bash
+scripts/setup-dcmtk.sh --source-dir /path/to/dcmtk/bin
+scripts/setup-microdicom.sh --source-dir /path/to/microdicom
+```
+
+Or download your hosted release assets directly:
+
+```bash
+scripts/setup-dcmtk.sh --archive-url https://<gitea-host>/<owner>/<repo>/releases/download/<tag>/dcmtk-bin.tar.gz
+scripts/setup-microdicom.sh --archive-url https://<gitea-host>/<owner>/<repo>/releases/download/<tag>/microdicom.zip
+```
+
+Example:
+
+```bash
+scripts/setup-dcmtk.sh --archive-url https://devone.aplikasi.web.id/gitea/farrel/dicom-iso/releases/download/1/dcmtk-bin.tar.gz
+scripts/setup-microdicom.sh --archive-url https://devone.aplikasi.web.id/gitea/farrel/dicom-iso/releases/download/1/microdicom.zip
+```
+
 Create a local config file from the template:
 
 ```bash
@@ -40,6 +64,7 @@ cp config.example.yaml config.yaml
 ```
 
 Then adjust the paths, hosts, ports, and tokens for your environment.
+For local staging via the setup scripts, point config at `.local/dcmtk-bin/` and `.local/microdicom/`.
 
 ## Build
 A normal Go build is enough in a friendly environment: