issuelens-config

name	issuelens-config
description	Load validated, capability-scoped IssueLens customization instructions from a target repository, with legacy and built-in fallbacks when .github/issuelens.yml is absent.

IssueLens Repository Configuration

Before applying repository-specific policy, call the issuelens-config tool with the explicit owner/repository and exactly one supported domain:

• criticality
• duplicate_detection
• labeling
• assignment
• notification_content
• planning

The trusted tool discovers a case-insensitive filename match for .github/issuelens.yml, validates its schema, and returns only the requested instruction content. It reports one of these sources:

• configured — use the instruction file selected by issuelens.yml.
• legacy — no path was configured for this domain, so the tool loaded the capability's established legacy file.
• built-in — no configured or legacy instruction exists; use the capability's built-in behavior.

Target repositories do not need .github/issuelens.yml or customization Markdown files. When configStatus is absent, continue with the returned legacy or built-in fallback. When a present config omits the requested domain, continue with that domain's legacy or built-in fallback. Absence and omission are not errors. When the tool fails because a present configuration is invalid, ambiguous, too large, or references a missing file, stop that capability. Do not silently bypass a present but invalid configuration, and do not perform a related write. For planning, return a blocked result without generating planning artifacts from fallback behavior.