[bandzalkin]

Summary

This adds a room-owned native RPC adapter for OMP so a Band turn stays attached to its background work instead of ending at the first yield. Prompt acceptance, an initial result, or agent_end is not enough: the adapter waits for both the matching prompt outcome and native session settlement, and reports failures from resumed work on the same turn.

• Give each room its own process, workspace and persistent session, with restoration and history recovery. Model/effort selection, custom tools, structured text/image results and external MCP servers use native RPC.
• Install Band's communication and completion policy in OMP's genuine system prompt and verify it before inference. Room/requester metadata and previously handled history remain data, not higher-authority instructions. Required MCP connection receipts must also be present before inference.
• Keep reply ownership in Band's turn ledger: native assistant text and permission narration do not count as a delivered reply or deliberate decline.
• Bind callbacks to the owning turn. Timeout, cancellation and transport failure close the native process and captured descendants before another turn can use a fresh process. Cleanup waits through caller cancellation; Windows descendant termination is forced, not a graceful-exit guarantee.
• Preserve offered permission choices and native event identity. Cancelled selects get independent, best-effort permission records; privacy projection and encoding failures use opaque payloads without inventing reply effects or dropping the native record.

Requires band-sdk[omp] and OMP 18.8.9 or later. A room workspace is not an OS sandbox, and native approval settings do not grant Band platform permissions.

Validation

Regression coverage includes background settlement ordering, resumed errors, cancellation/restart, process custody, startup readiness, permission-record identity and privacy failures.

[bandzalkin]

Rebased onto current main (d7ab3429) at 242a3c96268e; the description's new first section lists the conflict resolutions and the verification at this head.

[bandzalkin]

Provenance note (this branch outgrew its title): besides the background-yield fix it started with, fix/omp-background-yield now carries the native OMP typed-activity work:

• 1f95b787 — tool started/finished keyed by toolCallId in _emit_event and permission wait around the _permission UI handler, using the feat: Report Band tool calls as turn activity #841 helper API (this landed here instead of a separate PR after the modify/delete conflict on omp_acp.py made a stacked PR impractical; the previously opened feat(integrations): report native OMP tool and permission activity #880 was closed as superseded).
• 41fb96e7 — gate fix: the activity hooks are wrapped in if Emit.TOOL_CALLS in self.features.emit:. Live frame capture showed tool names reaching the room with tool reporting switched off; this closes that. The runtime-level ToolNamesObserver (feat: gate activity tool names on the tool-call emit choice #874) does not catch this path, so the gate lives at the call sites here.
• the Merge #874 … commits — restack plumbing so the branch builds on the current gate lineage.

One anomaly to flag rather than hide: commit 41fb96e7 carries author sim-artifacts <sim-only@invalid> — a quarantine git identity leaking from a shared worktree at commit time. The content is our work (reviewed above); we chose not to rewrite history on an open PR. Subsequent commits are correctly authored.

[bandzalkin]

F-8 follow-up (board task 4, part 1): this branch gains a test guard, no code change. The question whether an OMP continuation's band-tool labels can outlive a Tool-calls-&-results flip is now answered at the tree, two ways:

• Within a live turn: the gate flag lives on the shared ExecutionContext and ToolNamesObserver reads it at report time (feat: gate activity tool names on the tool-call emit choice #874 d764959b), so the next room-message turn's on_event sync renames the continuation's very next frame. Guarded by test_flip_after_binding_hides_names_in_the_running_turn (red on the pre-fix tree).
• After the turn was taken over: a stale continuation report can no longer name anything — WorkingStateReporter.update re-checks ownership under its lock, so frames from a non-owning scope never reach the wire (verified falsifiable: bypassing owns_activity makes the new test_continuation_frame_after_takeover_never_reaches_wire fail).

Commit ddcaa947 adds the second guard here so both halves of the window stay pinned; the replay consumes it through this branch.

[bandzalkin]

Closing: superseded by in-repo PR(s) #897, #898 (native adapter beside omp_acp), #893 and #894 (shared fixes carved out), #902 (activity hooks) with the same content, one concern each and a clean single-author history.