Why this matters
The bug. user.profile.displayName is three dereferences. If any of user, profile, or displayName is null/undefined, the next access throws. In a React tree, the throw crashes the entire component subtree unless caught by an error boundary.
The fix. Optional chaining (?.) returns undefined instead of throwing when the left side is nullish. Pair with ?? for a default value. The puzzle accepts either the bare ?. chain or the ?? "" defaulted form.
Bigger picture. Optional chaining is sometimes a code smell — frequently appearing ?. chains suggest the type system isn't being enforced strictly enough. Consider where the undefined is coming from and whether the upstream code should guarantee a shape instead.
Review heuristic
Search the diff for ! non-null assertions, unwrap() calls, and as Type casts. Each is an assertion the author is making to the compiler. Each needs to be either justified in a comment or replaced with a real null check.
External reference: CWE-476: NULL Pointer Dereference.