StoryWeave update: quota handling, SEO landing page, and full genre workflow audit

Shipped and validated a practical round of StoryWeave updates.

What changed:

- Fixed package quota / token allowance behavior after a subscription ends.

- Added a new SEO landing page for the AI novel writing workspace.

- Completed a full human-author simulation across all supported story types.

- Documented the next stabilization plan for genre-aware writing defaults, cleaner manuscript export, outline reliability, and a more focused author workspace.

The biggest learning from the genre audit:

StoryWeave can already support the full creation loop, from project setup to outline, chapters, scenes, and Markdown export. But to feel truly useful for long-form authors, the product needs cleaner manuscript output, stronger genre-specific defaults, and fewer workbench-style details exposed to writers.

A lot of this is behind-the-scenes work, but it directly improves how reliable StoryWeave feels for real writing workflows.

Still building. If you try StoryWeave and have feedback, I’d love to hear it.