Nick SzaunigandClaude Opus 5.5
ef33e5549b
- 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]>
22 lines
866 B
TypeScript
22 lines
866 B
TypeScript
import { Module } from '@nestjs/common';
|
|
import { AuditModule } from '../audit/audit.module';
|
|
import { QueensModule } from '../queens/queens.module';
|
|
import { TasksModule } from '../tasks/tasks.module';
|
|
import { CleanupController } from './cleanup.controller';
|
|
import { CleanupService } from './cleanup.service';
|
|
import { SuggestionsModule } from './suggestions.module';
|
|
|
|
/**
|
|
* The clean-up of an ended colony, API only: it settles tasks and the
|
|
* queen, which pulls QueensService (and with it the webhooks) in. Kept apart
|
|
* from SuggestionsModule so the CLI jobs, which import that one, do not
|
|
* need them. The permission resolver comes from the global
|
|
* PermissionsModule.
|
|
*/
|
|
@Module({
|
|
imports: [SuggestionsModule, TasksModule, QueensModule, AuditModule],
|
|
controllers: [CleanupController],
|
|
providers: [CleanupService],
|
|
})
|
|
export class CleanupModule {}
|