feat: add speaker mapping and workflow improvements

README.md

@@ -42,6 +42,12 @@ compatibility path. Diarization is optional and produces anonymous speaker
 labels. A label identifies a participant only when the user explicitly
 confirms the mapping; automatic speaker-name inference is not allowed.
 
+After a diarized run, the result view lists detected `SPEAKER_XX` labels with
+short transcript excerpts. Confirmed mappings regenerate only the protocol
+from the existing diarized transcript; audio preparation, Whisper and Pyannote
+are not rerun. `Unmapped / Unknown` remains valid, and the original anonymous
+diarized transcript is preserved.
+
 ## Product Outputs
 
 The product direction includes:
@@ -108,6 +114,41 @@ Optional machine-specific settings include:
 - `MKA_DIARIZATION_CONTAINER_IMAGE` (required for container diarization)
 - `MKA_DIARIZATION_CONTAINER_ARGS` (default: no extra arguments), encoded as a
   JSON array of strings so ordering and leading dashes are preserved exactly
+- `MKA_GLOSSARY_DATABASE` (default: `data/database/glossary.sqlite3`), the local
+  SQLite file used by the global terminology glossary
+
+## Terminology glossary
+
+The Streamlit **Terminology glossary** section manages recurring product,
+material, organization, acronym, and technical names. Store canonical core
+terms such as `Secugrid HS`, not every compound such as `Secugrid HS Düse`.
+Aliases help the protocol model recognize transcript variants while retaining
+the surrounding wording. Only active entries are added to Meeting Context as
+authoritative terminology for direct protocol generation; inactive entries
+remain stored but are omitted. The production database starts empty.
+
+The database defaults to `data/database/glossary.sqlite3`. It is created and
+bootstrapped automatically and can be moved with `MKA_GLOSSARY_DATABASE`.
+Glossary integration does not rewrite raw or diarized transcript artifacts.
+
+## Input configuration import and export
+
+Use **Export inputs** to save the current Meeting Assistant run-input form as a
+small, versioned JSON file and **Import inputs** to restore it later. The file
+contains meeting metadata, participant records, language, date, audio
+normalization, and diarization choices. It contains form configuration only:
+generated prompts, protocols, run artifacts, and source-media contents are not
+included.
+
+The original source filename may be retained as a reminder, but importing does
+not restore an upload. Select the audio file explicitly before starting the new
+run.
+
+Protocol generation with `qwen3.8:27b` explicitly requests a 32,768-token
+Ollama context with thinking disabled; Ollama's machine default may otherwise
+be only 4,096. Keep normal prompt input at approximately 29,000 tokens or less.
+Although a 31,038-token synthetic prompt passed, larger input is not assumed
+safe merely because the model advertises a 262,144-token native context.
 
 For example, a compatible AMD ROCm workstation can configure validated
 container access without adding controls to the Streamlit UI: