docs: align Feed Directory metadata and terminology

Unify registry.id / directory.* requirements across MCP and contributor
guides, and replace stale "included feeds" / lowercase "feed directory"
wording with consistent Feed Directory terminology.

Author: gildesmarais

README.md

@@ -50,7 +50,7 @@ The Codespace provides a cloud development environment with Node.js pre-installe
 
 - **New to RSS?** → Start with the [web application](https://html2rss.github.io/web-application)
 - **Ruby Developer?** → Check out the [Ruby gem documentation](https://html2rss.github.io/ruby-gem)
-- **Need a specific feed?** → Browse the [feed directory](https://html2rss.github.io/feed-directory)
+- **Need a specific feed?** → Browse the [Feed Directory](https://html2rss.github.io/feed-directory)
 - **Want to contribute?** → See our [contributing guide](https://html2rss.github.io/get-involved/contributing)
 
 ## Contributing

src/content/docs/ruby-gem/guides/ai-agent-workflows.mdx

@@ -94,7 +94,7 @@ When an agent is tasked with creating a durable YAML feed configuration:
 
 1. **Capture:** Call `capture_config`. YAML is `payload.yaml` (`items` + `enhance: true`). Check `payload.articles_count` and `has_selectors`.
 2. **Recon (optional):** Call `inspect_url` for `final_url`, `status`, `scheme_downgrade`, and `alternate_feeds` if the draft is weak.
-3. **Rewrite:** If the destination is html2rss-configs, declare `registry.id`, add `directory.topics`, and set explicit channel `title`/`url`. Strive to keep `enhance: true` (set `false` only when chrome leaks into items).
+3. **Rewrite:** If the destination is html2rss-configs, declare `registry.id`, `directory.topics` (non-empty), `directory.title`, and mirror `channel.title` (required for Feed Directory configs). Optional `directory.summary` (max 160 characters). Set explicit channel `url`. Strive to keep `enhance: true` (set `false` only when chrome leaks into items).
 4. **Validate:** Pass `yaml` (or `config`) to `validate_config`. Exactly one of those arguments.
 5. **Apply:** Call `apply_config`. `isError` plus `payload.item_count: 0` means the config is not shippable — channel title in the XML is not success.
 

src/content/docs/ruby-gem/guides/capturing-feed-configs.mdx

@@ -100,7 +100,7 @@ MCP `capture_config` returns that YAML in `payload.yaml`. `validate_config` / `a
 1. Validate: `html2rss validate my-feed.yml`
 2. Render: `html2rss feed my-feed.yml`
 3. Tighten the items selector, strategy, or `request.botasaurus` options if needed
-4. For Feed Directory contributions, add `directory.topics` and keep `enhance: true` unless chrome leaks (see [Creating Custom Feeds](/creating-custom-feeds/#sharing-your-config))
+4. For Feed Directory contributions, declare `registry.id`, `directory.topics` (non-empty), `directory.title`, and mirror `channel.title`; keep `enhance: true` unless chrome leaks (see [Creating Custom Feeds](/creating-custom-feeds/#sharing-your-config))
 
 ## Related
 

src/content/docs/ruby-gem/reference/mcp-server.mdx

@@ -165,7 +165,7 @@ Four-step workflow for a durable feed config:
 3. Call `validate_config` with `yaml` (or `config`) — must not be `isError`.
 4. Call `apply_config` — `isError` if zero items. Confirm `payload.item_count` before shipping.
 
-If the destination is html2rss-configs, rewrite the draft with `registry.id`, `directory.topics`, and explicit channel `title`/`url`.
+If the destination is html2rss-configs, rewrite the draft with `registry.id`, `directory.topics` (non-empty), `directory.title`, and mirror `channel.title` (required for Feed Directory configs). Optional `directory.summary` (max 160 characters). Set explicit channel `url`.
 
 - **Arguments:**
   - `url` _(string, required)_: Target URL to analyze.

src/content/docs/web-application/deployment.mdx

@@ -18,7 +18,7 @@ The examples use `html2rss/web:1`, the recommended major-version tag. Pin an exa
 There are two materially different deployment modes:
 
 - **Automatic generation enabled:** primary self-hosted workflow, requires `AUTO_SOURCE_ENABLED=true` and `HTML2RSS_ACCESS_TOKEN`
-- **Included feeds fallback only:** lower-maintenance path when the Feed Directory already covers your needs
+- **Feed Directory only:** lower-maintenance path when the Feed Directory already covers your needs
 
 If you do not need page-URL generation yet, keep `AUTO_SOURCE_ENABLED` off and ship the fallback mode only.
 

src/content/docs/web-application/getting-started.mdx

@@ -95,7 +95,7 @@ When output quality is poor, change the input URL first before assuming setup is
 
 ## Fallback Path
 
-If the site you want is already in the feed directory, or you want a fast sample before creating another generated feed, use the feed directory on your own instance.
+If the site you want is already in the Feed Directory, or you want a fast sample before creating another generated feed, use the Feed Directory on your own instance.
 
 - [Use the Feed Directory](/web-application/guides/use-the-feed-directory/)
 - [Feed Directory](/feed-directory/)

src/content/docs/web-application/guides/use-the-feed-directory.mdx

@@ -7,7 +7,7 @@ description: "Use the built-in Feed Directory from your own html2rss-web instanc
 
 ## How to Use Them
 
-1. **Find a feed** in the [Feed Directory](/feed-directory/) (loaded from the active instance catalog)
+1. **Find a feed** in the [Feed Directory](/feed-directory/) (loaded from your active `html2rss-web` instance)
 2. **Set the Instance URL** to your own `html2rss-web` address when it differs from the default
 3. **Open the feed path** from your instance (for example `/anthropic.com/news.rss`)
 4. **Add it to your feed reader**
@@ -33,8 +33,8 @@ Just replace `localhost:4000` with your own `html2rss-web` address.
 
 Use a custom config when:
 
-- the site you want is not in the directory
-- the directory feed misses fields you care about
+- the site you want is not in the Feed Directory
+- the Feed Directory feed misses fields you care about
 - you need a more specific page, section, or output format
 
 Next steps:

src/content/docs/web-application/index.mdx

@@ -20,7 +20,7 @@ Start with **[Getting Started](/web-application/getting-started/)** to:
 
 - **Web interface:** direct feed creation from page URLs
 - **Access-controlled generation:** `POST /api/v1/feeds` expects the token configured on your instance
-- **Included Feed Directory:** packaged fallback feeds you can use immediately from your own deployment
+- **Feed Directory:** pre-built feeds synced from signed registry bundles on your own deployment
 - **Config-based extension path:** move to custom feeds when you need reviewable rules
 - **Caching and HTTP handling:** shipped as part of the deployment
 - **Generated API contract:** OpenAPI is published at `/openapi.yaml`