feat(WP-67): merge behandelportal into this repo as a monorepo

Restructures into apps/ssp + apps/behandelportal (two Angular projects)
plus libs/shared + libs/beheer (cross-app libraries), replacing WP-61's
separate sibling repo. That split had already produced real drift: a
hand-vendored copy of the backend's OpenAPI doc, a shared/ui+layout tree
forked and silently diverging (7 files), and beheer + the styles.scss
token bridge duplicated byte-for-byte across both repos.

- git mv the SSP's src/app/* into apps/ssp/; fold shared/, beheer/,
  environments/, the Storybook docs/*.mdx, and styles.scss into
  libs/shared + libs/beheer (all confirmed identical between the two
  repos before merging). auth stays deliberately duplicated per
  ADR-0002 (actor-specific, expected to diverge) - amended there.
- One generated API client (libs/shared), no more vendored swagger.json.
- .dependency-cruiser split into a base factory + one config per app,
  and Storybook into .storybook-ssp/.storybook-behandelportal - both
  forced by the @auth/* alias resolving to different directories per app.
- SiteHeaderComponent/ShellComponent gained HEADER_NAV_ITEMS/
  HEADER_ADMIN_LINKS/DEBUG_PANEL injection tokens so each app supplies
  its own nav/admin-links/dev-panel instead of one being hardcoded.
- CLAUDE.md, ARCHITECTURE.md, dependencies.md, and ADR-0002 updated;
  WP-67 backlog entry documents the full decision trail.

npm run ci green (lint, dep:check x2, 360 tests across ssp/
behandelportal/shared/beheer, both localized builds, backend tests,
snippet + api-client drift); both dev servers, both Storybook
instances, and docker compose verified working.

The old sibling repo (/home/eho/repos/behandelportal) is left
untouched, not deleted.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

apps/ssp/src/app/brief/ui/besluit-panel/besluit-panel.stories.ts

@@ -0,0 +1,65 @@
+import type { Meta, StoryObj } from '@storybook/angular';
+import { LibraryPassage } from '@brief/domain/brief';
+import { BesluitPanelComponent } from './besluit-panel.component';
+
+const text = (t: string): LibraryPassage['content'] => ({
+  paragraphs: [{ nodes: [{ type: 'text', text: t }] }],
+});
+
+const passages: LibraryPassage[] = [
+  {
+    passageId: 'p-kern-positief',
+    scope: 'global',
+    sectionKey: 'kern',
+    label: 'Toewijzing',
+    version: 1,
+    besluit: 'positief',
+    content: text('Toegewezen.'),
+  },
+  {
+    passageId: 'p-kern-negatief',
+    scope: 'global',
+    sectionKey: 'kern',
+    label: 'Afwijzing',
+    version: 1,
+    besluit: 'negatief',
+    content: text('Afgewezen.'),
+  },
+  {
+    passageId: 'p-kern-scholing',
+    scope: 'global',
+    sectionKey: 'kern',
+    label: 'Onvoldoende scholing',
+    version: 1,
+    besluit: 'negatief',
+    reason: 'onvoldoende_scholing',
+    content: text('Onvoldoende scholing.'),
+  },
+  {
+    passageId: 'p-kern-gegevens',
+    scope: 'global',
+    sectionKey: 'kern',
+    label: 'Onjuiste gegevens',
+    version: 1,
+    besluit: 'negatief',
+    reason: 'onjuiste_gegevens',
+    content: text('Onjuiste gegevens.'),
+  },
+];
+
+const meta: Meta<BesluitPanelComponent> = {
+  title: 'Domein/Brief/Besluit Panel',
+  component: BesluitPanelComponent,
+  args: { passages },
+};
+export default meta;
+type Story = StoryObj<BesluitPanelComponent>;
+
+/** Pick a besluit; a negatief besluit reveals the reason checkboxes. Each change emits
+    `selectionChange` and the kern's standaardteksten follow live — no generate button. */
+export const Default: Story = {};
+
+/** Re-seeded from a persisted letter: a negatief besluit with a reden already ticked. */
+export const NegatiefMetReden: Story = {
+  args: { besluit: 'negatief', initialRedenen: ['onvoldoende_scholing'] },
+};