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/remote.py

@@ -136,7 +136,8 @@ def publish_dispatch(job_id: str, registry_dir: str, session: str, instructions:
                            exceptions=(OSError, TimeoutError, ConnectionError, ValueError))(
         broker_config_from_job(job), topic, body, True)
     mqtt_common.append_event(job_id, {"event": "dispatched", "topic": topic, "session": session,
-                                      "attempt_id": payload["attempt_id"]})
+                                      "attempt_id": payload["attempt_id"]},
+                             logs_dir=mqtt_common.get_logs_dir(registry_dir))
     logger.info("dispatched job %s to remote session %s on %s", job_id, session, topic)
     return topic