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/data/src/main/kotlin/com/example/architecture/feature/characters/data/datasource/KtorCharacterDataSource.kt

@@ -8,7 +8,7 @@ import com.example.architecture.feature.characters.data.dto.CharactersResponseDt
 import io.ktor.client.HttpClient
 
 /**
- * Remote data source for characters. Returns raw DTOs (no mapping here — the repository maps via
+ * Remote data source for characters. Returns raw DTOs (no mapping here - the repository maps via
  * CharacterMapper). Errors already surface as [DataError.Network] from the typed `get` helper.
  */
 internal class KtorCharacterDataSource(

feature/characters/data/src/test/kotlin/com/example/architecture/feature/characters/data/NetworkCharacterRepositoryTest.kt

@@ -22,7 +22,7 @@ import org.junit.jupiter.api.Test
 
 /**
  * Data-layer test for [NetworkCharacterRepository]. A Ktor [MockEngine] is swapped into the real
- * [HttpClientFactory] (`create(engine)` takes the engine precisely so tests can do this) — so the
+ * [HttpClientFactory] (`create(engine)` takes the engine precisely so tests can do this) - so the
  * full path under test is genuine: Ktor request → status/JSON handling in `safeCall` → DTO mapping →
  * domain model. Covers success mapping, a 404 and a 5xx mapped to typed [DataError.Network], and a
  * malformed-body → SERIALIZATION case.