Resource rejected ideas

One page per rejected idea (won't do). Check here and deferred first; a decision recorded here is not re-argued by a new roadmap item or proposal. Grid-editor decisions live with the sheet editor.

• Dashboard pages — a page is a second dashboard; the explorer is the hierarchy
• Games integration — a game save is one blob; achievements are the right touchpoint
• Generic event bus — the tRPC mutation path already is the event taxonomy
• JSON Patch content saves — the patch format is generic, a diff that stays small is not; a dictionary delta needs no diff
• JSON/config parity — our resources aren't declarative config
• Note workspace nesting — the explorer is the hierarchy and the Sheet is the database; a Note holding either is a second home
• Owner-named versions — a recovery point somebody has to remember to take is not recovery, and its Save verb read as durability
• Offline editing — queued offline saves guarantee contentVersion conflicts; single write path is the design
• Pin to dashboard — Dashboard is a data product, not a portal homepage
• Portal chrome extras — cosmetic fidelity to needs we don't have
• Raised request body limit — raises the limit for every procedure and keeps the server in the data path of every large save
• Resource icon customization — the type icon is the identity signal; tags personalize
• Streamed tRPC content saves — validation buffers the whole document anyway, and a stream carries no id or version beside it
• Survey Creator licence — Esposter is open source, free to use and not intended for commercialisation, which SurveyJS's open-source exception covers; buying a licence or rebuilding the designer solves a problem we do not have while that holds
• Todo archive state — the Completed section already is the archive; a third state is a second place for the same item
• VuetifyComponent resource type — a demo, not a user artifact
• Webpage site pages — a page is a second webpage; the explorer is the hierarchy