Inspector Adapt Integration & Audit 1.4.0

Inspector Core observes and delegates to the existing Adapt controller; it never owns apply.

Read flow

selection
  → getVelinAPI(element)
  → controller.collectSignals()
  → controller.evaluatePolicy()
  → optional controller.rankOnly()
  → sanitized controller.getAuditLog()

Delegated actions

inspector.getAvailableIntents();
inspector.applyIntent(intent);
inspector.getAudit();
inspector.undoLast();

Safety

applyIntent still runs validator, guardrails, Semantic Apply, and audit. The Inspector pre-rejects forbidden types/payload keys but does not replace engine validation.

Events

Existing velin-adapt-change, velin-adapt-apply, velin-adapt-error, and safe velin-adapt-ai-* events are sufficient for Core consumers.

No runtime start

createInspector() does not call startAdapt. Its runtime-start boundary returns { ok: false, reason: 'inspector-does-not-start-runtime' }.