fix: revert VP9 neko config to fix laggy mouse movement

[hiroTamada]

Checklist

• A link to a related issue in our repository: Reverts the capture config from [kernel-cus-78] feat: update neko config #175
• A description of the changes proposed in the pull request.
• @mentions of the person or team responsible for reviewing proposed changes.

Summary

• Removes the VP9 capture configuration from neko.yaml that was added in [kernel-cus-78] feat: update neko config #175, reverting to Neko's default codec (VP8)

Problem

The VP9 encoder config introduced in v35 (#175) causes significant input latency (laggy mouse movement) in live view on 4-vCPU unikernel instances. VP9 encoding with threads: 4 saturates all available vCPUs, starving the input processing pipeline.

This was confirmed by deploying v33, v34, and v35 side-by-side on the same dev metro — v34 (pre-#175) feels responsive while v35 (post-#175) has noticeable mouse lag.

Fix

Revert to Neko's default codec (VP8), which restores the responsiveness seen in v34. VP9 tuning can be revisited later with either:

• More aggressive speed settings (cpu-used: 8, threads: 2)
• Larger instance sizes where the CPU headroom exists
• H264 as an alternative low-latency codec

Test plan

• Deployed v34 and v35 images side-by-side on dev metro and confirmed v34 has no mouse lag
• Build and deploy a new image with this change and verify mouse responsiveness matches v34

Made with Cursor

---

Note

Low Risk
Low risk config-only change that removes a custom VP9 encoder pipeline; primary risk is unintended codec/quality behavior changes in WebRTC clients after reverting to defaults.

Overview
Reverts the custom capture.video VP9 configuration in images/chromium-headful/neko.yaml, removing the tuned GStreamer vp9enc pipelines and related params.

Neko will fall back to its default capture/codec settings (expected to reduce CPU usage and input latency, at the cost of any VP9-specific quality/compatibility tweaks).

^{Written by Cursor Bugbot for commit a5d0a39. This will update automatically on new commits. Configure here.}