Recognize when a bypass is available

A constraint bypass makes a hard limitation irrelevant instead of fighting it. The whole skill is telling apart a constraint that belongs to the outcome you need from one that belongs only to the first method you reached for. The first kind cannot be removed. The second kind sometimes can.

This task gives you three design problems. Each one comes with an obvious solution that works inside a constraint. For each problem, decide whether the constraint can be bypassed or whether it is a real property of the outcome, and justify your answer.

Clone the template repository and open the 02-recognize-bypass folder. This is a written task, so there is no starter code. Work through each problem in SOLUTION.md: give your verdict, name the exact constraint, and explain your reasoning. Where a bypass exists, show how it removes the constraint rather than only reducing its cost. Push your work to your own fork and submit the repository URL.