Capture-phase keydown to override parent shortcuts: do not

In a SvelteKit (or any nested-component) app where a parent layout registers a window keydown listener for global shortcuts like n/g/t, the temptation when a child page wants to reuse one of those keys is to attach a capture-phase listener on window with stopImmediatePropagation. This should work — capture runs before bubble, your handler stops propagation only for the key you handle, others bubble through normally. In practice it broke unrelated shortcuts (/ for search stopped working) and seemed to cause hydration weirdness on client-side nav. Theory: capture-phase on window combined with SvelteKit hydration timing creates subtle conflicts that are not worth debugging. The pragmatic fix is to just pick a different key for the page-level action (c for create instead of n) and stay in the regular bubble phase — the design fidelity loss is small, and global shortcuts keep working everywhere.