REDI-101: replace em/en dashes with hyphens in prose & comments

Em dashes are a common AI-writing tell; swap them (and en dashes) for plain
hyphens across the README and all KDoc/comment prose so the repo reads as
hand-authored. Byte-level replace of U+2014/U+2013 -> '-'; arrows and the
ellipsis are left untouched.

The two functional em dashes are intentionally kept: the `DASH = "—"`
blank-field UI placeholder in CharacterDetailUi and the preview sample that
mirrors it -- those are deliberate UX, not prose.

feature/characters/presentation-views/src/main/kotlin/com/example/architecture/feature/characters/presentation/views/CharacterListFragment.kt

@@ -23,7 +23,7 @@ import org.koin.androidx.viewmodel.ext.android.viewModel
 
 /**
  * Classic Views renderer for the characters list. It drives the **same** [CharacterListViewModel] as
- * the Compose screen — proving the presentation logic (State/Action/Event/UI-model) is truly
+ * the Compose screen - proving the presentation logic (State/Action/Event/UI-model) is truly
  * UI-agnostic. Koin's `by viewModel()` supplies the VM (and its `SavedStateHandle`).
  *
  * `:app` (the interop owner) wires [onCharacterClick] / [onNavigateBack]; the Fragment never touches

feature/characters/presentation-views/src/main/kotlin/com/example/architecture/feature/characters/presentation/views/CharacterStatusViews.kt

@@ -6,7 +6,7 @@ import com.example.architecture.feature.characters.domain.model.CharacterStatus
 
 /**
  * Views-renderer presentation helpers for [CharacterStatus]. These intentionally mirror the Compose
- * renderer's helpers but return platform types (a string-res id and an ARGB Int) — each renderer
+ * renderer's helpers but return platform types (a string-res id and an ARGB Int) - each renderer
  * owns its own resources, so the small label duplication across modules is expected.
  */
 @StringRes