[ukyovfx]

Summary

Adds an opt-in Task detail Working-files panel on the v1.0.70 source baseline. It lists server-created revisions, uploads and downloads through Kitsu's existing authenticated client, and keeps failed upload retries attached to the same WorkingFile ID. Browser-file revisions remain distinct from AYON workfiles/publishes. The upload form is limited to assigned users; project managers/admins can view without being assigned, and clients do not see the panel.

Verification

• vitest run tests/unit/widgets/taskworkingfiles.spec.js tests/unit/pages/task.spec.js tests/unit/locales/parity.spec.js: 71 passed.
• ESLint on changed Vue/JS/test files: passed.
• Vite production build: passed. Existing CSS pseudo-element and bundle-size warnings remain.
• Synthetic tests only. No live Kitsu/Zou, authenticated browser, AYON, or Production environment was contacted.

Known acceptance blocker

The inspected Zou 1.0.94 Working-file routes use project/entity access checks. The list and download routes do not enforce task assignment; the create route also auto-assigns the current user. The UI gates are not a server-side security boundary. This PR does not claim that an unassigned user is blocked from calling the APIs directly. Before adopting the feature, verify and, if needed, separately change Zou authorization semantics and regression-test existing clients. Also run an authenticated browser UAT with synthetic accounts and exact deployed Kitsu/Zou versions.

No deployment, service change, migration, or Production data access was performed.

[ukyovfx]

Withdrawn by the author. This implementation is no longer being pursued upstream.