From 4ff59cb752fb0c4453d5cc1b354b708533411782 Mon Sep 17 00:00:00 2001 From: mlandolfi90 Date: Tue, 28 Jul 2026 14:34:33 -0400 Subject: [PATCH] fix(daemon): print the validation detail when the secure endpoint cannot be created The MCP-client path swallowed the reason: any refusal inside the ancestor DACL walk surfaced as a bare 'secure daemon endpoint could not be created', undiagnosable in the field. The worker path already prints cbm_daemon_ipc_validation_detail(); do the same here. Co-Authored-By: Claude Fable 5 Signed-off-by: mlandolfi90 --- src/main.c | 5 ++++- 1 file changed, 4 insertions(+), 1 deletion(-) diff --git a/src/main.c b/src/main.c index 5d26fa13b..a417eae8f 100644 --- a/src/main.c +++ b/src/main.c @@ -2119,7 +2119,10 @@ int main(int argc, char **argv) { cbm_daemon_ipc_endpoint_t *endpoint = cbm_daemon_bootstrap_endpoint_new(NULL); if (!endpoint) { - (void)fprintf(stderr, "codebase-memory-mcp: secure daemon endpoint could not be created\n"); + const char *validation_detail = cbm_daemon_ipc_validation_detail(); + (void)fprintf(stderr, + "codebase-memory-mcp: secure daemon endpoint could not be created%s%s\n", + validation_detail[0] ? " - " : "", validation_detail); return EXIT_FAILURE; }