Protractor ignoreSynchronization configuration for mixed Angular and non‑Angular pages

Goal: ensure Protractor executes actions reliably on pages that switch between Angular‑rendered views and server‑side or static content without timing out or performing steps too early.

Constraint: the ignoreSynchronization flag defaults to false, which tells Protractor to wait for Angular bootstraps; however, there is no documented rule for when to set it to true in mixed‑mode applications, and the appropriate value may differ between local developer machines and production CI pipelines where extra bundles or lazy modules affect timing.

Specific questions: Should ignoreSynchronization be configured globally or overridden per‑test step? How can a team determine the correct value for a given mix of Angular and non‑Angular navigation? What lightweight verification can confirm that the flag prevents hangs without altering test logic?