fix: move download and enable button to outside of details tab

[mykh-hailo]

• Resolves: App management: The "download and enable" button should be moved outside the sidebar tab #44125

Summary

This change improves discoverability of app lifecycle actions in the App Store sidebar by moving install, update, remove, enable/disable, App API deploy options, and “delete data on remove” out of the Details tab and into the sidebar header description area, next to badges and the store rating.

The Details tab now focuses on group limits, dependencies, metadata, and links (interact section), while primary actions stay visible without switching tabs.

Checklist

• Code is properly formatted
• Sign-off message is added to all commits
• Tests (unit, integration, api and/or acceptance) are included
• Screenshots before/after for front-end changes
• Documentation (manuals or wiki) has been updated or is not required
• Backports requested where applicable (ex: critical bugfixes)
• Labels added where applicable (ex: bug/enhancement, 3. to review, feature component)
• Milestone added for target branch/version (ex: 32.x for stable32)

AI (if applicable)

• The content of this PR was partly or fully generated using AI

[susnux]

Can you please add screenshots?
How does this look on mobile?

[mykh-hailo]

@susnux Here are the screenshots before and update.

Screenshot for Wide Screens.

Before	After

Screenshot for narrow screens.

Before	After

P.S. We have the title and score and the button section is clipped on the left. To fix this issue, we have to fix NcAppSidebar component.

[mykh-hailo]

@susnux I updated the code with the latest master branch.
I'd appreciate it if you check it please.

[mykh-hailo]

@susnux , @skjnldsv
Can you possibly give me any feedback on this PR please?

[mykh-hailo]

@susnux , @skjnldsv , @szaimen , @nfebe , @sorbaugh
I'd appreciate it if you have time to review this PR.

[artonge]

Looks good overall

[artonge]

Looks good

[szaimen]

Hi @mykh-hailo thanks a lot for the contribution!

I just tested this and there seems to be some problems with the limit apps to groups feature (it should be put onto a new line probably and not be positioned like a block element:

Grabacion.2026-04-13.163329.mp4

Additionally, there seems to be some problems with updating the internal state when using the enable, install or disable buttons so that always a full page reload is required to update the state:

Grabacion.2026-04-13.163527.mp4

[mykh-hailo]

@szaimen Thank you for your comments.
I updated the code base for that.
I'd appreciate it if you review it again.

[mykh-hailo]

@susnux , @szaimen I think we can merge this branch.
The cypress test failure is not related to my update.
My update is for the app sidebar but the test is for the app list.

[mykh-hailo]

@szaimen , @susnux please help me to merge this PR.
I don't think the cypress test is related to my updates.

[miaulalala]

Hey @mykh-hailo - seems there's some conflicts and unrelated changes.

To fix it, can you:

• sync your fork with the latest master as described here: https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork
• check out your master branch and run git pull
• check out this branch again
• git rebase origin/master -> this will bring some conflcts for the dist files - it doesn't matter how you resolve them as they need rebuilding anyway.
• When finished rebasing, build the JS files (npm ci && npm run build`), commit those
• git push --force-with-lease

[artonge]

@mykh-hailo the failing settings/apps.cy.ts e2e test seems really related.

[mykh-hailo]

@artonge can I update settings/apps.cy.ts?

[mykh-hailo]

@artonge I updated the test for it.
could you review again please?

[mykh-hailo]

@artonge , @szaimen , I updated the test for my update code but I am not sure if git actions use it.
Can you help me with that?

[szaimen]

Hi @mykh-hailo I fear I cannot help you further on this. Probably best if you post your questions in https://cloud.nextcloud.com/call/xs25tz5y going forward. Thanks!

[mykh-hailo]

Just one question @szaimen
I updated the cypress test for my update.
It will make this PR to pass the test successfully.

@mykh-hailo unfortinately the failing test seems to be related to your changes. Maybe the test needs to be adjusted?

[mykh-hailo]

@szaimen Hope you are doing great.
I check the test result and none of the failures are related to my updates.
Can you check it again and help me to merge it?

[szaimen]

Hi @mykh-hailo i think this change is now done with #57290. sorry for not informing you earlier. I didnt notice @susnux was working on the same change in a different PR.

[susnux]

Yes with the Vue 3 migration this is already accomplished.
But thank you anyways very much, your contributions are highly appreciated!