Install a bundled buzz-memory skill on desktop startup

[salman1993]

Why

Agents learn memory procedures only from the base prompt and a short patch section in the CLI skill. They miss conventions that keep memory usable as it grows: a core index, source metadata, cross-links, and safe edits.

What

Install a bundled buzz-memory skill next to buzz-cli on startup. Agents load it on demand through each harness's skill discovery. Adapted from block/buzz#8127.

How

The skill text is #8127's nest_memory_skill.md. Each CLI claim was checked against buzz mem and buzz messages thread --link at the pinned Buzz revision (4f51b9e). Core-memory loading at session creation was checked against the pinned buzz-acp.

ensure_buzz_cli_skill becomes ensure_buzz_skills. It installs each skill with its own .skill-version marker and Claude, Codex and Goose links, using the same preserve and repair policy as #667. Each skill installs independently, so a blocked CLI migration does not stop the memory skill. Only buzz-cli migrates the old Claude-only layout. A real .claude/skills/buzz-memory directory is treated as a custom skill and preserved.

Not carried over from #8127:

• The base prompt and onboarding nudge. buzz-app gets these from the pinned buzz-acp, so they would need a Buzz change and a pin bump.
• The NIP-AE convention section, which belongs to the Buzz repo.
• Trimming the memory section from buzz_cli_skill.md. It stays a verbatim upstream copy that shares its version marker with old Buzz. The overlap is consistent with the new skill.

Risk

Startup now also writes ~/.buzz/.agents/skills/buzz-memory and its provider links. Installation errors are logged and do not stop the app from opening. Custom agent workspaces are untouched.

Testing

• cargo test -p buzz-agent-controller skills::: 8 passed. New coverage checks fresh install and discovery, refresh on the skill's own marker without touching current CLI edits, preservation of a custom memory directory with supporting files, and isolation from a failed CLI migration.
• The isolation regression fails when the installer stops at the first skill error, and passes on this change.
• native_host_provisions_skills_before_agent_controls_are_used passes: native host startup installs both skills in an isolated workspace.
• No browser cases added or removed.

Deferred: agent review, human desktop acceptance, and Windows execution. To check, run bin/just desktop from this branch. Confirm that ~/.buzz/.agents/skills/buzz-memory/SKILL.md exists and resolves through .claude, .codex and .goose/skills/buzz-memory. Then ask a managed agent to recall a prior decision and confirm it loads buzz-memory before using buzz mem. Development builds write to the real ~/.buzz.

🤖 Generated with Claude Code