Track blocked 2026-03-21 batch candidates

[chenrui333]

Blocked candidates from the 2026-03-21 tap batch:

• asciify-them: depends on opencv-python, and PyPI currently publishes wheels only for that package (no sdist), so this is not a clean source-build formula path.
• buddy: upstream is GitHub-source only and local pip --dry-run resolves wheel-only runtime deps (numpy, pillow, imageio-ffmpeg), which would require vendoring prebuilt Python wheels.
• lixplore: resource resolution expands to a large scientific stack (numpy, scipy, scikit-learn, pandas, matplotlib, gensim, wordcloud) and also a wheel-only pyvis dependency, so it is not currently a clean tap formula.
• traul: local bun install --frozen-lockfile succeeds, but bun build --compile src/index.ts --outfile traul fails resolving platform-specific @node-llama-cpp/* modules from node-llama-cpp.

This issue is the blocker ledger for the remaining uncovered shortlist items after packaging the rest of the 2026-03-21 batch.

[chenrui333]

Rechecked the four candidates against current upstream/package state on 2026-07-18.

• asciify-them is now at 1.1.1. The original wheels-only premise is stale: its exact opencv-python 4.12.0.88 pin now has an sdist. It needs a fresh source-build evaluation rather than remaining classified as impossible.
• buddy still uses the source repo and depends on numpy, imageio, and imageio-ffmpeg, but the previously cited imageio-ffmpeg release line now has an sdist. It also merits a fresh build evaluation.
• lixplore remains blocked by the large scientific dependency surface and pyvis 0.3.2 still being wheel-only.
• traul 0.2.0 still carries the platform-specific @node-llama-cpp/* optional packages in bun.lock, so its compile blocker has not clearly been removed.

Leaving this tracker open, but narrowing the actionable work to fresh asciify-them and buddy build checks; lixplore and traul remain blocked.