[Feature]: Add afd-plugin repository adapter and knowledge integration #38

Summary

Implement InferMatrixCopilot-side support for vllm-project/afd-plugin, following the repository request in vllm-project/afd-plugin#196.

This issue tracks the adapter, knowledge, routing, and validation work in InferMatrixCopilot. It does not request changes to AFD runtime behavior.

Scope

Repository adapter

Add a human-reviewed adapter for afd-plugin:

• adapters/afd_plugin/manifest.yaml;
• repository identity, default branch, protected-branch policy, language, and CI provider;
• module ownership and risk map for:
  • afd_plugin/compat;
  • configuration and validation;
  • connectors and distributed execution;
  • model_executor and v1 workers/runners;
  • csrc/gpu and csrc/npu;
  • unit, contract, and hardware E2E tests;
• draft profile bootstrapped through the existing repo-profile playbook.

Repository knowledge

Add the smallest useful repo-specific knowledge slice:

• knowledge/repos/afd-plugin/_index.md;
• knowledge/repos/afd-plugin/rules.md;
• registration in knowledge/repos/_index.md.

The initial rules should be distilled from AFD's existing AGENTS.md, CLAUDE.md, README.md, pyproject.toml, CI workflows, and test layout. They should cover:

• exact vLLM/vLLM-Ascend compatibility claims;
• plugin registration and --additional-config boundaries;
• upstream-first compatibility patches and signature preservation;
• connector/distributed ownership and synchronization;
• non-AFD isolation;
• CPU-safe versus GPU/NPU validation;
• reproducible hardware, software, topology, and performance evidence.

Do not copy the vLLM-Omni knowledge tree or create broad generated summaries.

Direct MCP routing

Generalize repository identity and changed-file routing so canonical AFD URLs can resolve to the afd-plugin knowledge slice without adding a permanent AFD-specific hard-coded branch.

Unmatched changed paths must remain visible to the host reviewer.

Tests and documentation

Add focused tests for:

• adapter resolution by alias and repository path;
• knowledge-slice scoping;
• canonical vllm-project/afd-plugin URL normalization;
• changed-file routing for compatibility, connectors, runners, native backends, and tests.

Document the local configuration needed to manage the target checkout, while keeping paths and credentials in ignored configuration.

Constraints

• Existing AFD AGENTS.md, CLAUDE.md, .agents/skills/run-e2e, CI, and repository-owned scripts remain authoritative.
• The default review path remains read-only.
• No automatic PR comments, pushes, or writes to protected branches.
• Repo-specific knowledge must be owner-scoped, indexed, evidence-backed, and validated by both knowledge-tree validators.
• Do not add a new playbook unless the existing repo-neutral playbooks cannot support the target.

Acceptance criteria

• A clean AFD checkout can be profiled without modifying the target repository.
• A maintainer can review and promote the generated adapter/profile.
• A sample AFD PR returns relevant repository-specific knowledge routes.
• CPU-safe checks and hardware-gated evidence are distinguished.
• Existing vLLM-Omni behavior and routing tests remain green.
• The implementation remains reusable for future repositories rather than introducing another repo-specific core branch.

Related work

• afd-plugin#196 — maintainer-facing initialization request.
• InferMatrixCopilot#3 — GitHub event automation RFC.
• InferMatrixCopilot#24 — review routing and latency feedback.