DC-083: claim license-manager.js coverage for Hermes

DC-PRODUCTION-GRADE-BACKLOG.md

@@ -145,7 +145,7 @@
 - **impact:** Any execSync with interpolation is a potential RCE. This is the same class of bug P0-2 already fixed — finish the job.
 
 ### DC-083: 30 source files have zero test coverage
-- **status:** partial (coverage 65pct->75pct)
+- **status:** in-progress (license-manager.js — revenue path — claimed by hermes 2026-08-12)
 - **details:** The test gap scan found 30 source files with NO corresponding test file, including critical paths: `license-manager.js` (534 lines, the entire revenue validation path), `config-schema.js`, `middleware.js` (the auth/rate-limit/CORS stack), `startup-validator.js`, all 7 DNS provider modules (`technitium.js`, `cloudflare.js`, `rfc2136.js`, `manual.js`, `base.js`, `registry.js`, `email.js`), `docker-maintenance.js`, `config/migrations.js`, `event-workers.js`, `keychain-manager.js`, `event-store.js`, `host-registry.js`. Fix: prioritize license-manager.js (revenue path) and middleware.js (security stack) first, then work through the rest. Effort: ~8 hr (can be done incrementally, 2-3 files per PR).
 - **impact:** license-manager.js validates Pro licenses — an untested bug there could silently break activation for every paying customer.
 
@@ -278,6 +278,7 @@
 
 ### DC-106: Caddyfile-as-code — visual reverse proxy builder
 - **status:** pending
+- **status:** in-progress (auto-claimed at 20260812T222443Z)
 - **details:** Instead of editing Caddyfile text, provide a visual builder: "I want requests to blog.yourdomain.com to go to container X on port 80, with authentication, rate limiting, and compression." Generate the Caddyfile block from the form. Show a live preview of the generated config. Apply via Caddy admin API. This eliminates the need to learn Caddyfile syntax entirely. Effort: ~3 hr.
 - **impact:** Caddyfile syntax is the #1 technical barrier. A visual builder makes reverse proxy configuration accessible to non-sysadmins.