[Fix] Gitea pull requests miss linked user assignments

[roomote-roomote]

​Opened on behalf of @daniel-lxs. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Resolve PR attribution and linked identity from the exact target repository's provider and host instead of workspace-wide provider stamps.
• Preserve provider and host attribution for complete homogeneous ALL_REPOSITORIES tasks while failing closed for mixed, missing, host-ambiguous, or incomplete selections and environment mappings.
• Use linked Gitea usernames for delegated PR assignment and preserve existing assignees when Gitea pull requests are refreshed.
• Cover target repository resolution, aggregate attribution, provider-specific assignment wording, and Gitea create/update behavior with focused regression tests.

Why this change was made

Workspace-wide provider stamps can describe a primary repository rather than the repository receiving a pull request. That could leak a GitHub identity into a Gitea task or omit the correct Gitea assignee, especially in mixed-provider and multi-host workspaces.

Impact

Pull request attribution and assignment now follow the exact target repository provider and host. Fully resolved homogeneous aggregate tasks retain linked attribution, while ambiguous or incomplete selections and environment mappings safely fall back to Roomote without assigning the wrong user. The final rebased branch passed focused provider and pull-request tests, formatting, package typechecks, and the repository pre-push gate; two unrelated repository-wide test assertions passed when rerun in isolation.

[roomote-community]

No code issues found in the latest updates. See task

• Resolve PR attribution from the target repository's exact provider and host.
• Fail closed when an ALL_REPOSITORIES selection contains a missing or ambiguous repository mapping.
• Preserve host-scoped linked attribution for homogeneous ALL_REPOSITORIES tasks (packages/cloud-agents/src/server/task-run-queue.ts:2053).
• Fail closed when an environment workspace has incomplete repository mapping coverage (packages/cloud-agents/src/server/task-run-queue.ts:2050).

_{Reviewed 2cd50a2}

[roomote-roomote]

Fixed in 2cd50a2: environment workspaces now persist complete provider coverage and use the same fail-closed classification for provider/host stamping. Incomplete configured mappings resolve to no provider map and clear stale scalar attribution before prompt generation. Eight provider-stamping tests pass, package TypeScript and changed-file lint/format checks pass, and the full pre-push gate passes. The review thread is resolved and the refreshed Roomote code review found no issues.

[roomote-roomote]

Rebased onto current develop and completed the follow-up environment coverage fix in fd4fedf. Target provider/host attribution, Gitea assignment, and aggregate fail-closed behavior are preserved; focused tests, formatting, package typechecks, and the repository pre-push gate pass. The remaining review thread is resolved and refreshed checks are running.