| [Doc][skill] Rework main2main skill and add deterministic automation scripts (#9232)
### What this PR does / why we need it?
This PR reworks the main2main skill into a structured, script-driven
pipeline for keeping vLLM-Ascend aligned with upstream vLLM main.
It follows the direction in RFC #7074: make main2main caller-agnostic,
script-deterministic, incremental, CI-gated, and bounded. The skill now
separates high-level agent guidance from deterministic helper scripts
and detailed reference material.
New structure:
```text
main2main/
├── SKILL.md
│ └── Compact entrypoint: guardrails, workflow overview, and pre-completion checklist.
├── scripts/
│ ├── detect_commits.py
│ │ └── Initialize workspace and detect base/target vLLM commits.
│ ├── plan_steps.py
│ │ └── Deterministic step planner for bounded upstream commit ranges.
│ ├── step-planner.yaml
│ │ └── Classification, weight, and budget configuration for step planning.
│ ├── check_and_commit.py
│ │ └── Validate commit paths and create signed commits only after CI passes.
│ └── run_main2main_ci.py
│ └── Run CI and extract structured log summaries.
└── reference/
├── adapt-guide.md
│ └── Detailed method for the Adapt phase.
├── diagnosis-guide.md
│ └── Detailed method for the Fix-CI loop.
├── final-summary.md
│ └── Final reviewer-facing summary template.
└── error-pattern-examples.md
└── Concrete examples for common CI error fixes.
```
Key workflow changes:
- Splits upstream vLLM commit drift into bounded steps before
adaptation.
- Updates the pinned vLLM commit reference per step.
- Requires CI verification for every step, including no-op adapt steps.
- Uses structured CI log summaries instead of reading raw logs into
agent context.
- Commits only after CI passes or only environment flakes remain.
- Stops cleanly on bounded fix-loop failure by saving patch and failure
summary instead of silently skipping failed steps.
- This reduces manual main2main maintenance by making repeatable
operations deterministic and keeping the agent focused on the hard
parts: understanding upstream API changes, adapting vLLM-Ascend code,
and diagnosing CI failures.
Reference:
[#7074](https://github.com/vllm-project/vllm-ascend/issues/7074)
### Does this PR introduce _any_ user-facing change?
### How was this patch tested?
- vLLM version: v0.20.2
- vLLM main:
https://github.com/vllm-project/vllm/commit/0d4d334eaa583b9c09aa4eb7538c22db99fd84b3
---------
Signed-off-by: Meihan-chen <zr010426ztt@outlook.com> | 9 天前 |