Link to another page not updated when renaming the page can lead to a strange behaviour

[estux]

Describe the bug
It's a problem related to links not fully updated when renaming pages. Let me explain this case.
Context:
I'm using a public shared Collective as a (live updated) Knowledge Base of an event where we'll host some people. There are some pages with more static infos (like infos about accommodations and food) and other pages updated daily (used as Announcements channel). The problem arose with links to this second ones. (I'm testing the functionalities before building out all of the knowledge base)

Bug:
I have a page named "Announcements" with some sub-pages that I will create daily. Every sub-page has the name of the day (until today) but there's a page named "Tomorrow" for things to announce in advance for tomorrow's activities.
The structure is something like this:

• Announcements
  • Tomorrow (last part of the url: Tomorrow?fileId=419855)
  • 17-06-2024 (last part of the url: 17-06-2024?fileId=419776)
  • 16-06-2024
  • 15-06-2024

In the main page Announcements I have a link to the page "Tomorrow" and here's the culprit: every day I rename the page Tomorrow with the date of that day and I create a new page named "Tomorrow" (that is exactly the same name of the old page) but the link in the Announcements page is malformed (and not updated) leading to strange behaviour.
Back to my previous example:
The link in the page "Announcements" was pointing to Tomorrow?fileId=419776 in the origin, then I renamed the file to 17-06-2024 but the link in the page Announcements remained unchanged (still points to Tomorrow?fileId=419776).
Desktop browser (Firefox 127):

• clicking the link it will lead to the file named Tomorrow (that is every day a new one), so the page with fileId=419855 (but the link points to Tomorrow?fileId=419776 so it seems it prioritized the name vs fileId)

Mobile browser (Firefox/Fennec):

• clicking the link one time will lead to a blank page, then clicking the reload arrow it will lead to the file named Tomorrow like with the desktop browser.

In my case paradoxically it's good that it will load always the page named Tomorrow but I think this is not an intentional behaviour (and on mobile there's the blank page as first result, so still not optimal).

To Reproduce
Steps to reproduce the behavior:

1. Create a page in a Collective
2. Create some sub-pages of this page
3. In the main page place a link (with smart picker or drag-n-drop) to one of the sub-pages
4. then change the name of this linked sub-page and create another sub-page with exactly the same name of the renamed one
5. go in the main page and click the link, this will lead to the newly added sub-page and not to the old renamed one (but usually the link should follow the page, not the name)

Expected behavior
The link should follow the page (even renamed) and not the name (that can be used by a new page). I admit though that in some cases like mine it could be useful to choose if the link should follow the name (thus linking every time to a new page with the same name) or the page (even when it's renamed).

Screenshots
If applicable, add screenshots to help explain your problem.

Server details:

• Collectives app version: 2.12.0
• Nextcloud version: 28.0.6
• PHP Version: 8.2.14
• Database: mysql 10.5.23

Client details:

• OS: Windows 10
• Browser: Firefox
• Browser version: 127.0
• Device: laptop

Logs

Nextcloud log (data/nextcloud.log)

Insert your Nextcloud log here

Browser log

Insert your browser log here, this could for example include:

a) The javascript console log
b) The network log
c) ...