All network request errors from user actions must be displayed to the user

[DavidNic11]

[k5s-bot]

🤖 Starting work on this now.

[k5s-bot]

🤖 Watch live or take over the session here: https://claude.ai/code/session_01U1BmUXSKHAhMiMbtzMpCuR

[k5s-bot]

Pull request opened: #64

Summary

I triaged issue #56 ("All network request errors from user actions must be displayed to the user") against imaustink/glyph and resolved it.

What I found: Glyph already has a robust feedback system (a global notificationsStore toast store + per-page inline error state), and most user actions already surface errors through it. But an audit turned up a set of user-initiated actions that await a network write with no catch, so failures became silent unhandled rejections — the user saw nothing, and success-only side effects (navigation, closing a dialog) just didn't happen.

What I changed — routed each silent action through the same feedback mechanism its file already uses (error toast via notificationsStore.error(apiErrorMessage(...)), or existing inline error state):

• Sidebar: new page, new page from template, new folder, drag-to-root move
• Note view: title, tags, priority edits
• Tasks board: add lane
• Task detail: visibility change, delete task
• Organizations: delete org, rename org, remove member
• OAuth clients: rotate secret, rotate & revoke, revoke client, remove org, revoke token, revoke all tokens, load-tokens-on-select
• Template manager: save (create/update), keeping the edit form open on failure so input isn't lost

Verification:

• pnpm check (svelte-check): 0 errors, 0 warnings
• pnpm build: succeeds
• Existing unit test suit…

---

✅ Opened pull request: imaustink/glyph#64