Implement agentic maintenance infrastructure for automated repository workflows

.github/ISSUE_TEMPLATE/cap-modeling-task.yml

@@ -0,0 +1,98 @@
+name: CAP Framework Modeling Task
+description: Task for developing CodeQL queries and models for SAP CAP framework
+title: "[CAP]: "
+labels: ["cap-framework", "agent-task", "codeql"]
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🤖 Agent Assignment
+
+        This issue will be handled by the **`cap-modeling-agent`** which specializes in CodeQL modeling for SAP CAP framework.
+
+        The agent follows:
+        - `.github/instructions/javascript_cap_ql.instructions.md`
+        - `.github/prompts/cap_framework_development.prompt.md`
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Task Description
+      description: Describe the CAP modeling task
+      placeholder: |
+        Example: Model new CAP event handler pattern for remote flow sources
+        Example: Fix false positive in SQL injection query for CAP
+        Example: Add test case for CAP authorization bypass
+    validations:
+      required: true
+
+  - type: dropdown
+    id: task_type
+    attributes:
+      label: Task Type
+      description: What kind of task is this?
+      options:
+        - New Query
+        - Query Improvement
+        - New Library Model
+        - Bug Fix
+        - Test Case Addition
+        - False Positive Fix
+        - False Negative Fix
+    validations:
+      required: true
+
+  - type: dropdown
+    id: vulnerability_type
+    attributes:
+      label: Vulnerability Type (if applicable)
+      description: What type of vulnerability does this relate to?
+      options:
+        - SQL Injection
+        - XSS
+        - Path Injection
+        - Log Injection
+        - Authorization Bypass
+        - Information Disclosure
+        - Other
+        - Not Applicable
+
+  - type: textarea
+    id: example_code
+    attributes:
+      label: Example Code
+      description: Provide example CAP code that demonstrates the pattern
+      placeholder: |
+        ```javascript
+        srv.on('READ', 'Books', async (req) => {
+          const userInput = req.data.query;
+          await srv.run(`SELECT * FROM Books WHERE title = '${userInput}'`);
+        });
+        ```
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any additional information or related resources
+      placeholder: |
+        - Related CAP documentation
+        - Similar patterns in other frameworks
+        - Test database considerations
+
+  - type: checkboxes
+    id: requirements
+    attributes:
+      label: Requirements Checklist
+      description: Verify these will be met
+      options:
+        - label: Test cases created with expected results
+          required: true
+        - label: CodeQL tests pass (`codeql test run`)
+          required: true
+        - label: Query formatted (`codeql query format`)
+          required: true
+        - label: Follows test-driven development
+          required: false

.github/ISSUE_TEMPLATE/cds-extractor-task.yml

@@ -0,0 +1,82 @@
+name: CDS Extractor Development Task
+description: Task for developing, testing, or maintaining the CodeQL CDS extractor
+title: "[CDS-EXTRACTOR]: "
+labels: ["cds-extractor", "agent-task"]
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🤖 Agent Assignment
+
+        This issue will be handled by the **`cds-extractor-agent`** which specializes in TypeScript development for the CodeQL CDS extractor.
+
+        The agent follows:
+        - `.github/instructions/extractors_cds_tools_ts.instructions.md`
+        - `.github/prompts/cds_extractor_development.prompt.md`
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Task Description
+      description: Describe what needs to be done with the CDS extractor
+      placeholder: |
+        Example: Add support for parsing CDS annotations
+        Example: Fix failing test in compiler module
+        Example: Upgrade @sap/cds dependency to latest version
+    validations:
+      required: true
+
+  - type: dropdown
+    id: task_type
+    attributes:
+      label: Task Type
+      description: What kind of task is this?
+      options:
+        - New Feature
+        - Bug Fix
+        - Dependency Upgrade
+        - Performance Improvement
+        - Refactoring
+        - Testing
+        - Documentation
+    validations:
+      required: true
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any additional information, error messages, or relevant files
+      placeholder: |
+        - Error messages
+        - Relevant file paths
+        - Related issues or PRs
+        - Expected vs actual behavior
+
+  - type: textarea
+    id: acceptance_criteria
+    attributes:
+      label: Acceptance Criteria
+      description: How will we know this task is complete?
+      placeholder: |
+        - [ ] Tests pass
+        - [ ] Build succeeds
+        - [ ] Feature works as expected
+        - [ ] Documentation updated
+
+  - type: checkboxes
+    id: requirements
+    attributes:
+      label: Requirements Checklist
+      description: Verify these will be met
+      options:
+        - label: All tests must pass (`npm run build:all`)
+          required: true
+        - label: No trailing whitespace
+          required: true
+        - label: Follows TypeScript best practices
+          required: true
+        - label: Test-driven development approach
+          required: false

.github/ISSUE_TEMPLATE/dependency-upgrade.yml

