pi-smart-compact 10.0.0 → 10.0.1

package/ARCHITECTURE.md

@@ -104,9 +104,8 @@ Registered in [`src/index.ts`](https://github.com/alpertarhan/pi-smart-compact/b
 
 The table lists the owning surfaces. Other host events support them:
 session switch/fork/tree and `model_select` cancel speculative
-preparation and queued edits; `session_start` also names known conflicting
-compaction or context-editing extensions (`app/extension-conflicts.ts`,
-name-based evidence from the live command/tool registry, one notice);
+preparation and queued edits; `session_start` initializes replay, cache,
+tool exposure, policy and navigation state;
 `before_agent_start` injects the one-shot native continuity bridge;
 `message_end` feeds damage monitoring and the host prompt-cache ledger;
 `context_with_system` and `cache_warming_decision` serve held automatic trims
@@ -338,14 +337,10 @@ bytes, and hold the per-origin caps without losing earlier evidence.
 ### Session navigation and apply-time validation
 
 `app/register-navigation.ts` owns anchors, cross-session recall, pivots, the
-anchor footer and the Anthropic anchor cache marker (`app/anchor-cache.ts`;
-semantics adapted from pi-toolkit's auto-context under its MIT license).
+anchor footer and the Anthropic anchor cache marker (`app/anchor-cache.ts`).
 `app/navigation-data.ts` reads both owned anchors (`custom_message` entries of
 type `smart-context-anchor`, plus `smart_navigation` tool results) and legacy
-`context` tool anchors recorded by pi-toolkit; recall scans other sessions'
-JSONL read-only. pi-toolkit's auto-context extension is not a supported
-co-resident: two anchor and pruning owners are unsafe in any load order, and
-`piToolkit.context.thinningEnabled` is no longer read.
+`context` tool anchors; recall scans other sessions' JSONL read-only.
 
 A human anchor is a `sendMessage` custom message followed by a native label on
 that entry; a human pivot navigates to the label so Pi's `custom_message`
@@ -1039,7 +1034,6 @@ stores by default.
 | `app/session-lineage.ts` | read-only in-memory load of `parentSession` ancestors (depth, size and cycle bounds) |
 | `app/session-handoff.ts` | handoff seed from recorded state only; preview and `ctx.newSession` seeding |
 | `app/host-cache-ledger.ts` | session-local ledger of Pi's own requests: rebuild detection, cause attribution, cache lifetime |
-| `app/extension-conflicts.ts` | startup detection of known conflicting compaction/context-editing extensions; name-based, one notice |
 | `app/artifact-storage.ts` | read-only storage inventory and lineage classification |
 | `app/visual-archive.ts` | bounded evidence selection, persisted archive validation, request-local image rehydration |
 | `app/native-compaction.ts` | native engine: nested-request compaction, clean-turn cut, route/size checks, replay |

package/CHANGELOG.md

@@ -2,6 +2,18 @@
 
 ## [Unreleased]
 
+## [10.0.1] - 2026-09-28
+
+### Removed
+
+- Name-based startup scanning of unrelated extensions and instructions to
+  disable or uninstall them. An unrelated command name no longer produces a
+  guessed extension-conflict warning. Actual compaction lifecycle and
+  continuity-state checks remain in place.
+- Unrelated extension lists and compatibility-policing guidance from current
+  product documentation and release notes. Required and optional dependency
+  instructions, legacy session-data support and license attribution remain.
+
 ## [10.0.0] - 2026-09-28
 
 **Pi Continuity**: the stable release of the context-hygiene and session-continuity
@@ -22,10 +34,9 @@ rework. This release includes the work recorded in the unpublished
 - Mnemopi, its optional Bun runtime and image rendering are separate optional
   components, not automatic downloads. Readiness shows the correct install
   command. The default local graph does not require these components.
-- Use only one context-editing owner. Do not load pi-toolkit auto-context
-  alongside Continuity navigation. Claude subscription requests require the
-  separate adapter with final-payload normalization; the published adapter
-  `0.2.2` alone does not cover nested calls (upstream PR #10).
+- Claude subscription requests require the separate adapter with final-payload
+  normalization; the published adapter `0.2.2` alone does not cover nested calls
+  (upstream PR #10).
 
 ### Added
 

package/README.md

@@ -19,7 +19,7 @@ this extension adds context hygiene and continuity policies around it.
 > The TUI still says **Smart Compact**. No data or configuration migration is
 > needed. [Identity and naming](./docs/identity.md).
 >
-> **Pi Continuity 10.0.0:** upgrading from 9.x? Update Pi to 0.87.1 or newer
+> **Pi Continuity 10.0.1:** upgrading from 9.x? Update Pi to 0.87.1 or newer
 > and read the [upgrade notes](./docs/guide.md#upgrade-from-9x). Optional memory
 > engines and image rendering are installed separately. The
 > [changelog](./CHANGELOG.md) records the full release and its evidence limits.
@@ -149,8 +149,6 @@ session backups or archived tool output.
   model-runtime calls. Full coverage needs final-payload normalization
   ([upstream PR #10](https://github.com/minzique/pi-claude-oauth-adapter/pull/10)).
   [Compatibility details](./docs/guide.md#summary-format-provider-compaction-and-images).
-- **Use one context-editing owner.** Do not load pi-toolkit's auto-context
-  alongside session navigation. See [extension compatibility](./docs/guide.md#working-with-other-extensions-and-features).
 - **Cost and quality need live evidence.** Cancelled or discarded preparation
   still costs. Offline pilots do not establish billed savings, model fidelity
   or production readiness. [Evaluation limits](./docs/evaluation.md).

package/dist/constants.d.ts

@@ -8,7 +8,7 @@ import type { CompressionProfile, ProfileConfig } from "./types.ts";
  * `package.json#version`. Do not hand-edit this line for releases; bump
  * package.json and run `bun run sync-version`.
  */
-export declare const VERSION = "10.0.0";
+export declare const VERSION = "10.0.1";
 /**
  * Opt-in components that are not installed with the extension: optional peer
  * dependencies in package.json, pinned to the versions the release audit

package/dist/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAEN,KAAK,YAAY,EAEjB,MAAM,iCAAiC,CAAC;AAoEzC,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAC;AAyDtE,MAAM,CAAC,OAAO,UAAU,qBAAqB,CAAC,EAAE,EAAE,YAAY,QAwmB7D"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../src/index.ts"],"names":[],"mappings":"AAAA;;;;GAIG;AAEH,OAAO,EAEN,KAAK,YAAY,EAEjB,MAAM,iCAAiC,CAAC;AAmEzC,OAAO,EAAE,aAAa,EAAE,aAAa,EAAE,MAAM,wBAAwB,CAAC;AAyDtE,MAAM,CAAC,OAAO,UAAU,qBAAqB,CAAC,EAAE,EAAE,YAAY,QA8lB7D"}

package/dist/index.js

@@ -5,7 +5,7 @@ import {
 } from "@earendil-works/pi-coding-agent";
 
 // src/constants.ts
-var VERSION = "10.0.0";
+var VERSION = "10.0.1";
 var OPTIONAL_COMPONENTS = {
   mnemopi: { name: "@oh-my-pi/pi-mnemopi", version: "18.3.1", enables: "Mnemopi memory store" },
   bun: { name: "bun", version: "1.4.2", enables: "Mnemopi worker runtime when no Bun 1.3.14+ is on PATH" },
@@ -15807,72 +15807,6 @@ function createCompactionCommitStore(options = {}) {
   };
 }
 
-// src/app/extension-conflicts.ts
-var KIND = {
-  "context-fold": "compaction",
-  "pi-context-prune": "context-editing",
-  "pi-dcp": "context-editing",
-  "pi-fold": "context-editing",
-  "pi-openai-toolkit": "compaction",
-  "pi-toolkit": "context-editing"
-};
-var SEGMENT_OWNER = {
-  "context-fold": "context-fold",
-  dcp: "pi-dcp",
-  "pi-context-prune": "pi-context-prune",
-  "pi-dcp": "pi-dcp",
-  "pi-fold": "pi-fold",
-  "pi-openai-toolkit": "pi-openai-toolkit"
-};
-function segments(info) {
-  const out = new Set;
-  if (!info)
-    return out;
-  for (const text of [info.path ?? "", info.source ?? "", info.baseDir ?? ""]) {
-    for (const raw of text.toLowerCase().split(/[\\/:]+/)) {
-      const segment = raw.replace(/(.)@.*$/, "$1").replace(/\.(?:[cm]?[jt]s|git)$/, "");
-      if (segment)
-        out.add(segment);
-    }
-  }
-  return out;
-}
-function detectExtensionConflicts(registry) {
-  const entries = [
-    ...registry.commands.filter((command) => command.source === "extension").map((command) => ({ name: command.name.toLowerCase(), label: `/${command.name} command`, segments: segments(command.sourceInfo) })),
-    ...registry.tools.map((tool) => ({ name: tool.name.toLowerCase(), label: `${tool.name} tool`, segments: segments(tool.sourceInfo) }))
-  ].filter((entry) => !(entry.segments.has("pi-smart-compact") || entry.name.startsWith("smart_") || entry.name === "smart-compact"));
-  const found = new Map;
-  const add = (name, evidence) => {
-    if (!found.has(name))
-      found.set(name, evidence);
-  };
-  const bareFold = [];
-  for (const entry of entries) {
-    const owner = [...entry.segments].map((segment) => SEGMENT_OWNER[segment]).find(Boolean);
-    if (owner)
-      add(owner, `${entry.label} from ${owner}`);
-    else if (entry.segments.has("pi-toolkit") && entry.name === "context")
-      add("pi-toolkit", `${entry.label} from pi-toolkit`);
-    else if (entry.name === "fold-handoff")
-      add("context-fold", entry.label);
-    else if (entry.name === "prune")
-      add("pi-context-prune", entry.label);
-    else if (entry.name === "fold")
-      bareFold.push(entry);
-  }
-  for (const entry of bareFold)
-    add(found.has("context-fold") ? "context-fold" : "pi-fold", entry.label);
-  return [...found].map(([name, evidence]) => ({ name, kind: KIND[name], evidence })).sort((a, b) => a.name.localeCompare(b.name));
-}
-function conflictNotice(conflicts) {
-  const names = conflicts.map((conflict) => conflict.name);
-  const list = names.length === 1 ? names[0] : `${names.slice(0, -1).join(", ")} and ${names.at(-1)}`;
-  const verb = names.length === 1 ? "also compacts or edits" : "also compact or edit";
-  const evidence = conflicts.map((conflict) => `${conflict.name}: ${conflict.evidence}`).join("; ");
-  return `${list} ${verb} this conversation (${evidence}). Two owners of the same history are not safe in any load order: summaries can be discarded and cache prefixes rewritten twice. Keep only one loaded (Pi: /settings \u203A packages, or the extensions list).`;
-}
-
 // src/app/native-continuity-bridge.ts
 import crypto6 from "crypto";
 import fs13 from "fs";
@@ -23888,7 +23822,7 @@ function smartCompactExtension(pi) {
       const calls = displaced.reduce((sum, pending) => sum + (pending.metricsSnapshot?.totalCalls ?? 0), 0);
       reportIssue({
         key: "compact.foreign-displaced",
-        message: actor + " was applied instead of Continuity's prepared summary; that summary (" + calls + " model call" + (calls === 1 ? "" : "s") + ") was discarded and its continuity state was not saved. If another compaction extension is installed, keep only one."
+        message: actor + " was applied instead of Continuity's prepared summary; that summary (" + calls + " model call" + (calls === 1 ? "" : "s") + ") was discarded and its continuity state was not saved."
       }, ctx);
       await Promise.all(displaced.flatMap((pending) => applyFailureWrites.get(pending.runId) ?? []));
       return;
@@ -23896,7 +23830,7 @@ function smartCompactExtension(pi) {
     if (source === "extension") {
       reportIssue({
         key: "compact.foreign-extension",
-        message: actor + " was applied; Continuity did not summarize it and recorded no continuity state or metrics for it. If that is unintended, keep only one compaction extension."
+        message: actor + " was applied; Continuity did not summarize it and recorded no continuity state or metrics for it."
       }, ctx);
     } else if (automaticConfig().autoTrigger) {
       reportIssue({
@@ -24007,17 +23941,6 @@ function smartCompactExtension(pi) {
   pi.on("session_start", (_event, ctx) => {
     nativeReplay.refresh(ctx);
     flushIssues(ctx);
-    try {
-      const conflicts = detectExtensionConflicts({ commands: typeof pi.getCommands === "function" ? pi.getCommands() : [], tools: pi.getAllTools() });
-      if (conflicts.length > 0)
-        reportIssue({ key: "interop.conflicts", message: conflictNotice(conflicts) }, ctx);
-    } catch (error) {
-      reportIssue({
-        key: "interop.detect",
-        message: "Could not check loaded extensions for conflicts (" + errorDetail(error) + "). Other compaction extensions are not detected at startup. Please report this if it repeats.",
-        error
-      }, ctx);
-    }
     invalidatePreparation(ctx);
     hostCache.reset(resolveSessionId(ctx));
     toolExposure.atBoundary();

package/dist/rtk.js

@@ -198,7 +198,7 @@ class SecretScrubber {
 }
 
 // src/constants.ts
-var VERSION = "10.0.0";
+var VERSION = "10.0.1";
 var OPTIONAL_COMPONENTS = {
   mnemopi: { name: "@oh-my-pi/pi-mnemopi", version: "18.3.1", enables: "Mnemopi memory store" },
   bun: { name: "bun", version: "1.4.2", enables: "Mnemopi worker runtime when no Bun 1.3.14+ is on PATH" },

package/docs/RELEASE.md

@@ -38,8 +38,7 @@ package installation.
       plus the final-payload patch, [upstream PR #10](https://github.com/minzique/pi-claude-oauth-adapter/pull/10),
       until it is released) and record
       the paired archive paths and hashes at final packaging — do not
-      reconstruct them from memory. pi-toolkit's auto-context must not be
-      loaded with the candidate.
+      reconstruct them from memory.
 - [ ] Confirm Pi remains a host peer (`">=0.87.1"`) and TypeBox a wildcard peer (`"*"`); neither is bundled.
 - [ ] Confirm the visual renderer remains optional/external and the font plus its license ship in `assets/`, together with the on-demand context guide `assets/skills/context-management/SKILL.md`. Verify default Node loading without the optional addon and a real PNG render where supported.
 - [ ] Confirm Mnemopi stays an optional external engine with TypeBox external in its worker, and that `bun`, `@oh-my-pi/pi-mnemopi` and `@resvg/resvg-js` remain optional peers pinned to `OPTIONAL_COMPONENTS` (never `optionalDependencies`). Verify a plain install pulls none of them in, the failure names the install command for the install root, the installed Node-host worker runs on the user-installed `bun` component under a Pi-style npm root with no Bun on `PATH`, and the fail-closed missing-engine and missing-Bun failures submit no memory request and create no store.

package/docs/configuration.md

@@ -7,7 +7,7 @@ Pi Continuity is the product name only. Settings keep their technical names:
 everything lives under the `smartCompact` key, and the settings screen is opened
 with `/smart-compact settings`.
 
-Defaults on this page were checked against Pi Continuity `10.0.0`. For an older
+Defaults on this page were checked against Pi Continuity `10.0.1`. For an older
 installation, use [the changelog](../CHANGELOG.md) and the
 [upgrade notes](./guide.md#upgrade-from-9x) before adopting these settings.
 

package/docs/evaluation.md

@@ -381,7 +381,6 @@ no provider request.
 | Command | Default | Purpose |
 | --- | --- | --- |
 | `bun scripts/session-pilot.ts` | Offline | Real `AgentSession` with scripted model transport, Pi Continuity only: tools, anchor and pivot with carryover, trimming/retrieval, rewind, compaction and reopen |
-| `NODE_PATH="$PWD/node_modules" bun scripts/context-compat-pilot.ts /path/to/pi-lens` | Offline | Real Pi dispatch with an explicit local pi-lens path in both load orders: read-guard coverage and the anchor cached prefix across trim |
 | `PSC_CLAUDE_OAUTH_EXTENSION=<pi-claude-oauth-adapter>/extensions/index.ts bun scripts/native-host-pilot.ts` | Offline fake provider | Provider-native compaction on stock Pi; the Anthropic OAuth route needs the standalone adapter (patched final-payload build for billing on nested requests). `PSC_NATIVE_ROUTES=codex-oauth,openai-api-key` runs without it and `PSC_PILOT_SHORT=1` shortens each route. `PSC_NATIVE_LIVE=1` sends real, ledger-capped requests and needs explicit approval |
 | `bun run scripts/rtk-pilot.ts /absolute/path/to/rtk` | Local only | Synthetic RTK rewrite contract; characters, not provider tokens |
 | `bun run scripts/visual-pilot.ts --model=provider/id` | Offline planning | Bitmap versus text evidence; `--live` authorizes at most 9 sequential requests and needs explicit approval |

package/docs/guide.md

@@ -15,7 +15,7 @@ This guide is task oriented. For every setting, default and range, see the
 release evidence, see [evaluation](./evaluation.md).
 
 > [!NOTE]
-> **Which version this describes.** This guide targets Pi Continuity `10.0.0`,
+> **Which version this describes.** This guide targets Pi Continuity `10.0.1`,
 > the stable release of the context-hygiene and continuity rework. The earlier
 > `9.8.0-canary.*` entries in the changelog are historical local candidates,
 > not npm releases. See [upgrade notes](#upgrade-from-9x) when coming from 9.x
@@ -35,7 +35,7 @@ release evidence, see [evaluation](./evaluation.md).
 - [Session navigation](#session-navigation)
 - [Agent tools](#agent-tools)
 - [Memory: what is stored where](#memory-what-is-stored-where)
-- [Working with other extensions and features](#working-with-other-extensions-and-features)
+- [Pi host integration](#pi-host-integration)
 - [Experimental features](#experimental-features)
 - [Recovery](#recovery)
 - [Storage and privacy](#storage-and-privacy)
@@ -97,17 +97,14 @@ speculative background preparation are off until selected.
 and stored paths keep their names; do not rename existing data directories.
 
 1. Update Pi to **0.87.1+** and use **Node.js 22.19+**. Install the release with
-   `pi install npm:pi-smart-compact@10.0.0`, then reload or restart Pi.
+   `pi install npm:pi-smart-compact@10.0.1`, then reload or restart Pi.
 2. Open `/smart-compact` in the TUI. The bare command now opens Home; **Compact
    now** starts the interactive compaction flow. Print/RPC/SDK use still runs
    compaction directly. Review requires **A** to apply, not Enter.
 3. Expect the agent to see `smart_tools` first. It loads navigation, history,
    memory and compaction tools on demand. Choose **Always available** only if
    you want all permitted tools exposed from the start.
-4. Keep one context-editing owner. Disable pi-toolkit auto-context or another
-   overlapping cleanup/compaction extension before using these features; see
-   [extension compatibility](#working-with-other-extensions-and-features).
-5. Review **Memory store** if you use project memory. Exactly one backend is
+4. Review **Memory store** if you use project memory. Exactly one backend is
    used, with no silent fallback. Mnemopi and image snapshots now require
    [separately installed optional components](../README.md#optional-components);
    the default local memory store does not.
@@ -374,7 +371,7 @@ size, an `artifact-<hash>` ID and short first/last excerpts.
 - Not offloaded: errors, images, shell commands, writes, unknown tools,
   `read`/`read_symbol`/`read_enclosing` deliveries, instruction/skill-file
   reads and `smart_context` itself. File reads stay inline on first delivery,
-  so read-before-edit guards such as pi-lens see what was actually read.
+  so read-before-edit guards see what was actually read.
 - This is not a summary. The agent has to search or read the omitted parts
   when it needs them. Total savings depend on how much it reads back.
 - Each file is at most 2 MiB. A session holds at most 256 files or 32 MiB; at
@@ -449,8 +446,8 @@ other switches are kept), **Search other sessions**, **Return to an anchor**,
 newest anchor, so the context before it is read from cache while later turns
 change), **Anchor status** (footer, display only) and **Navigation guide**.
 
-Anchors recorded by pi-toolkit's `context` tool in earlier sessions stay
-readable in browse and search.
+Legacy `context` tool anchors recorded in earlier sessions stay readable in
+browse and search.
 
 ### Hand off to a new session
 
@@ -595,25 +592,9 @@ memory**) needs the TUI and applies only to the local store. It offers:
 It shows counts and asks for confirmation. Mnemopi, Hindsight, continuity
 state, backups and artifacts are not affected.
 
-## Working with other extensions and features
+## Pi host integration
 
-At session start Pi Continuity checks the loaded commands and tools for known
-compaction or context-editing extensions (pi-openai-toolkit, context-fold,
-pi-fold, pi-context-prune, pi-dcp, pi-toolkit's `context` tool) and shows one
-notice naming them. The check is name-based evidence, not proof, and finds
-nothing for unknown extensions; the runtime notices below (foreign compaction
-applied, foreign cache rebuilds) still cover those.
-
-### pi-toolkit
-
-Session navigation replaces the anchor, recall and pivot features of
-pi-toolkit's `context` tool, and Pi Continuity is the only owner of trimming.
-Do not load pi-toolkit's context-management extension together with Pi
-Continuity: two extensions recording anchors and pruning the same branch are
-not safe in any load order. The `piToolkit.context.thinningEnabled` key is not
-read by Pi Continuity. Anchors recorded earlier by pi-toolkit stay readable.
-
-### Other compaction extensions and Pi's built-in compaction
+### Pi compaction lifecycle
 
 Pi applies one compaction per request: the last extension to answer
 `session_before_compact` wins, and with no answer Pi's built-in summarizer
@@ -625,7 +606,7 @@ runs. When something other than Pi Continuity applies the compaction:
   the winner and the model calls that were wasted.
 - Another extension's compaction shows a once-per-session notice even when
   nothing was prepared, because Pi Continuity recorded no state or metrics
-  for it. Keep only one compaction extension loaded.
+  for it.
 - Pi's built-in compaction shows a notice only while automatic compaction is
   on (nothing was ready when Pi asked); earlier continuity state still carries
   over through the capsule.

package/package.json

@@ -1,6 +1,6 @@
 {
 	"name": "pi-smart-compact",
-	"version": "10.0.0",
+	"version": "10.0.1",
 	"description": "Pi Continuity — context hygiene and session continuity for Pi Coding Agent: recoverable cleanup, checkpoints, memory and verified compaction.",
 	"type": "module",
 	"packageManager": "bun@1.4.2",

package/dist/app/extension-conflicts.d.ts

@@ -1,15 +0,0 @@
-import type { SlashCommandInfo, ToolInfo } from "@earendil-works/pi-coding-agent";
-export interface ConflictingExtension {
-    name: string;
-    kind: "compaction" | "context-editing";
-    evidence: string;
-}
-export interface ExtensionRegistry {
-    commands: SlashCommandInfo[];
-    tools: ToolInfo[];
-}
-/** Known compaction or context-editing extensions visible in the live command/tool registry. Name-based evidence, not proof. */
-export declare function detectExtensionConflicts(registry: ExtensionRegistry): ConflictingExtension[];
-/** One notice naming every conflicting extension. */
-export declare function conflictNotice(conflicts: ConflictingExtension[]): string;
-//# sourceMappingURL=extension-conflicts.d.ts.map

package/dist/app/extension-conflicts.d.ts.map

@@ -1 +0,0 @@
-{"version":3,"file":"extension-conflicts.d.ts","sourceRoot":"","sources":["../../src/app/extension-conflicts.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,gBAAgB,EAAE,QAAQ,EAAE,MAAM,iCAAiC,CAAC;AAElF,MAAM,WAAW,oBAAoB;IACnC,IAAI,EAAE,MAAM,CAAC;IACb,IAAI,EAAE,YAAY,GAAG,iBAAiB,CAAC;IACvC,QAAQ,EAAE,MAAM,CAAC;CAClB;AAED,MAAM,WAAW,iBAAiB;IAChC,QAAQ,EAAE,gBAAgB,EAAE,CAAC;IAC7B,KAAK,EAAE,QAAQ,EAAE,CAAC;CACnB;AAmCD,gIAAgI;AAChI,wBAAgB,wBAAwB,CAAC,QAAQ,EAAE,iBAAiB,GAAG,oBAAoB,EAAE,CA0B5F;AAED,qDAAqD;AACrD,wBAAgB,cAAc,CAAC,SAAS,EAAE,oBAAoB,EAAE,GAAG,MAAM,CAMxE"}