chore: Introduce AI coding agent friendly skill

[mlakov]

Add AI Coding Agent Skill for cds-feature-ord Integration

New Features

✨ Introduces a new AI coding agent skill (.skills/integrate-cds-feature-ord/SKILL.md) that guides an AI agent through integrating the com.sap.cds:cds-feature-ord plugin into an existing CAP Java project to expose Open Resource Discovery (ORD) metadata endpoints.

Changes

• .skills/integrate-cds-feature-ord/SKILL.md: New skill file that provides a structured, step-by-step walkthrough for ORD integration, including:
  • Argument-based dispatch to run only specific steps (e.g., maven, config, auth, mtx)
  • Step 1: Adding the Maven dependency for both single- and multi-module project layouts
  • Step 2a: Generating ORD resources at build time via .cdsrc.json or pom.xml cds-maven-plugin execution
  • Step 2b: MTX sidecar integration for multitenancy/extensibility scenarios
  • Step 3: Full configuration reference for ORD endpoints, classpath paths, and OData V4 path overrides
  • Step 4: Authentication configuration (mTLS for production vs. open access for local development)
  • Step 5: Verification steps using curl against local endpoints
  • Troubleshooting table covering common failure scenarios (404, 401, 500, missing perspectives)
  • Implementation notes on ServiceLoader activation, version alignment, and known limitations
  • Next steps pointing to ORD metadata customisation via CDS annotations

• 🔄 Regenerate and Update Summary

PR Bot Information

Version: 1.29.14

• File Content Strategy: Full file content
• Summary Prompt: Default Prompt
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• Output Template: Default Template
• Correlation ID: 2f99f1d0-8cea-11f1-83b8-51ed3b94338a

[hyperspace-pr-bot]

The skill document is well-structured and the @cap-js/ord sidecar dependency pin was flagged. One additional issue worth noting: the hardcoded 6.0.0 version in both Maven dependency snippets will silently guide AI agents to install a potentially outdated version whenever the library advances past that release — consider either instructing the agent to dynamically resolve the latest version from Maven Central or at minimum pairing the version constant with a prominent "check for latest release" instruction.

PR Bot Information

Version: 1.29.14

• File Content Strategy: Full file content
• Experiment Variant: control
• LLM: anthropic--claude-4.6-sonnet
• Event Trigger: pull_request.opened
• Correlation ID: 2f99f1d0-8cea-11f1-83b8-51ed3b94338a

[zongqichen]

LGTM