[Gap-Audit] 010 Unified Blog: implement offline editing + sync + conflict resolution + migration tooling

[TortoiseWolfe]

Summary

Blog renders work in production with markdown processing, SEO analysis, and TOC generation. Three advanced user stories are not implemented.

What's shipped

• src/lib/blog/markdown-processor.ts (503 LOC) + tests
• src/lib/blog/seo-analyzer.ts (568 LOC) + tests
• src/lib/blog/toc-generator.ts (342 LOC) + tests
• src/app/blog/* routes render posts

Gaps

• User Story 2: Offline editing & sync not implemented
• User Story 3: Conflict resolution UI not implemented
• User Story 4: Content migration tooling not implemented

Reference

• Spec: features/core-features/010-unified-blog-content/spec.md

[TortoiseWolfe]

Next-session primer

Goal: implement offline editing, sync, conflict resolution, and migration tooling for the blog (User Stories 2/3/4 of features/core-features/010-unified-blog-content/spec.md).

Effort: large (~2-3 days) — three distinct features
Blocked on: nothing, but explicitly P3 (defer)

Why P3

The blog renders work in production today: 3 modules in src/lib/blog/ (markdown-processor, seo-analyzer, toc-generator), routes at src/app/blog/*, full unit-test coverage (#34 closed in batch 4). What's missing is offline-edit UX which has zero current users — defer until there's demand.

When you do it

• Offline editing: reuse src/lib/offline-queue/base-queue.ts (extended in batch 4 with cross-tab safety) — add a blog-adapter.ts next to payment-adapter.ts and message-adapter.ts
• Conflict resolution: study src/lib/messaging/cache.ts for the existing offline-cache pattern; conflict UI needs a side-by-side diff component
• Migration tooling: separate concern — script under scripts/blog-migrate/ to import from common CMS exports (Markdown frontmatter, Hugo, Jekyll)

Files

• src/lib/blog/ — extend with offline + conflict modules
• src/lib/offline-queue/blog-adapter.ts (new)
• scripts/blog-migrate/ (new directory)

Verification

Define E2E specs against tests/e2e/blog/ to exercise offline draft → reconnect → sync → conflict, and unit specs for the migration converter.