docs(delegate-job): the audit log is next to the registry unless DELEGATE_JOB_LOGS_DIR moves it

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

.agents/skills/multi-agent-mux-delegate-job/SKILL.md

@@ -134,10 +134,11 @@ Which tree wins, by execution context:
 `python -m`: for `-m` the current directory precedes `PYTHONPATH`, so a frozen
 loop whose working directory happened to contain a `lib_py` package would have
 silently executed live code. The working directory is left untouched; the
-registry and audit-log paths resolve to `MAM_JOBS_DIR` / `DELEGATE_JOB_LOGS_DIR`
-when set, otherwise to `$WORKSPACE_ROOT/.mam/jobs` and
-`$WORKSPACE_ROOT/.mam/delegate_job_logs` (the workspace `lib.sh` exports), and
-only without either to the cwd-relative `.mam/...` (Issue #15 — this is what
+registry path resolves to `MAM_JOBS_DIR` when set, otherwise to
+`$WORKSPACE_ROOT/.mam/jobs` (the workspace `lib.sh` exports), and only without
+either to the cwd-relative `.mam/jobs`; the audit log is the
+`delegate_job_logs` next to the registry in use unless `DELEGATE_JOB_LOGS_DIR`
+names another root (Issue #57, Issue #15 — this is what
 stops a caller whose cwd is not the workspace, such as the pytest suite, from
 registering jobs into a foreign registry).