feat: RSSフィードの自動配信機能を追加

[shin902]

Summary

nanoclaw.yaml にチャンネル別RSSフィード設定を追加し、15分ポーリングで新着記事URLを自動配信する機能を実装しました。

Changes

• src/rss-config.ts (新規)

  • nanoclaw.yaml の rss.channels セクションを読み込む
  • readRssConfig() — YAMLキャッシュ付き、不正な設定は警告ログでスキップ

• src/db.ts (変更)

  • rss_seen_items テーブル (feed_url, item_id, seen_at) を追加
  • hasSeenItem() / markItemSeen() アクセサ関数を追加
  • 既存DBへの後方互換（CREATE TABLE IF NOT EXISTS）

• src/rss-poller.ts (新規)

  • 15分間隔 (RSS_POLL_INTERVAL = 15 * 60 * 1000) でフィードをポーリング
  • fast-xml-parser でRSS/Atomをパース
  • pubDate 昇順に1記事ずつ sendMessage を呼ぶ
  • フィード取得失敗時は logger.warn でスキップし、他フィードを継続

• src/index.ts (変更)

  • main() 内で startRssPoller() を起動
  • sendMessage ラッパーで未登録チャンネルへの配信を防止

• .claude/skills/setup-rss/SKILL.md (新規)

  • RSS設定手順スキルファイル

• src/rss.test.ts (新規)

  • 設定読み込み、既読管理、ポーラーのテスト（10件）

Test Results

• TypeScript型チェック: ✅ クリア
• 全テスト: 351件合格（新規10件含む）

設定例

rss:
  channels:
    - jid: "dc:1234567890"
      feeds:
        - url: "https://example.com/feed.xml"
          name: "Example Blog"

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 848e4291b6

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Parse Atom entries from feed documents

When fetchFeed sees an Atom document (parsed.feed), it still reads only channel.item/rss.item, so Atom <entry> elements are never collected and the poller silently delivers nothing for Atom feeds. This breaks the advertised RSS/Atom support for any channel configured with common Atom sources.

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Mark items seen only after send succeeds

markItemSeen is called before sendMessage, so any transient send failure (API error, timeout, disconnected channel) permanently drops that article: it is recorded as seen and filtered out on all future polls. Move the seen-marker after a successful send (or roll it back on error) to avoid data loss.

Useful? React with 👍 / 👎.