Add outline import feature; drop Dto naming, map entities at the API boundary

Services now return entities; endpoints (and the agent toolsets) map to
*Response records instead of services building wire DTOs themselves.
Also brings in the outline-import agent, MCP tool, ledger and web dialog
that were already in progress on disk.

src/Novelly.Mcp/Tools/ProjectTools.cs

@@ -31,8 +31,9 @@ public static class ProjectTools
         [Description("Genre or category.")] string? genre = null,
         [Description("One-sentence pitch.")] string? logline = null,
         [Description("Paragraph-length summary of the whole book.")] string? synopsis = null,
+        [Description("Free-form notes on theme, tone, comparable titles.")] string? notes = null,
         [Description("Target manuscript length in words.")] int? targetWordCount = null) =>
-        api.PostAsync("/api/projects", new { title, author, genre, logline, synopsis, targetWordCount }, ct);
+        api.PostAsync("/api/projects", new { title, author, genre, logline, synopsis, notes, targetWordCount }, ct);
 
     [McpServerTool(Name = "update_project_brief")]
     [Description("Revise a project's top-level fields. Only the fields you supply change; "