bmrc-org-config

Use the useOrgConfig hook to access live merged config values like thresholds and locations inside components. The OrgConfigProvider subscribes to the Firestore doc and falls back to defaults if no provider is present, so it never throws.

Call the store getters from org-config-store.ts, such as getThresholds() or getLocationsRuntime(), in pure lib code like item-status.ts or inventory.ts. These read the runtime singleton merged from Firestore, not the frozen defaults.

Admin edits are ignored when code imports frozen constants like THRESHOLDS or LOCATIONS, or reads config at module scope before Firestore loads. Move config access inside render functions or useMemo keyed on hook values to stay reactive.

The pickArray merge logic falls back to default values when an array is empty or missing, so deleting the last location resurrects the default set. You cannot configure an empty list; this protects against partial or corrupt documents.

Add the field to the type interface and DEFAULT_ORG_CONFIG, update applyOrgConfigDoc for new top-level keys, extend buildResult in the hook if needed, add a form control in the matching settings tab, and consume it via the hook or getter.

No, renaming a category or site does not relabel already-saved records. Old documents keep their original strings, so display code must tolerate unknown values.