OCI journey - OIE upgrade: API changes guide

[brentschaus-okta]

Description:

• What's changed?: Adds inbound cross-links to the new API changes after the upgrade guide (/docs/guides/oie-upgrade-api-changes/main/) from related, non-Journeys docs, so readers encountering the affected APIs are routed to the upgrade guidance.

  • Identity Engine limitations guide (docs/guides/ie-limitations/): added an
    intro pointer plus per-section Further information links mapping each
    limitation (email reset, question reset, Sessions APIs, SMS factors, audience,
    password recovery) to its matching guide section.
  • Authentication API reference (docs/reference/api/authn/): linked the
    deviceToken caution → "Device token behavior changed", the IdP-initiated
    step-up section → audience change, and Recovery operations → Classic
    password-recovery limitations. Also fixed a stray trailing > typo in the
    deviceToken caution.
  • Classic Engine MFA guide (docs/guides/mfa/): added a Factors-API-changes
    link to the existing "If you're using Identity Engine" note.
  • Classic Engine session-cookie guide (docs/guides/session-cookie/): added
    the Sessions-API-changes link alongside the existing session references.

Notes:

• Verified all target anchors resolve against the new guide's headings. yarn markdown-lint shows no new findings — the only flagged lines are pre-existing smart-apostrophe baseline issues in mfa and authn, unchanged by this PR (smart-char counts identical before/after). The authn reference is the legacy prose reference; some API reference now lives in okta-oas3/Redocly, so those prose anchors may not be the long-term canonical surface.
• Navbar placement may need revisiting as the broader journey doc structure firms up. The guide links to two support.okta.com articles (Device Token in Auth API, v1/sessions/me APIs) that should be click-tested before merge.

• Is this PR related to a Monolith release?
  No. Targeting the July monthly developer docs release (code freeze June 26, 2026.07.0).

Resolves

• OKTA-1185560

Netlify preview link

Preview link

[okta-prod-github-app]

Acrolinx score

A minimum Acrolinx Score of 80 is required. The total score is an average of the subscores.
Select Total score to review the Acrolinx scorecard for your article. Try to increase your individual scores, for example: Correctness. Your content will be clearer and more consistent.

Article	Total score Required:80	Word and phrases (Brand, terms) Preferred: 80	Correctness (Spelling, grammar) Preferred: 80	Clarity (Readability) Preferred: 80	Inclusive language (+ accesibility) Preferred: 80
✅ packages/@okta/vuepress-site/docs/guides/ie-limitations/main/index.md	84	94	84	64
✅ packages/@okta/vuepress-site/docs/guides/index.md	87	67	80	78
✅ packages/@okta/vuepress-site/docs/guides/mfa/main/index.md	87	100	100	81
✅ packages/@okta/vuepress-site/docs/guides/oie-upgrade-api-changes/index.md	100	100	100	100
✅ packages/@okta/vuepress-site/docs/guides/oie-upgrade-api-changes/main/index.md	84	87	81	81
✅ packages/@okta/vuepress-site/docs/guides/session-cookie/main/index.md	93	100	89	85

Successfully checked 6 of 6 documents.
See summary in Content Analysis Dashboard

Reopen the pull request or push new changes to check again.

Depending on the Acrolinx server configuration, the
links expire after some time and you must have a login for the
Acrolinx server to access them again.