fix(router): derive the router base from the served URL

History mode broke deep links on the /index.php/... URL form. Nextcloud
serves the same app under BOTH /apps/stackiq/... and
/index.php/apps/stackiq/..., but generateUrl() returns only the form the
instance is configured for. Arriving on the other form left the path
outside the router base, vue-router could not resolve it, and the
catch-all redirected to '/' -- the visitor landed on the Dashboard with
no error and the deep link was silently swallowed.

Measured before the fix:

  /apps/stackiq/komplianties            -> Compliance
  /index.php/apps/stackiq/komplianties  -> Dashboard   <- silently wrong

Hash routing never had this: the route travelled in the fragment, so the
path prefix was irrelevant. This is the one real regression the switch
introduced, and it would have applied to every app in the rollout.

The e2e suite navigates via /index.php/..., which is exactly how it was
caught -- two index specs failed while manual browsing on the pretty URL
looked fine.

Now both forms resolve, with the path preserved.

Author: rubenvdlinde

src/main.js

@@ -130,6 +130,34 @@ const pageTypesProp = { ...defaultPageTypes }
 const customComponentsProp = { ...customComponents }
 const registryProp = { ...registry }
 
+/**
+ * The router base for THIS page load.
+ *
+ * ⚠️ `generateUrl('/apps/stackiq')` alone is not enough. Nextcloud serves the
+ * same app under BOTH `/apps/stackiq/...` and `/index.php/apps/stackiq/...`,
+ * but `generateUrl()` returns only the form the instance is configured for. If
+ * a visitor arrives on the other form — a bookmark, an emailed deep link, an
+ * integration that hardcodes `/index.php` — the path no longer starts with the
+ * router base, vue-router cannot resolve it, and the catch-all redirects to
+ * `/`. The user lands on the Dashboard with no error: the deep link is
+ * silently swallowed.
+ *
+ * Hash routing never had this, because the route travelled in the fragment and
+ * the path prefix was irrelevant. Measured on this app before the fix:
+ * `/apps/stackiq/komplianties` rendered Compliance, while
+ * `/index.php/apps/stackiq/komplianties` rendered the Dashboard — and that is
+ * the form the e2e suite uses, which is how it was caught.
+ *
+ * So derive the base from the URL actually being served, falling back to
+ * `generateUrl()` when the app segment is absent.
+ *
+ * @return {string} The base path vue-router should strip from the URL.
+ */
+function routerBase() {
+	const match = window.location.pathname.match(/^(.*\/apps\/stackiq)(?:\/|$)/)
+	return match ? match[1] : generateUrl('/apps/stackiq')
+}
+
 /**
  * Resolve `@resolve:<key>` IAppConfig sentinels in `manifest.pages[].config`
  * (e.g. `@resolve:voorzieningen_register`) APP-SIDE, before the router and
@@ -167,7 +195,7 @@ async function bootstrap() {
 		// /organisaties/abc-123 all return 200 with the app shell. Without
 		// that route a deep link 404s at the SERVER on reload, which is the
 		// reason apps fell back to hash mode (fleet #133).
-		history: createWebHistory(generateUrl('/apps/stackiq')),
+		history: createWebHistory(routerBase()),
 		routes: routesFromManifest(resolvedManifest),
 	})