diff --git a/CHANGELOG.md b/CHANGELOG.md
index 3cbb32ef..bc95c544 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -7,6 +7,41 @@ and this project uses [independent versioning](README.md#versioning) for Framewo
 
 ---
 
+## Framework 4.35.0 / CLI 3.33.0 — 2026-07-13
+
+### Added (Framework)
+
+- **`AUDIT-ROUNDS-PATTERN.md` governance doc (EN/es/zh-CN) ([#341]).** Documents the per-round
+  audit layout (sibling of `FOLLOW-UPS-BACKLOG-PATTERN.md`): the `--round <label>` namespacing, the
+  resulting subfolder layout, telemetry `round:` tagging, and back-compat. Listed in
+  `QUICK-REFERENCE.md`.
+- **`AGENT-RULES.md` §12 (Audit Checkpoint) — two new bullets (EN/es/zh-CN).** "Audit a stable
+  state" (#345 — PR → CI green → `--prepare` → launch auditors) and "Multi-round audits" (#341).
+
+### Changed (Framework)
+
+- **Audit skills thread `--round <label>` ([#341]).** `straymark-audit-prompt`,
+  `straymark-audit-execute`, and `straymark-audit-review` (all four shipped copies each —
+  `.agent`/`.claude`/`.gemini`/`.codex`) now document the per-round subfolder paths and pass the
+  round label through the triad. `straymark-audit-review` also corrects the stale "CLI rejects
+  re-audit" note to describe the new append-a-new-round behavior. `straymark-audit-prompt` gained
+  the #345 "audit a stable state" note.
+
+### Added (CLI)
+
+- **`straymark charter audit --round <label>` ([#341]).** Optional per-round namespacing for
+  multi-phase Charters that need more than one external-audit round. The whole triad (prompt,
+  `report-*.md`, `review.md`) is written under `.straymark/audits/<CHARTER-ID>/<label>/`, so rounds
+  never overwrite each other and the non-recursive `report-*.md` glob scopes to exactly the current
+  round — fixing the cross-round report pollution into `review.md`/telemetry. The label is validated
+  as a filesystem-safe slug. Each merged `external_audit` entry carries a `round:` field, and
+  `--merge-into` **appends** a new round to an already-populated telemetry block (instead of bailing)
+  as long as the round label is new; re-merging the same round, or merging into a populated block
+  without a round label, is still rejected. Omit `--round` for single-round Charters (flat layout,
+  fully back-compatible).
+
+---
+
 ## CLI 3.32.0 — 2026-07-12
 
 ### Added (CLI)
diff --git a/Cargo.lock b/Cargo.lock
index ed0d6718..71601603 100644
--- a/Cargo.lock
+++ b/Cargo.lock
@@ -2573,7 +2573,7 @@ dependencies = [
 
 [[package]]
 name = "straymark-cli"
-version = "3.32.0"
+version = "3.33.0"
 dependencies = [
  "anyhow",
  "arborist-metrics",
diff --git a/README.md b/README.md
index 50cb8db6..c9e9c9ff 100644
--- a/README.md
+++ b/README.md
@@ -277,8 +277,8 @@ StrayMark uses independent version tags for each component:
 
 | Component | Tag prefix | Example | Includes |
 | --- | --- | --- | --- |
-| Framework | `fw-` | `fw-4.34.0` | Templates (12 types), governance, directives, Charter template + schema |
-| CLI | `cli-` | `cli-3.32.0` | The `straymark` binary |
+| Framework | `fw-` | `fw-4.35.0` | Templates (12 types), governance, directives, Charter template + schema |
+| CLI | `cli-` | `cli-3.33.0` | The `straymark` binary |
 | Loom (EXPERIMENTAL) | `loom-` | `loom-0.4.2` | The `straymark-loom` visualization server, downloaded on demand by `straymark loom serve` |
 
 Check installed versions with `straymark status` or `straymark about`.
diff --git a/cli/Cargo.toml b/cli/Cargo.toml
index a3ed813f..e21faa57 100644
--- a/cli/Cargo.toml
+++ b/cli/Cargo.toml
@@ -1,6 +1,6 @@
 [package]
 name = "straymark-cli"
-version = "3.32.0"
+version = "3.33.0"
 edition = "2021"
 description = "CLI for StrayMark — the cognitive discipline your AI-assisted projects need"
 license = "MIT"
diff --git a/cli/src/commands/charter/audit.rs b/cli/src/commands/charter/audit.rs
index 5fee8304..3580c860 100644
--- a/cli/src/commands/charter/audit.rs
+++ b/cli/src/commands/charter/audit.rs
@@ -142,6 +142,7 @@ pub fn run(
     calibrate: bool,
     finalize: bool,
     merge_into: Option<&str>,
+    round: Option<&str>,
 ) -> Result<()> {
     // --merge-into only makes sense with --merge-reports (or the deprecated
     // --finalize that aliases to it).
@@ -149,6 +150,10 @@ pub fn run(
         bail!("--merge-into is only valid with --merge-reports (or the deprecated --finalize)");
     }
 
+    // #341: an optional round label namespaces the audit triad. Validate it as a
+    // filesystem-safe slug before it becomes a path component.
+    let round = round.map(sanitize_round_label).transpose()?;
+
     let resolved = utils::resolve_project_root(path)
         .ok_or_else(|| anyhow!("StrayMark not installed. Run 'straymark init' first."))?;
     let project_root = &resolved.path;
@@ -170,7 +175,13 @@ pub fn run(
     // v1 canonical path: .straymark/audits/<CHARTER-ID>/. The audit-prompt is
     // written directly to this dir; reports land here as report-*.md; the
     // future review.md consolidated by the audit-review skill lands here too.
-    let audit_dir = straymark_dir.join("audits").join(&canonical_id);
+    // #341: with --round <label>, the whole triad is namespaced under a
+    // per-round subfolder so multi-phase audit rounds don't collide, and the
+    // non-recursive report-*.md glob scopes to exactly this round.
+    let audit_dir = match &round {
+        Some(label) => straymark_dir.join("audits").join(&canonical_id).join(label),
+        None => straymark_dir.join("audits").join(&canonical_id),
+    };
     utils::ensure_dir(&audit_dir)?;
 
     let range_explicit = range.is_some();
@@ -209,6 +220,7 @@ pub fn run(
             &charter,
             &canonical_id,
             merge_into.map(Path::new),
+            round.as_deref(),
         );
     }
 
@@ -220,13 +232,22 @@ pub fn run(
             &charter,
             &canonical_id,
             merge_into.map(Path::new),
+            round.as_deref(),
         );
     }
 
     // Default action: prepare. The --prepare flag is accepted for
     // self-documenting invocations but is also the implicit default.
     let _ = prepare;
-    run_prepare(project_root, &straymark_dir, &audit_dir, &charter, &range, range_explicit)
+    run_prepare(
+        project_root,
+        &straymark_dir,
+        &audit_dir,
+        &charter,
+        &range,
+        range_explicit,
+        round.as_deref(),
+    )
 }
 
 // ── Step 1: prepare ────────────────────────────────────────────────────────
@@ -238,12 +259,16 @@ fn run_prepare(
     charter: &Charter,
     range: &str,
     range_explicit: bool,
+    round: Option<&str>,
 ) -> Result<()> {
     println!(
-        "{} {} ({})",
+        "{} {} ({}{})",
         "PREPARE".cyan().bold(),
         "audit prompt".bold(),
-        charter.frontmatter.charter_id.dimmed()
+        charter.frontmatter.charter_id.dimmed(),
+        round
+            .map(|r| format!(", round {}", r).dimmed().to_string())
+            .unwrap_or_default()
     );
 
     // #208: a multi-batch Charter whose earlier phases already merged to the base
@@ -303,8 +328,9 @@ fn run_prepare(
     println!(
         "    1. Open one or more auditor CLIs (gemini-cli, claude-cli, copilot-cli, etc.)"
     );
+    let round_arg = round.map(|r| format!(" --round {r}")).unwrap_or_default();
     println!("       in this repo and invoke {} in each.",
-        format!("/straymark-audit-execute {}", charter.frontmatter.charter_id).cyan());
+        format!("/straymark-audit-execute {}{}", charter.frontmatter.charter_id, round_arg).cyan());
     println!(
         "       Recommended: at least 2 auditors of different model families."
     );
@@ -323,7 +349,7 @@ fn run_prepare(
     );
     println!(
         "       return to this agent and run: {}",
-        format!("/straymark-audit-review {}", charter.frontmatter.charter_id).cyan()
+        format!("/straymark-audit-review {}{}", charter.frontmatter.charter_id, round_arg).cyan()
     );
     println!("    4. The review skill consolidates the reports and merges YAML");
     println!("       into telemetry.");
@@ -347,6 +373,7 @@ fn run_merge_reports(
     charter: &Charter,
     canonical_id: &str,
     merge_into: Option<&Path>,
+    round: Option<&str>,
 ) -> Result<()> {
     println!(
         "{} {} ({})",
@@ -431,11 +458,12 @@ fn run_merge_reports(
     println!();
 
     if let Some(target) = merge_into {
-        merge_external_audit_into(target, &auditor_summaries, canonical_id)?;
+        merge_external_audit_into(target, &auditor_summaries, canonical_id, round)?;
         println!(
-            "  {} Merged external_audit array into {}",
+            "  {} Merged external_audit array into {}{}",
             "✔".green().bold(),
-            relative_path(project_root, target).display()
+            relative_path(project_root, target).display(),
+            round.map(|r| format!(" (round {r})")).unwrap_or_default(),
         );
         println!();
         println!(
@@ -446,7 +474,7 @@ fn run_merge_reports(
         println!("  {}", "external_audit YAML — paste into telemetry:".bold());
         println!("  {}", "(charter_telemetry.external_audit array)".dimmed());
         println!();
-        println!("{}", render_external_audit_yaml(&auditor_summaries, canonical_id));
+        println!("{}", render_external_audit_yaml(&auditor_summaries, canonical_id, round));
         println!();
     }
     Ok(())
@@ -467,6 +495,7 @@ fn merge_external_audit_into(
     telemetry_path: &Path,
     auditor_summaries: &[AuditorSummary],
     canonical_charter_id: &str,
+    round: Option<&str>,
 ) -> Result<()> {
     if !telemetry_path.exists() {
         bail!(
@@ -517,17 +546,37 @@ fn merge_external_audit_into(
         }
     };
 
+    // #341: a round label lets multiple audit rounds coexist in one telemetry
+    // file. When the array is already populated we APPEND the new round instead
+    // of bailing — provided a round label is given and this exact round isn't
+    // already recorded (the same-round guard prevents silent duplication).
     if matches!(placeholder, ExternalAuditState::Populated) {
-        bail!(
-            "{} already has a populated `external_audit:` block. Re-audit\n  \
-             (appending to an existing array) is not supported in v0. Re-run\n  \
-             `straymark charter audit <id> --merge-reports` (without --merge-into)\n  \
-             to print the new YAML, then merge manually if you want to append.",
-            telemetry_path.display()
-        );
+        let Some(label) = round else {
+            bail!(
+                "{} already has a populated `external_audit:` block. Appending needs a\n  \
+                 round label so the rounds stay distinguishable: re-run with\n  \
+                 `--round <label> --merge-into ...` to add a new round, or omit\n  \
+                 --merge-into to print the YAML and merge manually.",
+                telemetry_path.display()
+            );
+        };
+        if external_audit_has_round(existing_external_audit, label) {
+            bail!(
+                "{} already has external_audit entries for round `{}` — refusing to\n  \
+                 duplicate them. Use a different --round label, or remove that round's\n  \
+                 entries by hand before re-merging.",
+                telemetry_path.display(),
+                label
+            );
+        }
+        let rendered = render_external_audit_yaml(auditor_summaries, canonical_charter_id, round);
+        content = append_to_external_audit_block(&content, &rendered)?;
+        std::fs::write(telemetry_path, &content)
+            .with_context(|| format!("Failed to write {}", telemetry_path.display()))?;
+        return Ok(());
     }
 
-    let rendered = render_external_audit_yaml(auditor_summaries, canonical_charter_id);
+    let rendered = render_external_audit_yaml(auditor_summaries, canonical_charter_id, round);
 
     match placeholder {
         ExternalAuditState::Missing => {
@@ -543,7 +592,7 @@ fn merge_external_audit_into(
         ExternalAuditState::EmptyPlaceholder => {
             content = replace_empty_external_audit_placeholder(&content, &rendered)?;
         }
-        ExternalAuditState::Populated => unreachable!("guarded above"),
+        ExternalAuditState::Populated => unreachable!("handled above"),
     }
 
     std::fs::write(telemetry_path, &content)
@@ -907,10 +956,17 @@ impl AuditorSummary {
     }
 }
 
-fn render_external_audit_yaml(summaries: &[AuditorSummary], canonical_charter_id: &str) -> String {
+fn render_external_audit_yaml(
+    summaries: &[AuditorSummary],
+    canonical_charter_id: &str,
+    round: Option<&str>,
+) -> String {
     let mut out = String::new();
     for (idx, s) in summaries.iter().enumerate() {
         out.push_str(&format!("    - auditor: \"{}\"\n", s.auditor));
+        if let Some(label) = round {
+            out.push_str(&format!("      round: \"{}\"\n", label));
+        }
         out.push_str(&format!("      findings_total: {}\n", s.findings_total));
         out.push_str("      findings_by_category:\n");
         for cat in [
@@ -942,6 +998,122 @@ fn render_external_audit_yaml(summaries: &[AuditorSummary], canonical_charter_id
 
 // ── Helpers ────────────────────────────────────────────────────────────────
 
+/// Validate a `--round` label as a filesystem-safe slug before it becomes a
+/// path component (#341). Rejects empty, `.`/`..`, over-long, path separators,
+/// spaces, and leading non-alphanumerics — so it can never escape the Charter's
+/// audit directory or collide with a hidden file.
+fn sanitize_round_label(label: &str) -> Result<String> {
+    let trimmed = label.trim();
+    if trimmed.is_empty() {
+        bail!("--round label must not be empty");
+    }
+    if trimmed == "." || trimmed == ".." {
+        bail!("--round label `{}` is not a valid directory name", trimmed);
+    }
+    if trimmed.chars().count() > 64 {
+        bail!("--round label is too long (max 64 chars): `{}`", trimmed);
+    }
+    if !trimmed
+        .chars()
+        .all(|c| c.is_ascii_alphanumeric() || matches!(c, '.' | '_' | '-'))
+    {
+        bail!(
+            "--round label `{}` must be a simple slug (letters, digits, '.', '_', '-') — \
+             no path separators or spaces.",
+            trimmed
+        );
+    }
+    if !trimmed.chars().next().unwrap().is_ascii_alphanumeric() {
+        bail!("--round label `{}` must start with a letter or digit.", trimmed);
+    }
+    Ok(trimmed.to_string())
+}
+
+/// True when the parsed `external_audit` sequence already contains an entry
+/// tagged with the given round label — the same-round guard for append (#341).
+fn external_audit_has_round(external_audit: Option<&serde_yaml::Value>, label: &str) -> bool {
+    external_audit
+        .and_then(|v| v.as_sequence())
+        .map(|seq| {
+            seq.iter().any(|entry| {
+                entry
+                    .as_mapping()
+                    .and_then(|m| m.get(serde_yaml::Value::String("round".into())))
+                    .and_then(|r| r.as_str())
+                    == Some(label)
+            })
+        })
+        .unwrap_or(false)
+}
+
+/// Append a rendered `external_audit` block (4-space `- ` items) to an existing
+/// populated block-style array, right after its last entry line (#341). Bails on
+/// inline flow form (`external_audit: [ ... ]`) or a missing/empty block — those
+/// fall back to a manual-merge instruction upstream.
+fn append_to_external_audit_block(content: &str, rendered: &str) -> Result<String> {
+    let lines: Vec<&str> = content.split_inclusive('\n').collect();
+
+    let mut key_idx = None;
+    for (i, line) in lines.iter().enumerate() {
+        let after_indent = line
+            .trim_end_matches(['\n', '\r'])
+            .trim_start_matches([' ', '\t']);
+        if let Some(rest) = after_indent.strip_prefix("external_audit:") {
+            let rest = rest.trim();
+            if rest.is_empty() || rest.starts_with('#') {
+                key_idx = Some(i);
+                break;
+            }
+            bail!(
+                "external_audit is written in inline flow form; this CLI appends only to \
+                 block-style arrays. Omit --merge-into to print the YAML and merge the new \
+                 round manually."
+            );
+        }
+    }
+    let key_idx = key_idx.ok_or_else(|| {
+        anyhow!("could not locate the `external_audit:` key in the telemetry to append to.")
+    })?;
+    let key_indent = indent_width(lines[key_idx]);
+
+    // The sequence body is the run of following lines that are blank or indented
+    // deeper than the key; the insertion point is after its last non-blank line.
+    let mut insert_after = key_idx;
+    for (j, line) in lines.iter().enumerate().skip(key_idx + 1) {
+        if line.trim().is_empty() {
+            continue;
+        }
+        if indent_width(line) > key_indent {
+            insert_after = j;
+        } else {
+            break;
+        }
+    }
+    if insert_after == key_idx {
+        bail!("`external_audit:` block appears empty; expected a populated array to append to.");
+    }
+
+    let mut out = String::with_capacity(content.len() + rendered.len());
+    for (k, line) in lines.iter().enumerate() {
+        out.push_str(line);
+        if k == insert_after {
+            if !out.ends_with('\n') {
+                out.push('\n');
+            }
+            out.push_str(rendered);
+            if !out.ends_with('\n') {
+                out.push('\n');
+            }
+        }
+    }
+    Ok(out)
+}
+
+/// Count leading spaces/tabs — the indentation width of a YAML line.
+fn indent_width(line: &str) -> usize {
+    line.chars().take_while(|c| *c == ' ' || *c == '\t').count()
+}
+
 fn canonical_charter_id(charter_id: &str) -> String {
     // CHARTER-NN[-slug] → CHARTER-NN.
     charter_id
@@ -1186,4 +1358,111 @@ prompt_used: prompts/auditor-primary.prompt.md
         assert_eq!(s.audit_quality.as_deref(), Some("high"));
         assert_eq!(s.prompt_used, "prompts/auditor-primary.prompt.md");
     }
+
+    // ── #341: per-round namespacing ───────────────────────────────────────
+
+    #[test]
+    fn sanitize_round_label_accepts_slugs_rejects_unsafe() {
+        assert_eq!(sanitize_round_label("fase-1").unwrap(), "fase-1");
+        assert_eq!(sanitize_round_label("  round_2.a  ").unwrap(), "round_2.a");
+        let long = "x".repeat(65);
+        for bad in ["", ".", "..", "a/b", "a b", "-lead", "café", long.as_str()] {
+            assert!(sanitize_round_label(bad).is_err(), "should reject {bad:?}");
+        }
+    }
+
+    fn summary(name: &str) -> Vec<AuditorSummary> {
+        vec![AuditorSummary {
+            auditor: name.into(),
+            findings_total: 1,
+            findings_by_category: Default::default(),
+            audit_quality: None,
+            prompt_used: String::new(),
+        }]
+    }
+
+    #[test]
+    fn render_external_audit_yaml_tags_round_when_present() {
+        let with = render_external_audit_yaml(&summary("gpt-5"), "CHARTER-01", Some("fase-1"));
+        assert!(with.contains("round: \"fase-1\""), "got:\n{with}");
+        let without = render_external_audit_yaml(&summary("gpt-5"), "CHARTER-01", None);
+        assert!(!without.contains("round:"), "got:\n{without}");
+    }
+
+    #[test]
+    fn external_audit_has_round_detects_label() {
+        let yaml: serde_yaml::Value =
+            serde_yaml::from_str("- auditor: a\n  round: fase-1\n- auditor: b\n  round: fase-2\n")
+                .unwrap();
+        assert!(external_audit_has_round(Some(&yaml), "fase-1"));
+        assert!(external_audit_has_round(Some(&yaml), "fase-2"));
+        assert!(!external_audit_has_round(Some(&yaml), "fase-3"));
+        assert!(!external_audit_has_round(None, "fase-1"));
+    }
+
+    #[test]
+    fn append_to_external_audit_block_inserts_after_last_entry() {
+        let content = "charter_telemetry:\n  closed_at: \"2026-07-13\"\n  external_audit:\n    - auditor: \"gpt-5\"\n      round: \"fase-1\"\n      findings_total: 3\n  outcome:\n    completed_as_planned: true\n";
+        let rendered = "    - auditor: \"claude\"\n      round: \"fase-2\"\n      findings_total: 1\n";
+        let out = append_to_external_audit_block(content, rendered).unwrap();
+        let ea = out.find("external_audit:").unwrap();
+        let claude = out.find("claude").unwrap();
+        let outcome = out.find("outcome:").unwrap();
+        assert!(ea < claude && claude < outcome, "append must land inside the block:\n{out}");
+        let parsed: serde_yaml::Value = serde_yaml::from_str(&out).unwrap();
+        let seq = parsed["charter_telemetry"]["external_audit"].as_sequence().unwrap();
+        assert_eq!(seq.len(), 2);
+    }
+
+    #[test]
+    fn append_to_external_audit_block_rejects_inline_flow() {
+        let content = "charter_telemetry:\n  external_audit: [ {auditor: x} ]\n";
+        assert!(append_to_external_audit_block(content, "    - auditor: y\n").is_err());
+    }
+
+    fn write_telemetry(dir: &Path, external_audit: &str) -> PathBuf {
+        let p = dir.join("CHARTER-01.telemetry.yaml");
+        std::fs::write(
+            &p,
+            format!(
+                "charter_telemetry:\n  charter_id: \"CHARTER-01\"\n  closed_at: \"2026-07-13\"\n{external_audit}  outcome:\n    completed_as_planned: true\n"
+            ),
+        )
+        .unwrap();
+        p
+    }
+
+    #[test]
+    fn merge_external_audit_into_appends_second_round() {
+        let tmp = tempfile::TempDir::new().unwrap();
+        let p = write_telemetry(tmp.path(), "  external_audit: []\n");
+        merge_external_audit_into(&p, &summary("gpt-5"), "CHARTER-01", Some("fase-1")).unwrap();
+        merge_external_audit_into(&p, &summary("claude"), "CHARTER-01", Some("fase-2")).unwrap();
+        let content = std::fs::read_to_string(&p).unwrap();
+        let parsed: serde_yaml::Value = serde_yaml::from_str(&content).unwrap();
+        let ea = &parsed["charter_telemetry"]["external_audit"];
+        assert_eq!(ea.as_sequence().unwrap().len(), 2);
+        assert!(external_audit_has_round(Some(ea), "fase-1"));
+        assert!(external_audit_has_round(Some(ea), "fase-2"));
+    }
+
+    #[test]
+    fn merge_external_audit_into_rejects_same_round_twice() {
+        let tmp = tempfile::TempDir::new().unwrap();
+        let p = write_telemetry(tmp.path(), "  external_audit: []\n");
+        merge_external_audit_into(&p, &summary("gpt-5"), "CHARTER-01", Some("fase-1")).unwrap();
+        let err = merge_external_audit_into(&p, &summary("claude"), "CHARTER-01", Some("fase-1"))
+            .unwrap_err();
+        assert!(err.to_string().contains("round `fase-1`"), "got: {err}");
+    }
+
+    #[test]
+    fn merge_external_audit_into_populated_without_round_bails() {
+        let tmp = tempfile::TempDir::new().unwrap();
+        let p = write_telemetry(tmp.path(), "  external_audit: []\n");
+        merge_external_audit_into(&p, &summary("gpt-5"), "CHARTER-01", Some("fase-1")).unwrap();
+        let err =
+            merge_external_audit_into(&p, &summary("claude"), "CHARTER-01", None).unwrap_err();
+        assert!(err.to_string().contains("round label"), "got: {err}");
+    }
 }
diff --git a/cli/src/main.rs b/cli/src/main.rs
index 75b840b3..7c458544 100644
--- a/cli/src/main.rs
+++ b/cli/src/main.rs
@@ -611,6 +611,14 @@ enum CharterCommands {
         /// (file already has external_audit) is rejected with a clear error.
         #[arg(long)]
         merge_into: Option<String>,
+        /// Optional round label for multi-phase audits (#341). Namespaces the
+        /// whole triad under .straymark/audits/CHARTER-NN/<label>/ so a Charter
+        /// audited across more than one round (e.g. one per code-heavy phase)
+        /// does not collide on flat paths, and the report-*.md glob scopes to
+        /// this round only. Omit for single-round Charters (flat, unchanged).
+        /// The label must be a simple slug ([A-Za-z0-9._-], no path separators).
+        #[arg(long)]
+        round: Option<String>,
         /// Project directory (default: current directory)
         #[arg(long = "path", default_value = ".")]
         path: String,
@@ -877,6 +885,7 @@ fn main() {
                 calibrate,
                 finalize,
                 merge_into,
+                round,
                 path,
             } => commands::charter::audit::run(
                 &path,
@@ -887,6 +896,7 @@ fn main() {
                 calibrate,
                 finalize,
                 merge_into.as_deref(),
+                round.as_deref(),
             ),
             CharterCommands::RefreshSuggest {
                 module,
diff --git a/cli/tests/charter_audit_test.rs b/cli/tests/charter_audit_test.rs
index b49ab92f..cd484153 100644
--- a/cli/tests/charter_audit_test.rs
+++ b/cli/tests/charter_audit_test.rs
@@ -119,6 +119,54 @@ fn audit_unknown_charter_fails() {
         .stderr(predicate::str::contains("CHARTER-99 not found"));
 }
 
+#[test]
+fn audit_prepare_round_namespaces_prompt_under_subfolder() {
+    // #341: --round <label> namespaces the whole triad under
+    // .straymark/audits/CHARTER-NN/<label>/ so multi-phase rounds don't collide.
+    if !bash_available() {
+        eprintln!("skipping: git not available");
+        return;
+    }
+    let dir = TempDir::new().unwrap();
+    setup_straymark(dir.path());
+    write_charter(dir.path());
+    init_repo_with_diff(dir.path());
+
+    cargo_bin_cmd!("straymark")
+        .args(["charter", "audit", "CHARTER-01", "--prepare", "--round", "fase-1", "--path"])
+        .arg(dir.path().to_str().unwrap())
+        .assert()
+        .success()
+        .stdout(predicate::str::contains("round fase-1"))
+        // The next-step guidance threads the round through.
+        .stdout(predicate::str::contains("--round fase-1"));
+
+    // Prompt lands in the round subfolder, NOT at the flat charter root.
+    let round_path = audit_dir(dir.path(), "CHARTER-01")
+        .join("fase-1")
+        .join("audit-prompt.md");
+    assert!(round_path.exists(), "expected prompt at {}", round_path.display());
+    let flat_path = audit_dir(dir.path(), "CHARTER-01").join("audit-prompt.md");
+    assert!(
+        !flat_path.exists(),
+        "round-scoped prepare must not write the flat prompt"
+    );
+}
+
+#[test]
+fn audit_prepare_rejects_unsafe_round_label() {
+    let dir = TempDir::new().unwrap();
+    setup_straymark(dir.path());
+    write_charter(dir.path());
+
+    cargo_bin_cmd!("straymark")
+        .args(["charter", "audit", "CHARTER-01", "--prepare", "--round", "../escape", "--path"])
+        .arg(dir.path().to_str().unwrap())
+        .assert()
+        .failure()
+        .stderr(predicate::str::contains("simple slug"));
+}
+
 #[test]
 fn audit_prepare_writes_unified_prompt_to_canonical_location() {
     if !bash_available() {
diff --git a/dist/.agent/workflows/straymark-audit-execute.md b/dist/.agent/workflows/straymark-audit-execute.md
index 4e823384..8e69a810 100644
--- a/dist/.agent/workflows/straymark-audit-execute.md
+++ b/dist/.agent/workflows/straymark-audit-execute.md
@@ -23,14 +23,14 @@ The skill is the second step of the v1 audit cycle:
 Two positional arguments: `<CHARTER-ID>` and an optional `<AUDITOR-SLUG>` — e.g. `/straymark-audit-execute CHARTER-06 deepseek-v4-pro`. The second argument is the operator-provided auditor identity (see step 2); it is never inferred from the CLI you are running in.
 
 **Case A — Charter provided** (`/straymark-audit-execute CHARTER-04 [AUDITOR-SLUG]`):
-Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/`.
+Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/` — or, when the operator passed `--round <label>` (a multi-round audit), `.straymark/audits/CHARTER-04/<label>/`. Every path below (prompt, report) gains the same `/<label>/` segment, and the same `--round <label>` is threaded through to `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
 
 **Case B — Charter omitted** (`/straymark-audit-execute`):
 Auto-discover pending prompts. Resolve the auditor identity (step 2 — from the argument or the operator) and produce its slug. Then:
 
 ```bash
 # List all audit prompts that exist
-ls .straymark/audits/*/audit-prompt.md 2>/dev/null
+ls .straymark/audits/*/audit-prompt.md .straymark/audits/*/*/audit-prompt.md 2>/dev/null
 ```
 
 For each found `.straymark/audits/<CHARTER-ID>/audit-prompt.md`, check whether a report from this model already exists at `.straymark/audits/<CHARTER-ID>/report-<slug>.md`. The set of "pending" prompts is the ones WITHOUT a corresponding report.
diff --git a/dist/.agent/workflows/straymark-audit-prompt.md b/dist/.agent/workflows/straymark-audit-prompt.md
index df91a8e0..4bd3d3a9 100644
--- a/dist/.agent/workflows/straymark-audit-prompt.md
+++ b/dist/.agent/workflows/straymark-audit-prompt.md
@@ -12,6 +12,8 @@ Use this skill when the developer agreed to run an external audit at the Charter
 
 The Charter should be in `in-progress` or `declared` status — auditing closed Charters is allowed but atypical (warn the operator and proceed only on confirmation).
 
+> **Audit a stable state.** Generate the prompt only when the state under audit is stable: the PR's CI is green, the working tree is clean, and commits are pushed. `--prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix (or uncommitted work changes the tree), the prompt goes stale and the auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) when the tree is dirty or has unpushed commits.
+
 ## Instructions
 
 ### 1. Resolve the Charter
@@ -36,6 +38,8 @@ The CLI writes the resolved prompt to:
 .straymark/audits/<CHARTER-ID>/audit-prompt.md
 ```
 
+> **Multi-round audits (`--round`).** For a multi-phase Charter audited in more than one round (e.g. one external-audit round per code-heavy phase), pass `--round <label>` so the whole triad (prompt, reports, review) is namespaced under `.straymark/audits/<CHARTER-ID>/<label>/` instead of the flat charter root. This keeps rounds from overwriting each other and scopes the `report-*.md` glob to just this round. Omit `--round` for single-round Charters. Thread the same `--round <label>` through `/straymark-audit-execute` and `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 The prompt is self-contained: it embeds the Charter content, the originating AILOGs, the git diff over the resolved range (default `origin/main..HEAD`, falls back to `HEAD~1..HEAD` if no upstream is reachable), and the discipline rules (REGLA ABSOLUTA — SOLO LECTURA, evidence-citation, severity calibration). The prompt template lifts the seven universal sections from Sentinel's pre-StrayMark audit skill and parameterizes the project-specific hardcodes.
 
 > Multi-batch Charters — pass an explicit `--range`. When auditing one phase of a Charter whose earlier phases already merged to the base branch, the default `origin/main..HEAD` excludes the already-merged commits and the prompt silently under-covers the phase. Pass `--range <charter-first-commit>..HEAD` so all of the phase's commits are in the diff. The CLI prints a warning when it detects completed batches in the Charter's Batch Ledger and no explicit range was given.
diff --git a/dist/.agent/workflows/straymark-audit-review.md b/dist/.agent/workflows/straymark-audit-review.md
index cc7a0287..c43e7635 100644
--- a/dist/.agent/workflows/straymark-audit-review.md
+++ b/dist/.agent/workflows/straymark-audit-review.md
@@ -18,6 +18,8 @@ After the operator has commissioned the audits in N auditor-side CLIs (each runn
 
 If only some audits have completed, **do not proceed** — invoking the skill with incomplete reports produces a partial consolidated analysis. Verify with the operator that all the CLIs they opened have finished writing their reports under `.straymark/audits/<CHARTER-ID>/report-*.md`.
 
+> **Multi-round audits (`--round`).** If the operator passed `--round <label>` (a Charter audited across more than one round), every path in this skill gains a `/<label>/` segment: reports at `.straymark/audits/<CHARTER-ID>/<label>/report-*.md`, the consolidated `review.md` under the same subfolder, and the CLI merge step run with `--round <label>`. Consolidate only the reports in that subfolder. Omit `--round` for single-round Charters. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 ## Instructions
 
 ### 1. Resolve the Charter and verify report set
@@ -198,11 +200,11 @@ Run the CLI's merge step to validate all reports against the schema and emit the
 **Branch A — telemetry exists** (operator already ran `straymark charter close` for this Charter, perhaps without audit, and is now adding audit findings retroactively):
 
 ```bash
-straymark charter audit <CHARTER-ID> --merge-reports \
+straymark charter audit <CHARTER-ID> --merge-reports [--round <label>] \
   --merge-into .straymark/charters/<CHARTER-ID>.telemetry.yaml
 ```
 
-The CLI appends the `external_audit:` array to the telemetry YAML. The CLI v1 deliberately rejects re-audit (file already has `external_audit:`) — if that fires, surface the message to the operator. Manual append is the fallback.
+The CLI appends the `external_audit:` array to the telemetry YAML. If the telemetry already has a populated `external_audit:` block, the CLI rejects the merge **unless** you pass `--round <label>` with a round not already recorded — then it appends the new round's entries (each tagged with `round:`) instead of bailing. Re-merging the *same* round is still rejected to avoid duplication; manual append is the fallback.
 
 **Branch B — telemetry does NOT exist** (the typical case: operator audits BEFORE closing):
 
diff --git a/dist/.claude/skills/straymark-audit-execute/SKILL.md b/dist/.claude/skills/straymark-audit-execute/SKILL.md
index ca26242c..3193d1f1 100644
--- a/dist/.claude/skills/straymark-audit-execute/SKILL.md
+++ b/dist/.claude/skills/straymark-audit-execute/SKILL.md
@@ -26,14 +26,14 @@ The skill is the second step of the v1 audit cycle:
 Two positional arguments: `<CHARTER-ID>` and an optional `<AUDITOR-SLUG>` — e.g. `/straymark-audit-execute CHARTER-06 deepseek-v4-pro`. The second argument is the operator-provided auditor identity (see step 2); it is never inferred from the CLI you are running in.
 
 **Case A — Charter provided** (`/straymark-audit-execute CHARTER-04 [AUDITOR-SLUG]`):
-Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/`.
+Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/` — or, when the operator passed `--round <label>` (a multi-round audit), `.straymark/audits/CHARTER-04/<label>/`. Every path below (prompt, report) gains the same `/<label>/` segment, and the same `--round <label>` is threaded through to `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
 
 **Case B — Charter omitted** (`/straymark-audit-execute`):
 Auto-discover pending prompts. Resolve the auditor identity (step 2 — from the argument or the operator) and produce its slug. Then:
 
 ```bash
 # List all audit prompts that exist
-ls .straymark/audits/*/audit-prompt.md 2>/dev/null
+ls .straymark/audits/*/audit-prompt.md .straymark/audits/*/*/audit-prompt.md 2>/dev/null
 ```
 
 For each found `.straymark/audits/<CHARTER-ID>/audit-prompt.md`, check whether a report from this model already exists at `.straymark/audits/<CHARTER-ID>/report-<slug>.md`. The set of "pending" prompts is the ones WITHOUT a corresponding report.
diff --git a/dist/.claude/skills/straymark-audit-prompt/SKILL.md b/dist/.claude/skills/straymark-audit-prompt/SKILL.md
index c5c63491..53d23157 100644
--- a/dist/.claude/skills/straymark-audit-prompt/SKILL.md
+++ b/dist/.claude/skills/straymark-audit-prompt/SKILL.md
@@ -14,6 +14,8 @@ Use this skill when the developer agreed to run an external audit at the Charter
 
 The Charter should be in `in-progress` or `declared` status — auditing closed Charters is allowed but atypical (warn the operator and proceed only on confirmation).
 
+> **Audit a stable state.** Generate the prompt only when the state under audit is stable: the PR's CI is green, the working tree is clean, and commits are pushed. `--prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix (or uncommitted work changes the tree), the prompt goes stale and the auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) when the tree is dirty or has unpushed commits.
+
 ## Instructions
 
 ### 1. Resolve the Charter
@@ -38,6 +40,8 @@ The CLI writes the resolved prompt to:
 .straymark/audits/<CHARTER-ID>/audit-prompt.md
 ```
 
+> **Multi-round audits (`--round`).** For a multi-phase Charter audited in more than one round (e.g. one external-audit round per code-heavy phase), pass `--round <label>` so the whole triad (prompt, reports, review) is namespaced under `.straymark/audits/<CHARTER-ID>/<label>/` instead of the flat charter root. This keeps rounds from overwriting each other and scopes the `report-*.md` glob to just this round. Omit `--round` for single-round Charters. Thread the same `--round <label>` through `/straymark-audit-execute` and `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 The prompt is self-contained: it embeds the Charter content, the originating AILOGs, the git diff over the resolved range (default `origin/main..HEAD`, falls back to `HEAD~1..HEAD` if no upstream is reachable), and the discipline rules (REGLA ABSOLUTA — SOLO LECTURA, evidence-citation, severity calibration). The prompt template lifts the seven universal sections from Sentinel's pre-StrayMark audit skill and parameterizes the project-specific hardcodes.
 
 > **Multi-batch Charters — pass an explicit `--range`.** When auditing one phase of a Charter whose earlier phases already merged to the base branch, the default `origin/main..HEAD` *excludes* the already-merged commits and the prompt silently under-covers the phase. Pass `--range <charter-first-commit>..HEAD` so all of the phase's commits are in the diff. The CLI prints a warning when it detects completed batches in the Charter's Batch Ledger and no explicit range was given.
diff --git a/dist/.claude/skills/straymark-audit-review/SKILL.md b/dist/.claude/skills/straymark-audit-review/SKILL.md
index 766c7c2a..45e04506 100644
--- a/dist/.claude/skills/straymark-audit-review/SKILL.md
+++ b/dist/.claude/skills/straymark-audit-review/SKILL.md
@@ -21,6 +21,8 @@ After the operator has commissioned the audits in N auditor-side CLIs (each runn
 
 If only some audits have completed, **do not proceed** — invoking the skill with incomplete reports produces a partial consolidated analysis. Verify with the operator that all the CLIs they opened have finished writing their reports under `.straymark/audits/<CHARTER-ID>/report-*.md`.
 
+> **Multi-round audits (`--round`).** If the operator passed `--round <label>` (a Charter audited across more than one round), every path in this skill gains a `/<label>/` segment: reports at `.straymark/audits/<CHARTER-ID>/<label>/report-*.md`, the consolidated `review.md` under the same subfolder, and the CLI merge step run with `--round <label>`. Consolidate only the reports in that subfolder. Omit `--round` for single-round Charters. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 ## Instructions
 
 ### 1. Resolve the Charter and verify report set
@@ -201,11 +203,11 @@ Run the CLI's merge step to validate all reports against the schema and emit the
 **Branch A — telemetry exists** (operator already ran `straymark charter close` for this Charter, perhaps without audit, and is now adding audit findings retroactively):
 
 ```bash
-straymark charter audit <CHARTER-ID> --merge-reports \
+straymark charter audit <CHARTER-ID> --merge-reports [--round <label>] \
   --merge-into .straymark/charters/<CHARTER-ID>.telemetry.yaml
 ```
 
-The CLI appends the `external_audit:` array to the telemetry YAML. The CLI v1 deliberately rejects re-audit (file already has `external_audit:`) — if that fires, surface the message to the operator. Manual append is the fallback.
+The CLI appends the `external_audit:` array to the telemetry YAML. If the telemetry already has a populated `external_audit:` block, the CLI rejects the merge **unless** you pass `--round <label>` with a round not already recorded — then it appends the new round's entries (each tagged with `round:`) instead of bailing. Re-merging the *same* round is still rejected to avoid duplication; manual append is the fallback.
 
 **Branch B — telemetry does NOT exist** (the typical case: operator audits BEFORE closing):
 
diff --git a/dist/.codex/skills/straymark-audit-execute/SKILL.md b/dist/.codex/skills/straymark-audit-execute/SKILL.md
index cdd665d6..372228f4 100644
--- a/dist/.codex/skills/straymark-audit-execute/SKILL.md
+++ b/dist/.codex/skills/straymark-audit-execute/SKILL.md
@@ -24,14 +24,14 @@ The skill is the second step of the v1 audit cycle:
 Two positional arguments: `<CHARTER-ID>` and an optional `<AUDITOR-SLUG>` — e.g. `/straymark-audit-execute CHARTER-06 deepseek-v4-pro`. The second argument is the operator-provided auditor identity (see step 2); it is never inferred from the CLI you are running in.
 
 **Case A — Charter provided** (`/straymark-audit-execute CHARTER-04 [AUDITOR-SLUG]`):
-Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/`.
+Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/` — or, when the operator passed `--round <label>` (a multi-round audit), `.straymark/audits/CHARTER-04/<label>/`. Every path below (prompt, report) gains the same `/<label>/` segment, and the same `--round <label>` is threaded through to `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
 
 **Case B — Charter omitted** (`/straymark-audit-execute`):
 Auto-discover pending prompts. Resolve the auditor identity (step 2 — from the argument or the operator) and produce its slug. Then:
 
 ```bash
 # List all audit prompts that exist
-ls .straymark/audits/*/audit-prompt.md 2>/dev/null
+ls .straymark/audits/*/audit-prompt.md .straymark/audits/*/*/audit-prompt.md 2>/dev/null
 ```
 
 For each found `.straymark/audits/<CHARTER-ID>/audit-prompt.md`, check whether a report from this model already exists at `.straymark/audits/<CHARTER-ID>/report-<slug>.md`. The set of "pending" prompts is the ones WITHOUT a corresponding report.
diff --git a/dist/.codex/skills/straymark-audit-prompt/SKILL.md b/dist/.codex/skills/straymark-audit-prompt/SKILL.md
index ce1a8b3f..def2bbaf 100644
--- a/dist/.codex/skills/straymark-audit-prompt/SKILL.md
+++ b/dist/.codex/skills/straymark-audit-prompt/SKILL.md
@@ -13,6 +13,8 @@ Use this skill when the developer agreed to run an external audit at the Charter
 
 The Charter should be in `in-progress` or `declared` status — auditing closed Charters is allowed but atypical (warn the operator and proceed only on confirmation).
 
+> **Audit a stable state.** Generate the prompt only when the state under audit is stable: the PR's CI is green, the working tree is clean, and commits are pushed. `--prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix (or uncommitted work changes the tree), the prompt goes stale and the auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) when the tree is dirty or has unpushed commits.
+
 ## Instructions
 
 ### 1. Resolve the Charter
@@ -37,6 +39,8 @@ The CLI writes the resolved prompt to:
 .straymark/audits/<CHARTER-ID>/audit-prompt.md
 ```
 
+> **Multi-round audits (`--round`).** For a multi-phase Charter audited in more than one round (e.g. one external-audit round per code-heavy phase), pass `--round <label>` so the whole triad (prompt, reports, review) is namespaced under `.straymark/audits/<CHARTER-ID>/<label>/` instead of the flat charter root. This keeps rounds from overwriting each other and scopes the `report-*.md` glob to just this round. Omit `--round` for single-round Charters. Thread the same `--round <label>` through `/straymark-audit-execute` and `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 The prompt is self-contained: it embeds the Charter content, the originating AILOGs, the git diff over the resolved range (default `origin/main..HEAD`, falls back to `HEAD~1..HEAD` if no upstream is reachable), and the discipline rules (REGLA ABSOLUTA — SOLO LECTURA, evidence-citation, severity calibration). The prompt template lifts the seven universal sections from Sentinel's pre-StrayMark audit skill and parameterizes the project-specific hardcodes.
 
 > **Multi-batch Charters — pass an explicit `--range`.** When auditing one phase of a Charter whose earlier phases already merged to the base branch, the default `origin/main..HEAD` *excludes* the already-merged commits and the prompt silently under-covers the phase. Pass `--range <charter-first-commit>..HEAD` so all of the phase's commits are in the diff. The CLI prints a warning when it detects completed batches in the Charter's Batch Ledger and no explicit range was given.
diff --git a/dist/.codex/skills/straymark-audit-review/SKILL.md b/dist/.codex/skills/straymark-audit-review/SKILL.md
index 1376979a..8d4fce80 100644
--- a/dist/.codex/skills/straymark-audit-review/SKILL.md
+++ b/dist/.codex/skills/straymark-audit-review/SKILL.md
@@ -19,6 +19,8 @@ After the operator has commissioned the audits in N auditor-side CLIs (each runn
 
 If only some audits have completed, **do not proceed** — invoking the skill with incomplete reports produces a partial consolidated analysis. Verify with the operator that all the CLIs they opened have finished writing their reports under `.straymark/audits/<CHARTER-ID>/report-*.md`.
 
+> **Multi-round audits (`--round`).** If the operator passed `--round <label>` (a Charter audited across more than one round), every path in this skill gains a `/<label>/` segment: reports at `.straymark/audits/<CHARTER-ID>/<label>/report-*.md`, the consolidated `review.md` under the same subfolder, and the CLI merge step run with `--round <label>`. Consolidate only the reports in that subfolder. Omit `--round` for single-round Charters. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 ## Instructions
 
 ### 1. Resolve the Charter and verify report set
@@ -199,11 +201,11 @@ Run the CLI's merge step to validate all reports against the schema and emit the
 **Branch A — telemetry exists** (operator already ran `straymark charter close` for this Charter, perhaps without audit, and is now adding audit findings retroactively):
 
 ```bash
-straymark charter audit <CHARTER-ID> --merge-reports \
+straymark charter audit <CHARTER-ID> --merge-reports [--round <label>] \
   --merge-into .straymark/charters/<CHARTER-ID>.telemetry.yaml
 ```
 
-The CLI appends the `external_audit:` array to the telemetry YAML. The CLI v1 deliberately rejects re-audit (file already has `external_audit:`) — if that fires, surface the message to the operator. Manual append is the fallback.
+The CLI appends the `external_audit:` array to the telemetry YAML. If the telemetry already has a populated `external_audit:` block, the CLI rejects the merge **unless** you pass `--round <label>` with a round not already recorded — then it appends the new round's entries (each tagged with `round:`) instead of bailing. Re-merging the *same* round is still rejected to avoid duplication; manual append is the fallback.
 
 **Branch B — telemetry does NOT exist** (the typical case: operator audits BEFORE closing):
 
diff --git a/dist/.gemini/skills/straymark-audit-execute/SKILL.md b/dist/.gemini/skills/straymark-audit-execute/SKILL.md
index cdd665d6..372228f4 100644
--- a/dist/.gemini/skills/straymark-audit-execute/SKILL.md
+++ b/dist/.gemini/skills/straymark-audit-execute/SKILL.md
@@ -24,14 +24,14 @@ The skill is the second step of the v1 audit cycle:
 Two positional arguments: `<CHARTER-ID>` and an optional `<AUDITOR-SLUG>` — e.g. `/straymark-audit-execute CHARTER-06 deepseek-v4-pro`. The second argument is the operator-provided auditor identity (see step 2); it is never inferred from the CLI you are running in.
 
 **Case A — Charter provided** (`/straymark-audit-execute CHARTER-04 [AUDITOR-SLUG]`):
-Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/`.
+Use the literal Charter value. Construct the audit dir path: `.straymark/audits/CHARTER-04/` — or, when the operator passed `--round <label>` (a multi-round audit), `.straymark/audits/CHARTER-04/<label>/`. Every path below (prompt, report) gains the same `/<label>/` segment, and the same `--round <label>` is threaded through to `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
 
 **Case B — Charter omitted** (`/straymark-audit-execute`):
 Auto-discover pending prompts. Resolve the auditor identity (step 2 — from the argument or the operator) and produce its slug. Then:
 
 ```bash
 # List all audit prompts that exist
-ls .straymark/audits/*/audit-prompt.md 2>/dev/null
+ls .straymark/audits/*/audit-prompt.md .straymark/audits/*/*/audit-prompt.md 2>/dev/null
 ```
 
 For each found `.straymark/audits/<CHARTER-ID>/audit-prompt.md`, check whether a report from this model already exists at `.straymark/audits/<CHARTER-ID>/report-<slug>.md`. The set of "pending" prompts is the ones WITHOUT a corresponding report.
diff --git a/dist/.gemini/skills/straymark-audit-prompt/SKILL.md b/dist/.gemini/skills/straymark-audit-prompt/SKILL.md
index ce1a8b3f..def2bbaf 100644
--- a/dist/.gemini/skills/straymark-audit-prompt/SKILL.md
+++ b/dist/.gemini/skills/straymark-audit-prompt/SKILL.md
@@ -13,6 +13,8 @@ Use this skill when the developer agreed to run an external audit at the Charter
 
 The Charter should be in `in-progress` or `declared` status — auditing closed Charters is allowed but atypical (warn the operator and proceed only on confirmation).
 
+> **Audit a stable state.** Generate the prompt only when the state under audit is stable: the PR's CI is green, the working tree is clean, and commits are pushed. `--prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix (or uncommitted work changes the tree), the prompt goes stale and the auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) when the tree is dirty or has unpushed commits.
+
 ## Instructions
 
 ### 1. Resolve the Charter
@@ -37,6 +39,8 @@ The CLI writes the resolved prompt to:
 .straymark/audits/<CHARTER-ID>/audit-prompt.md
 ```
 
+> **Multi-round audits (`--round`).** For a multi-phase Charter audited in more than one round (e.g. one external-audit round per code-heavy phase), pass `--round <label>` so the whole triad (prompt, reports, review) is namespaced under `.straymark/audits/<CHARTER-ID>/<label>/` instead of the flat charter root. This keeps rounds from overwriting each other and scopes the `report-*.md` glob to just this round. Omit `--round` for single-round Charters. Thread the same `--round <label>` through `/straymark-audit-execute` and `/straymark-audit-review`. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 The prompt is self-contained: it embeds the Charter content, the originating AILOGs, the git diff over the resolved range (default `origin/main..HEAD`, falls back to `HEAD~1..HEAD` if no upstream is reachable), and the discipline rules (REGLA ABSOLUTA — SOLO LECTURA, evidence-citation, severity calibration). The prompt template lifts the seven universal sections from Sentinel's pre-StrayMark audit skill and parameterizes the project-specific hardcodes.
 
 > **Multi-batch Charters — pass an explicit `--range`.** When auditing one phase of a Charter whose earlier phases already merged to the base branch, the default `origin/main..HEAD` *excludes* the already-merged commits and the prompt silently under-covers the phase. Pass `--range <charter-first-commit>..HEAD` so all of the phase's commits are in the diff. The CLI prints a warning when it detects completed batches in the Charter's Batch Ledger and no explicit range was given.
diff --git a/dist/.gemini/skills/straymark-audit-review/SKILL.md b/dist/.gemini/skills/straymark-audit-review/SKILL.md
index 1376979a..8d4fce80 100644
--- a/dist/.gemini/skills/straymark-audit-review/SKILL.md
+++ b/dist/.gemini/skills/straymark-audit-review/SKILL.md
@@ -19,6 +19,8 @@ After the operator has commissioned the audits in N auditor-side CLIs (each runn
 
 If only some audits have completed, **do not proceed** — invoking the skill with incomplete reports produces a partial consolidated analysis. Verify with the operator that all the CLIs they opened have finished writing their reports under `.straymark/audits/<CHARTER-ID>/report-*.md`.
 
+> **Multi-round audits (`--round`).** If the operator passed `--round <label>` (a Charter audited across more than one round), every path in this skill gains a `/<label>/` segment: reports at `.straymark/audits/<CHARTER-ID>/<label>/report-*.md`, the consolidated `review.md` under the same subfolder, and the CLI merge step run with `--round <label>`. Consolidate only the reports in that subfolder. Omit `--round` for single-round Charters. See `.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md`.
+
 ## Instructions
 
 ### 1. Resolve the Charter and verify report set
@@ -199,11 +201,11 @@ Run the CLI's merge step to validate all reports against the schema and emit the
 **Branch A — telemetry exists** (operator already ran `straymark charter close` for this Charter, perhaps without audit, and is now adding audit findings retroactively):
 
 ```bash
-straymark charter audit <CHARTER-ID> --merge-reports \
+straymark charter audit <CHARTER-ID> --merge-reports [--round <label>] \
   --merge-into .straymark/charters/<CHARTER-ID>.telemetry.yaml
 ```
 
-The CLI appends the `external_audit:` array to the telemetry YAML. The CLI v1 deliberately rejects re-audit (file already has `external_audit:`) — if that fires, surface the message to the operator. Manual append is the fallback.
+The CLI appends the `external_audit:` array to the telemetry YAML. If the telemetry already has a populated `external_audit:` block, the CLI rejects the merge **unless** you pass `--round <label>` with a round not already recorded — then it appends the new round's entries (each tagged with `round:`) instead of bailing. Re-merging the *same* round is still rejected to avoid duplication; manual append is the fallback.
 
 **Branch B — telemetry does NOT exist** (the typical case: operator audits BEFORE closing):
 
diff --git a/dist/.straymark/00-governance/AGENT-RULES.md b/dist/.straymark/00-governance/AGENT-RULES.md
index 97f2960e..a9c0164b 100644
--- a/dist/.straymark/00-governance/AGENT-RULES.md
+++ b/dist/.straymark/00-governance/AGENT-RULES.md
@@ -378,6 +378,8 @@ These are heuristics, not rigid rules — you are close to the context, refine t
 - The checkpoint **does not** block any subsequent action. If the developer ignores it and runs `charter close`, close proceeds normally — there is no enforcement and there will not be (this is a permanent v0+v1 design decision; see `Propuesta/straymark-audit-skills.md` §2.2).
 - The checkpoint is **not** counted in any quality metric. There is no "% Charters audited" KPI in `straymark metrics` — by design, to avoid creating an incentive to inflate the audit count.
 - If the developer accepts the audit, the workflow proceeds via three skills in sequence: `/straymark-audit-prompt` (writes the unified prompt at the canonical path) → `/straymark-audit-execute` × N (one per auditor-side CLI the operator opens — these run in those CLIs, not in the main agent) → `/straymark-audit-review` (consolidates N reports inline into `.straymark/audits/<id>/review.md` and merges the YAML into telemetry). Operators never copy/paste prompts or reports — file exchange happens via canonical paths under `.straymark/audits/`.
+- **Audit a stable state (#345).** Generate the prompt only when the state under audit is stable — the PR's CI is green, the working tree is clean, and commits are pushed. `charter audit --prepare` embeds the git diff at generation time, so if in-flight CI later forces a fix the prompt goes stale and auditors review a revision that no longer exists. Sequence: **PR → CI green → `--prepare` → launch auditors.** The CLI warns (does not block) on a dirty tree or unpushed commits.
+- **Multi-round audits (#341).** A Charter audited across more than one round (e.g. one round per code-heavy phase) namespaces each round with `--prepare --round <label>`, writing the triad under `.straymark/audits/<id>/<label>/` so rounds do not collide and the `report-*.md` glob scopes per round. See [`AUDIT-ROUNDS-PATTERN.md`](AUDIT-ROUNDS-PATTERN.md).
 
 ---
 
@@ -412,4 +414,4 @@ When a project accumulates a high volume of AILOGs across multiple Charters and
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md b/dist/.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md
new file mode 100644
index 00000000..3aae3856
--- /dev/null
+++ b/dist/.straymark/00-governance/AUDIT-ROUNDS-PATTERN.md
@@ -0,0 +1,85 @@
+# Audit Rounds Pattern - StrayMark
+
+> Per-round namespacing for Charters that need more than one external-audit round.
+
+**Languages**: English | [Español](i18n/es/AUDIT-ROUNDS-PATTERN.md) | [简体中文](i18n/zh-CN/AUDIT-ROUNDS-PATTERN.md)
+
+---
+
+## Status
+
+**Since fw-4.35.0 / cli-3.33.0** (Issue #341). Optional and back-compatible: single-round Charters need nothing new.
+
+## The problem
+
+The external-audit subsystem (`straymark charter audit`, `/straymark-audit-execute`, `/straymark-audit-review`) originally assumed **exactly one audit round per Charter**. But multi-phase Charters are a first-class concept, and phase-scoped auditing is the recommended practice for them. When one Charter needs **more than one** external-audit round (e.g. one per code-heavy phase), the flat, single-round layout breaks in two ways:
+
+1. **Fixed flat paths overwrite.** Every round wrote `audit-prompt.md`, `report-*.md`, and `review.md` to the same `.straymark/audits/<CHARTER-ID>/` directory, so a second round silently clobbered the first's prompt, and preserving history needed a manual `git mv` archival dance.
+2. **Cross-round glob pollution.** The `report-*.md` glob (both `--merge-reports` and the review skill) is flat and non-recursive. If a prior round's reports sat flat with any name still matching `report-*.md`, they were pulled into the **current** round's consolidated `review.md` and telemetry — mixing rounds.
+
+## The pattern: `--round <label>`
+
+Pass an optional round label to namespace the whole triad under a per-round subfolder:
+
+```bash
+# Round 1 — security phase
+straymark charter audit CHARTER-01 --prepare --round fase-1 --range <phase-1-first-commit>..HEAD
+# → .straymark/audits/CHARTER-01/fase-1/audit-prompt.md
+
+# ...auditors write reports into the same subfolder, then:
+straymark charter audit CHARTER-01 --merge-reports --round fase-1 \
+  --merge-into .straymark/charters/CHARTER-01.telemetry.yaml
+```
+
+The label must be a simple slug (`[A-Za-z0-9._-]`, starts alphanumeric, no path separators or spaces) — it becomes a directory name.
+
+### Resulting layout
+
+```
+.straymark/audits/CHARTER-01/
+  fase-1/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-2/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-3/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+```
+
+Because each round lives in its own subfolder and the glob is non-recursive, rounds never overwrite each other (fixes problem 1) and the merge scopes to exactly the current round's reports (fixes problem 2).
+
+### Threading the label
+
+The same `--round <label>` flows through the whole triad — the CLI's `--prepare` guidance and the skills echo it:
+
+- `/straymark-audit-prompt <CHARTER-ID>` → `charter audit --prepare --round <label>`
+- `/straymark-audit-execute <CHARTER-ID> --round <label>` → reads/writes under the subfolder
+- `/straymark-audit-review <CHARTER-ID> --round <label>` → consolidates only that subfolder
+
+## Telemetry: multiple rounds coexist
+
+Each `external_audit` entry merged with `--round` carries a `round:` field, so rounds stay distinguishable inside one telemetry file:
+
+```yaml
+charter_telemetry:
+  external_audit:
+    - auditor: "gpt-5-2-codex"
+      round: "fase-1"
+      findings_total: 5
+      # ...
+    - auditor: "claude-sonnet-5"
+      round: "fase-2"
+      findings_total: 2
+      # ...
+```
+
+`--merge-into` **appends** a new round to an already-populated `external_audit:` block instead of bailing — provided the round label is new. Re-merging the **same** round is still rejected (the same-round guard prevents silent duplication); merging into a populated block **without** a round label is also rejected (rounds must stay distinguishable). Use a fresh `--round <label>` per round.
+
+## Back-compat
+
+Omit `--round` entirely and everything behaves exactly as before fw-4.35.0: flat paths under `.straymark/audits/<CHARTER-ID>/`, a single `external_audit` block with no `round:` field, and `--merge-into` rejecting any populated array. Single-round Charters (the common case) need no change.
+
+## Related
+
+- [AGENT-RULES.md §12](AGENT-RULES.md) — the Audit Checkpoint that frames when to run an external audit, plus the stable-state and multi-round bullets.
+- [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) — sibling pattern doc (registry layout convention this one mirrors).
+
+---
+
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/C4-DIAGRAM-GUIDE.md b/dist/.straymark/00-governance/C4-DIAGRAM-GUIDE.md
index a3ea2765..2fb5f74c 100644
--- a/dist/.straymark/00-governance/C4-DIAGRAM-GUIDE.md
+++ b/dist/.straymark/00-governance/C4-DIAGRAM-GUIDE.md
@@ -234,4 +234,4 @@ Use a Level 1 (Context) diagram to illustrate:
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/DOCUMENTATION-POLICY.md b/dist/.straymark/00-governance/DOCUMENTATION-POLICY.md
index 4d9b66ab..54049aeb 100644
--- a/dist/.straymark/00-governance/DOCUMENTATION-POLICY.md
+++ b/dist/.straymark/00-governance/DOCUMENTATION-POLICY.md
@@ -319,4 +319,4 @@ See also [ADR-2025-01-20-001] for architectural context.
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/QUICK-REFERENCE.md b/dist/.straymark/00-governance/QUICK-REFERENCE.md
index 2f26d9c3..383643e4 100644
--- a/dist/.straymark/00-governance/QUICK-REFERENCE.md
+++ b/dist/.straymark/00-governance/QUICK-REFERENCE.md
@@ -259,7 +259,8 @@ Mark `review_required: true` when:
 |---------|----------|
 | Follow-ups backlog (first-class registry + native `followups` CLI) *(fw-4.10.0+, first-class fw-4.21.0+)* | [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) |
 | Polish Charter as debt-detection ("surface declaration without wiring" anti-pattern) *(fw-4.18.0+)* | [POLISH-CHARTER-PATTERN.md](POLISH-CHARTER-PATTERN.md) |
+| External audit rounds (per-round namespacing for multi-phase Charters) *(fw-4.35.0+)* | [AUDIT-ROUNDS-PATTERN.md](AUDIT-ROUNDS-PATTERN.md) |
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/es/AGENT-RULES.md b/dist/.straymark/00-governance/i18n/es/AGENT-RULES.md
index cfa9a848..fc896bbd 100644
--- a/dist/.straymark/00-governance/i18n/es/AGENT-RULES.md
+++ b/dist/.straymark/00-governance/i18n/es/AGENT-RULES.md
@@ -378,6 +378,8 @@ Son heurísticas, no reglas rígidas — estás cerca del contexto, afínalas co
 - El checkpoint **no** bloquea ninguna acción posterior. Si el developer lo ignora y corre `charter close`, close procede normalmente — no hay enforcement y no lo habrá (decisión de diseño v0+v1 permanente; ver `Propuesta/straymark-audit-skills.md` §2.2).
 - El checkpoint **no** se cuenta en ninguna métrica de calidad. No hay KPI "% Charters auditados" en `straymark metrics` — por diseño, para evitar incentivos a inflar el conteo.
 - Si el developer acepta la auditoría, el workflow procede vía tres skills en secuencia: `/straymark-audit-prompt` (escribe el prompt unificado en el path canónico) → `/straymark-audit-execute` × N (una por CLI auditora que abra el operador — estas corren en esas CLIs, no en el agente principal) → `/straymark-audit-review` (consolida N reports inline en `.straymark/audits/<id>/review.md` y mergea el YAML en la telemetría). Los operadores nunca copian/pegan prompts ni reports — el intercambio de archivos sucede vía paths canónicos bajo `.straymark/audits/`.
+- **Audita un estado estable (#345).** Genera el prompt solo cuando el estado auditado es estable — la CI del PR en verde, el árbol de trabajo limpio y los commits pusheados. `charter audit --prepare` embebe el git diff al momento de generarlo, así que si la CI en vuelo luego fuerza un fix, el prompt queda obsoleto y los auditores revisan una revisión que ya no existe. Secuencia: **PR → CI verde → `--prepare` → lanzar auditores.** El CLI avisa (no bloquea) si el árbol está sucio o hay commits sin pushear.
+- **Auditorías multi-ronda (#341).** Un Charter auditado en más de una ronda (p. ej. una ronda por fase con mucho código) namespacea cada ronda con `--prepare --round <label>`, escribiendo la tríada bajo `.straymark/audits/<id>/<label>/` para que las rondas no colisionen y el glob `report-*.md` se acote por ronda. Ver [`AUDIT-ROUNDS-PATTERN.md`](AUDIT-ROUNDS-PATTERN.md).
 
 ---
 
@@ -412,4 +414,4 @@ Cuando un proyecto acumula un volumen alto de AILOGs a lo largo de múltiples Ch
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/es/AUDIT-ROUNDS-PATTERN.md b/dist/.straymark/00-governance/i18n/es/AUDIT-ROUNDS-PATTERN.md
new file mode 100644
index 00000000..2f2f1c79
--- /dev/null
+++ b/dist/.straymark/00-governance/i18n/es/AUDIT-ROUNDS-PATTERN.md
@@ -0,0 +1,85 @@
+# Patrón de Rondas de Auditoría - StrayMark
+
+> Namespacing por ronda para Charters que necesitan más de una ronda de auditoría externa.
+
+**Idiomas**: [English](../../AUDIT-ROUNDS-PATTERN.md) | Español | [简体中文](../zh-CN/AUDIT-ROUNDS-PATTERN.md)
+
+---
+
+## Estado
+
+**Desde fw-4.35.0 / cli-3.33.0** (Issue #341). Opcional y retrocompatible: los Charters de una sola ronda no necesitan nada nuevo.
+
+## El problema
+
+El subsistema de auditoría externa (`straymark charter audit`, `/straymark-audit-execute`, `/straymark-audit-review`) asumía originalmente **exactamente una ronda de auditoría por Charter**. Pero los Charters multi-fase son un concepto de primera clase, y la auditoría acotada por fase es la práctica recomendada para ellos. Cuando un Charter necesita **más de una** ronda de auditoría externa (p. ej. una por fase con mucho código), el layout plano de una sola ronda se rompe de dos formas:
+
+1. **Los paths planos fijos se sobrescriben.** Cada ronda escribía `audit-prompt.md`, `report-*.md` y `review.md` en el mismo directorio `.straymark/audits/<CHARTER-ID>/`, así que una segunda ronda pisaba silenciosamente el prompt de la primera, y preservar el historial requería un baile manual de archivado con `git mv`.
+2. **Contaminación cross-ronda del glob.** El glob `report-*.md` (tanto en `--merge-reports` como en la skill de review) es plano y no-recursivo. Si los reports de una ronda previa quedaban planos con cualquier nombre que aún matcheara `report-*.md`, eran arrastrados al `review.md` consolidado y a la telemetría de la ronda **actual** — mezclando rondas.
+
+## El patrón: `--round <label>`
+
+Pasa una etiqueta de ronda opcional para namespacear la tríada completa bajo un subfolder por ronda:
+
+```bash
+# Ronda 1 — fase de seguridad
+straymark charter audit CHARTER-01 --prepare --round fase-1 --range <primer-commit-fase-1>..HEAD
+# → .straymark/audits/CHARTER-01/fase-1/audit-prompt.md
+
+# ...los auditores escriben sus reports en el mismo subfolder, luego:
+straymark charter audit CHARTER-01 --merge-reports --round fase-1 \
+  --merge-into .straymark/charters/CHARTER-01.telemetry.yaml
+```
+
+La etiqueta debe ser un slug simple (`[A-Za-z0-9._-]`, empieza con alfanumérico, sin separadores de path ni espacios) — se convierte en un nombre de directorio.
+
+### Layout resultante
+
+```
+.straymark/audits/CHARTER-01/
+  fase-1/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-2/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-3/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+```
+
+Como cada ronda vive en su propio subfolder y el glob es no-recursivo, las rondas nunca se sobrescriben (arregla el problema 1) y el merge se acota exactamente a los reports de la ronda actual (arregla el problema 2).
+
+### Threading de la etiqueta
+
+El mismo `--round <label>` fluye por toda la tríada — la guía de `--prepare` del CLI y las skills lo repiten:
+
+- `/straymark-audit-prompt <CHARTER-ID>` → `charter audit --prepare --round <label>`
+- `/straymark-audit-execute <CHARTER-ID> --round <label>` → lee/escribe bajo el subfolder
+- `/straymark-audit-review <CHARTER-ID> --round <label>` → consolida solo ese subfolder
+
+## Telemetría: múltiples rondas coexisten
+
+Cada entrada de `external_audit` mergeada con `--round` lleva un campo `round:`, así que las rondas quedan distinguibles dentro de un mismo archivo de telemetría:
+
+```yaml
+charter_telemetry:
+  external_audit:
+    - auditor: "gpt-5-2-codex"
+      round: "fase-1"
+      findings_total: 5
+      # ...
+    - auditor: "claude-sonnet-5"
+      round: "fase-2"
+      findings_total: 2
+      # ...
+```
+
+`--merge-into` **hace append** de una nueva ronda a un bloque `external_audit:` ya poblado en lugar de rechazar — siempre que la etiqueta de ronda sea nueva. Re-mergear la **misma** ronda sigue siendo rechazado (el guard de misma-ronda previene la duplicación silenciosa); mergear en un bloque poblado **sin** etiqueta de ronda también se rechaza (las rondas deben quedar distinguibles). Usa un `--round <label>` nuevo por ronda.
+
+## Retrocompatibilidad
+
+Omite `--round` por completo y todo se comporta exactamente como antes de fw-4.35.0: paths planos bajo `.straymark/audits/<CHARTER-ID>/`, un solo bloque `external_audit` sin campo `round:`, y `--merge-into` rechazando cualquier array poblado. Los Charters de una sola ronda (el caso común) no necesitan cambio.
+
+## Relacionado
+
+- [AGENT-RULES.md §12](AGENT-RULES.md) — el Punto de Control de Auditoría que enmarca cuándo correr una auditoría externa, más los bullets de estado-estable y multi-ronda.
+- [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) — pattern doc hermano (la convención de layout de registro que este espeja).
+
+---
+
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/es/C4-DIAGRAM-GUIDE.md b/dist/.straymark/00-governance/i18n/es/C4-DIAGRAM-GUIDE.md
index beaa0492..ea0e84ed 100644
--- a/dist/.straymark/00-governance/i18n/es/C4-DIAGRAM-GUIDE.md
+++ b/dist/.straymark/00-governance/i18n/es/C4-DIAGRAM-GUIDE.md
@@ -234,4 +234,4 @@ Usar un diagrama de Nivel 1 (Contexto) para ilustrar:
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/es/DOCUMENTATION-POLICY.md b/dist/.straymark/00-governance/i18n/es/DOCUMENTATION-POLICY.md
index 9574630a..a103c7ec 100644
--- a/dist/.straymark/00-governance/i18n/es/DOCUMENTATION-POLICY.md
+++ b/dist/.straymark/00-governance/i18n/es/DOCUMENTATION-POLICY.md
@@ -312,4 +312,4 @@ Ver también [ADR-2025-01-20-001] para contexto arquitectónico.
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/es/QUICK-REFERENCE.md b/dist/.straymark/00-governance/i18n/es/QUICK-REFERENCE.md
index 42fe07b6..c447f0c7 100644
--- a/dist/.straymark/00-governance/i18n/es/QUICK-REFERENCE.md
+++ b/dist/.straymark/00-governance/i18n/es/QUICK-REFERENCE.md
@@ -231,7 +231,8 @@ Marcar `review_required: true` cuando:
 |--------|-----------|
 | Backlog de follow-ups (registry de primera clase + CLI nativo `followups`) *(fw-4.10.0+, primera clase fw-4.21.0+)* | [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) |
 | Polish Charter como detección de deuda (anti-patrón "declaración de superficie sin cableado") *(fw-4.18.0+)* | [POLISH-CHARTER-PATTERN.md](POLISH-CHARTER-PATTERN.md) |
+| Rondas de auditoría externa (namespacing por ronda para Charters multi-fase) *(fw-4.35.0+)* | [AUDIT-ROUNDS-PATTERN.md](AUDIT-ROUNDS-PATTERN.md) |
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/zh-CN/AGENT-RULES.md b/dist/.straymark/00-governance/i18n/zh-CN/AGENT-RULES.md
index 4e701345..53b9c049 100644
--- a/dist/.straymark/00-governance/i18n/zh-CN/AGENT-RULES.md
+++ b/dist/.straymark/00-governance/i18n/zh-CN/AGENT-RULES.md
@@ -373,6 +373,8 @@ confidence: high | medium | low
 - 检查点**不**阻塞任何后续操作。如果 developer 忽略它并运行 `charter close`，close 正常进行——没有强制执行，将来也不会有（这是 v0+v1 永久设计决策；见 `Propuesta/straymark-audit-skills.md` §2.2）。
 - 检查点**不**计入任何质量度量。`straymark metrics` 中没有"已审计 Charter 百分比"KPI——按设计，避免产生虚胖审计计数的激励。
 - 如果 developer 接受审计，工作流通过三个 skills 依次推进：`/straymark-audit-prompt`（在规范路径写入统一 prompt）→ `/straymark-audit-execute` × N（每个操作员打开的审计员 CLI 一个 — 这些运行在那些 CLI 中，不在主代理中）→ `/straymark-audit-review`（在 `.straymark/audits/<id>/review.md` 中内联合并 N 个 reports 并将 YAML 合并到遥测）。操作员从不复制/粘贴 prompts 或 reports — 文件交换通过 `.straymark/audits/` 下的规范路径进行。
+- **审计一个稳定状态（#345）。** 仅在受审状态稳定时生成 prompt — PR 的 CI 为绿、工作树干净且 commits 已推送。`charter audit --prepare` 在生成时嵌入 git diff，因此若进行中的 CI 之后强制修复，prompt 会过时，审计员会审查一个不再存在的修订版。顺序：**PR → CI 绿 → `--prepare` → 启动审计员。** 当工作树脏或有未推送 commits 时 CLI 会警告（不阻断）。
+- **多轮审计（#341）。** 跨多轮审计的 Charter（例如每个代码密集阶段一轮）用 `--prepare --round <label>` 为每轮命名，将三件套写入 `.straymark/audits/<id>/<label>/`，使各轮不冲突且 `report-*.md` 通配按轮限定。参见 [`AUDIT-ROUNDS-PATTERN.md`](AUDIT-ROUNDS-PATTERN.md)。
 
 ---
 
@@ -407,4 +409,4 @@ confidence: high | medium | low
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/zh-CN/AUDIT-ROUNDS-PATTERN.md b/dist/.straymark/00-governance/i18n/zh-CN/AUDIT-ROUNDS-PATTERN.md
new file mode 100644
index 00000000..36b11fb8
--- /dev/null
+++ b/dist/.straymark/00-governance/i18n/zh-CN/AUDIT-ROUNDS-PATTERN.md
@@ -0,0 +1,85 @@
+# 审计轮次模式 - StrayMark
+
+> 为需要多于一轮外部审计的 Charter 提供按轮命名。
+
+**语言**: [English](../../AUDIT-ROUNDS-PATTERN.md) | [Español](../es/AUDIT-ROUNDS-PATTERN.md) | 简体中文
+
+---
+
+## 状态
+
+**自 fw-4.35.0 / cli-3.33.0 起**（Issue #341）。可选且向后兼容：单轮 Charter 无需任何新增。
+
+## 问题
+
+外部审计子系统（`straymark charter audit`、`/straymark-audit-execute`、`/straymark-audit-review`）最初假设**每个 Charter 恰好一轮审计**。但多阶段 Charter 是一等概念，按阶段审计是它们的推荐做法。当一个 Charter 需要**多于一轮**外部审计（例如每个代码密集阶段一轮）时，扁平的单轮布局会在两方面失效：
+
+1. **固定扁平路径互相覆盖。** 每轮都把 `audit-prompt.md`、`report-*.md` 和 `review.md` 写入同一个 `.straymark/audits/<CHARTER-ID>/` 目录，因此第二轮会静默覆盖第一轮的 prompt，而保留历史需要手动 `git mv` 归档。
+2. **跨轮通配污染。** `report-*.md` 通配（`--merge-reports` 和 review skill 都用）是扁平且非递归的。如果上一轮的 reports 以任何仍匹配 `report-*.md` 的名字扁平存放，它们会被拉进**当前**轮的合并 `review.md` 和遥测中 — 混淆各轮。
+
+## 模式：`--round <label>`
+
+传入可选的轮次标签，将整个三件套命名到按轮的子目录下：
+
+```bash
+# 第 1 轮 — 安全阶段
+straymark charter audit CHARTER-01 --prepare --round fase-1 --range <阶段1首个commit>..HEAD
+# → .straymark/audits/CHARTER-01/fase-1/audit-prompt.md
+
+# ...审计员将 reports 写入同一子目录，然后：
+straymark charter audit CHARTER-01 --merge-reports --round fase-1 \
+  --merge-into .straymark/charters/CHARTER-01.telemetry.yaml
+```
+
+标签必须是简单 slug（`[A-Za-z0-9._-]`，以字母数字开头，无路径分隔符或空格）— 它会成为目录名。
+
+### 结果布局
+
+```
+.straymark/audits/CHARTER-01/
+  fase-1/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-2/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+  fase-3/  { audit-prompt.md, report-*.md, review.md, external-audit-pending.yaml }
+```
+
+因为每轮位于自己的子目录且通配非递归，各轮永不互相覆盖（修复问题 1），合并恰好限定到当前轮的 reports（修复问题 2）。
+
+### 传递标签
+
+同一个 `--round <label>` 贯穿整个三件套 — CLI 的 `--prepare` 指引和各 skill 都会回显它：
+
+- `/straymark-audit-prompt <CHARTER-ID>` → `charter audit --prepare --round <label>`
+- `/straymark-audit-execute <CHARTER-ID> --round <label>` → 在子目录下读写
+- `/straymark-audit-review <CHARTER-ID> --round <label>` → 仅合并该子目录
+
+## 遥测：多轮共存
+
+每个用 `--round` 合并的 `external_audit` 条目携带 `round:` 字段，使各轮在同一遥测文件中保持可区分：
+
+```yaml
+charter_telemetry:
+  external_audit:
+    - auditor: "gpt-5-2-codex"
+      round: "fase-1"
+      findings_total: 5
+      # ...
+    - auditor: "claude-sonnet-5"
+      round: "fase-2"
+      findings_total: 2
+      # ...
+```
+
+`--merge-into` 会将新一轮**追加**到已填充的 `external_audit:` 块，而非报错 — 前提是轮次标签是新的。重新合并**同一**轮仍会被拒绝（同轮守卫防止静默重复）；在**没有**轮次标签的情况下合并到已填充块也会被拒绝（各轮必须保持可区分）。每轮使用新的 `--round <label>`。
+
+## 向后兼容
+
+完全省略 `--round`，一切行为与 fw-4.35.0 之前完全一致：`.straymark/audits/<CHARTER-ID>/` 下的扁平路径、无 `round:` 字段的单个 `external_audit` 块，以及 `--merge-into` 拒绝任何已填充数组。单轮 Charter（常见情形）无需改动。
+
+## 相关
+
+- [AGENT-RULES.md §12](AGENT-RULES.md) — 界定何时运行外部审计的审计检查点，以及稳定状态与多轮的条目。
+- [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) — 姊妹 pattern doc（本文档所镜像的注册表布局约定）。
+
+---
+
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/zh-CN/C4-DIAGRAM-GUIDE.md b/dist/.straymark/00-governance/i18n/zh-CN/C4-DIAGRAM-GUIDE.md
index e27e2de9..9bd41128 100644
--- a/dist/.straymark/00-governance/i18n/zh-CN/C4-DIAGRAM-GUIDE.md
+++ b/dist/.straymark/00-governance/i18n/zh-CN/C4-DIAGRAM-GUIDE.md
@@ -234,4 +234,4 @@ Rel(api, db, "Reads/Writes", "SQL")
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/zh-CN/DOCUMENTATION-POLICY.md b/dist/.straymark/00-governance/i18n/zh-CN/DOCUMENTATION-POLICY.md
index b66b43b5..35dd2349 100644
--- a/dist/.straymark/00-governance/i18n/zh-CN/DOCUMENTATION-POLICY.md
+++ b/dist/.straymark/00-governance/i18n/zh-CN/DOCUMENTATION-POLICY.md
@@ -311,4 +311,4 @@ review_outcome: approved                # approved | revisions_requested | rejec
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/.straymark/00-governance/i18n/zh-CN/QUICK-REFERENCE.md b/dist/.straymark/00-governance/i18n/zh-CN/QUICK-REFERENCE.md
index a96c0d26..15c11f63 100644
--- a/dist/.straymark/00-governance/i18n/zh-CN/QUICK-REFERENCE.md
+++ b/dist/.straymark/00-governance/i18n/zh-CN/QUICK-REFERENCE.md
@@ -231,7 +231,8 @@ risk_level: low | medium | high | critical
 |------|------|
 | Follow-ups backlog（一等公民注册表 + 原生 `followups` CLI） *(fw-4.10.0+,自 fw-4.21.0+ 起为一等公民)* | [FOLLOW-UPS-BACKLOG-PATTERN.md](FOLLOW-UPS-BACKLOG-PATTERN.md) |
 | Polish Charter 作为债务检测("声明了表层但未接线"反模式) *(fw-4.18.0+)* | [POLISH-CHARTER-PATTERN.md](POLISH-CHARTER-PATTERN.md) |
+| 外部审计轮次(多阶段 Charter 的按轮命名) *(fw-4.35.0+)* | [AUDIT-ROUNDS-PATTERN.md](AUDIT-ROUNDS-PATTERN.md) |
 
 ---
 
-*StrayMark fw-4.34.0 | [Strange Days Tech](https://strangedays.tech)*
+*StrayMark fw-4.35.0 | [Strange Days Tech](https://strangedays.tech)*
diff --git a/dist/dist-manifest.yml b/dist/dist-manifest.yml
index e93cffa4..94d09580 100644
--- a/dist/dist-manifest.yml
+++ b/dist/dist-manifest.yml
@@ -1,4 +1,4 @@
-version: "4.34.0"
+version: "4.35.0"
 description: "StrayMark distribution manifest"
 repository: "https://github.com/StrangeDaysTech/straymark"
 
diff --git a/docs/adopters/CLI-REFERENCE.md b/docs/adopters/CLI-REFERENCE.md
index b49089af..65884cf8 100644
--- a/docs/adopters/CLI-REFERENCE.md
+++ b/docs/adopters/CLI-REFERENCE.md
@@ -45,8 +45,8 @@ StrayMark uses **independent version tags** for each component:
 
 | Component | Tag prefix | Example | What it includes |
 |-----------|-----------|---------|------------------|
-| Framework | `fw-` | `fw-4.34.0` | Templates (12 types), governance docs, directives, Charter template + schema |
-| CLI | `cli-` | `cli-3.32.0` | The `straymark` binary |
+| Framework | `fw-` | `fw-4.35.0` | Templates (12 types), governance docs, directives, Charter template + schema |
+| CLI | `cli-` | `cli-3.33.0` | The `straymark` binary |
 | Loom (EXPERIMENTAL) | `loom-` | `loom-0.4.2` | The `straymark-loom` visualization server, downloaded on demand by `straymark loom serve` |
 
 Framework and CLI are released independently. A framework update does not require a CLI update, and vice versa.
diff --git a/docs/i18n/es/README.md b/docs/i18n/es/README.md
index 501ae94b..36f7f35f 100644
--- a/docs/i18n/es/README.md
+++ b/docs/i18n/es/README.md
@@ -240,8 +240,8 @@ StrayMark usa tags de versión independientes para cada componente:
 
 | Componente | Prefijo de tag | Ejemplo | Incluye |
 |------------|---------------|---------|---------|
-| Framework | `fw-` | `fw-4.34.0` | Plantillas (12 tipos), gobernanza, directivas, plantilla + schema de Charter |
-| CLI | `cli-` | `cli-3.32.0` | El binario `straymark` |
+| Framework | `fw-` | `fw-4.35.0` | Plantillas (12 tipos), gobernanza, directivas, plantilla + schema de Charter |
+| CLI | `cli-` | `cli-3.33.0` | El binario `straymark` |
 | Loom (EXPERIMENTAL) | `loom-` | `loom-0.4.2` | El servidor de visualización `straymark-loom`, descargado bajo demanda por `straymark loom serve` |
 
 Verifica las versiones instaladas con `straymark status` o `straymark about`.
diff --git a/docs/i18n/es/adopters/CLI-REFERENCE.md b/docs/i18n/es/adopters/CLI-REFERENCE.md
index c572f7a8..ae2762cc 100644
--- a/docs/i18n/es/adopters/CLI-REFERENCE.md
+++ b/docs/i18n/es/adopters/CLI-REFERENCE.md
@@ -45,8 +45,8 @@ StrayMark usa **tags de versión independientes** para cada componente:
 
 | Componente | Prefijo de tag | Ejemplo | Qué incluye |
 |------------|---------------|---------|-------------|
-| Framework | `fw-` | `fw-4.34.0` | Plantillas (12 tipos), docs de gobernanza, directivas |
-| CLI | `cli-` | `cli-3.32.0` | El binario `straymark` |
+| Framework | `fw-` | `fw-4.35.0` | Plantillas (12 tipos), docs de gobernanza, directivas |
+| CLI | `cli-` | `cli-3.33.0` | El binario `straymark` |
 | Loom (EXPERIMENTAL) | `loom-` | `loom-0.4.2` | El servidor de visualización `straymark-loom`, descargado bajo demanda por `straymark loom serve` |
 
 Framework y CLI se publican de forma independiente. Una actualización del framework no requiere actualización del CLI, y viceversa.
diff --git a/docs/i18n/zh-CN/README.md b/docs/i18n/zh-CN/README.md
index 1ee56780..6fb003a9 100644
--- a/docs/i18n/zh-CN/README.md
+++ b/docs/i18n/zh-CN/README.md
@@ -258,8 +258,8 @@ StrayMark 为每个组件使用独立的版本标签：
 
 | 组件 | 标签前缀 | 示例 | 包含内容 |
 |------|----------|------|----------|
-| Framework | `fw-` | `fw-4.34.0` | 模板（12 种类型）、治理文档、指令、Charter 模板 + schema |
-| CLI | `cli-` | `cli-3.32.0` | `straymark` 二进制文件 |
+| Framework | `fw-` | `fw-4.35.0` | 模板（12 种类型）、治理文档、指令、Charter 模板 + schema |
+| CLI | `cli-` | `cli-3.33.0` | `straymark` 二进制文件 |
 | Loom（实验性） | `loom-` | `loom-0.4.2` | `straymark-loom` 可视化服务器，由 `straymark loom serve` 按需下载 |
 
 使用 `straymark status` 或 `straymark about` 查看已安装的版本。
diff --git a/docs/i18n/zh-CN/adopters/CLI-REFERENCE.md b/docs/i18n/zh-CN/adopters/CLI-REFERENCE.md
index e1c54204..ac24ed93 100644
--- a/docs/i18n/zh-CN/adopters/CLI-REFERENCE.md
+++ b/docs/i18n/zh-CN/adopters/CLI-REFERENCE.md
@@ -45,8 +45,8 @@ StrayMark 为每个组件使用**独立的版本标签**：
 
 | 组件 | 标签前缀 | 示例 | 包含内容 |
 |------|----------|------|----------|
-| Framework | `fw-` | `fw-4.34.0` | 模板（12 种类型）、治理文档、指令 |
-| CLI | `cli-` | `cli-3.32.0` | `straymark` 二进制文件 |
+| Framework | `fw-` | `fw-4.35.0` | 模板（12 种类型）、治理文档、指令 |
+| CLI | `cli-` | `cli-3.33.0` | `straymark` 二进制文件 |
 | Loom（实验性） | `loom-` | `loom-0.4.2` | `straymark-loom` 可视化服务器，由 `straymark loom serve` 按需下载 |
 
 Framework 和 CLI 独立发布。Framework 更新不需要 CLI 更新，反之亦然。