@solvice/routing 0.19.1-beta.0 → 0.19.2-beta.0

package/dist/runs.d.ts

@@ -258,7 +258,7 @@ export interface components {
          *     New values may be added; clients must accept unknown values and handle
          *     them generically, for example by showing `message`.
          *
-         *     Known values: `unreachable`, `max_leg_travel`, `required_skills`, `serves_tags`, `capacity`, `time_window`, `eligible_vehicles`, `shift_end`, `max_distance`, `max_route_duration`, `max_stops`, `sequence`, `tag_order`, `shipment`, `break`, `multi_trip`, `same_vehicle`, `same_day`, `same_route`, `compatible_vehicles`, `synchronized`, `time_lag`, `all_or_none`, `period_limit`, `quota`, `unknown`. An open set: a later release may add values, so accept any string and handle the ones you know.
+         *     Known values: `unreachable`, `max_leg_travel`, `required_skills`, `serves_tags`, `capacity`, `time_window`, `eligible_vehicles`, `shift_end`, `max_distance`, `max_route_duration`, `max_stops`, `sequence`, `tag_order`, `shipment`, `break`, `multi_trip`, `unload_before_end`, `same_vehicle`, `same_day`, `same_route`, `compatible_vehicles`, `synchronized`, `time_lag`, `all_or_none`, `period_limit`, `quota`, `max_intake`, `unknown`. An open set: a later release may add values, so accept any string and handle the ones you know.
          * @example capacity
          */
         ConstraintCode: string;
@@ -365,6 +365,24 @@ export interface components {
             id: string;
             /** @description Where the depot is. */
             location: components["schemas"]["Place"];
+            /**
+             * @description The most load the depot may receive across the whole request, per
+             *     named dimension: a tip site's intake limit. Not per day: it sums every
+             *     shift of every day.
+             *
+             *     Counted is the load on board on arrival at each reload here (including
+             *     a shift's `initial_load` on its first trip and the final tip of
+             *     `unload_before_end`), plus the load on board at the end of a shift
+             *     whose `end` is this depot (not with `unload_before_end`, which unloads
+             *     at a reload first). A shift's start never counts, and an unused shift
+             *     receives nothing. A dimension left out is uncapped; `0` means the
+             *     depot takes none of it. A hard limit: a task that would overfill every
+             *     depot its trip can tip at stays unassigned (reason `max_intake`).
+             *
+             *     Each dimension must be one a task or vehicle declares, and some shift
+             *     must reload here, or end here without `unload_before_end`.
+             */
+            max_intake?: null | components["schemas"]["Quantities"];
             /**
              * Format: double
              * @description Money charged once per reload visit, in the objective's currency.
@@ -690,7 +708,10 @@ export interface components {
             tags?: string[] | null;
             /**
              * @description Soft target for this task, measured at its arrival (default) or
-             *     departure. On a shipment it is measured on the **delivery** leg.
+             *     departure. On a shipment it is measured on the **delivery** leg and
+             *     cannot be combined with `delivery.target` (HTTP 400
+             *     `conflicting_fields`); `pickup.target` adds a separate target on the
+             *     pickup leg.
              */
             target?: null | components["schemas"]["Target"];
             /** @description Time windows for this visit. */
@@ -1819,9 +1840,9 @@ export interface components {
              * @description Seconds past this task's `target.at`, measured at the stop's arrival
              *     (plus any `windowed` break taken on arrival there, idle before it
              *     included) or departure per `target.on`; `0` when met. Present only on a task
-             *     stop carrying a target. A shipment's target is measured on its
-             *     delivery leg, so it appears on the `:delivery` stop and never on the
-             *     `:pickup` stop.
+             *     stop carrying a target. A shipment's own `target` is measured on its
+             *     delivery leg, so it appears on the `:delivery` stop; a `pickup.target`
+             *     or `delivery.target` appears on that leg's stop.
              * @example 0
              */
             target_lateness_s?: number | null;
@@ -2550,10 +2571,11 @@ export interface components {
             /**
              * Format: int32
              * @description Maximum trips (depot legs) in this shift, across all reload depots.
-             *     Counts trips, not reloads: `trips = reloads_used + 1`. `max_trips: 1`
-             *     means a single trip — reloads are permitted in `reloads` but the cap
-             *     prevents ever using one. `reloads` present with `max_trips` absent
-             *     means unlimited trips. A single reload depot can only be
+             *     Counts trips, not reloads: `trips = reloads_used + 1`, where the final
+             *     unload of `unload_before_end` is not counted. `max_trips: 1` means a
+             *     single trip — reloads are permitted in `reloads` but the cap prevents
+             *     ever using one, other than that final unload. `reloads` present with
+             *     `max_trips` absent means unlimited trips. A single reload depot can only be
              *     revisited up to 8 times per shift regardless of `max_trips`;
              *     a `max_trips` beyond that against one depot
              *     is accepted but the extra headroom is unreachable — list more than
@@ -2627,6 +2649,16 @@ export interface components {
              * @example 2026-07-01T17:00:00+02:00
              */
             to: string;
+            /**
+             * @description When `true`, a route that would end with load on board first unloads
+             *     at one of this shift's `reloads` depots: a final `reload` stop, at the
+             *     depot the solver finds cheapest, taking that depot's
+             *     `service_duration_s` and `per_reload`. It does not count toward
+             *     `max_trips`. A route whose last trip carries no load ends without one.
+             *     `true` without `reloads` is rejected with HTTP 400
+             *     `conflicting_fields`. Default `false`.
+             */
+            unload_before_end?: boolean | null;
         };
         /**
          * @description The `Costs` fields for one shift, minus `per_used_vehicle`. A shift is one
@@ -2862,7 +2894,10 @@ export interface components {
             tags?: string[] | null;
             /**
              * @description Soft target for this task, measured at its arrival (default) or
-             *     departure. On a shipment it is measured on the **delivery** leg.
+             *     departure. On a shipment it is measured on the **delivery** leg and
+             *     cannot be combined with `delivery.target` (HTTP 400
+             *     `conflicting_fields`); `pickup.target` adds a separate target on the
+             *     pickup leg.
              */
             target?: null | components["schemas"]["Target"];
         };
@@ -2920,6 +2955,14 @@ export interface components {
              * @example 60
              */
             setup_duration_s?: number | null;
+            /**
+             * @description Soft target for this leg, measured at its arrival (default) or
+             *     departure. Same type, units and validation as the task-level
+             *     `target`. The shipment's own `target` is measured on the delivery
+             *     leg, so sending it with `delivery.target` is rejected with HTTP 400
+             *     (`conflicting_fields`).
+             */
+            target?: null | components["schemas"]["Target"];
             /** @description Time windows for this stop. */
             time_windows?: components["schemas"]["TimeWindow"][] | null;
         };
@@ -3931,15 +3974,16 @@ export interface components {
              */
             code: components["schemas"]["ConstraintCode"];
             /**
-             * @description The capacity dimension over its limit. Only on `capacity`.
+             * @description The capacity dimension over its limit. Only on `capacity`,
+             *     `unload_before_end` and `max_intake`.
              * @example weight
              */
             dimension?: string | null;
             /**
              * Format: int64
              * @description How far over the limit, in `unit`. On `capacity`, `time_window` (the
-             *     seconds late), `shift_end`, `max_distance`, `max_route_duration` and
-             *     `quota`.
+             *     seconds late), `shift_end`, `max_distance`, `max_route_duration`,
+             *     `quota`, `unload_before_end` and `max_intake`.
              * @example 15
              */
             excess?: number | null;

package/dist/v3.d.ts

@@ -54,7 +54,7 @@ export interface paths {
         put?: never;
         /**
          * Suggest best insertions for the tasks outside the plan
-         * @description Takes the same body as `POST /v3/routing/evaluate` (`problem` + committed `plan`), plus optional `options`. Every task of `problem` that is not in `plan` is a task to place: finds its feasible insertion positions and returns them as `insertions`, ranked by `delta.cost`, the change in the plan's cost in money. Each insertion lists the stops it adds (`placements`) and every plan route it changes, whole (`routes`): swap those routes into `plan` to apply it. An empty `insertions` carries a `reason` whose `code` is `time_limit`, `candidates_exhausted` or `infeasible` (an open set) and whose `message` says the same in English. The committed plan is never modified. Limitation: suggest never opens a new reload trip on a multi-trip vehicle.
+         * @description Takes the same body as `POST /v3/routing/evaluate` (`problem` + committed `plan`), plus optional `options`. Every task of `problem` that is not in `plan` is a task to place: finds its feasible insertion positions and returns them as `insertions`, ranked by `delta.cost`, the change in the plan's cost in money. The members of a `synchronized` or `time_lag` group outside `plan` are one task to place: each insertion places every member, and with the default `on: service_start` a crew's members start within `max_spread_s` of one another (`service_start`); a `time_lag` keeps its lag. Each insertion lists the stops it adds (`placements`) and every plan route it changes, whole (`routes`): swap those routes into `plan` to apply it. An empty `insertions` carries a `reason` whose `code` is `time_limit`, `candidates_exhausted` or `infeasible` (an open set) and whose `message` says the same in English. The committed plan is never modified. Limitation: suggest never opens a new reload trip on a multi-trip vehicle.
          */
         post: operations["suggest"];
         delete?: never;
@@ -296,7 +296,7 @@ export interface components {
          *     New values may be added; clients must accept unknown values and handle
          *     them generically, for example by showing `message`.
          *
-         *     Known values: `unreachable`, `max_leg_travel`, `required_skills`, `serves_tags`, `capacity`, `time_window`, `eligible_vehicles`, `shift_end`, `max_distance`, `max_route_duration`, `max_stops`, `sequence`, `tag_order`, `shipment`, `break`, `multi_trip`, `same_vehicle`, `same_day`, `same_route`, `compatible_vehicles`, `synchronized`, `time_lag`, `all_or_none`, `period_limit`, `quota`, `unknown`. An open set: a later release may add values, so accept any string and handle the ones you know.
+         *     Known values: `unreachable`, `max_leg_travel`, `required_skills`, `serves_tags`, `capacity`, `time_window`, `eligible_vehicles`, `shift_end`, `max_distance`, `max_route_duration`, `max_stops`, `sequence`, `tag_order`, `shipment`, `break`, `multi_trip`, `unload_before_end`, `same_vehicle`, `same_day`, `same_route`, `compatible_vehicles`, `synchronized`, `time_lag`, `all_or_none`, `period_limit`, `quota`, `max_intake`, `unknown`. An open set: a later release may add values, so accept any string and handle the ones you know.
          * @example capacity
          */
         ConstraintCode: string;
@@ -403,6 +403,24 @@ export interface components {
             id: string;
             /** @description Where the depot is. */
             location: components["schemas"]["Place"];
+            /**
+             * @description The most load the depot may receive across the whole request, per
+             *     named dimension: a tip site's intake limit. Not per day: it sums every
+             *     shift of every day.
+             *
+             *     Counted is the load on board on arrival at each reload here (including
+             *     a shift's `initial_load` on its first trip and the final tip of
+             *     `unload_before_end`), plus the load on board at the end of a shift
+             *     whose `end` is this depot (not with `unload_before_end`, which unloads
+             *     at a reload first). A shift's start never counts, and an unused shift
+             *     receives nothing. A dimension left out is uncapped; `0` means the
+             *     depot takes none of it. A hard limit: a task that would overfill every
+             *     depot its trip can tip at stays unassigned (reason `max_intake`).
+             *
+             *     Each dimension must be one a task or vehicle declares, and some shift
+             *     must reload here, or end here without `unload_before_end`.
+             */
+            max_intake?: null | components["schemas"]["Quantities"];
             /**
              * Format: double
              * @description Money charged once per reload visit, in the objective's currency.
@@ -650,6 +668,7 @@ export interface components {
          *           "arrival": "2026-07-01T09:30:00+02:00",
          *           "id": "job-2",
          *           "latest_arrival": "2026-07-01T10:15:00+02:00",
+         *           "service_start": "2026-07-01T09:30:00+02:00",
          *           "shift": "mon",
          *           "type": "job",
          *           "vehicle": "v1"
@@ -876,7 +895,10 @@ export interface components {
             tags?: string[] | null;
             /**
              * @description Soft target for this task, measured at its arrival (default) or
-             *     departure. On a shipment it is measured on the **delivery** leg.
+             *     departure. On a shipment it is measured on the **delivery** leg and
+             *     cannot be combined with `delivery.target` (HTTP 400
+             *     `conflicting_fields`); `pickup.target` adds a separate target on the
+             *     pickup leg.
              */
             target?: null | components["schemas"]["Target"];
             /** @description Time windows for this visit. */
@@ -1034,6 +1056,7 @@ export interface components {
          *       "arrival": "2026-07-01T09:30:00+02:00",
          *       "id": "s1:pickup",
          *       "latest_arrival": "2026-07-01T10:15:00+02:00",
+         *       "service_start": "2026-07-01T09:30:00+02:00",
          *       "shift": "mon",
          *       "type": "pickup",
          *       "vehicle": "v1"
@@ -1054,10 +1077,23 @@ export interface components {
              * @description Latest arrival that still keeps the rest of the route feasible
              *     (RFC 3339, in the offset of `arrival`) — the smaller of the task's own time-window latest and
              *     the route's forward slack here. Under priced lateness it may be
-             *     **earlier** than `arrival`.
+             *     **earlier** than `arrival`. For a `synchronized` or `time_lag` member it
+             *     is at most `arrival` plus the wait before `service_start`: arriving
+             *     later would move the start its partners are booked to meet.
              * @example 2026-07-01T10:15:00+02:00
              */
             latest_arrival: string;
+            /**
+             * Format: date-time
+             * @description Service start (RFC 3339, in the offset of `arrival`): `arrival` plus
+             *     any wait for the time window or a break, and for a `synchronized` or
+             *     `time_lag` member the hold for its partners, as `service_start` on the
+             *     route stop. With the default `on: service_start`, the members of a
+             *     crew start here within the relation's `max_spread_s`: the booking time
+             *     (`on: departure` aligns their ends instead; a `time_lag` keeps its lag).
+             * @example 2026-07-01T09:30:00+02:00
+             */
+            service_start: string;
             /** @description Shift of that plan route. */
             shift: string;
             /**
@@ -2052,9 +2088,9 @@ export interface components {
              * @description Seconds past this task's `target.at`, measured at the stop's arrival
              *     (plus any `windowed` break taken on arrival there, idle before it
              *     included) or departure per `target.on`; `0` when met. Present only on a task
-             *     stop carrying a target. A shipment's target is measured on its
-             *     delivery leg, so it appears on the `:delivery` stop and never on the
-             *     `:pickup` stop.
+             *     stop carrying a target. A shipment's own `target` is measured on its
+             *     delivery leg, so it appears on the `:delivery` stop; a `pickup.target`
+             *     or `delivery.target` appears on that leg's stop.
              * @example 0
              */
             target_lateness_s?: number | null;
@@ -2451,10 +2487,11 @@ export interface components {
             /**
              * Format: int32
              * @description Maximum trips (depot legs) in this shift, across all reload depots.
-             *     Counts trips, not reloads: `trips = reloads_used + 1`. `max_trips: 1`
-             *     means a single trip — reloads are permitted in `reloads` but the cap
-             *     prevents ever using one. `reloads` present with `max_trips` absent
-             *     means unlimited trips. A single reload depot can only be
+             *     Counts trips, not reloads: `trips = reloads_used + 1`, where the final
+             *     unload of `unload_before_end` is not counted. `max_trips: 1` means a
+             *     single trip — reloads are permitted in `reloads` but the cap prevents
+             *     ever using one, other than that final unload. `reloads` present with
+             *     `max_trips` absent means unlimited trips. A single reload depot can only be
              *     revisited up to 8 times per shift regardless of `max_trips`;
              *     a `max_trips` beyond that against one depot
              *     is accepted but the extra headroom is unreachable — list more than
@@ -2528,6 +2565,16 @@ export interface components {
              * @example 2026-07-01T17:00:00+02:00
              */
             to: string;
+            /**
+             * @description When `true`, a route that would end with load on board first unloads
+             *     at one of this shift's `reloads` depots: a final `reload` stop, at the
+             *     depot the solver finds cheapest, taking that depot's
+             *     `service_duration_s` and `per_reload`. It does not count toward
+             *     `max_trips`. A route whose last trip carries no load ends without one.
+             *     `true` without `reloads` is rejected with HTTP 400
+             *     `conflicting_fields`. Default `false`.
+             */
+            unload_before_end?: boolean | null;
         };
         /**
          * @description The `Costs` fields for one shift, minus `per_used_vehicle`. A shift is one
@@ -2776,7 +2823,10 @@ export interface components {
             tags?: string[] | null;
             /**
              * @description Soft target for this task, measured at its arrival (default) or
-             *     departure. On a shipment it is measured on the **delivery** leg.
+             *     departure. On a shipment it is measured on the **delivery** leg and
+             *     cannot be combined with `delivery.target` (HTTP 400
+             *     `conflicting_fields`); `pickup.target` adds a separate target on the
+             *     pickup leg.
              */
             target?: null | components["schemas"]["Target"];
         };
@@ -2834,6 +2884,14 @@ export interface components {
              * @example 60
              */
             setup_duration_s?: number | null;
+            /**
+             * @description Soft target for this leg, measured at its arrival (default) or
+             *     departure. Same type, units and validation as the task-level
+             *     `target`. The shipment's own `target` is measured on the delivery
+             *     leg, so sending it with `delivery.target` is rejected with HTTP 400
+             *     (`conflicting_fields`).
+             */
+            target?: null | components["schemas"]["Target"];
             /** @description Time windows for this stop. */
             time_windows?: components["schemas"]["TimeWindow"][] | null;
         };
@@ -3234,8 +3292,11 @@ export interface components {
              *     the range are a 400, never clamped. It also sets how widely a unit of
              *     several stops is searched (such a unit is never searched exhaustively):
              *     each stop after the unit's first keeps at most
-             *     `max(8, 4 × max_insertions)` partial placements. A single-stop task has every
-             *     feasible position considered unless `time_limit_s` runs out first.
+             *     `max(8, 4 × max_insertions)` partial placements. A `synchronized` or
+             *     `time_lag` group is the exception: every start slot of one member is
+             *     tried, each other member at its cheapest slot, whatever this value. A
+             *     single-stop task has every feasible position considered unless
+             *     `time_limit_s` runs out first.
              * @default 5
              * @example 5
              */
@@ -3394,6 +3455,7 @@ export interface components {
          *                   "arrival": "2026-07-01T09:30:00+02:00",
          *                   "id": "job-2",
          *                   "latest_arrival": "2026-07-01T10:15:00+02:00",
+         *                   "service_start": "2026-07-01T09:30:00+02:00",
          *                   "shift": "mon",
          *                   "type": "job",
          *                   "vehicle": "v1"
@@ -3659,6 +3721,7 @@ export interface components {
          *               "arrival": "2026-07-01T09:30:00+02:00",
          *               "id": "job-2",
          *               "latest_arrival": "2026-07-01T10:15:00+02:00",
+         *               "service_start": "2026-07-01T09:30:00+02:00",
          *               "shift": "mon",
          *               "type": "job",
          *               "vehicle": "v1"
@@ -3695,10 +3758,9 @@ export interface components {
             /** @description Why `insertions` is empty; absent otherwise. */
             reason?: null | components["schemas"]["SuggestReason"];
             /**
-             * @description The unit's lead: its first member in placement order. That is the
-             *     visit, the shipment, the first stop of a `sequence` chain in the
-             *     unit, or else the member that comes first in problem order (`jobs`,
-             *     then `shipments`).
+             * @description The unit's lead: the visit, the shipment, the first stop of a
+             *     `sequence` chain in the unit, or else, a crew included, the member
+             *     that comes first in problem order (`jobs`, then `shipments`).
              * @example job-2
              */
             task: string;
@@ -4308,15 +4370,16 @@ export interface components {
              */
             code: components["schemas"]["ConstraintCode"];
             /**
-             * @description The capacity dimension over its limit. Only on `capacity`.
+             * @description The capacity dimension over its limit. Only on `capacity`,
+             *     `unload_before_end` and `max_intake`.
              * @example weight
              */
             dimension?: string | null;
             /**
              * Format: int64
              * @description How far over the limit, in `unit`. On `capacity`, `time_window` (the
-             *     seconds late), `shift_end`, `max_distance`, `max_route_duration` and
-             *     `quota`.
+             *     seconds late), `shift_end`, `max_distance`, `max_route_duration`,
+             *     `quota`, `unload_before_end` and `max_intake`.
              * @example 15
              */
             excess?: number | null;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@solvice/routing",
-  "version": "0.19.1-beta.0",
+  "version": "0.19.2-beta.0",
   "description": "TypeScript client for the Solvice V3 routing API, generated from its OpenAPI spec.",
   "license": "Apache-2.0",
   "homepage": "https://docs.solvice.io/guides/platform/sdks/typescript",