Task 38 - "Generate and record the observed behaviour of simulated pipe for each pipe specification" - appears to have 22h of work that needs to be done between 1200h on Sat 11/6 to 1200h on Tue, 14/6. However for some reason 11 June has default timings [0900-1300; 2200-2300] or 5h workday even though it falls in the [Unamed] 11h workweek. I am sure this was not what you had intended when you created the workweek of 11-18 June. Validate this by using a split screen with "task usage" in the bottom window. This is a curious situation and I have not been able to replicate this type of error. (Which version of MSP are you using and is it Std/Prof?) In your plan, I did a workaround by creating an exception for 11 June, and increasing work hours from the default 5h to 11h. The critical path now extends backward and migrates up to the next available "constrained task" ie, Task 23.
By removing all constraints, you get the critical path from the beginning of the network.
Analyze the plan by inserting columns for Work, Free Slack & Total Slack and you will see a pattern created by constraints.
Another unrelated observation:
Your standard day is defined as 5h. When you define duration of a task, for example, Task 41, as 1.6 "days", it implies 1.6*5h = 8h NOT 1.6*11h = 17.6h as you might have expected to see during the [Unamed] June work week. This is because, MSP converts days into hours using the definition in Tools/Options-->Calendar tab. To be absolutely sure, enter duration in hours.
Anyone else for an explanation on what is happening on 11 June?