Summary

For an already-installed community app, changing only the title in CloudronManifest.json (same id, new version, same everything else) causes the update in app UI updates to fail. The docs describe title as display-only and describe id as the app's identity, so a title-only change should not break an update.

Reproduction

1. Community app installed on an instance from a CloudronVersions.json URL.
2. In CloudronManifest.json, bump version and change only title (keep id identical).
3. Publish the new version to CloudronVersions.json / host it.
4. Attempt the update from the dashboard (or cloudron update).

Expected: update succeeds; the app's displayed name reflects the new title

Actual: the update fails. Reverting title to its previous value and publishing again lets the update proceed. I removed and reinstalled the app afterwards, so I no longer have the original task/box log.

What the docs say

The title field is documented purely as:

"The title is the primary app title displayed on the Cloudron App Store."

Only id is documented as identity:

"The id is a unique human friendly App Store id."

https://docs.cloudron.io/packaging/manifest/

Questions

1. Is title intended to be immutable/identity for an already-installed app, i.e. is the effective key id + title rather than just id? If so, the manifest docs should state that plainly — they currently present title as display-only.
2. If it's not intended, is this a validation bug? The update appears to reject a manifest that differs only in a display field.
3. Is there a supported way to rename an existing community app via the manifest? Using the dashboard app label is a workaround, not a fix — the manifest title is what new installs and the App Store use, so the installed app and the package listing then diverge.

Want to clarify before I attempt more renames via CloudronManifest.json title.

EDIT :
This is not about ca.cloudron.io which accepts the title change. It's about installed app dashboard, Updates / Check for updates / update.