Why this PR

Audit of docs.plexicus.ai against the current platform (~100 PRs merged on plexicus/platform in May) surfaced two issues:

1. Brand positioning out of date — getting-started pages still call Plexicus a CNAPP. Per current GTM positioning, Plexicus is an AI-Native ASPM platform (CNAPP belongs to Wiz).
2. Six major capabilities have no docs — features that shipped or are actively being rolled out are invisible to documentation users.

What changed

Brand fixes

• getting-started/introduction.mdx — replaced CNAPP positioning with ASPM; added Azure DevOps, AI assistants, and current compliance list
• getting-started/key-features.mdx — repositioned as ASPM; added AI Remediation, Pentest Agent, AI Code Security suite, Compliance sections

New pages (6)

Sidebar updates

• Added Azure DevOps under SCM Integrations
• New top-level Security Capabilities category (Scanners, Pentest Agent, AI Remediation)
• New top-level Compliance category
• Added SSO under Settings

Brand-rules compliance

All new and edited copy uses ASPM positioning. The pentest feature is documented as "Plexicus pentest agent" (never the internal codename). Deep code analysis is referred to as "Deep Analysis" / "deep semantic code analysis" — no Joern/CPG references.

Before merge — content owner review

The new pages are written from current platform behavior and GTM positioning, but specific details may need product-team verification:

• Pentest agent scan profile names (Light / Standard / Deep) — confirm with platform team
• AI Remediation throttle defaults (5 PRs/repo/day) — confirm
• SCIM Plexicus role names (Admin / Cyberoper / Developer) — confirm exact strings
• Compliance framework availability — confirm which are "Available" vs "Pathway"
• Scanner language coverage table — verify against actual processor support
• Add screenshots where existing pages have them (Azure DevOps connector UI, etc.)