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.
This commit is contained in:
@@ -204,6 +204,15 @@ dotnet publish src/Novelly.Mcp -c Release -o ./mcp-server
|
||||
The API must be running. If it is not, the tools say so in a message the model can act on
|
||||
rather than failing opaquely.
|
||||
|
||||
### Importing an existing outline
|
||||
|
||||
`.claude/agents/outline-importer.md` is a Claude Code subagent that reads an author's outline
|
||||
already on disk — chapter files and character dossiers in the folder shape described in that
|
||||
file — and writes it into a new Novelly project over the MCP server above. It's read-only against
|
||||
the source files and keeps a resumable ledger (`.novelly-import.json`) next to them, since a full
|
||||
book is more tool calls than fit in one turn. Invoke it with the source folder path once the API is
|
||||
running and `.mcp.json` is set up.
|
||||
|
||||
## API surface
|
||||
|
||||
`GET /api/health`, plus:
|
||||
|
||||
Reference in New Issue
Block a user