State management (Svelte 5 runes)
Generated from
pattern-library/registry.json— do not edit by hand; change the registry and runbun run patterns:build.
Index card — the docs below are the canonical explanation; deep-tier pattern pages additionally carry invariants and emulation notes.
Category: Architecture & Request Pipeline · Tier: light · Maturity: proven (verified 2026-08-20 @ 1a130d67) · Risk: low — structural pattern, no external services
Establishes v10r's rune-based state strategy — $state/$derived for component state, .svelte.ts modules or the Context API for shared state, with an SSR-safety rule against module-level state leaking across requests.
When to use: Reach for it when deciding whether shared reactive state should be a .svelte.ts module or Context-API-provided, especially anything touched during SSR.
Docs
Code
Tests
src/lib/state/layer-stack.svelte.test.ts(GitHub · GitLab)src/lib/state/branch-operation-monitor.svelte.test.ts(GitHub · GitLab)
Machine-readable record: architecture-state-management in pattern-library/registry.json.