style: travel planner

Author: manfredsteyer

ai-server/src/mastra/agents/travel-planner-agent.prompt.ts

@@ -8,16 +8,21 @@ render the result as UI widgets via showComponents.
 1. Extract from the user request:
    - from         (departure city — use EXACTLY the name as given by the user, no translation)
    - to           (destination city — use EXACTLY the name as given by the user, no translation)
-   - stops        (intermediate stop cities in travel order — use EXACTLY the names as given by the user, no translation;
-                   e.g. "Stopp in Wien" → stops: ["Wien"], "via Vienna" → stops: ["Vienna"];
-                   if no stops mentioned → stops: [])
+   - stops        (intermediate stop cities on the OUTBOUND journey only — use EXACTLY the names as given by the user, no translation;
+                   e.g. "Stopp in Wien", "über Wien", "via Wien" → stops: ["Wien"];
+                   only add a city here if the user explicitly says it is on the way TO the destination;
+                   if no outbound stops mentioned → stops: [])
+   - returnStops  (intermediate stop cities on the RETURN journey only — use EXACTLY the names as given by the user, no translation;
+                   e.g. "beim Heimflug Stopp in Paris", "auf dem Rückweg über Paris", "return via Paris", "on the way back stop in Paris" → returnStops: ["Paris"];
+                   only add a city here if the user explicitly mentions it is on the way BACK / return / Heimflug / Rückflug / Rückweg;
+                   if no return stops mentioned → returnStops: [])
    - departDate   (ISO 8601)
    - returnDate   (ISO 8601)
    Resolve relative dates ("morgen", "nächste Woche", "ab Mai") against today's date.
    If from/to or dates are missing, still proceed with your best guess.
 
 2. Call the workflow tool "packageTourWorkflow" exactly ONCE with
-   { from, to, stops, departDate, returnDate }.
+   { from, to, stops, returnStops, departDate, returnDate }.
    It returns:
    - legs          — array of { from, to, candidates[] } in travel order:
                      [from→stops[0]], …, [stops[n-1]→to], [to→stops[n-1]], …, [stops[0]→from]
@@ -42,11 +47,13 @@ render the result as UI widgets via showComponents.
    - Only skip the hotel (same-day transit) if the arrival is in the morning or afternoon
      AND there is a plausible onward flight the same day AND the user's request gives no hint
      of a longer stop.
-   - If an overnight stay is needed → pick ONE hotel from destination.hotels
-     based on the user's preferences (stars, budget, location, etc.) and render a hotelWidget.
-   - If a city requires an overnight stay but destination.hotels is empty (or no
-     candidate matches the preferences), do NOT render a hotelWidget for that city
-     and note it in the messageWidget instead.
+   - If an overnight stay is needed → ALWAYS render a hotelWidget. Pick ONE hotel from
+     destination.hotels that best matches the user's preferences (stars, budget, location).
+     Preferences are a guide for ranking candidates, NOT a hard filter — if no hotel
+     perfectly matches, pick the closest available option and note the compromise briefly
+     in the messageWidget. NEVER skip a city's hotel because of unmet preferences.
+   - Only omit a hotelWidget if destination.hotels is completely empty (no candidates at all),
+     in which case note it in the messageWidget.
 
 4. Render the result with EXACTLY ONE showComponents call, in this order:
    1. messageWidget({ text: "<summary of the proposed trip in the user's language>" })

ai-server/src/mastra/workflows/package-tour-workflow.ts

@@ -11,7 +11,15 @@ const packageInputSchema = z.object({
   stops: z
     .array(z.string())
     .default([])
-    .describe('Intermediate stop cities in travel order between from and to.'),
+    .describe(
+      'Intermediate stop cities on the OUTBOUND journey, in travel order between from and to.',
+    ),
+  returnStops: z
+    .array(z.string())
+    .default([])
+    .describe(
+      'Intermediate stop cities on the RETURN journey, in travel order between to and from.',
+    ),
   departDate: z
     .string()
     .describe('Planned outbound departure date (ISO 8601, e.g. 2026-05-15).'),
@@ -106,8 +114,8 @@ const findFlightsStep = createStep({
     };
     await emitStepStatus(ctx, 'findFlights', 'started');
 
-    const { from, to, stops } = inputData;
-    const citySequence = [from, ...stops, to, from];
+    const { from, to, stops, returnStops } = inputData;
+    const citySequence = [from, ...stops, to, ...returnStops, from];
     const legPairs = citySequence
       .slice(0, -1)
       .map((city, i) => ({ from: city, to: citySequence[i + 1] }));
@@ -155,7 +163,7 @@ const findHotelsStep = createStep({
     await emitStepStatus(ctx, 'findHotels', 'started');
 
     const init = getInitData<z.infer<typeof packageInputSchema>>();
-    const cities = [...init.stops, init.to];
+    const cities = [...init.stops, init.to, ...init.returnStops];
     const bridge = readBridge(requestContext);
     const agent = mastra.getAgent('hotelAgent');
 

src/app/domains/ticketing/ai/travel-planner/travel-planner-page.css

@@ -455,7 +455,7 @@
 
 .flight-cell {
   flex: 1 1 0;
-  min-height: 205px;
+  min-height: 200px;
   display: flex;
   flex-direction: column;
 }