code-coordinator 0.5.235__tar.gz → 0.5.237__tar.gz

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.235
+Version: 0.5.237
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/code_coordinator.egg-info/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: code-coordinator
-Version: 0.5.235
+Version: 0.5.237
 Summary: Coordinate Claude Code workers across multiple machines and repos.
 Author-email: John Donaghy <johnfdonaghy@gmail.com>
 License-Expression: LicenseRef-FSL-1.1-MIT

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/code_coordinator.egg-info/SOURCES.txt

@@ -62,6 +62,7 @@ coord/conflict_fix.py
 coord/dao.py
 coord/db.py
 coord/dead_end.py
+coord/decomposition_chat.py
 coord/deploy_manifest.py
 coord/deploy_units.py
 coord/deps.py
@@ -478,6 +479,7 @@ tests/test_dashboard_terminal.py
 tests/test_dashboard_terminal_live.py
 tests/test_db.py
 tests/test_dead_end.py
+tests/test_decomposition_chat.py
 tests/test_deploy_coord_db_backup.py
 tests/test_deploy_coord_web_dist.py
 tests/test_deploy_coord_web_rollback.py

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/code_coordinator.egg-info/scm_file_list.json

@@ -91,6 +91,7 @@
     "coord/dashboard/terminal.py",
     "coord/db.py",
     "coord/dead_end.py",
+    "coord/decomposition_chat.py",
     "coord/deploy/README.md",
     "coord/deploy/coord-agent.service",
     "coord/deploy/coord-db-backup.service",
@@ -550,6 +551,7 @@
     "tests/test_dashboard_terminal_live.py",
     "tests/test_db.py",
     "tests/test_dead_end.py",
+    "tests/test_decomposition_chat.py",
     "tests/test_deploy_coord_db_backup.py",
     "tests/test_deploy_coord_web_dist.py",
     "tests/test_deploy_coord_web_rollback.py",

code_coordinator-0.5.237/code_coordinator.egg-info/scm_version.json

@@ -0,0 +1,8 @@
+{
+  "tag": "0.5.237",
+  "distance": 0,
+  "node": "g855b16cb40a1e4b711059e218b94cd1b8c19f38b",
+  "dirty": false,
+  "branch": "HEAD",
+  "node_date": "2026-08-23"
+}

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/coord/acceptance.py

@@ -838,6 +838,36 @@ def _issue_header_re(issue_number: int) -> re.Pattern[str]:
     return re.compile(rf"^(\s*)['\"]?{issue_number}['\"]?\s*:\s*(#.*)?$")
 
 
+def _parse_list_item_scalar(line: str) -> str | None:
+    """Resolve one YAML block-sequence item line (``- ...``) to its parsed
+    scalar value — the same value :func:`parse_manifest_text` would produce
+    for it — rather than the raw text as written. #2296: a Playwright test id
+    always starts with ``[chromium]``, so its manifest entry is *always*
+    quoted (an unquoted leading ``[`` is a YAML flow sequence, not a string);
+    comparing the raw scalar against the parsed id then never matches. Going
+    through :mod:`yaml` here instead handles double- and single-quoted
+    scalars (incl. the ``''`` embedded-quote escape) and, since YAML's own
+    comment rule applies, a ``#`` inside a quoted scalar is correctly treated
+    as data rather than truncated as a comment.
+
+    Returns ``None`` for anything that isn't a well-formed single-item
+    sequence line (blank/comment-only, flow-style, malformed YAML, or a
+    non-string value) so the caller leaves such lines untouched rather than
+    risk misclassifying them.
+    """
+    stripped = line.strip()
+    if not stripped.startswith("-"):
+        return None
+    try:
+        parsed = yaml.safe_load(stripped)
+    except yaml.YAMLError:
+        return None
+    if not isinstance(parsed, list) or len(parsed) != 1:
+        return None
+    value = parsed[0]
+    return value if isinstance(value, str) else None
+
+
 def _strip_cleared_ids_from_issue_block(
     body: "list[str]", issue_number: int, cleared_ids: "set[str]",
 ) -> "tuple[list[str], bool]":
