feat(WALM-264): permanent V1 memory deletion — flag-gated UI + backend

[harrymove-ctrl]

What

Implements WALM-264 per the agreed plan: a UI-only delete feature for old V1 memories — the app programmatically builds the system::delete_blob PTB from the user's blobs, the user only signs, and the backend submits the tx + deletes the DB rows in the same call. Everything ships off by default behind ENABLE_MEMORY_DELETION (server) + VITE_ENABLE_MEMORY_DELETION (app) — nothing is user-visible until rollout is agreed.

Flow (plan §1)

FE enumerate owned Blob objects (walrusClient.getBlobType — no hardcoded package)
   ∩ relayer DB blob_id set (§5.2, via new authenticated /api/memory-blob-ids)
→ FE build delete PTB, batched 950/tx (Sui 1024-command cap §3)
→ POST /sponsor (Enoki) → user signs the sponsored bytes   ← the ONLY user action
→ POST /api/delete-memories { digest, signature, blobIds }
   → BE submits via the sidecar sponsor-execute path → waits for on-chain success
   → only then delete_by_blob_id(blob_id, auth.owner) per blob
   → { digest, deletedRows }

Tickets

• T2 — backend: POST /api/delete-memories in protected_routes, owner from Extension(auth) (never the body). Submits first, aborts everything if the tx doesn't land; cleanup_expired_blob remains the self-heal backstop. sponsor.rs's sidecar call extracted into call_sidecar_sponsor_execute, shared with the existing /sponsor/execute proxy.
• T2b — §5.2 scoping: new read-only POST /api/memory-blob-ids (authenticated, same flag gate) exposing the owner's vector_entries blob_id set — realizes "get the set from the V1 relayer" for the browser; mixed V1/V2 wallets never see non-memory blobs in the delete list.
• T1 — frontend: CleanupSection card in the Dashboard (mirrors the Delegate keys card — same Card shell, table classes, 52px header pills). Transport-aware enumeration (gRPC listOwnedObjects / JSON-RPC getOwnedObjects), u256→base64url blob-id conversion matching the relayer DB, batch loop resumable mid-run, confirm dialog with the plain-words permanent-deletion warning (§0/§5.3).
• T3 — banner: dismissible "You have N old memories — delete them" in the Dashboard shell, localStorage dismissal.
• T4 — guide: docs/fundamentals/deleting-old-memories.md (registered in docs.json) + in-UI warning copy.

Also included (found while testing on mainnet)

• fix: JSON-RPC nested UID shape in registry lookup — fetchAccountIdForOwner read the Table id as a string; JSON-RPC returns { id: { id } }, so every lookup on the JSON-RPC path failed with Invalid params and SetupWizard tried create_account for wallets that already have accounts (aborts EAccountAlreadyExists). Regression from the feat(relayer): gRPC write path for the JSON-RPC sunset (2026-07-31) #355 compat layer, hidden until now because testnet runs gRPC. This one matters for any mainnet deploy.
• fix: apiCall nonce-based auth — utils/api.ts still signed the legacy 4-part message with no x-nonce, so the auth middleware rejected it with 426; now signs the current 6-part message like SDK v0.4+.

Verified

• cargo test: 296 pass (5 pre-existing failures on clean dev, unrelated); cargo check --tests clean
• App: tsc -b + vite build + verify-dist-assets pass
• Live on localhost against mainnet (tech-lead env) and testnet gRPC: enumeration, §5.2 scoping, selection, confirm, sponsor request all exercised end-to-end up to the Enoki allowlist boundary

Before enabling the flag (not blockers for this merge)

1. SEC2-84: add system::delete_blob to the Enoki Portal sponsor allowlist (testnet + mainnet apps) — Enoki currently rejects the sponsor dry-run with "not part of an allow-listed move call target".
2. E2E on the 189-blob wallet 0x158a78f0… per §6 once the allowlist is in.
3. Decide reclaimed-Storage handling (§5.4) — currently transferred back to the owner.

[jessiemongeon1]

Style Guide Audit

Audited 1 file(s) against the Sui Documentation Style Guide.

19 violation(s) found. All must be fixed before merge.

docs/fundamentals/deleting-old-memories.md (19 violation(s))

19 violation(s) (16 regex, 3 claude)

• Line 14 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 16 — Use present tense, not future
  • Current: will
  • Fix: Use present tense verb
• Line 17 — Use "basic" not "simple"
  • Current: simply
  • Fix: (remove)
• Line 20 — "on-chain" is one word → "onchain"
  • Current: on-chain
  • Fix: onchain
• Line 29 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 30 — "on-chain" is one word → "onchain"
  • Current: on-chain
  • Fix: onchain
• Line 32 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 34 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 35 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 39 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 40 — "on-chain" is one word → "onchain"
  • Current: on-chain
  • Fix: onchain
• Line 46 — "on-chain" is one word → "onchain"
  • Current: on-chain
  • Fix: onchain
• Line 51 — No em dashes in prose
  • Current: —
  • Fix: Rewrite with comma, parentheses, or split sentence
• Line 52 — "on-chain" is one word → "onchain"
  • Current: on-chain
  • Fix: onchain
• Line 1 — Frontmatter needs description
  • Current: (missing or placeholder)
  • Fix: Add a complete sentence description
• Line 1 — Frontmatter needs keywords
  • Current: (missing or placeholder)
  • Fix: Add relevant keywords
• Line 9 — No special symbols for emphasis
  • Current: ## ⚠️ Deletion is permanent
  • Fix: ## Deletion is permanent
• Line 29 — No quotation marks in prose
  • Current: from the "old memories" banner or the "Delete old
  • Fix: from the old memoriesbanner or theDelete old memories section
• Line 41 — Passive voice
  • Current: Reclaimed Walrus storage objects are returned to your wallet.
  • Fix: You receive the reclaimed Walrus storage objects in your wallet.

---

Automated audit using the Sui Documentation Style Guide.