feat: Agent readiness — Link headers, markdown negotiation, A2A/MCP compliance - #202
Conversation
|
Warning Review limit reached
Next review available in: 47 minutes Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available. How can I continue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews. How do review limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability. For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window. Please refer docs for additional details. Review details⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (12)
📝 WalkthroughWalkthroughAdds Cloudflare Worker markdown negotiation with fallback content, new public markdown pages, expanded agent and MCP discovery metadata, and updated well-known headers and routing configuration. ChangesAgent delivery and discovery
Estimated code review effort: 3 (Moderate) | ~20 minutes Sequence Diagram(s)sequenceDiagram
participant Client
participant Worker
participant ASSETS
Client->>Worker: Request with Accept: text/markdown
Worker->>ASSETS: Fetch requested markdown asset
ASSETS-->>Worker: Asset response
Worker-->>Client: Markdown response or fallback content
Possibly related PRs
Suggested labels: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Preview for Bayan Flow Staging ready!
Preview alias |
Codecov Report✅ All modified and coverable lines are covered by tests. 📢 Thoughts on this report? Let us know! |
…ompliance - Add service-desc, service-doc, describedby Link headers (RFC 8288) - Update api-catalog Content-Type with RFC 9727 profile parameter - Add A2A required fields to agent-card.json (version, skills, supportedInterfaces) - Create .well-known/mcp.json at scanner-expected path - Add Cloudflare Worker for Accept: text/markdown content negotiation - Add markdown summary files for all public pages - Update wrangler.jsonc with Worker entry point and assets binding
b472964 to
ee0ac25
Compare
Contribution workflow
develop: This PR targetsdevelop, notmain.Description
Make Bayan Flow agent-ready by implementing three agent discovery standards and fixing multiple isitagentready.com scanner failures:
service-desc,service-doc,describedbyrelation types so agents can discover machine-readable resources from HTTP headersAccept: text/markdownType of Change
Related Issues
Fixes # (isitagentready.com scan failures)
Changes Made
service-desc,service-doc,describedbyLink headers topublic/_headersversion,skills,supportedInterfaces) toagent-card.json/.well-known/mcp.jsonat scanner-expected path (was only at/.well-known/mcp/server-card.json)worker/index.js— Cloudflare Worker fetch handler forAccept: text/markdowncontent negotiationpublic/markdown/(index, app, roadmap, privacy, terms, fallback)wrangler.jsoncwith Worker entry point and assets bindingTesting
pnpm test:run)pnpm lint)pnpm format:check)pnpm build)Test Results
Breaking Changes
Additional Notes
Post-merge manual steps required:
_a2a._agentsand_mcp._agentsSVCB records to includealpn="h2" port=443 mandatory=alpn,portScanner check results after deployment:
Summary by CodeRabbit
New Features
Documentation
Configuration