[coolestnick]

Closes #286

What and why

Skills and playbooks could be created and imported but never removed in the app, even though the backend already exposes a delete endpoint. This adds a Delete action to the skill detail dialog and to the playbook detail, so people can clear out what they no longer need.

How it works

Both surfaces share one small component, SkillDeleteAction, which reuses the existing InlineDeleteConfirm strip rather than inventing a new pattern:

• A quiet Delete button opens a confirm strip with Cancel and a red Delete.
• Confirming calls the existing delete endpoint, refreshes the list, and closes the dialog.
• If the call fails, a plain error line appears and the strip stays so you can retry.
• Cancel leaves the item untouched.

Deleting the last variant of a grouped skill closes the dialog; deleting one of several leaves the rest open. Runs that already used a skill keep their recorded version, so history is preserved.

Tests

A new interaction test covers the confirm and the list refresh, Cancel leaving the item untouched, and the failed-delete error path. Full suite green: typecheck, bun run test (1771 pass), lint, and build.

How to see it

Open a skill (Skills) or a playbook (Playbooks), and use the new Delete button at the bottom of the detail.

Before / after

	Before	After
Skill detail
Playbook detail
Confirm strip

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}