Local memory import shows up as a background task; footer memories pill removed

What

Claude Code can keep "memory", notes it carries from one conversation to the next. This release adds the pieces of a feature that imports local memory notes, shown as a background task (work that keeps running while you continue). It also removes the memories item from the footer, the status line at the bottom of the screen.

• local_memory_import is a new background task type, run by LocalMemoryImportTask. Stopping it aborts the work and marks it killed.
• The task list labels it "memory import" and shows progress as memory import ${windowsDone}/${windowsPlanned}.
• Its activity text reads "still reading local memory notes; running the command again later continues it", so an unfinished import picks up where it left off.
• The Background tasks dialog gains a local-memory-import group.
• The task list shows the task only when an internal value is set. What sets it, and what starts an import, was not traced.
• Two new names, local_memory_import_offer and local_memory_import_stage, are added to a list of feature names.
• The localMemoryToAccount and promoteMemory command entries are still hidden when IS_DEMO is set.
• The memory settings now read a stale_note value from remote configuration, and a new helper checks the server-controlled switch tengu_async_snowglobe.
• The footer's session-memories badge and its view memories hint are removed. The memories footer item is gone from the keyboard handler, so it no longer opens the session memories view.

Why

The task-list side of a local memory import is largely in place, but the findings do not show how an import is started, so you may not see it yet. If you used the footer to open your session memories, that shortcut is no longer there.