Expose Session interface without privileged Capability projections

[devjusty]

Parent

#8 — Spec: Session-only scan coordination (ADR-0001)

What to build

Investigators and UI code read Capability state only through the Scan Session (session.capabilities.<id>). The public Session interface no longer offers WordPress- or homepage-named projections (scanResult, scanError, homepageResult, homepageIsRunning, homepageError). Adding a Capability does not require new privileged Context fields.

Acceptance criteria

• Privileged projections removed from the React scan coordinator and Scan Context results value.
• Call sites that needed those fields read session.capabilities.<id> instead (behaviour unchanged for investigators).
• Contract tests fail if privileged projections return on the Session interface.
• Glossary/ADR vocabulary used; no Capability-specific names on the coordination surface.

Blocked by

None — can start immediately (parallel with activity-log extraction).

[devjusty]

Implemented: privileged projections removed from useScan + ScanContext; contract tests lock the Session interface; call sites already use session.capabilities.