Merge remote-tracking branch 'origin/master' into feat/web-message-feedback-ui

Adapt to two contract changes master introduced:

- The generated Remote face now wraps every business result in
  RemoteResult, folding carrier failures into an ok:false branch instead
  of rejecting. The controller reads that envelope at its three call
  sites and maps a carrier failure onto the same settled shape the
  controls already render; three specs cover the new branch.
- Client packages split their tsconfig into host and client halves, and
  the host aggregate now compiles any test not named *.client.spec.*.
  Rename this package's specs to the client convention and drop the
  ../connection project reference, which pointed at a solution file that
  no longer carries the client sources.

Keep master's mount loop with its rollback-on-failure in api-remotes and
add messageFeedbackRemote to it.

apps/web/tests/support.ts

@@ -119,3 +119,17 @@ export async function saveFailureShot(page: Page, name: string): Promise<void> {
     // Best-effort evidence: a dead page/browser at failure time must not mask the real assertion error.
   }
 }
+
+/**
+ * The conversation engine's Context key format, restated here rather than
+ * imported: these specs live in the Host compiler aggregate, which must not
+ * reach the Client plane. The engine's own copy is
+ * `conversationContextKey` in dsh-client-runtime; a drift between them makes
+ * the key miss its rendered node, so the assertion fails loudly.
+ * @param kind - Definition kind.
+ * @param id - Definition-local business identity.
+ * @returns the engine-owned Context key.
+ */
+export function conversationContextKey(kind: string, id: string): string {
+  return `${kind.length}:${kind}${id}`
+}