docs(9-ai-sessions): add Compliance section for the lc-compliance plugin

[steveatlc]

Summary

Documents the lc-compliance Claude Code plugin shipping in refractionPOINT/lc-ai. The plugin has two halves and both are covered:

• Case-reviewer agents (one per framework, D&R-driven AI Sessions) classify in-scope cases against control citations on case_created events and write audit-grade documentation directly into the case.
• Four interactive Claude Code skills (compliance-lookup, compliance-gap, compliance-deploy, compliance-baseline-deploy) for ad-hoc control lookups, gap analysis against live orgs, guided reviewer-agent deployment, and full rule-baseline deployment.

Covered frameworks: CMMC v2, NIST SP 800-53 Rev 5, PCI DSS v4.0, HIPAA Security Rule, SOC 2, ISO/IEC 27001:2022, CIS Controls v8.

What this PR contains

New files — docs/9-ai-sessions/compliance/

File	Purpose
index.md	Overview, two-shape model (agent + skills), quickstart
installation.md	Plugin install, prerequisites, first-deploy sequence (with per-framework scope-tag table)
frameworks.md	Per-framework citation formats, accepted scope tags, verification levels, framework-specific skill args (--baseline for NIST 800-53, --ig for CIS v8)
skills.md	Full reference for all four skills with arguments and examples
case-reviewer-agent.md	Agent lifecycle, scoped permissions, scope check, evidence model, classification tags, customization
gap-analysis.md	Report anatomy (sections A–G), remediation paths, multi-tenant note

Nav placement

Compliance is nested as a sub-section under AI Sessions (after API Reference), not promoted to a top-level tab:

- AI Sessions:
    # ... existing entries unchanged ...
    - API Reference: 9-ai-sessions/api-reference.md
    - Compliance:
        - Overview: 9-ai-sessions/compliance/index.md
        - Installation: 9-ai-sessions/compliance/installation.md
        - Frameworks: 9-ai-sessions/compliance/frameworks.md
        - Skills Reference: 9-ai-sessions/compliance/skills.md
        - Case-Reviewer Agent: 9-ai-sessions/compliance/case-reviewer-agent.md
        - Gap Analysis: 9-ai-sessions/compliance/gap-analysis.md

The case-reviewer agent is literally a D&R-driven AI Session and the four skills are Claude Code tooling, so the semantic fit is inside the existing AI Sessions group; this also keeps the top-level nav at 10 tabs rather than worsening the existing horizontal-overflow situation.

Modified existing pages — cross-link surface

To make the new section discoverable from natural parent contexts, seven existing pages get conservative additive edits. Each adds one or two See Also / Related entries pointing at the relevant Compliance page. No other prose changes; no deletions.

Page	Edit
9-ai-sessions/index.md	Adds Compliance to the D&R-driven use-case bullet list and to the Documentation list at the bottom.
9-ai-sessions/dr-sessions.md	New ## See Also section framing the case-reviewer agent as a canonical D&R-driven session example.
5-integrations/extensions/limacharlie/cases.md	Two new entries in the existing ## See Also (the compliance reviewer operates on cases).
5-integrations/extensions/limacharlie/integrity.md	Two new entries in ## Related Articles (FIM rules ship as part of every framework baseline).
5-integrations/extensions/limacharlie/exfil.md	New ## See Also section (exfil rules ship as part of every framework baseline).
2-sensors-deployment/sensor-tags.md	One new entry in ## See Also pointing at the per-framework scope-tag conventions.
7-administration/config-hive/secrets.md	New ## See Also section. Surfaces previously-implicit cross-references to Adapters, Outputs, and AI Sessions alongside the new Compliance Installation reference.

Validation

• mkdocs build and mkdocs build --strict both pass.
• pymarkdown scan passes on all changed files with the repo's standard rule disables (MD013, MD033, MD041, MD046, MD060, MD024).
• 23 internal cross-link probes (every new inbound and outbound compliance link) verified 200 against a local mkdocs serve.

Out of scope (deliberate)

• No use-case landing page under 1-getting-started/use-cases/. A compliance.md use-case page could plausibly sit alongside incident-response.md, mssp-msp-mdr.md, enterprises.md, etc., but writing one is content work distinct from this cross-linking pass. Flagged as future follow-up.
• No asset additions under docs/assets/images/. No new screenshots or diagrams beyond the inline Mermaid sequence already in case-reviewer-agent.md.
• No mkdocs.yml redirect entries. These pages have no Readme.io predecessors, so redirect_maps doesn't need updating.

🤖 Generated with Claude Code