Skip to content

Research 0106 — Public Doc Stub Sweep

Research-0106

Date: 2026-05-14

Question

After the vmaf-tune scaffold closures, which public docs still carry stale stub/scaffold labels that are contradicted by current implementation status?

Findings

  • docs/usage/vmaf-tune-resolution-aware.md still described --resolution-aware as a stub even though resolution.py, corpus.iter_rows, and tests/test_resolution.py already exercise the default-on model selector.
  • docs/development/ossf-scorecard.md, docs/development/ffmpeg-patches-refresh.md, and docs/ai/per-pr-doc-bar.md had enough substantive content to stand as real topic pages, but still carried Research-0086 stub banners.
  • docs/ai/ensemble-training-kit.md and docs/ai/models/vmaf_tiny_v5.md describe proposed/deferred surfaces. They should say that directly instead of using a generic stub label.
  • tools/vmaf-tune docs still had stale Phase-D ADR references pointing at the old ADR-0276 path instead of ADR-0392.

Decision

Remove stale stub banners from public usage, AI, and development docs when the page already has a real accepted/proposed/deferred status to communicate. Leave true scaffold-only artefact pages alone, including U2Net mirror and local sidecar training.

Validation

rg -n '^# .*\\(stub\\)|^# .*stub|> \\*\\*Stub\\*\\*|0276-vmaf-tune-phase-d|full prose follows|later PR' \
  docs/usage docs/ai docs/development tools/vmaf-tune/README.md tools/vmaf-tune/src/vmaftune \
  -g '*.md' -g '*.py'