fix(memhub): Linux lifecycle checks the write queue, not recall without a model

The lifecycle verification imported a conversation on a runner with no
generation model and then expected recall to find it. Under SDK authority
nothing reaches the SDK, not even its raw layer, until a model is active,
so the check could never pass and blocked the Linux release archive.

It now asserts what the runner can prove: the imported and appended turns
reach Core's durable write queue, and survive an idempotent upgrade.
docs/TODO-raw-recall-without-model.md records the product gap.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

memhub/scripts/platform/linux/linux-runtime-scripts.test.mjs

@@ -66,7 +66,6 @@ describe("Linux runtime scripts", () => {
       '"stop"',
       '"init"',
       '"scan"',
-      '"recall"',
       '"uninstall"',
     ]) {
       assert.match(script, new RegExp(command));
@@ -88,9 +87,11 @@ describe("Linux runtime scripts", () => {
       script,
       /Exit 1 is a valid transient receipt[\s\S]{0,300}\[0, 1, 3\]/,
     );
-    assert.match(script, /append_recalled/);
+    assert.match(script, /initial_queued/);
+    assert.match(script, /append_queued/);
+    assert.match(script, /FROM memory_write_jobs/);
     assert.match(script, /idempotent_upgrade_instance_id_changed/);
-    assert.match(script, /post_upgrade_recalled/);
+    assert.match(script, /post_upgrade_queued/);
     assert.match(script, /uninstall_preserved_data/);
     assert.match(script, /is-enabled/);
     assert.match(script, /is-active/);