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/AnthropicClientTests.cs

@@ -1,9 +1,8 @@
 using Microsoft.Extensions.Options;
-using NovelSoftware.Application;
-using NovelSoftware.Application.Agent;
-using NovelSoftware.Infrastructure.Anthropic;
+using Novelly.Api.Agent;
+using Novelly.Api.Common;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 [TestFixture]
 public class AnthropicClientTests

tests/Novelly.Api.Tests/BeatServiceTests.cs

@@ -1,7 +1,11 @@
-using NovelSoftware.Application;
-using NovelSoftware.Application.Dtos;
+using Novelly.Api.Beats;
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Common;
+using Novelly.Api.Projects;
+using Novelly.Api.Scenes;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 [TestFixture]
 public class BeatServiceTests : ServiceTestFixture

tests/Novelly.Api.Tests/ListingTests.cs

@@ -1,10 +1,12 @@
 using Microsoft.Extensions.Logging.Abstractions;
 using Microsoft.Extensions.Options;
-using NovelSoftware.Application.Agent;
-using NovelSoftware.Application.Dtos;
-using NovelSoftware.Domain;
+using Novelly.Api.Agent;
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Projects;
+using Novelly.Api.Scenes;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 /// <summary>
 /// Covers the list endpoints, which sort and aggregate in SQL rather than in memory.

tests/Novelly.Api.Tests/NovelAgentServiceTests.cs

@@ -1,10 +1,10 @@
 using System.Text.Json;
 using Microsoft.Extensions.Logging.Abstractions;
 using Microsoft.Extensions.Options;
-using NovelSoftware.Application.Agent;
-using NovelSoftware.Application.Dtos;
+using Novelly.Api.Agent;
+using Novelly.Api.Projects;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 [TestFixture]
 public class NovelAgentServiceTests : ServiceTestFixture

tests/Novelly.Api.Tests/Novelly.Api.Tests.csproj

@@ -1,4 +1,4 @@
-<Project Sdk="Microsoft.NET.Sdk">
+<Project Sdk="Microsoft.NET.Sdk">
 
   <PropertyGroup>
     <TargetFramework>net10.0</TargetFramework>
@@ -24,8 +24,7 @@
   </ItemGroup>
 
   <ItemGroup>
-    <ProjectReference Include="..\..\src\NovelSoftware.Infrastructure\NovelSoftware.Infrastructure.csproj" />
-    <ProjectReference Include="..\..\src\NovelSoftware.Api\NovelSoftware.Api.csproj" />
+    <ProjectReference Include="..\..\src\Novelly.Api\Novelly.Api.csproj" />
   </ItemGroup>
 
-</Project>
+</Project>

tests/Novelly.Api.Tests/ProjectDataTests.cs

@@ -1,9 +1,11 @@
 using Microsoft.EntityFrameworkCore;
-using NovelSoftware.Application;
-using NovelSoftware.Application.Dtos;
-using NovelSoftware.Domain;
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Common;
+using Novelly.Api.Projects;
+using Novelly.Api.Scenes;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 [TestFixture]
 public class ProjectDataTests : ServiceTestFixture

tests/Novelly.Api.Tests/ServiceTestFixture.cs

@@ -1,6 +1,11 @@
-using NovelSoftware.Application.Services;
+using Novelly.Api.Beats;
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Projects;
+using Novelly.Api.Scenes;
+using Novelly.Api.Tags;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 /// <summary>
 /// Shared plumbing for the service tests: a fresh in-memory database and a matching set

tests/Novelly.Api.Tests/TagServiceTests.cs

@@ -1,7 +1,11 @@
 using Microsoft.EntityFrameworkCore;
-using NovelSoftware.Application.Dtos;
+using Novelly.Api.Beats;
+using Novelly.Api.Chapters;
+using Novelly.Api.Characters;
+using Novelly.Api.Projects;
+using Novelly.Api.Tags;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 [TestFixture]
 public class TagServiceTests : ServiceTestFixture

tests/Novelly.Api.Tests/TestDatabase.cs

@@ -1,8 +1,8 @@
 using Microsoft.Data.Sqlite;
 using Microsoft.EntityFrameworkCore;
-using NovelSoftware.Infrastructure.Persistence;
+using Novelly.Api.Data;
 
-namespace NovelSoftware.Tests;
+namespace Novelly.Api.Tests;
 
 /// <summary>
 /// A throwaway SQLite database held in memory. Using real SQLite rather than the