Remove Scenes, group beats by multiple characters; strip comments repo-wide

Drop the Scene entity/grouping in favor of chapters carrying prose directly
and beats belonging to many characters. Add markdown editor + character
multi-select components to the web client. Remove all XML doc and inline
comments across the touched C#/TS/CSS files in favor of self-documenting
names, and record that convention in CLAUDE.md. Add .mcp.json (local MCP
server config, no secrets) and ignore .idea/.

.claude/agents/outline-importer.md

@@ -149,10 +149,10 @@ For each chapter file:
    Keep the Part tag exactly as written ("Part I", "Part II"); keep the thread tag as the raw
    Thread text so multi-POV chapters aren't lossy even though `povCharacterId` had to pick one or
    none.
-4. For each beat table row, resolve the Character column the same way: a single clear name gets
-   auto-created if it isn't in the ledger yet; a list ("Glokta, West, Jezal") or vague reference
-   stays unresolved rather than guessing which one the beat belongs to. Then
-   `create_beat(chapterId, title: <Beat column>, whatHappened: <What column>, whatsNext: <Why column>, characterId: <resolved id, else omit>)`,
+4. For each beat table row, resolve the Character column the same way: a single clear name, or a
+   list ("Glokta, West, Jezal"), gets each name auto-created if it isn't in the ledger yet; a
+   vague reference stays unresolved rather than guessing who the beat belongs to. Then
+   `create_beat(chapterId, title: <Beat column>, whatHappened: <What column>, whatsNext: <Why column>, characterIds: <resolved ids, else omit>)`,
    in table order (the API appends in call order, so no explicit `sortOrder` needed).
 5. If `## Notes` is present, `update_chapter(chapterId, notes: ...)`.
 6. Record `chapters[number] = chapterId`, append `number` to `completedChapters`.