fix: complete all P3 audit findings — empty modules, docs drift, detekt, worktree

P3-1: Delete 17 empty Gradle modules (core:agents/observability/policies/stages,
      infrastructure:scheduler/security/telemetry, all 7 plugins/*, all 3
      interfaces/*). Zero source files, zero dependents, identical build.gradle
      stubs. Remove from settings.gradle. Keep .adoc spec docs as roadmap refs.
P3-2: Fix docs drift — rename :core:orchestration to :core:kernel in
      core-orchestration-submodule-spec.md, rewrite stale chat-transcript
      modules-and-spec.md as proper doc.
      (CLAUDE.md Router context isolation clarification is local-only,
       file is gitignored.)
P3-3: Reduce detekt maxIssues from 999999 to 120 (actual current count ~107).
      (CLAUDE.md detekt description updated locally; file is gitignored.)
P3-4: Remove stale locked worktree agent-a98d45277ce4b0040 (contained only
      cosmetic test style changes and an unused kotlinx-datetime dep).

docs/modules/core-orchestration-submodule-spec.md

@@ -1,20 +1,20 @@
 ---
-name: "Core Orchestration Submodule Spec"
-description: "Specification for :core:orchestration – execution kernel"
+name: "Core Kernel Submodule Spec"
+description: "Specification for :core:kernel – execution kernel"
 depth: 2
 links: ["../index.md", "./core-module-spec.md", "./core-sessions-submodule-spec.md", "./core-transitions-submodule-spec.md"]
 ---
 
-# :core:orchestration module specification
+# :core:kernel module specification
 
-version: 0.1-draft
-status: foundational specification
+version: 0.2
+status: implemented (SessionOrchestrator + ReplayOrchestrator)
 
 ---
 
 # 1. purpose
 
-`:core:orchestration` is the execution kernel of correx. It coordinates the entire workflow lifecycle by composing:
+`:core:kernel` is the execution kernel of correx. It coordinates the entire workflow lifecycle by composing:
 
 * session management
 * stage scheduling
@@ -30,7 +30,7 @@ It is the "brain" that wires together all other core modules and ensures work pr
 
 # 2. responsibilities
 
-`:core:orchestration` owns:
+`:core:kernel` owns:
 
 * workflow execution loop
 * stage scheduling and sequencing
@@ -46,7 +46,7 @@ It is the "brain" that wires together all other core modules and ensures work pr
 
 # 3. non-responsibilities
 
-`:core:orchestration` MUST NOT own:
+`:core:kernel` MUST NOT own:
 
 * domain logic (that’s in events, transitions, validation, etc.)
 * persistence
@@ -61,7 +61,7 @@ It coordinates; it does not implement low‑level mechanics.
 
 # 4. architectural role
 
-`:core:orchestration` acts as:
+`:core:kernel` acts as:
 
 * the top‑level orchestrator
 * the only component that directly calls other core modules in a defined sequence
@@ -112,7 +112,7 @@ Each iteration is a transaction in the event stream.
 
 # 7. orchestration events
 
-`:core:orchestration` emits high‑level events:
+`:core:kernel` emits high‑level events:
 
 * `WorkflowStarted`
 * `WorkflowCompleted`