📖About

Make Logbook blogs living documents that gain UPDATE posts as Carolverse changes. FOUR parts: (1) ADD-POST: extend the Author (tools/author_blog.py) with an add-post mode that appends exactly ONE authored update post to an existing blog session (manual --text or --brief), routed through the Author prompt (never hand-inserted), leaving hero + existing posts untouched; expose a reusable add_post() function for programmatic callers. (2) SCANNER: a Hermione-owned daily scheduled process (run-audited + cron, per the building-scheduled-processes skill) that scans each blog, checks recent initiatives for material changes relevant to that blog (conservative LLM relevance check, fail-open), and adds an update post via add_post(); tracks what it has already posted so it never double-posts. (3) POLICIES: add policy rows — blogs are living/append-only (updates are new posts, never in-place edits or hand-inserts); every blog+post goes through the Author; blogs auto-update from recent initiatives; manual posts allowed as corrections/afterthoughts/additions. (4) CAROLOPEDIA: update Orion Logbook entity description to state blogs are living and gain update posts. Owner of the scanner = Hermione (Process Monitor).

✅Success criteria

• Author has an add-post mode (manual + programmatic add_post()) that appends one authored update post without touching hero/existing posts (must_have)
• Hermione-owned daily scanner is registered, run-audited and cron-triggered; adds update posts from recent initiatives without double-posting (must_have)
• Blog policies added (living/append-only, via Author, auto-update, manual posts allowed) (must_have)
• Orion Logbook description in Carolopedia reflects living blogs (must_have)