Upgrade Pixelbot to Pixeltable 0.7.7

[pierrebrunelle]

Problem

Pixelbot was pinned to Pixeltable 0.6.5, mutated its catalog during startup, exposed database mutation and removed Reve APIs, and could not be installed as a clean backend package. Its frontend also shipped a 981 kB initial JavaScript chunk and had lint failures.

Result

This upgrades Pixelbot to 3.0.0 on Pixeltable 0.7.7 and moves the application to the app-first TableModel and FastAPIRouter workflow. It introduces the fresh pixelbot_v3 catalog, isolates CSV scratch tables, removes Reve and catalog mutation routes, adds catalog/file/URL/webhook boundaries, packages the lazy-loaded SPA in the Python wheel, and updates the bundled Pixeltable skill and documentation.

The old agents catalog is never opened or changed.

Validation

• Ruff check and format pass
• Mypy passes all 21 backend source files
• Pytest: 10 passed
• Frontend: 3 tests passed, lint passed, production build passed
• Initial JS chunk: 271.64 kB; largest route chunk: 146.57 kB
• Wheel and sdist build successfully
• Clean Python 3.11 wheel installation includes the SPA
• Pixeltable schema check passes
• Fresh-catalog dry run reports 21 creates, zero unsupported changes, and zero destructive changes

Release blocker

A full local schema apply was stopped after five minutes while the Pixeltable 0.7.7 daemon consumed CPU creating video_transcript_sentences; six preceding models were created without error. The clean second diff and service start/health/log/stop checks remain required CI release gates. Provider calls, hosted deployment, Cloud behavior, and the 48 agent trials were not run.

Detailed evidence and reproduction commands are in docs/pixeltable-0.7.7-upgrade.md.