ApiCore

309 Commits 2 Branches 0 Tags

2 Commits

Include renames

Author	SHA1	Message	Date
Nick SzaunigandClaude Opus 5.5	c2f71bcb03	fix: T4a browser check findings Backend Image / build-and-push (push) Failing after 2m45s Details Frontend Image / build-and-push (push) Successful in 5m52s Details - Withdrawal wording from one backend helper everywhere ("bis einschließlich TT.MM. – ab TT.MM. wieder erntefähig", year when it crosses New Year); withdrawal-status returns lastBlockedDay and the ready text, the frontend no longer computes dates - Calendar events name colony or apiary, withdrawal events carry product and detail; compact withdrawal rows on mobile - One bottling warning per colony and treatment; pre-save hint - Offline: online-only actions disabled with a reason, cached data shows its timestamp, open sheets block submit offline - Mobile: no horizontal scroll at 360 px, touch targets >= 44 px, toasts and the add button no longer cover content - Cleanup sheet without destructive preselection; natural sort of colony codes; collapsible automation rule cards; varroa list newest first with chart axes; text fixes Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-14 18:26:09 +02:00
Nick SzaunigandClaude Opus 5.5	ef33e5549b	feat: T4 wave 5 - colony end cleanup, withdrawal chain, next steps, inspection takeover UI - Colony end releases the queen in the same transaction; open suggestions become obsolete and a CLEANUP suggestion lists open tasks and the queen; apply-cleanup validates evidence and blocks reactivated colonies - Withdrawal chain: plausibility warnings on harvest and bottling, conflict notifications also when a treatment is entered or corrected after the harvest (naming bottled lots), withdrawal spans in the calendar and M365 sync, Berlin-day end events - Next 3 steps per colony and the "Heute" endpoint with ranking and an explicit merge table by intent - Inspection-triggered rule suggestions follow the colony's latest inspection (resolve when the finding is gone, refresh when it stays) - Frontend: colony card takeover in the inspection form, feed status as condition, occupied frames 0-40; legacy offline entries keep syncing - Notifications and preferences are deleted with their user Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>	2026-10-14 16:28:07 +02:00

Author

SHA1

Message

Date

Nick SzaunigandClaude Opus 5.5

c2f71bcb03

fix: T4a browser check findings

Backend Image / build-and-push (push) Failing after 2m45s

Details

Frontend Image / build-and-push (push) Successful in 5m52s

Details

- Withdrawal wording from one backend helper everywhere ("bis
  einschließlich TT.MM. – ab TT.MM. wieder erntefähig", year when it
  crosses New Year); withdrawal-status returns lastBlockedDay and the
  ready text, the frontend no longer computes dates
- Calendar events name colony or apiary, withdrawal events carry
  product and detail; compact withdrawal rows on mobile
- One bottling warning per colony and treatment; pre-save hint
- Offline: online-only actions disabled with a reason, cached data
  shows its timestamp, open sheets block submit offline
- Mobile: no horizontal scroll at 360 px, touch targets >= 44 px,
  toasts and the add button no longer cover content
- Cleanup sheet without destructive preselection; natural sort of
  colony codes; collapsible automation rule cards; varroa list newest
  first with chart axes; text fixes

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

2026-10-14 18:26:09 +02:00

Nick SzaunigandClaude Opus 5.5

ef33e5549b

feat: T4 wave 5 - colony end cleanup, withdrawal chain, next steps, inspection takeover UI

- Colony end releases the queen in the same transaction; open
  suggestions become obsolete and a CLEANUP suggestion lists open
  tasks and the queen; apply-cleanup validates evidence and blocks
  reactivated colonies
- Withdrawal chain: plausibility warnings on harvest and bottling,
  conflict notifications also when a treatment is entered or corrected
  after the harvest (naming bottled lots), withdrawal spans in the
  calendar and M365 sync, Berlin-day end events
- Next 3 steps per colony and the "Heute" endpoint with ranking and an
  explicit merge table by intent
- Inspection-triggered rule suggestions follow the colony's latest
  inspection (resolve when the finding is gone, refresh when it stays)
- Frontend: colony card takeover in the inspection form, feed status as
  condition, occupied frames 0-40; legacy offline entries keep syncing
- Notifications and preferences are deleted with their user

Co-Authored-By: Claude Opus 5.5 (1M context) <[email protected]>

2026-10-14 16:28:07 +02:00