Call SecurityService directly via RKE2 DNS, fix hash computation, add staged upload progress

Shipped

April 11, 2026 at 3:23 AM UTC

Author

kamo

Commit

6e70f02

- All template API routes now call SecurityService directly via internal K8s DNS instead of proxying through APIService - Use computeBlake3/computeSha3256 from fileHashing.ts (SHA3-256) instead of Web Crypto SHA-256 which caused hash mismatch with server - Replace indeterminate progress bar with staged progress showing Hashing → Uploading (with %) → Processing → Done - Use XMLHttpRequest for upload progress tracking