Reorganise by feature, rename to Novelly, add Aspire and a pre-push hook

The layered split into Domain/Application/Infrastructure/Api was forcing
organisation by layer: adding one capability meant touching four projects and
four folders that each held a slice of it. Those four projects are now one
feature-organised Novelly.Api, where each folder — Projects, Characters,
Chapters, Beats, Scenes, Tags, Agent — holds its entity, DTOs, service and
endpoints together. Common/ holds what genuinely crosses features (the patch
semantics, the two exception types, DraftStatus) and Data/ holds the DbContext
and migrations.

Six .NET projects become five: the three layer projects are gone, and
Novelly.AppHost and Novelly.ServiceDefaults are new.

- Namespaces move from NovelSoftware.* to Novelly.*, including the entity type
  names recorded in the EF model snapshots. The migration ids are untouched, so
  an existing novel.db still migrates cleanly — verified against a fresh file.
- Aspire orchestration mirrors the mic-check setup: the AppHost starts the API
  on :5080 and the Vite dev server on :5173, and the API picks up OpenTelemetry,
  health checks and service discovery from ServiceDefaults. /health and /alive
  now answer in development.
- A Husky pre-push hook runs scripts/ci/prepush.sh: build, test, then a web
  build. The scripts are plain bash so CI can run the same steps.
- The MCP server's env var is now NOVELLY_API_URL.

Verified beyond the build: 44 tests pass, the web client builds, the API was
exercised over curl (project/chapter/beat/tag round trip, tag cross-reference,
503 on the agent without a key while conversation listing still returns 200),
the MCP server was driven over stdio JSON-RPC (26 tools, errors still surface
the API's own message rather than being flattened), and the AppHost was run to
confirm both resources come up and Vite proxies /api through to the API.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01S56bfZMGe1hnhpWP4CjjNw

src/Novelly.Api/Beats/Beat.cs

@@ -0,0 +1,45 @@
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Scenes;
+using Novelly.Api.Tags;
+
+namespace Novelly.Api.Beats;
+
+/// <summary>
+/// One row of a chapter's outline: a short label, who it belongs to, what happened, and
+/// what it sets up. Beats are the planning layer — flat and ordered within a chapter,
+/// with no nesting. A beat may optionally be grouped under the <see cref="Scene"/> that
+/// will eventually carry its prose.
+/// </summary>
+public class Beat
+{
+    public Guid Id { get; set; } = Guid.NewGuid();
+
+    public Guid ChapterId { get; set; }
+    public Chapter? Chapter { get; set; }
+
+    /// <summary>Optional grouping: the scene this beat will be written into.</summary>
+    public Guid? SceneId { get; set; }
+    public Scene? Scene { get; set; }
+
+    /// <summary>Position within the chapter. Gaps are allowed.</summary>
+    public int SortOrder { get; set; }
+
+    /// <summary>A three-to-five word handle for the beat, not a sentence.</summary>
+    public string Title { get; set; } = string.Empty;
+
+    /// <summary>Whose beat this is. Optional — not every beat belongs to one person.</summary>
+    public Guid? CharacterId { get; set; }
+    public Character? Character { get; set; }
+
+    /// <summary>The event itself.</summary>
+    public string? WhatHappened { get; set; }
+
+    /// <summary>What it sets in motion — the hook into the next beat.</summary>
+    public string? WhatsNext { get; set; }
+
+    public List<Tag> Tags { get; set; } = [];
+
+    public DateTimeOffset CreatedAt { get; set; } = DateTimeOffset.UtcNow;
+    public DateTimeOffset UpdatedAt { get; set; } = DateTimeOffset.UtcNow;
+}