adapter(vllm-omni): target releases/v0.30.0 for the next rebase (#168)

## Change

Point the vllm-omni adapter's wheel pick and commit assignment at
`releases/v0.30.0`.

The v0.29.0 campaign merged as vllm-project/vllm-omni#7230, so the
adapter should now track the next release branch.

## Note for the reviewer

`releases/v0.30.0` is **cut but not yet tagged** (`f2aad6aa7`, branched
2026-09-15), and when this was written it carried no cherry-picks beyond
the main commit it was branched from. This tracks the branch head; the
pin moves to the tag commit once v0.30.0 is released, which is also when
`docker/Dockerfile.ci` in the target repo can drop its restored
commit-wheel block and go back to a published release image.

Tag cadence has been 15 days (0.28 Aug 24, 0.29 Sep 8), so expect the
re-pin around Sep 22.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude Opus 5 (1M context) <noreply@anthropic.com>

Author: tzhouam

adapters/vllm_omni/manifest.yaml

@@ -25,9 +25,11 @@ upstream:
   kind: fork_tracking
   repo_path: ${VLLM_UPSTREAM_REPO}
   remote: origin
-  # v0.29.0 alignment campaign (audited 2026-09-05): wheel pick and
-  # commit assignment target the release branch, not upstream main
-  target_branch: releases/v0.29.0
+  # v0.30.0 alignment campaign (2026-09-17): wheel pick and commit
+  # assignment target the release branch, not upstream main. The branch
+  # is cut but NOT yet tagged, so this tracks the branch head and is
+  # re-pinned to the tag commit once v0.30.0 is released.
+  target_branch: releases/v0.30.0
 
 # Repo-specific slice of the SHARED, human-curated knowledge base (the vendored
 # community docs at the repo-root `knowledge/` = settings.knowledge_dir;