fix: Paket 0 – data integrity, security hardening and field usability

Backend
- Backup covers every Prisma model (bundle v3); a guard test fails for any
  new model that is neither backed up nor explicitly excluded. Unsealed
  bundles may only add rows to 27 legacy master/field tables and never
  overwrite; counters, ledgers, settings, roles etc. need a sealed file.
  Shared import limit BACKUP_MAX_IMPORT_BYTES (default 50 MB, max 256 MB)
  with warnings in log and UI; replaced document files are removed after
  commit.
- Post-commit side effects (automation, calendar sync, webhooks) run via
  runAfterCommit and never turn a committed write into a 500, so retries
  with the same Idempotency-Key no longer create duplicates.
- Calendar outbox is multi-replica safe: per-entry claims with stale
  takeover, revision-based settle, new Graph event only on 404/410,
  transactionId on create, 30 s Graph timeout, URL-encoded ids, GUID
  validation for groupId, "run now" in background and resets FAILED.
- Automation tasks are deduplicated under a row lock on the rule.
- Update DTOs follow one null rule: omitted = unchanged, null clears a
  nullable field, null on a required field is a 400.
- Varroa mites/day is recomputed on correction; withdrawal status is
  checked against the harvest date (?at=), bounded colonyIds; inspection
  create is audited; updates re-enqueue calendar entries.
- Dashboard, statistics and apiary/colony guards treat WEAK, CONSPICUOUS
  and QUEENLESS colonies as living.
- Prisma errors and body-parser errors are logged without query values or
  request bodies.
- Migration 20261012100000_calendar_sync_claims; schema index name aligned
  with the existing database object.

Frontend
- Sticky save bar sticks again (no scroll container ancestors, card uses
  overflow-clip), safe-area insets, scroll-padding, FAB hidden on forms,
  sticky desktop sidebar.
- Inspections record yes / no / not checked instead of silent defaults.
- All living colonies are selectable; shared RecordSelect, EnumSelect,
  ChoiceGroup and TriStateField replace per-page copies; selects show
  names instead of ids; labels point at real controls.
- Emptied optional fields are sent as null (emptyToNull) so every field
  can be cleared; dates default to the local day and are sent via
  toApiDate.
- Harvest withdrawal warning uses the harvest date; backup page warns when
  a backup outgrows the import limit and lists skipped tables.

Build and docs
- Docker builds fail unless lint, typecheck and unit tests pass.
- ARCHITECTURE.md updated (assumptions 9-12, 19-21, section 8) and spec
  docs/superpowers/specs/2026-10-12-plattform-rueckgrat-und-fahrplan-design.md
  for the backbone (api/worker/job roles, domain event outbox) and the
  feature roadmap T3-T7.

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

ApiCore-Backend/src/feedings/dto/update-feeding.dto.ts

@@ -6,4 +6,6 @@ import { CreateFeedingDto } from './create-feeding.dto';
  * the wrong colony is a data-entry error, and re-filing it is the only way to
  * repair the colony's history without deleting the record.
  */
-export class UpdateFeedingDto extends PartialType(CreateFeedingDto) {}
+export class UpdateFeedingDto extends PartialType(CreateFeedingDto, {
+  skipNullProperties: false,
+}) {}

ApiCore-Backend/src/feedings/feedings.service.spec.ts

@@ -17,6 +17,7 @@ describe('FeedingsService', () => {
     };
   };
   let auditLog: { record: jest.Mock };
+  let calendarSync: { enqueue: jest.Mock; cancel: jest.Mock };
 
   const feeding = { id: 'feeding-1', colonyId: 'colony-1', date: new Date() };
 
@@ -31,7 +32,7 @@ describe('FeedingsService', () => {
       },
     };
     auditLog = { record: jest.fn() };
-    const calendarSync = { enqueue: jest.fn(), cancel: jest.fn() };
+    calendarSync = { enqueue: jest.fn(), cancel: jest.fn() };
     service = new FeedingsService(
       prisma as unknown as PrismaService,
       auditLog as unknown as AuditLogService,
@@ -91,6 +92,15 @@ describe('FeedingsService', () => {
     );
   });
 
+  it('update re-enqueues the calendar sync so a changed date moves the event', async () => {
+    prisma.feeding.findUnique.mockResolvedValue(feeding);
+    prisma.feeding.update.mockResolvedValue(feeding);
+
+    await service.update('feeding-1', { date: '2026-05-02' }, 'user-1');
+
+    expect(calendarSync.enqueue).toHaveBeenCalledWith('FEEDING', 'feeding-1');
+  });
+
   it('summaryByColony sums amounts per unit', async () => {
     prisma.feeding.groupBy.mockResolvedValue([
       { unit: 'l', _sum: { amount: 5.5 } },

ApiCore-Backend/src/feedings/feedings.service.ts

@@ -86,6 +86,9 @@ export class FeedingsService {
       beforeData: before,
       afterData: feeding,
     });
+    // A changed date or colony must move the calendar event, not leave the
+    // old one behind.
+    await this.calendarSync.enqueue('FEEDING', feeding.id);
     return feeding;
   }
 }