The memory panel cannot say the memory folder was refused, so a refused folder reads as 'nothing saved' #2101

Implementation: FlyBot (ours) — PR follows within 24h. Do not pick up without a pickup-ok comment on this issue.

Written-by: FlyBot Lead
Claimed-by: FlyBot Lead
Claim-Id: 1dcfee666d624428ae95d5d57a0e3185
Branch: dev/2-memory-blocked-empty
Base: 1778add
At: 2026-11-02T02:13:33Z

A memory folder that is refused reads as "this Bot has never saved anything" — the panel has no word for "I could not read it".

What happens today (live main 1778add0ace4, read not assumed)

• core/src/host/memory.js:445 — when a segment of the memory folder is not a plain directory, warnFolder() writes one host log line (ds-bot: memory folder is not a plain directory %s; keeping it empty) and the reader answers exactly what it answers for a missing folder.
• folderKind() (:462-474) already knows the difference and already knows the failing path: it answers real / absent / other, with at = the segment that failed. Nothing on the read path carries that answer outward.
• memoryView() (:1166-1189) returns botId, entries, sizes, limits, summary, fresh, summarizing, error. There is no field that says a folder was refused, so entries: [] is the only thing the client sees.
• core/src/client/memory-panel.js:69-72 therefore renders {name} has not saved anything yet plus "Bots keep lasting preferences… Tell {name} below" for every empty view — including the one where the Bot did save things and the home cannot read them.

So a user is told to type something that cannot be saved, and a silent refusal is indistinguishable from a fresh Bot. #2068 / #2079 / #2083 / #2089 were all spent on this refusal path; the refusal itself works, only the report is missing.

Reproduction

1. Home whose memory/ (or memory/bots, or a scope folder under it) is a symlink to a directory outside the home.
2. Open the Memory panel for a Bot.
3. Panel: {name} has not saved anything yet. Host log: the one keeping it empty warning. memory-view over the API: entries: [], nothing else says why.

Expected

• memory-view gains blocked: one entry per scope that is refused — { scope: 'own' | 'team', path } built from the existing folderKind(...) result, path = its at. Only kind === 'other' is blocked; absent is a normal empty home and must stay out of it. Empty answer when nothing is refused.
• The panel, when entries is empty and blocked is non-empty, renders one line above the existing empty title naming the path and saying the folder is not a plain directory so it cannot be read. With nothing blocked the copy is byte-identical to today.
• Because the suite has no React renderer, the decision goes in an exported pure helper in the panel model (same shape as bot-row-title / at-menu), tested directly.

Acceptance (red first)

1. Host: linked memory/ → blocked names that scope and the failing path, entries still []. Red today: the field does not exist.
2. Host: plain folder with no entries → blocked empty (guards against a flag that is always on), entries [], fresh unchanged.
3. Client: the helper answers the notice for a blocked view and null for a plain empty view. Red today.
4. core/test/i18n.test.js already fails any t('…') literal without a Chinese entry — the new strings go into DICTIONARY.zh (core/src/client/i18n.js).

Scope

core/src/host/memory.js, core/src/client/memory-panel.js, core/src/client/i18n.js, core/test/memory.test.js, one new client test file, docs/subsystems/core-host.md if the memory-view contract is documented there, one changelog.d/ fragment. Client and i18n files are mirrored into ds-bot/ through patches/ds-bot/ — npm run generate + scripts/ds-bot-patches.mjs canonical must stay no-op clean.

Not in scope

• Not changing the refusal itself, the entry/summary behaviour, permissions, or the once-per-folder warning.
• Not adding a "retry" or a repair path; the panel only says why it is empty.
• Not exposing host paths anywhere but this one line (the path is the home's own memory folder, which the panel already belongs to).

Dedup (checked before opening)

• Live main 1778add0ace4: the string has not saved anything yet exists only in core/ + ds-bot/ mirrors of the panel; no blocked field on the view; no client helper for it.
• Issues: "has not saved anything yet" → 0; memory panel empty → 0; folderKind → #2071 (closed, merged — it added the resolver and the refusal; this asks only to report the refusal); memory-view → 34 hits, reviewed #2068 / #1910 / #1740 / #1887, none about the empty state naming the refusal.