fix(mobile): let the host's transcript and catalog be the single mobile authority

[wgqqqqq]

Summary

The mobile surfaces now treat the host as the single authority for transcript, catalog, and execution state, instead of rebuilding that state from a local copy.

• Rust relay/core: a relay read resolves one requested turn through the derived turn catalog (with a deliberate full-scan fallback) and logs which mode served it; a persisted InProgress turn is no longer reported as running merely because this process does not own it.
• Shared Kotlin core: sessionsRevision / workspacesRevision hints are consumed with a coalescing floor, session and workspace invalidation stay on separate paths, refreshes are suspended while a turn is in flight, and composer send/stop require a connected host.
• HarmonyOS: draft text is owned by the submission that carried it, session and workspace rows resolve through keyed identity plus a current-snapshot lookup, streaming markdown treats host rewrites and deletions as authoritative, and an on-device catalog refresh fixture plus tool tests were added.
• iOS: a remote send settles against the draft revision it cleared, streaming text state treats host rewrites and deletions as authoritative, and the transcript path gained DEBUG-only timing.
• Android: a submitted draft survives activity recreation, the composer stays editable while a session hydrates, and the compact drawer paints its scrim with the semantic scrim token.

Fixes: no linked issue.

Type and Areas

Type: bug fix / regression fix

Areas: Rust core (assembly/core, services-integrations), mobile iOS, mobile Android, mobile HarmonyOS, mobile shared Kotlin core, mobile tooling/tests.

Motivation / Impact

Three user-visible failures shared one root cause: a mobile surface could act on a locally rebuilt view of host state instead of the host's own record.

• A late acknowledgement for an older send could clear a draft the user had already retyped.
• History paging paid one full transcript materialization per page, and an older page could be served without the log it had to answer from.
• A turn left InProgress on disk by a stopped executor was reported to the relay as still running, so a reconnecting client could show a live turn that nothing was executing.

An abandoned turn is now projected as Cancelled with finish_reason = interrupted in the relay read only; the persisted record keeps its original status so recovery and on-disk evidence are unchanged.

Verification

• cd src/apps/mobile/harmonyos && node --test tools/tests/*.test.cjs — 193 tests, 192 passed, 1 failed. The failure is workspace-editor.test.cjs "sidebar final entry hierarchy keeps modes in workspace plus and tools in the footer", which also fails on a clean worktree at this branch's pre-change commit 9f874c2c3; that test and its subject file are not touched by this branch.
• cargo test --locked -p openbitfun-core --no-default-features --features agent-runtime,git --lib agentic::coordination::coordinator::tests:: — 111 passed, 1 failed. remote_session_metadata_never_falls_back_to_a_local_workspace_binding fails identically on a clean checkout of upstream/main (d06151243, same assertion at coordinator.rs:15164), so it is inherited from the base, not introduced here, and that test is not part of this diff.
• cargo test --locked -p openbitfun-core --no-default-features --features agent-runtime,git --lib agentic::persistence::manager::tests:: — 56 passed, 0 failed, 1 ignored.
• pnpm run check:repo-hygiene — passed (product identity audit, filename and content rules).
• pnpm run fmt:rs — applied to the changed Rust files.

Not run in this environment: the Kotlin commonTest suites (Gradle/Android SDK), the iOS XCTest and Android instrumentation targets (Xcode / device), and tools/check-catalog-refresh.py (requires a real HarmonyOS device over hdc). Those changes are therefore covered only by review, not by an executed test here.

Reviewer Notes

Compatibility and remote scenarios:

• When a host omits sessionsRevision / workspacesRevision, the Kotlin and ArkTS observers keep the conservative invalidate-everything path, so an older host degrades to today's behaviour rather than to a missed invalidation.
• The composer gates are client-side affordances only; the relay still rejects a command from a disconnected surface, and stopping a turn requires a connected host rather than a reachable one that is mid-reconnect.
• The relay read remains a read: the abandoned-turn projection changes the response, never the persisted turn.

Known gaps that exist in the base and are deliberately not changed here:

• HostStreamState::evict clears record_seq but not record_index, while diff_records re-sends only when a record's hash changed, so an evicted session-record cannot be re-materialized by a later full synchronization. Fixing it re-inserts records at their original sequence rather than the tail, which is a separate change with its own ordering risk.
• The HarmonyOS stream client writes truncated (HostSessionStream.ets:228 and :278) but never reads it, so a possibly short history page is not surfaced as a degraded state.
• tools/tests/composer-submit.test.cjs supplies a stub committer for the send path, so the real ConversationCoreState.prepareComposerSubmission interaction (revision comparison, single rollback, draft survival after a failed send) is exercised only on the steer path.

The third checklist item below is intentionally left unchecked: this change set was not audited for new user-facing strings or locale keys.

Checklist

• This PR is focused and does not include secrets, temporary prompts, generated scratch files, or unrelated artifacts.
• Relevant verification is recorded above, or skipped checks are explained.
• User-facing strings, docs, and locales are updated where applicable.

Generated with OpenBitFun