/**
 * Client-side reserved-state-key predicate (design.md D20; task 10.16b).
 *
 * The server already refuses to serve, write, or delete a reserved internal
 * key through the public state API (`isReservedStateKey()` in
 * `src/core/state/state-manager.ts`, tasks 2.12–2.13) — this is not a second
 * line of defence against that. It exists so the state *view* itself never
 * renders a row for one, and offers no free-text key field that could even
 * be used to attempt writing one: rooms cannot be destroyed and enabled
 * flags cannot be flipped from the state view, because there is nothing
 * there to click.
 *
 * The prefix is duplicated here deliberately rather than imported from
 * `src/core/state/state-manager.ts` — that module pulls in Node-only state
 * persistence machinery this browser bundle must never contain. Both must
 * agree; `tests/reserved-keys.test.ts` and the server-side test suite both
 * assert against the literal `"$internal:"` prefix, so a change to one whose
 * value diverges from the other fails a test rather than silently disagreeing.
 */
/** Must match `INTERNAL_STATE_PREFIX` in `src/core/state/state-manager.ts`. */
export declare const RESERVED_STATE_KEY_PREFIX = "$internal:";
/** Pure predicate: whether `key` belongs to the reserved internal namespace. */
export declare function isReservedStateKey(key: string): boolean;
/** Filters a state key/value map down to the ordinary, presentable keys. */
export declare function filterReservedKeys<T>(state: Record<string, T>): Record<string, T>;
//# sourceMappingURL=reserved-keys.d.ts.map