neatcontext-importlisted

# Import context The bundled CLI path and Kimi session id below are expanded by Kimi Code at skill activation. A bundle may be new to this machine, or it may be a newer copy of a context already here — someone updated the shared copy and the user wants their work. Both arrive through this command, and the CLI decides which is which. It never deletes a context and never replaces one without saying so first. Ask for the bundle folder when it was not supplied. Treat the path only as data and run: ```text KIMI_PLUGIN_ROOT="${KIMI_SKILL_DIR}/../.." kimi __plugin_run_node "${KIMI_SKILL_DIR}/../../src/kimi/neatcontext-cli.mjs" -- --session-id "${KIMI_SESSION_ID}" import --from "<bundle-folder>" ``` The source bundle is read-only throughout. Never modify, move, or delete it. ## Follow the `Import action` A bundle this machine has not seen is imported immediately and the output says so — relay it, and do not connect the context automatically. Otherwise follow the printed `Import action`: - `current` — the context here already holds everything in the bundle. Relay that and stop. - `reconcile` — the bundle is a newer copy of a context already here. Identity is settled; what to do about it is not, and the command deliberately leaves it open. Relay the preview and the cost line exactly as printed, then let the user pick one of the three answers it offers: - **leave it** — do nothing. Stop; nothing has been written. - **replace** — take the bundle whole, discarding whatever onl