@@ -0,0 +1,106 @@
+name: Dependency Upgrade Task
+description: Task for upgrading CodeQL CLI, QLT, Node.js dependencies, or GitHub Actions
+title: "[DEPS]: "
+labels: ["dependencies", "agent-task"]
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🤖 Agent Assignment
+
+        This issue will be handled by the **`dependency-upgrade-agent`** which specializes in dependency maintenance.
+
+        The agent follows:
+        - `.github/instructions/dependency_upgrades.instructions.md`
+        - `.github/prompts/dependency_upgrade.prompt.md`
+
+  - type: dropdown
+    id: dependency_category
+    attributes:
+      label: Dependency Category
+      description: What type of dependency needs upgrading?
+      options:
+        - Node.js Package (CDS Extractor)
+        - CodeQL CLI
+        - QLT CLI
+        - GitHub Actions
+    validations:
+      required: true
+
+  - type: textarea
+    id: packages
+    attributes:
+      label: Package(s) to Upgrade
+      description: List the package(s) and desired versions
+      placeholder: |
+        - @sap/cds: 7.4.0 → 7.5.0
+        - axios: 1.5.0 → 1.6.2
+
+        Or for CLI:
+        - CodeQL CLI: 2.14.6 → 2.15.4
+
+        Or for Actions:
+        - actions/checkout: v3 → v4
+    validations:
+      required: true
+
+  - type: dropdown
+    id: upgrade_reason
+    attributes:
+      label: Reason for Upgrade
+      description: Why is this upgrade needed?
+      options:
+        - Security Vulnerability
+        - Bug Fix
+        - New Features
+        - Routine Maintenance
+        - Deprecation Warning
+    validations:
+      required: true
+
+  - type: textarea
+    id: breaking_changes
+    attributes:
+      label: Known Breaking Changes
+      description: Are there any known breaking changes? (Check release notes)
+      placeholder: |
+        - List breaking changes from release notes
+        - Or: "None identified"
+        - Or: "Need to review release notes"
+
+  - type: textarea
+    id: security_info
+    attributes:
+      label: Security Information
+      description: If this is a security fix, provide details
+      placeholder: |
+        - CVE number (if applicable)
+        - npm audit output
+        - Severity level
+        - Description of vulnerability
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any additional information
+      placeholder: |
+        - Links to release notes
+        - Related issues
+        - Testing considerations
+
+  - type: checkboxes
+    id: requirements
+    attributes:
+      label: Validation Checklist
+      options:
+        - label: Release notes reviewed
+          required: true
+        - label: Breaking changes documented
+          required: true
+        - label: Tests will pass after upgrade
+          required: true
+        - label: No new security vulnerabilities introduced
+          required: true

.github/ISSUE_TEMPLATE/github-maintenance.yml

@@ -0,0 +1,99 @@
+name: GitHub Maintenance Task
+description: Task for maintaining .github infrastructure (agents, instructions, prompts, templates, workflows)
+title: "[GITHUB]: "
+labels: ["github-maintenance", "agent-task"]
+assignees: []
+
+body:
+  - type: markdown
+    attributes:
+      value: |
+        ## 🤖 Agent Assignment
+
+        This issue will be handled by the **`github-maintenance-agent`** which specializes in maintaining `.github/` infrastructure.
+
+        The agent follows:
+        - `.github/instructions/github_maintenance.instructions.md`
+        - `.github/prompts/github_maintenance.prompt.md`
+
+  - type: dropdown
+    id: maintenance_type
+    attributes:
+      label: Maintenance Type
+      description: What needs to be maintained?
+      options:
+        - Add New Agent
+        - Update Existing Agent
+        - Add New Instruction File
+        - Update Instruction File
+        - Add New Prompt File
+        - Update Prompt File
+        - Add Issue Template
+        - Update Issue Template
+        - Add/Update PR Template
+        - Update Workflow
+        - Update PROMPTS.md
+        - Other
+    validations:
+      required: true
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Task Description
+      description: Describe what needs to be done
+      placeholder: |
+        Example: Create new agent for Java query development
+        Example: Update CAP agent to include new responsibilities
+        Example: Fix broken link in PROMPTS.md diagram
+        Example: Add validation workflow for agent files
+    validations:
+      required: true
+
+  - type: textarea
+    id: files_affected
+    attributes:
+      label: Files Affected
+      description: List the files that will be created, modified, or deleted
+      placeholder: |
+        - .github/agents/new-agent.md (create)
+        - .github/instructions/existing.instructions.md (update)
+        - PROMPTS.md (update diagram)
+
+  - type: textarea
+    id: hierarchy_impact
+    attributes:
+      label: Hierarchy Impact
+      description: How does this change affect the prompts hierarchy?
+      placeholder: |
+        - Adding new connection from issue template to instruction
+        - New prompt linked from instruction file
+        - No hierarchy changes (content update only)
+
+  - type: textarea
+    id: context
+    attributes:
+      label: Additional Context
+      description: Any additional information
+      placeholder: |
+        - References to similar agents/templates
+        - Reasons for the change
+        - Expected outcomes
+
+  - type: checkboxes
+    id: requirements
+    attributes:
+      label: Validation Checklist
+      options:
+        - label: Agent files have proper frontmatter (if applicable)
+          required: false
+        - label: Instruction files have applyTo pattern (if applicable)
+          required: false
+        - label: PROMPTS.md diagram updated (if structure changed)
+          required: false
+        - label: YAML syntax validated (for templates/workflows)
+          required: false
+        - label: No broken internal links
+          required: true
+        - label: Follows best practices from agents.md guide
+          required: true