`backlog_create({project})` cannot assign the new ticket to a team of the target project — only portable `role:*` ids are accepted

What happened

When an agent files a ticket in a sibling project of the same account/folder (backlog_create({ project: "<other project>", ... })), the ticket cannot be assigned to one of that project's agent teams. The tool description states: "A ticket filed elsewhere cannot carry an executor resolved here: pass a portable role:... id if you must assign it, never a project agent id, a teamId, skillIds or an accountProfileId." As a consequence the ticket lands in the sibling project assigned to a single generic role (e.g. role:architect), and there is no follow-up tool to fix it: backlog_update "acts on the CURRENT project only: an id from another project is refused and nothing is changed."

Steps to reproduce

1. Two projects in one account/folder; Project B has an agent team.
2. From a Project A console: backlog_create({ project: "Project B", title: "…", teamId: "<team id of B>" }).
3. The teamId is not applicable (contract accepts only role:*); the ticket is created with teamId: null and a role-based executor.
4. backlog_update({ taskId: "<id in B>", teamId }) from Project A → refused ("acts on the current project only").
5. Only fixes: a human click on B's board, or messaging an agent with a live console in B.

Evidence

Cross-project create response: scope "Filed in CrmApi…", teamId: null, agentId: "role:architect". Tool contracts: backlog_create project forbids teamId/agentId; backlog_update is current-project only.

Why it matters

Multi-repo products are the norm: a defect is often diagnosed in one repository and fixed in another. Today the routing step loses the executor, so either a human re-assigns every cross-project ticket by hand, or it is started by the wrong single agent instead of the project's reviewed pipeline.

AgentsRoom diagnostics

• App version: 1.222.0
• OS: linux 7.0.0-38-generic (x64)
• Agent CLI: claude
• App language: system

Problem to solve

Cross-project backlog_create accepts only portable role:* executors: it cannot pin a teamId or a project agentId of the target project, so the ticket is created with teamId: null and a generic role. backlog_update acts on the current project only, so the executor cannot be corrected from the originating project either.

Proposed behavior

Let cross-project create pin the target project's executor: accept a teamId of the target project (from teams_list scoped there, or a global-scope team visible to both) so the ticket runs that project's pipeline when it moves to in_progress; optionally a target-project agentId with local-create semantics; and validate server-side, refusing an id that does not resolve in the target project instead of silently dropping it. Complementary: let backlog_update({ project, taskId, teamId | agentId }) edit a sibling ticket's executor fields only.

Who benefits

Agents and teams on multi-repo products within one account/folder, routing tickets between repositories where the target repository already runs a reviewed multi-agent team pipeline.

Acceptance criteria

A cross-project ticket can be assigned to the target project's team and runs through that project's pipeline on in_progress; a mis-routed ticket is corrected without opening the other project or a manual human re-assignment.