chore: refresh CLAUDE.md repository guidance

[DYAI2025]

Repository / Claude guidance maintenance

This PR refreshes the root CLAUDE.md — the guidance file Claude Code loads for this repository. It is maintenance only.

• Updates only CLAUDE.md. No source, test, migration, contract or packages/ui/** file is touched.
• Reconstructed against current origin/master (f8e96e4ceb4f00ae5f5ac777c6eb47aa8f766d6f): every claim was re-measured against that tree, not against the older checkout the draft started from. It condenses the snapshot-heavy sections and adds what has landed since the file was last revised — the Sprint-7 acceptance gate (EYT-148), the two client shells (EYT-113), the Basisdesign v2 token source (EYT-80), the VPS staging state since 24.08.2026 with the release-images workflow, the scaffolded-vs-reserved module distinction, and the Turbo/Playwright/vitest traps.
• Guards pass. The two unit-tests suites that read CLAUDE.md — apps/api/test/handoff-guardrails.test.ts and apps/api/test/sprint7-acceptance-rule-guardrails.test.ts — run green on this branch (2 files, 58 tests). prettier --check CLAUDE.md and git diff --check are clean. No test was weakened, modified or skipped.
• Counter-mutation evidence. Replacing the phrase is binding for all Sprint-7 in CLAUDE.md turned the Sprint-7 guard red (wird von CLAUDE.md als bindend referenziert failed with the exact toContain assertion), then the phrase was restored. The guard is binding, not decorative.
• No EYT-160 implementation. EYT-160 has not been started; it will get its own branch off an unchanged origin/master.
• No EYT-158 implementation. PR feat(web): EYT-147 Dispositionswerkbank Slice 1 — die Woche ist die Werkbank #101 is not touched, and none of its files overlap with this change.
• No excluded local/untracked files. The originating checkout's untracked items (.claude/settings.json, .claude/settings.local.json, scripts/claude/, scripts/ops/sitzungszustand.sh, the Softwaredokumentation.md copies, untracked docs/plans/*) and its other uncommitted edits are deliberately not part of this branch. git diff --name-only origin/master...HEAD returns exactly CLAUDE.md.

Do not merge without the usual review; the branch carries a single commit.

🤖 Generated with Claude Code

https://claude.ai/code/session_016HxEf6BYZejbrpKdRcXt7e

Summary by Sourcery

Refresh CLAUDE.md so repository guidance accurately reflects the current architecture, workflows, deployment state, and verification requirements.

Enhancements:

• Refresh the repository’s Claude Code guidance to reflect the current architecture, module scaffolding, client shells, design-token source, testing pitfalls, and evidence-based verification practices.
• Replace stale repository snapshots with concise instructions for current CI, deployment, staging, and repository-identity workflows.
• Clarify deployment boundaries, staging status, release-image publishing, and safeguards around migrations, tenancy, authentication, and acceptance evidence.

Documentation:

• Update the root CLAUDE.md repository guidance without changing source code, tests, or other project files.

Tests:

• Validate the refreshed guidance against the handoff and Sprint 7 guardrail suites without weakening or modifying tests.

[sourcery-ai]

Sorry @DYAI2025, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 1 day and 19 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This maintenance-only PR rewrites the root CLAUDE.md to reflect the current repository state, replacing stale snapshots with concise authoritative guidance and adding current architecture, staging, verification, and tooling guardrails; no source or test implementation files are changed.

File-Level Changes

Change	Details	Files
Condense and rebaseline repository/product guidance against the current master tree.	Remove dated snapshot-heavy implementation and deployment details that should be re-measured. Clarify document authorities, architecture ADRs, MVP/design baselines, and current deployment state. Add guidance for the two client shells, Basisdesign v2 tokens, scaffolded versus reserved modules, and current staging/container workflows.	CLAUDE.md
Expand operational verification guidance and document tooling/test pitfalls.	Add repository identity and origin/master checks before mutations. Document Turbo cache replays, strict environment mode, Vitest filters, stale build output, Playwright configuration, and staging prerequisites. Add a command-oriented verification matrix covering formatting, builds, tests, migrations, tenant isolation, runtime, deployment, and CI evidence.	CLAUDE.md
Strengthen architectural, security, deployment, and testing guardrails in the repository instructions.	Refresh module-boundary rules, gateway/proxy behavior, client-shell/session rules, design-token ownership, and database/RLS constraints. Document VPS staging and release-image behavior while retaining cloud-staging and Railway caveats. Add compact instructions for preserving SHA-bound evidence, counter-mutation proof, blockers, and claim provenance.	CLAUDE.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.