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

tests/Novelly.Api.Tests/TestDatabase.cs

@@ -0,0 +1,42 @@
+using Microsoft.Data.Sqlite;
+using Microsoft.EntityFrameworkCore;
+using Novelly.Api.Data;
+
+namespace Novelly.Api.Tests;
+
+/// <summary>
+/// A throwaway SQLite database held in memory. Using real SQLite rather than the
+/// in-memory provider means the tests exercise the same relational behaviour the app
+/// ships with — cascade deletes, foreign keys and all.
+/// </summary>
+/// <remarks>
+/// NUnit reuses one fixture instance across every test in a class, so this must be built
+/// in <c>[SetUp]</c> and disposed in <c>[TearDown]</c>. A field initialiser would share
+/// one database for the whole class and let tests see each other's rows.
+/// </remarks>
+public class TestDatabase : IDisposable
+{
+    private readonly SqliteConnection _connection;
+
+    public TestDatabase()
+    {
+        _connection = new SqliteConnection("Data Source=:memory:");
+        _connection.Open();
+
+        Context = CreateContext();
+        Context.Database.EnsureCreated();
+    }
+
+    public NovelDbContext Context { get; }
+
+    /// <summary>A second context over the same database, for asserting on persisted state.</summary>
+    public NovelDbContext CreateContext() =>
+        new(new DbContextOptionsBuilder<NovelDbContext>().UseSqlite(_connection).Options);
+
+    public void Dispose()
+    {
+        Context.Dispose();
+        _connection.Dispose();
+        GC.SuppressFinalize(this);
+    }
+}