fix: post-merge cleanup after freight/develop merge

- Remove orphaned container publish route (service method dropped on develop)
- turbo.json concurrency as string "12" (parse + 11 persistent-task limit)
- database.config: synchronize false (migrations only; fixes weight_limit_rules boot crash)

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

apps/edr-freight-api/src/config/database.config.ts

@@ -117,7 +117,7 @@ export default registerAs("database", (): TypeOrmModuleOptions => {
     ],
     migrationsRun: true,
     // Schema changes via migrations only (synchronize breaks ITMLS backfill on existing rows).
-    synchronize: true,
+    synchronize: false,
     logging: process.env.NODE_ENV === "development",
   };
 });

apps/edr-freight-api/src/modules/train-scheduling/train-scheduling.controller.ts

@@ -427,10 +427,4 @@ export class TrainSchedulingController {
   cancelBulkTrainSchedule(@Param("id", ParseUUIDPipe) id: string) {
     return this.trainSchedulingService.cancelTrainSchedule(id);
   }
-
-  @Post('container/schedules/:id/publish')
-  @ApiOperation({ summary: 'Publish container train schedule' })
-  publishTrainSchedule(@Param('id', ParseUUIDPipe) id: string) {
-    return this.trainSchedulingService.publishTrainSchedule(id);
-  }
 }

turbo.json

@@ -1,5 +1,6 @@
 {
   "$schema": "https://turbo.build/schema.json",
+  "concurrency": "12",
   "tasks": {
     "build": {
       "dependsOn": ["^build"],