Let a plugin add links to the profile menu, and list the setting conflict kind

e2e-tests/full-flow.spec.ts

@@ -250,8 +250,9 @@ test.describe.serial("authenticated admin journey", () => {
   test("logout: signing out ends the session and returns to the login page", async () => {
     await page.goto("/dashboard");
     await page.locator("button.profile").click(); // open the profile dropdown
-    // Sign out is the only item in it — the menu offers nothing that goes nowhere.
-    await expect(page.locator("#profile-menu .menu-item")).toHaveText(["Sign out"]);
+    // The scheduling plugin's profile entry sits above Sign out, which stays last.
+    await expect(page.locator("#profile-menu .menu-item")).toHaveText(["My shifts", "Sign out"]);
+    await expect(page.locator('#profile-menu a.menu-item[href="/scheduling/mine"]')).toHaveCount(1);
     await page.locator('form[action="/logout"] button[type="submit"]').click();
     await page.waitForURL(/\/login(\?|$)/);
     // The session is gone: /dashboard is gated, so it bounces back to the login page (no admin nav).