[KaisennHu]

Summary

Extends the knowledge/repos/vllm-router/ slice, which #445 created and has since merged, with CI and release knowledge. It also merges the repository entry so one page routes both the bug/ and ci/ work topics, and brings the shared DI rule in line with the review feedback on this PR.

Router statements are checked against main@ddf78218 (2026-11-09) and against the published channels: PyPI, Docker Hub, and GitHub Releases.

Contents

1. _index.md — merged repository entry. Routes issue triage to bug/ and release work to ci/, keeps the package, module, and alias mapping, records the audited main revision, and states that no component owners or _routes.yaml exist yet.
2. ci/_index.md — CI entry. Describes the four Buildkite lanes with their real upload gates (non-default branch plus ready; default branch, merge queue, or merge-test; default branch with NIGHTLY=1 or nightly-test), the jobs each lane runs (P/D smoke, kv_aware e2e, gRPC P/D, GSM8K, gRPC prefix-KV perf, L1 encode perf, ROCm xGMI and RDMA matrices), the pytest markers, and the hardware presets.
3. ci/release-gates.md — release standard:
   1. Version sources: pyproject.toml is the only value version-check reads, while four files must be bumped together.
   2. Published-artifact cross-check: git tags, PyPI versions, Docker Hub tags, and GitHub Releases side by side, including tags without artifacts (v0.1.11, v0.1.13, v0.1.14) and the Docker-only v0.1.16.1.
   3. Hard gates: tag-to-pyproject.toml equality; x86_64 and aarch64 manylinux_2_28 builds with auditwheel; binary and wheel smoke tests; the twine PyPI chain; the Docker confirmation sequence; nightly image publication and 14-tag retention.
   4. Quality gates and evidence rules: L2 and L3 results; Python coverage read from the router coverage dashboard, with Rust coverage gated on a self-built collector agreed at kickoff; per-scenario performance comparison; requirement completion; remaining DI; critical-issue ownership.
   5. Failure modes and release steps, including manual GitHub Release authoring because no pipeline step creates releases.
4. knowledge/general/bug/guides/di-calculation.md and knowledge/general/bug/_index.md — shared DI rule refresh: DI is no longer accumulated by days open; breaching the SLO escalates the issue one severity level and DI takes the new level's base value. Severity criteria for critical, high, medium, and low are recorded there so the router page can link instead of restating them.

Metadata

No additional metadata changes in this diff. The vllm-router ownership tag and the repos/_index.md row landed with #445; this PR reuses them and only merges the entry page.

Validation

1. python knowledge/tools/check_knowledge_tree.py — no errors and no warnings for the merged entry, the CI pages, or the two updated DI pages. Three pre-existing errors remain for three rules.md pages elsewhere in the tree on a local Windows autocrlf checkout; their LF blobs are under the 32768-byte threshold, so these are line-ending artifacts of the local checkout and are unrelated to this change.
2. python knowledge/tools/check_wiki_lint.py — no errors and no warnings across 1531 pages.

Boundary

The vLLM Router slice covers issue triage, CI, and release knowledge only. components/, models/, and _routes.yaml are not established, and adapters/vllm_router only injects the triage briefing, so the release page must not be treated as a code owner during review.