Skip to content

docs: align feed-directory and AGENTS with registry sync catalog - #1245

Draft
gildesmarais wants to merge 6 commits into
mainfrom
docs/feed-directory-registry-sync
Draft

docs: align feed-directory and AGENTS with registry sync catalog#1245
gildesmarais wants to merge 6 commits into
mainfrom
docs/feed-directory-registry-sync

Conversation

@gildesmarais

@gildesmarais gildesmarais commented Aug 22, 2026

Copy link
Copy Markdown
Member

Stack (registry v1)

Land in order:

  1. html2rssfeat(registry): registry.v1 verify, catalog builder, and 0.28.0 hardening html2rss#476
  2. html2rss-configsrefactor(registry)!: flat configs repo, signed registry.v1 bundles html2rss-configs#317
  3. html2rss-webfeat(registry): index, signed sync, catalog API, and consolidation refactors html2rss-web#1097
  4. html2rss.github.iodocs: align feed-directory and AGENTS with registry sync catalog #1245this PR

What changed

  • AGENTS.md — ownership: html2rss-configsconfigs/ + tool/registry-build (#317); html2rss-webGET /api/v1/configs + Registry::Sync (#1097)
  • Catalog wire contract — rows include id, path, directory, channel, parameters, source; bundle rows add registry; local rows omit registry; browse UI ignores source/registry (parsing in adapters/catalog-api.ts)
  • src/content/docs/web-application/reference/monitoring.mdx — Prettier table alignment only (no monitoring semantics change)

Why

Feed-directory browse UI loads catalog from a running instance’s registry sync (#1097), backed by signed bundles from #317 and verify logic in #476. Contributor docs still described the old gem/catalog model.

Risk

  • Low — documentation-only; no runtime or build behavior change
  • User-facing contributor pages still link to legacy lib/html2rss/configs paths (follow-up PR)

Review map

Review map: whole PR is small — start at AGENTS.md cross-repo contracts section.

Validation

  • make check — lint + build pass on CI
  • Wire shape cross-checked against #1097 request specs and OpenAPI

Replace legacy lib/html2rss/configs links with configs/, document
registry.id in contribution workflows, and use directory feed terminology.
Align feed-config contribution steps with creating-custom-feeds for Feed Directory catalog metadata.
Unify registry.id / directory.* requirements across MCP and contributor
guides, and replace stale "included feeds" / lowercase "feed directory"
wording with consistent Feed Directory terminology.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant