chore: reconcile contribution rules and onboarding fixtures

Extract the guided setup test fixture without dropping cases. Supply current settings/discovery contracts and Opus 5.5 in the isolated Storybook boundary.

Co-Authored-By: Paperclip <noreply@paperclip.ing>

server/src/__tests__/issue-update-comment-wakeup-routes.test.ts

@@ -276,8 +276,6 @@ describe("issue update comment wakeups", () => {
     mockIssueService.getWakeableParentAfterChildCompletion.mockResolvedValue(null);
     mockIssueService.getCurrentScheduledRetry.mockResolvedValue(null);
     mockIssueService.listReviewAttention.mockResolvedValue(new Map());
-    // A fresh route graph is fixture preparation, not request execution. Keep
-    // per-case module resets while charging the cold transform to hookTimeout.
     routeFixture = await loadRouteFixture();
   });
 

server/src/__tests__/teams-catalog-install-no-overrides.test.ts

@@ -11,8 +11,6 @@ import {
 } from "./helpers/embedded-postgres.js";
 import { teamsCatalogService } from "../services/teams-catalog.js";
 
-// Bind the real creation resolver to the release target under test so the
-// catalog contract is stable across the machines running this fixture.
 vi.mock("../services/agent-runner-selection.js", async importOriginal => {
   const actual = await importOriginal<typeof import("../services/agent-runner-selection.js")>();
   return { ...actual, resolveNewAgentRunnerForCompany: async (_db: unknown, _companyId: string, input: Parameters<typeof actual.resolveNewAgentRunnerForCompany>[2]) =>