# Study Resource Depth

Phase 7 makes the study margin behave like a resource-aware workspace for the LibreBible packages that are currently available to HotView.

## Current Resource Surface

- Strong's links load through the active translation and show lemma, transliteration, definition, language, and pronunciation text when the lexicon entry provides it.
- Translation footnotes and study notes hydrate by visible chapter instead of requiring whole-library note loading.
- Matthew Henry Concise commentary loads for the selected verse range.
- Easton and Smith dictionary entries load from selected verse terms, linked English surfaces, and Strong's lemma surfaces.
- Context maps load OpenBible place matches for the visible page and highlight places tied to the selected verse.
- Related UBS Project MARBLE routes are listed when route titles match visible-page places.
- KJV audio loads chapter playlists from the packaged Eliran Wong source and can play the selected verse, the full chapter, or from the selected verse forward.

## Session Behavior

Maps and audio are first-class session resources now. Existing and new sessions can enable or disable:

- Strong's links
- footnotes
- commentary
- dictionary
- maps
- audio Bible
- timeline recording

Disabled maps and audio do not load their package data in the background. The map and audio cards also persist collapsed state through the shared study settings snapshot.

HotView is expected to run on `127.0.0.1:5174` in the active local loop. Vite's HMR websocket is pinned to that host so live updates keep flowing when the browser tab uses the same address.

## Pronunciation Boundary

The current Strong's package includes pronunciation text for some entries, so the definition card can show that text. The data repo does not currently include licensed pronunciation audio files tied to Strong's numbers, lemmas, Greek, Hebrew, or English terms. Until that exists, the app should not show pronunciation playback controls.

## Next Resource Work

Future resource depth should add new LibreBible packages first, then wire them through the same app-level resource client. Good next candidates are cross-references, additional commentaries, additional lexicons, atlas images, and licensed pronunciation-audio metadata.