Eight fresh tasks combine the expert unit's ideas across fictional freight, laboratory, parcel, ledger, warehouse, and retail workflows. You've already used every feature they require. The challenge is choosing the right data structure or lifetime rule without damaging the business output.
Some inputs can only be read once. Other tasks share a view with caller-owned memory or reuse a buffer after an object leaves it. Decide what must remain shared and what must become independent before writing the loop. Keep failed operations distinct from successful empty results.
The checks include longer inputs and changed equality or boundary conditions. They count repeated work where that is the lesson's point, while accepting different implementations that satisfy the contract. There is no stopwatch target. Read each request for its exact separator, cutoff, ordering, and ownership rule rather than reusing a previous exercise's assumptions.
A set answers membership while a separate result list preserves the first encounter order.