fix(delegation): audit-log root follows the registry (Issue #57)

get_logs_dir(registry_dir) resolves the audit-log root as the
delegate_job_logs next to the registry in use when DELEGATE_JOB_LOGS_DIR
is not set; sibling_logs_dir() is the pure sibling rule. Every writer and
reader that knows its registry (registry, engine, publish_event, remote,
job_subscriber, reconcile.sh, the loop runner's fingerprint exclusion)
passes that root instead of falling back to the workspace default.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

.agents/skills/lib_py/delegation/publish_event.py

@@ -241,7 +241,7 @@ def record_outcome(prepared: PreparedEvent, registry_dir: str,
         "payload": prepared.payload,
         "published": publish_ok,
         "publish_error": publish_error,
-    })
+    }, logs_dir=mqtt_common.get_logs_dir(registry_dir))
 
     if not local_event_recorded:
         registry.append_event(prepared.job_id, registry_dir, prepared.payload)