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/domain/src/main/kotlin/com/example/architecture/feature/characters/domain/usecase/GetCharactersPageUseCase.kt

@@ -9,14 +9,14 @@ import com.example.architecture.feature.characters.domain.model.CharactersPage
  * Loads one page of characters.
  *
  * **When to add a UseCase (convention note):** introduce a UseCase when a screen needs business
- * logic that does NOT belong in the ViewModel — non-trivial rules, or *composition* of several
+ * logic that does NOT belong in the ViewModel - non-trivial rules, or *composition* of several
  * repositories/sources into one domain operation. When the ViewModel would merely forward a single
  * repository call, skipping the UseCase and injecting the repository directly is perfectly fine.
  *
  * This particular UseCase is a **thin pass-through, included for illustration**: it adds no logic
  * beyond delegating to [CharacterRepository]. It earns its place only as a showcase of the
  * convention (domain-owned, `operator fun invoke`, constructor-injected). In a real app you would
- * grow it the moment list loading gained real behaviour (filtering, merging a local cache, …) — or
+ * grow it the moment list loading gained real behaviour (filtering, merging a local cache, …) - or
  * delete it and let the ViewModel call the repository.
  */
 class GetCharactersPageUseCase(

feature/characters/domain/src/test/kotlin/com/example/architecture/feature/characters/domain/usecase/GetCharactersPageUseCaseTest.kt

@@ -17,7 +17,7 @@ import org.junit.jupiter.api.Test
 
 /**
  * Tests for the (thin pass-through) [GetCharactersPageUseCase]: it must forward the requested page to
- * the repository and return its result verbatim — success and error alike. Pure JVM test on the
+ * the repository and return its result verbatim - success and error alike. Pure JVM test on the
  * JUnit 5 platform (see DomainModuleConventionPlugin); the [CharacterRepository] collaborator is a
  * MockK mock, stubbed with `coEvery` and verified with `coVerify`.
  */