Use autonomous-app-completion on the attached GLMChat V2.2.1 new-chat handover bundle.

Treat app/ and release/GLMCHAT_V2.2.1_SERVER_DIRECT_DEPLOY_CONTINUED_22072026154516.zip as the authoritative current release. Read documentation/current/NEW_CHAT_HANDOVER_*.txt, CURRENT_ISSUE_STATUS_*.txt and the latest validation report before acting.

Continue autonomously from the outstanding production gates. Do not redo or claim already completed checks without evidence. Before changing any application file, create a complete baseline snapshot from the actual files. Preserve all unrelated features, structure, styling, data, routes, PWA behaviour and PHP/SQLite/LiteSpeed architecture. Do not delete or overwrite production storage data.

Priority order:
1. Set up a PHP 8.2+ environment with sqlite3, curl, mbstring, zip, fileinfo, json and openssl.
2. Run the successful backend, authentication, migration and SQLite workflows.
3. Validate root and nested LiteSpeed deployment, rewrites, private-path denials, HTTPS, cookies and security headers.
4. Test an upgrade and rollback against a cloned real pre-V2.2.1 storage directory.
5. Run live Together text, vision, function/tool and TTS acceptance, including failure paths.
6. Test streaming, cancellation, concurrency, long-running workflows, quota pressure and file/ZIP handling.
7. Complete physical Android Chrome, Samsung Internet and TalkBack acceptance when available.
8. Obtain or identify the matching source repository before claiming build, type-check, lint or source test completion.

Fix confirmed defects using the smallest safe changes. After each stage, self-verify and continue without awaiting confirmation. On completion, regenerate the manifest/SBOM where applicable, create the required timestamped CHANGES_hhmmddmmyyyy.txt unified diff, update documentation, and provide a verified direct-deploy ZIP plus a complete new-chat handover bundle.