7 Commits

Include renames

Author	SHA1	Message	Date
Hermes	026437035d	[pending-judge] fix(r5): exercise the boot-timeout kill, total bridge-body handling, strict subdomain labels (judge r4 blockers) ... - __tests__/e2e-node/composition-root.e2e.test.js: `boot()` takes {timeoutMs, code} and the timeout rejection carries the child it killed; a NEW test drives the real timeout against a child that never reports PORT/READY and asserts the OS-observed SIGKILL on that child (marker e2e-timeout-kill) — the r4 claim is now exercised. - routes/deploys.js: bridge() coerces any non-object JSON body (null/[]/string) into the same failure shape as a non-JSON body, so no `body.ok` deref can 500 or report a false success; the subdomain label regex rejects leading AND trailing hyphens. - __tests__/routes/deploys.catalog.r4.test.js: trailing-dash rejection case + three malformed-successful-body cases (clean 502, never 500).	2026-10-07 08:31:14 -07:00
Hermes Agent	5cf5dac281	[pending-judge] fix(r4): audit contract, subdomain forwarding, timeout kill (judge r3 blockers) ... BLOCK0: catalog deploy audit now uses the REAL AuditLogger contract (auditLogger.log({action,resource,details,outcome,ip})) fire-and-forget via Promise.resolve().catch — async audit failures can never fail the deploy response (tested with a throwing audit backend). BLOCK1: verify.sh targeted-jest block captures jest exit code explicitly (set +e / rc / loud FAIL) — no silent termination under set -e. BLOCK2: subdomain advertised by the App Selector modal is now FORWARDED end-to-end (selector -> /deploys/catalog/deploy validated charset -> bridge --subdomain -> CLI CatalogInstallOptions, implemented in dc-catalog-2 r3); invalid subdomains 400 before the bridge (4 cases). POLISH: boot-timeout SIGKILLs the child (no leaked process). New r4 suite: 7 tests (audit shape success/failure, subdomain forward + 4 rejections). Full suite 157 suites / 3519 tests green.	2026-10-07 03:59:30 -07:00
Hermes Agent	0704676741	[pending-judge] feat(deploys): catalog deploy via shipdeck bridge (DC-CATALOG-3) ... GET /deploys/catalog/apps -> bridge /api/catalog/apps (73 embedded apps, single source of truth). POST /deploys/catalog/deploy {app,port,env} -> validated (service-id charset, port 1024-65535, env name/value rules) then proxied to bridge /api/catalog/deploy which runs the shipdeck CLI catalog deploy (OCI image -> hardened systemd service; NO Docker daemon). Audited as deploy.catalog with ok/seconds. 11 table-driven route tests incl. validation rejections never reaching the bridge + bridge-failure 502 shape. App Selector submit rewired from /apps/deploy (Docker chain) to /deploys/catalog/deploy — same modal, same fields (port, mediaPath, plex claim token as env), no new UI screens. Full suite 3510/3510 (156 suites).	2026-10-07 02:08:32 -07:00
DashCaddy Polish Loop	f9cbb13a3d	[grade=B] DC-131/132/133 install from any Git host ... Codex source gate: urn:ump:iw2tbbe6mssyl5divymmwo42ael65sbfrciztvyowo3zhrbtircq Generated assets gate: urn:ump:hintflviuxfpeidth42ry5fi4lwqsjhkxipzspfmk7vrvfc2cnqq	2026-09-14 20:10:14 -07:00
DashCaddy Polish Loop	65a447e27e	DC-130 rev3: log.error on unexpected bridge status in /status + test asserting the log call (13 tests green)	2026-09-14 04:19:55 -07:00
DashCaddy Polish Loop	121caef488	DC-130 rev2: fail-fast bridge bindings (host), /status gateway-error mapping (401/403/unreachable -> 502, probe-failure stays ok:false) + 3 new tests (13 total)	2026-09-14 04:11:30 -07:00
DashCaddy Polish Loop	1fc61c3fdb	DC-130: shipdeck deploys panel — bridge-proxied source deploys (routes + tests, opt-in via SHIPDECK_BRIDGE_URL)	2026-09-14 03:33:31 -07:00