🧩 Vercel Labs Integration — Wrap-vs-Build & Drift-Kill Plan

OrchestKit · audit 2026-06-22 · 3 parallel agents (pin inventory · watcher coverage · live ecosystem scan)
Are we reinventing the wheel? No. 100% wrap, 0% reinvent — no skill reimplements a tool; they're guidance + orchestration wrappers (compose 3 CLIs in /ork:dev, add guardrails like expect forbidding agent-browser chat). The catch: each wrapper snapshots version-specific prose into the skill body, and the snapshot is already stale — agent-browser 0.27→0.29.1 (missed the v0.28 MCP server + v0.20 Rust rewrite), emulate 0.6.1→0.7.0. The plan kills the snapshot tax.
① Verdict & Drift
② Maintenance model
③ Coverage gaps
④ Phased fix plan
⑤ Opportunities
Drift bar = how far our pinned version trails current npm latest (longer + redder = more behind). Click a card for what we missed.

The real decision isn't wrap-vs-build (we already wrap) — it's how thin the wrapper should be. Pick a target model per integration; the trade-off updates below.

🔭 What the watcher sees scripts/check-labs-versions.mjs

Hardcoded TARGETS = 4 skills only. The mechanism is sound (it rebuilds plugins/ + opens a bot PR weekly Mon 08:00 UTC) — coverage is the problem.
GapDetailSeverity

Phased so each step is independently shippable. P0–P1 are additive & low-risk; P3–P4 are the structural drift-kill.

Live npm view scan of the vercel-labs org (Jun 2026). Beyond catching up, here's what's new worth wrapping.

Fit = how naturally it slots into an AI-coding plugin. DIRECT overlaps ork's own format · HIGH · MED · WATCH