@@ -871,9 +901,8 @@ def _strip_cleared_ids_from_issue_block(
             i += 1
         new_sub = []
         for sub_line in sub:
-            code = sub_line.split("#", 1)[0].strip()
-            item_m = re.match(r"^-\s*(.+?)\s*$", code)
-            if item_m and item_m.group(1) in cleared_ids:
+            item = _parse_list_item_scalar(sub_line)
+            if item is not None and item in cleared_ids:
                 changed = True
                 continue
             new_sub.append(sub_line)
@@ -1286,7 +1315,12 @@ def clear_expected_red_via_pr(
 
     new_text = clear_expected_red_entries(text, issue_number, ids)
     if new_text is None:
-        return "expected_red text unchanged (nothing matched)"
+        # #2296: ids were passed in and none matched — that's a defect in
+        # the text surgery (or a manifest that no longer has this issue's
+        # block), not a benign no-op. Prefix `warning:` so it's greppable
+        # and so `coord acceptance expected-red --clear` doesn't report a
+        # clean sweep over an operation that actually did nothing.
+        return "warning: expected_red text unchanged (nothing matched)"
 
     get_head = getattr(ops, "get_default_branch_head", None)
     create_branch = getattr(ops, "create_remote_branch", None)

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/coord/agent.py

@@ -3643,6 +3643,112 @@ MILESTONE_CHAT_DENY_COMMANDS: list[str] = [
     "Bash(coord assign *)",
 ]
 
+DECOMPOSITION_CHAT_SYSTEM_PROMPT = """\
+You are a decomposition steward for a customer's APPROVED portal submission \
+that an operator just pulled into this session from the TUI's "Approved \
+work items" panel (#2533, ms-67 contract §4). Unlike `milestone-chat` above \
+(which proposes and waits for confirmation before writing anything), this \
+session's WHOLE JOB is to actually decompose the submission into real \
+coordinator work — there is no separate confirm-then-write step here \
+because pulling the row into this session already IS the operator's \
+confirmation.
+
+The first user message carries: the submission's OUTCOME, AUDIENCE, DONE \
+DEFINITION, and CONSTRAINTS (the four fields the customer described); its \
+mapped repo(s); and `coordinator.yml` topology context for those repo(s) \
+(depends_on, which machines claim each repo).
+
+Your job, in order:
+1. Decide whether this is ORACLE-LOOP-SHAPED work (docs/ORACLE_LOOP.md) — \
+big or cross-cutting enough to warrant a Gate-A contract + independent \
+test-author, or small enough to skip straight to normal dispatch. Discuss \
+this with the operator if it's not obvious; you don't need to wait for \
+explicit confirmation before filing, but flag your reasoning.
+2. Produce one or more GitHub issues describing the work, using:
+
+    coord issue create <repo> --title '<title>' --body '<body>'
+
+   (or `--body-file` for long markdown — never raw `gh issue create`, this \
+repo's own house rule). If the decomposition is milestone-shaped, file an \
+epic/tracking issue first (`coord milestone create <repo> --title '<title>'`) \
+and file the sub-issues, then `coord milestone add-child <repo> <epic> \
+<issue>` each of them onto it.
+3. Queue every filed issue via:
+
+    coord drive-queue add <repo> <issue>
+
+   — NEVER `coord assign` or `coord drive --tmux` (this repo's own standing \
+preference: always go through the drive queue, never ad-hoc dispatch).
+4. Record the portal link so downstream tooling can find this submission's \
+work again (2026-08-22 briefing amendment — this is NOT optional):
+
+    coord portal link <repo> <milestone_number> <submission_id>
+
+   Use the SUBMISSION_ID from your first user message and the milestone \
+number `coord milestone create` printed. If `coord portal link` fails (bad \
+repo, bad milestone number, daemon-host guard), that is a FAILURE of this \
+step — say so explicitly to the operator, do not silently move on.
+
+   **If your decomposition produced a single one-off issue with no \
+milestone/epic** (not a milestone-shaped decomposition): `coord portal \
+link` has NO non-milestone form today — it requires a `milestone_number`, \
+which a one-off issue doesn't have. Do NOT invent one or skip the link \
+silently. Say so explicitly in your final summary to the operator (e.g. \
+"this submission has no recorded portal link — coord portal link only \
+covers milestones, and #2533's own dispatcher found no equivalent for a \
+one-off issue"), so the gap is visible rather than silently lost.
+
+Rules:
+- Do NOT run raw `gh issue create`/`gh issue edit`/`gh pr *`/`gh api -X \
+POST|PATCH|DELETE` or any other mutating `gh` command — the write paths \
+above (`coord issue create`, `coord milestone create/add-child`, `coord \
+drive-queue add`, `coord portal link`) are the only ones you may use.
+- Do NOT run `coord assign <machine> <repo> <issue>` or `coord drive \
+--tmux` — always `coord drive-queue add`.
+- Do NOT run `coord approve` or `coord merge` — outside this session's job.
+- Do NOT run `git push`, `git commit`, or any command that writes to a repo \
+checkout — this session files issues and queues work, it does not touch code.
+- Keep the operator informed: summarize your decomposition plan before \
+filing, and report back what you filed/queued/linked (and any link gap) \
+when done.\
+"""
+
+# Deny list applied to decomposition-chat workers (#2533). Unlike
+# milestone-chat, this type's WHOLE job is to write (issue create /
+# milestone create+add-child / drive-queue add / portal link), so this list
+# is deliberately narrow — it blocks raw `gh` mutations, repo-write git
+# commands, destructive git ops, and the three unrelated `coord` write
+# commands (approve/merge/assign) explicitly out of scope, while every write
+# path this session actually needs (`coord issue create`, `coord milestone
+# create`/`add-child`, `coord drive-queue add`, `coord portal link`) is
+# allowed by omission.
+DECOMPOSITION_CHAT_DENY_COMMANDS: list[str] = [
+    "Bash(gh issue edit *)",
+    "Bash(gh issue create *)",
+    "Bash(gh issue delete *)",
+    "Bash(gh issue close *)",
+    "Bash(gh api -X PATCH *)",
+    "Bash(gh api -X POST *)",
+    "Bash(gh api -X DELETE *)",
+    "Bash(gh pr *)",
+    "Bash(gh repo *)",
+    "Bash(gh milestone *)",
+    "Bash(git push *)",
+    "Bash(git commit *)",
+    "Bash(git reset --hard *)",
+    "Bash(git reset * --hard *)",
+    "Bash(git branch -D *)",
+    "Bash(git branch * -D *)",
+    "Bash(git checkout -- .)",
+    "Bash(git clean -f *)",
+    "Bash(git clean * -f *)",
+    "Bash(rm -rf *)",
+    "Bash(rm -fr *)",
+    "Bash(coord approve *)",
+    "Bash(coord merge *)",
+    "Bash(coord assign *)",
+]
+
 MOCK_AUTHOR_SYSTEM_PROMPT = """\
 You are an independent mock-author agent for Gate A of a milestone \
 (#930, docs/ORACLE_LOOP.md) — the pre-work architecture gate. You have \
@@ -4238,6 +4344,20 @@ def default_worker_command(spec: AssignmentSpec, *, binary: str = DEFAULT_WORKER
         system_prompt = spec.system_prompt if spec.system_prompt else MILESTONE_CHAT_SYSTEM_PROMPT
         system_prompt += build_deny_prompt(MILESTONE_CHAT_DENY_COMMANDS)
         allowed_tools = "Read,Bash"
+    elif spec.type == "decomposition-chat":
+        # #2533 (ms-67 contract §4c): pull an approved portal submission
+        # into a briefed session that decides oracle-loop-shaped-or-not,
+        # files issue(s) via `coord issue create`, queues them via `coord
+        # drive-queue add`, and records `coord portal link` — a mutating
+        # chat type like milestone-chat above, with its own narrow deny
+        # list (see DECOMPOSITION_CHAT_DENY_COMMANDS) rather than
+        # new-issue-chat's blanket one, since this session's whole job is
+        # to write via those specific `coord` commands.
+        system_prompt = (
+            spec.system_prompt if spec.system_prompt else DECOMPOSITION_CHAT_SYSTEM_PROMPT
+        )
+        system_prompt += build_deny_prompt(DECOMPOSITION_CHAT_DENY_COMMANDS)
+        allowed_tools = "Read,Bash"
     elif spec.type == "mock-author":
         # #930 (docs/ORACLE_LOOP.md, Gate A): an independent mock-author
         # agent renders a viewable mock + writes `contract.md` under
@@ -4435,12 +4555,17 @@ def _user_message_line(text: str) -> bytes:
 # a non-closes-issue original (test-author/mock-author/...) — it gets a
 # worktree and runs `gh pr create`, the same GitHub-mutating shape as
 # `type="work"` had before #1142 gave it its own type, so it must stay here.
+# ``decomposition-chat`` (#2533) is a chat too — no git worktree — but its
+# whole job is to mutate GitHub (`coord issue create` / `coord milestone
+# create`/`add-child`) and the drive queue (`coord drive-queue add`), the
+# same "no worktree, but real mutation" shape ``milestone-chat`` has above.
 WRITE_CAPABLE_SPEC_TYPES: frozenset[str] = frozenset({
     "work",
     "review",
     "smoke",
     "conflict-fix",
     "milestone-chat",
+    "decomposition-chat",
     "mock-author",
     "test-author",
     "pr-helper",

{code_coordinator-0.5.235 → code_coordinator-0.5.237}/coord/commands/portal.py

@@ -284,6 +284,56 @@ def portal_link(
     )
 
 
+# ── #2533 (ms-67 PB-3): pull an approved submission into a decomposition chat ──
+
+
+@portal_group.command("decompose-chat")
+@_CONFIG_OPTION
+@click.argument("submission_id")
+@click.option(
+    "--machine",
+    "machine_override",
+    default=None,
+    help="Force a specific machine (must claim every repo the submission maps to).",
+)
+def portal_decompose_chat(config_path, submission_id: str, machine_override: str | None) -> None:
+    """Dispatch a ``type="decomposition-chat"`` session for SUBMISSION_ID (#2533).
+
+    The TUI's "Pull into decomposition session" action (ms-67 contract §4a/
+    §4c) shells this out, exactly the way `coord new-issue-chat` / `coord
+    milestone chat` already work — prints the new assignment id to stdout,
+    which the TUI binds a `ChatController` overlay to once it appears in the
+    board poll.
+
+    Briefs the session with SUBMISSION_ID's outcome / audience / done-
+    definition / constraints, its mapped repo(s), and `coordinator.yml`
+    topology context for those repo(s) (:mod:`coord.decomposition_chat`).
+    The session's own job — deciding whether the work is oracle-loop-shaped,
+    filing issue(s) via `coord issue create`, queueing them via `coord
+    drive-queue add`, and recording `coord portal link` — is described in its
+    system prompt (`coord.agent.DECOMPOSITION_CHAT_SYSTEM_PROMPT`), not here.
+
+    Reads through :func:`coord.approved_work.approved_submissions`, which
+    (like every other portal-bridge reader) resolves state out of this
+    machine's own ``~/.coord/coord.db`` — a daemon-host command, same as
+    ``link``/``publish-mocks`` above.
+    """
+    _refuse_if_thin_client("decompose-chat")
+
+    from coord.decomposition_chat import dispatch_decomposition_chat
+
+    cfg = _load_config(config_path)
+    try:
+        assignment_id, machine = dispatch_decomposition_chat(
+            submission_id, cfg, machine_override=machine_override
+        )
+    except RuntimeError as exc:
+        click.secho(f"error: {exc}", fg="red")
+        raise SystemExit(1) from exc
+    click.echo(assignment_id)
+    click.echo(f"# dispatched to {machine}", err=True)
+
+
 # ── #2513 (PDR-5): manual "publish mocks to portal" ─────────────────────────
 
 

code_coordinator-0.5.237/coord/decomposition_chat.py

@@ -0,0 +1,260 @@
+"""#2533 (ms-67 contract §4c): dispatch a `type="decomposition-chat"` session
+for "Pull into decomposition session" — the TUI action that turns an
+Approved-work-items row (a signed-off portal submission) into a briefed
+`claude -p` chat whose job is to decide whether the work is oracle-loop-shaped,
+file the resulting GitHub issue(s) via `coord issue create`, and queue them via
+`coord drive-queue add`.
+
+Used by `coord portal decompose-chat <submission_id>` (the CLI command the
+TUI shells out to, mirroring `coord new-issue-chat` / `coord milestone chat`
+— see `coord/new_issue_chat.py` / `coord/milestone_dispatch.py` for the two
+precedents this module follows).
+
+**Reads through the existing bridge, never a new direct portal read**
+(#2533's own briefing): the submission's four briefing fields (outcome /
+audience / done-definition / constraints) plus its server-resolved mapped
+repo(s) come from :func:`coord.approved_work.approved_submissions` — the same
+function that already serves the TUI's `/board` `approved_submissions` block
+(#2532) — rather than re-deriving them from `coord.portal_store` directly.
+
+**Machine selection is generalized to every mapped repo** (contract §4c):
+unlike :func:`coord.new_issue_chat.pick_new_issue_chat_machine` (one repo),
+a submission can map to more than one repo, and the picked machine must be
+able to work on ALL of them — a session that can only reach some of the
+repos it's meant to decompose into is worse than refusing outright. §6.7
+flags this as a genuinely open question the contract does not resolve beyond
+"refuse clearly" — this module's refusal is a plain `RuntimeError`, same
+posture every other dispatcher in this file already uses.
+"""
+from __future__ import annotations
+
+import time
+import uuid
+from typing import TYPE_CHECKING, Any
+
+if TYPE_CHECKING:  # pragma: no cover - typing only
+    from coord.config import Config
+    from coord.models import Machine
+
+#: Sentinel `issue_title` this module writes onto the dispatched assignment
+#: — mirrors `dispatch_new_issue_chat`'s own `"(new issue draft)"` sentinel
+#: for a chat type with no real GitHub issue yet. The TUI's own bind path
+#: (`tui/src/app/dialogs.rs::maybe_bind_pending_decomposition_chat`) matches
+#: on this exact string (with the submission id substituted in) since
+#: `Assignment` carries no `submission_id` column of its own — see that
+#: function's doc comment for why this is the module's own choice, not
+#: something #2533's contract pins.
+def _issue_title(submission_id: str) -> str:
+    return f"decomposition: {submission_id}"
+
+
+def pick_decomposition_chat_machine(cfg: "Config", repos: list[str]) -> "Machine | None":
+    """Pick a machine that can work on EVERY repo in *repos*.
+
+    Contract §4c: "the picked machine must list **all** of the submission's
+    mapped repos ... not just one." Returns the first unpaused machine
+    satisfying `m.can_work_on(r)` for every `r` in *repos*. `None` when
+    *repos* is empty (nothing to route) or no single machine covers them
+    all — callers must treat `None` as a hard refusal, never fall back to a
+    partial match.
+    """
+    from coord.machine_pause import paused_set
+
+    if not repos:
+        return None
+    paused = paused_set(cfg.machines)
+    for m in cfg.machines:
+        if m.name in paused:
+            continue
+        if all(m.can_work_on(r) for r in repos):
+            return m
+    return None
+
+
+def _repo_topology_context(cfg: "Config", repos: list[str]) -> str:
+    """One paragraph of `coordinator.yml` topology per mapped repo — the
+    "coordinator.yml topology context ... the same way docs/CUSTOMER_PORTAL.md's
+    design-round step already uses it" #2533's own body asks for.
+
+    No design-round dispatcher exists yet to copy a wire shape from (flagged
+    in ms-67 contract.md §5's own notes as a proposal, not a read-off-the-
+    schema fact) — this is this module's own reasonable rendering: the
+    repo's GitHub slug, its `depends_on`, and which configured machines
+    claim it.
+    """
+    lines: list[str] = []
+    for repo_name in repos:
+        repo_cfg = cfg.repo(repo_name)
+        if repo_cfg is None:
+            lines.append(f"- {repo_name}: (not found in coordinator.yml — check the mapping)")
+            continue
+        machines = [m.name for m in cfg.machines if m.can_work_on(repo_name)]
+        depends = ", ".join(repo_cfg.depends_on) if repo_cfg.depends_on else "(none)"
+        lines.append(
+            f"- {repo_cfg.name} ({repo_cfg.github}): depends_on={depends}; "
+            f"machines={', '.join(machines) if machines else '(none configured)'}"
+        )
+    return "\n".join(lines) if lines else "(no mapped repos)"
+
+
+def build_decomposition_chat_briefing(
+    *,
+    submission: dict[str, Any],
+    topology_context: str,
+) -> str:
+    """Compose the seed briefing the worker sees as its first user message.
+
+    Carries exactly the four submission fields #2533's own body names
+    (outcome / audience / done-definition / constraints) plus the mapped
+    repo(s) and `coordinator.yml` topology context — identical substance to
+    what the Approved-work-items detail pane already shows the operator
+    (ms-67 contract §4b: "nothing hidden between 'looks right in the panel'
+    and 'is what the session got'").
+    """
+    submission_id = submission.get("submission_id", "")
+    repos = submission.get("repos") or []
+    parts: list[str] = []
+    parts.append(f"=== Decomposition chat context for submission {submission_id} ===\n")
+    parts.append(f"Client: {submission.get('client', '')}")
+    parts.append(
+        f"Project: {submission.get('project_id', '')} ({submission.get('project_label', '')})"
+    )
+    parts.append("")
+    parts.append("OUTCOME:")
+    parts.append(submission.get("outcome", "") or "(none provided)")
+    parts.append("")
+    parts.append("AUDIENCE:")
+    parts.append(submission.get("audience", "") or "(none provided)")
+    parts.append("")
+    parts.append("DONE DEFINITION:")
+    parts.append(submission.get("done_definition", "") or "(none provided)")
+    parts.append("")
+    parts.append("CONSTRAINTS:")
+    parts.append(submission.get("constraints", "") or "(none provided)")
+    parts.append("")
+    parts.append(f"MAPPED REPO(S): {', '.join(repos) if repos else '(none)'}")
+    parts.append("")
+    parts.append("COORDINATOR.YML TOPOLOGY CONTEXT:")
+    parts.append(topology_context)
+    parts.append("")
+    parts.append("---")
+    parts.append(
+        "Decide whether this is oracle-loop-shaped work (docs/ORACLE_LOOP.md) "
+        "or small enough to skip straight to normal dispatch, then produce one "
+        "or more GitHub issues via `coord issue create` and queue them via "
+        "`coord drive-queue add`. Once queued, record the portal link via "
+        "`coord portal link` — see your system prompt for the exact command "
+        "and the one-off-issue caveat."
+    )
+    return "\n".join(parts)
+
+
+def dispatch_decomposition_chat(
+    submission_id: str,
+    config: "Config",
+    *,
+    machine_override: str | None = None,
+) -> tuple[str, str]:
+    """End-to-end: look up *submission_id*, pick a machine, seed the
+    briefing, dispatch a ``type="decomposition-chat"`` assignment. Returns
+    ``(assignment_id, machine_name)``.
+
+    Raises ``RuntimeError`` when the submission isn't a currently-approved
+    one, has no mapped repo, no machine claims every mapped repo (or the
+    forced ``machine_override`` doesn't), or the agent rejects the dispatch.
+    """
+    from coord.approved_work import approved_submissions
+
+    rows = approved_submissions(config)
+    submission = next((r for r in rows if r.get("submission_id") == submission_id), None)
+    if submission is None:
+        raise RuntimeError(
+            f"submission {submission_id!r} is not a currently-approved portal "
+            "submission (coord.approved_work.approved_submissions) — nothing to decompose"
+        )
+
+    repos: list[str] = submission.get("repos") or []
+    if not repos:
+        raise RuntimeError(
+            f"submission {submission_id!r} has no mapped repo (portal.project_repos "
+            "in coordinator.yml) — map its project before pulling it into a "
+            "decomposition session"
+        )
+
+    if machine_override:
+        machine = next((m for m in config.machines if m.name == machine_override), None)
+        if machine is None:
+            raise RuntimeError(f"machine {machine_override!r} not in coordinator.yml")
+        missing = [r for r in repos if not machine.can_work_on(r)]
+        if missing:
+            raise RuntimeError(
+                f"machine {machine_override!r} does not list repo(s) "
+                f"{', '.join(missing)} — submission {submission_id!r} maps to "
+                f"{', '.join(repos)}, all of which the target machine must claim"
+            )
+    else:
+        picked = pick_decomposition_chat_machine(config, repos)
+        if picked is None:
+            raise RuntimeError(
+                f"no single machine claims every repo submission {submission_id!r} "
+                f"maps to ({', '.join(repos)}) — decomposition-chat refuses rather "
+                "than dispatching a session that can't reach all of them "
+                "(ms-67 contract §4c/§6.7)"
+            )
+        machine = picked
+
+    topology_context = _repo_topology_context(config, repos)
+    briefing = build_decomposition_chat_briefing(
+        submission=submission, topology_context=topology_context
+    )
+
+    resolved_model = config.models.default
+    from coord.models import Assignment, Proposal
+
+    proposal = Proposal(
+        id=0,
+        machine_name=machine.name,
+        repo_name=repos[0],
+        # No existing issue yet — same 0 sentinel `new-issue-chat` uses.
+        issue_number=0,
+        issue_title=_issue_title(submission_id),
+        rationale="decomposition-chat",
+        briefing=briefing,
+        model=resolved_model,
+        type="decomposition-chat",
+        required_gates=[],
+    )
+
+    from coord.dispatch import dispatch_with_retry
+    from coord.state import record_dispatched_assignment
+
+    response = dispatch_with_retry(
+        proposal,
+        config,
+        max_retries=config.concurrency.max_retries,
+        backoff_base=config.concurrency.backoff_base,
+    )
+
+    assignment_id = response.get("id") or uuid.uuid4().hex[:12]
+
+    repo_cfg = config.repo(repos[0])
+    asg = Assignment(
+        machine_name=machine.name,
+        repo_name=repos[0],
+        issue_number=0,
+        issue_title=_issue_title(submission_id),
+        files_allowed=[],
+        files_forbidden=[],
+        briefing=briefing,
+        assignment_id=assignment_id,
+        status="running",
+        dispatched_at=time.time(),
+        type="decomposition-chat",
+        model=resolved_model,
+    )
+    record_dispatched_assignment(
+        assignment=asg,
+        repo_github=repo_cfg.github if repo_cfg is not None else repos[0],
+    )
+
+    return assignment_id, machine.name