Marc-André Bombeck 146a02319d refactor(medications): give the in-use clock list one owner ...

The supply tab carried its own copy of the two container kinds whose first
opening starts a degradation clock, with a comment saying it mirrored the
state machine's list. Nothing enforced the mirror — the state machine types
itself against the generated Prisma client, which the browser bundle cannot
carry, so a copy was the only way to say it.

Move the list into a client-safe module with no imports and let both sides
read it. The state machine re-exports it under the Prisma enum, so a renamed
or dropped container kind is now a compile error rather than a member that
quietly stops matching.

2026-07-27 14:47:54 +02:00

..

__tests__

test(medications): cover the container kind on the import and refund paths

2026-07-26 18:00:08 +02:00

clock-container-types.ts

refactor(medications): give the in-use clock list one owner

2026-07-27 14:47:54 +02:00

consumption.ts

fix(medications): apply the post-opening clock only where a container has one

2026-07-26 18:00:07 +02:00

service.ts

fix(medications): apply the post-opening clock only where a container has one

2026-07-26 18:00:07 +02:00

state-machine.ts

refactor(medications): give the in-use clock list one owner

2026-07-27 14:47:54 +02:00

summary.ts

fix(medications): keep the inventory supply helper free of server-only logging

2026-06-21 09:53:27 +02:00