docs(rules): update multi-agent rules with job-centric structure pointers

- Document automated job brief path under .mam/jobs/<job_id>/brief.md
- Document automated report redirection under .mam/jobs/<job_id>/<agent-session>-reports/report-final.md
- Correct stop_session.sh report cleanup claim to reflect manual cleanup
- Clarify onboarding brief mechanism under onboarding handshake protocol

.agents/MULTI_AGENT_RULES.md

@@ -122,12 +122,14 @@ To ensure that agents running in TMUX environments do not lose debug logs or pre
 - **Core Principle**: To prevent TUI character loss, truncation, and layout breakage during sequential input typing, all collaborative workflows must favor file-based markdown communication.
 - **Rules & Protocols**:
   - **Exception**: Extremely simple prompts (e.g., "Re-evaluate", "Check status", "Proceed") of 1 or 2 lines may be sent directly via tmux input buffers.
-  - **Task Delegation**: All detailed task briefs, specifications, and instructions must be written to a local Markdown file (e.g., `.mam/reports/brief-<job_id>.md` or a workspace path) first. The sender then issues a simple trigger command: `"Read <file_path> and execute."`
-  - **Result Reporting & Feedback**: All detailed review results, design proposals, implementation reports, and audit comments must be saved as Markdown files. To separate human-readable documents from the machine job registry (`.mam/jobs/`), every agent must save its outputs under `.mam/reports/<tmux_session_name>/` (using the full tmux session name matching the `name` field in `.mam/agent-sessions.yaml`, e.g., `.mam/reports/<workspace_slug>-creator-<agent>/report-<job_id>.md`) to ensure strict isolation across multiple roles/instances.
-  - **Cleanup & Retention Contract**:
-    - Files under `.mam/reports/` are audit-trail artifacts.
-    - These folders should be cleaned up automatically during `stop_session.sh` when a session is gracefully stopped or purged (`--purge-conversation`).
-    - Durable outcomes (such as final design plans, review verdicts, or security audit reports) that require version control must be explicitly copied to tracked directory paths (specifically under `.agents/reports/<tmux_session_name>/` or `docs/reports/`) to preserve collaborative audit trails in version history, instead of remaining in the gitignored `.mam/` runtime tree.
+  - **Task Delegation**:
+    - *Manual path*: Detailed task briefs may be written to a local Markdown file (e.g., `.mam/reports/brief-<job_id>.md` or a workspace path) first. The sender then issues a simple trigger command: `"Read <file_path> and execute."`
+    - *Automated path*: The automated job runner (`multi-agent-mux-delegate-job submit`) automatically provisions the brief at `.mam/jobs/<job_id>/brief.md` and sends a short pointer instruction to the agent.
+  - **Result Reporting & Feedback**:
+    - *Manual/Durable reviews*: Detailed reviews, design proposals, or audit reports must be saved under `.mam/reports/<tmux_session_name>/report-<job_id>.md`.
+    - *Automated job reports*: Automated execution results are saved directly to `.mam/jobs/<job_id>/<agent-session>-reports/report-final.md` as transient files.
+    - *Versioned promotions*: Any final design plans, review verdicts, or security audit reports that require version control must be explicitly copied to tracked directory paths (specifically under `.agents/reports/<tmux_session_name>/` or `docs/reports/`).
+  - **Cleanup & Retention Contract**: Files under `.mam/jobs/<job_id>/` and `.mam/reports/` are transient audit-trail artifacts. While durable outcomes are committed to version control under `.agents/reports/`, ephemeral directory trees can be cleaned up manually as needed; `stop_session.sh` does not automatically purge these report trees during session exit.
 
 ### ⏱️ Timeout Configuration & Alignment Rules
 - **Job Execution Limits (`timeout_sec` & `idle_timeout_sec`)**: Each job independently manages its overall execution timeout (`timeout_sec`, default 3600s) and idle timeout without receiving messages (`idle_timeout_sec`, default 120s).
@@ -157,7 +159,8 @@ Newly spawned Team Leader agents must align their context using the `--onboard`
    ```bash
    bash .agents/skills/multi-agent-mux-create/scripts/create_session.sh --workspace "$(pwd)" --agent <agent> --role <role> --onboard
    ```
-2. **Orienting the Agent**: The agent session starts up and automatically receives a registered job instructing it to:
+   This automated onboarding workflow registers a job, provisioning the brief under `.mam/jobs/<job_id>/brief.md` and sending a short pointer to the agent session.
+2. **Orienting the Agent**: The agent session starts up and automatically receives the registered onboarding brief instructing it to:
    - Read `README.md` and `.agents/MULTI_AGENT_RULES.md` to align with design principles and constraints.
    - Run `git status` and `git diff` to analyze active modifications.
    - Read `.mam/agent-sessions.yaml` to identify other running agents and verify its own assigned `role`.