Integrate OpenCut Classic

Operate the legacy repository as archived, unmaintained evaluation software.

Workflow

Read references/integration.md before cloning, installing, starting services, or changing configuration.
Verify remote, pinned commit, MIT license, and clean/dirty status.
Choose the narrowest route: static inspection, frontend-only dev, full local services, build/test, or optional WASM/desktop work.
Show all dependency, environment-file, Docker, port, and filesystem effects before installation.
Prefer frontend-only setup when database and Redis are unnecessary.
Keep Docker, database writes, container lifecycle, deploy scripts, package publication, and external services behind explicit approval.
Run a focused validation for the selected route and report archived status and known failures without upgrading claims.

Never call this maintained or production-ready.
Do not claim import, timeline, preview, or export works until reproduced on the pinned checkout with owned test media.
Do not place secrets in .env.local; start from the example and review every value.
Preserve dirty worktrees and existing containers.

Return repository identity, chosen route, prerequisites, commands, ports/containers changed, validation evidence, and unresolved legacy risks.