[MS-1377] Remove graph init state persistence that was never called

[BurningAXE]

JIRA ticket
Will be released in: 2026.2.0

Root cause analysis (for bugfixes only)

First known affected version: an old one

Notable changes

• Activity used the two parameter onSaveInstanceState() which is only called when persistableMode="persistAcrossReboots" flag is set
• It is not set for this activity and as a result this method was not never called
• This resulted in the isGraphInitialized flag not persisting between activity recreations
• In a surprising plot twist it turned out that this is actually the desired behaviour which explains why rotation was working as expected and it broke once I switched from the two parameter to the single parameter onSaveInstanceState() :D
• To avoid confusion and someone re-finding this issue and "fixing it", I'm deleting the dead code and changing the comment to state desired behaviour
• @alexandr-simprints since you wrote this initially, I'll wait for your review specifically before merging, in case I missed something

Testing guidance

• Trigger any workflow
• Rotate the device
• Continue workflow

Additional work checklist

• Effect on other features and security has been considered
• Design document marked as "In development" (if applicable)
• External (Gitbook) and internal (Confluence) Documentation is up to date (or ticket created)
• Test cases in Testiny are up to date (or ticket created)
• Other teams notified about the changes (if applicable)

[Copilot]

Pull request overview

Removes unused state persistence around the orchestrator navigation graph init flag, clarifying that graph initialization is intentionally not preserved across activity recreation (e.g., rotation / process recreation scenarios).

Changes:

• Removes PersistableBundle-based onSaveInstanceState() override and the unused persisted key for isGraphInitialized.
• Stops restoring isGraphInitialized from savedInstanceState, ensuring recreation re-initializes the graph.
• Updates the inline documentation comment to reflect the intended lifecycle behavior.

---

You can also share your feedback on Copilot code review. Take the survey.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[luhmirin-s]

Don't forget to test it :D