Task Plan

Checklist

Reuse the already-published managed-portal-20260519-f3f40b5-11.zip main bundle and cut updated installer/weights artifacts for the same tag.
Publish the updated installer and separate weights archive to 10.8.0.1 and verify the HTTP endpoints.
Commit and push the repository changes for the split-weights Ubuntu installer flow.

Scope: keep the existing OTA application ZIP for 20260519-f3f40b5-11, generate a refreshed installer plus separate people-flow weights archive for that same release tag, publish them to 10.8.0.1, and push the supporting repository changes to Git.
Expected touch points: .11 release artifacts, /var/www/html/ai_deploy on 10.8.0.1, deploy/package-managed-portal-ota.sh, deploy/install-managed-portal-ota.sh, README.md, .gitignore, and task tracking files.
Risk: reusing the existing main ZIP means the installer and weights archive must remain compatible with the already-published managed-portal-20260519-f3f40b5-11.zip.
Risk: the current local repository does not contain real weights payload files, so the separate weights archive may need to be generated from the .11 host release workspace or a stable host weights directory instead of local source control.
Risk: the commit must exclude local artifact files and only capture the intended repo changes.

Prove the refreshed installer and separate weights archive exist for tag 20260519-f3f40b5-11.
Prove both artifacts are downloadable from 10.8.0.1/ai_deploy.
Prove the Git commit/push contains only the intended repository changes.