Delete the JOURNEY-only type guard in JourneyItemService.append() so the existing item endpoints serve both Geschichte types. GeschichteType has exactly two constants, so an allowlist replacement would be unreachable dead code. Fix the not-found messages that claimed "Journey", and remove the now-orphaned GESCHICHTE_TYPE_MISMATCH error code end to end (ErrorCode, errors.ts union + mapping, i18n keys in de/en/es). Tests: three STORY append unit tests written red against the guard, plus end-to-end STORY coverage (append+retrieve, V72-style position-gap rows incl. removal, dangling document-deleted item). The two STORY-rejection tests die with the guard — no third enum value exists to feed it. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
68 KiB
68 KiB