akernel-runtime 0.1.1__tar.gz → 0.1.4__tar.gz

akernel_runtime-0.1.4/.env.example

@@ -0,0 +1,4 @@
+AKERNEL_OPENAI_API_KEY=replace-with-your-key
+AKERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
+AKERNEL_OPENAI_MODEL=gpt-5.5
+AKERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/.github/release-notes/v0.1.0.md

@@ -17,7 +17,7 @@ akernel
 Windows users can also install directly from GitHub:
 
 ```powershell
-irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-kernel/main/scripts/install_remote.ps1 | iex
+irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-akernel/main/scripts/install_remote.ps1 | iex
 akernel setup
 akernel
 ```
@@ -25,7 +25,7 @@ akernel
 The npm launcher package is prepared but not yet published in this release:
 
 ```powershell
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/.github/release-notes/v0.1.1.md

@@ -20,5 +20,5 @@ akernel
 
 ## Notes
 
-- The npm launcher remains prepared but unpublished until the npm scope and trusted publisher are configured.
+- The npm launcher remains prepared but unpublished until the `@context-akernel` npm scope and trusted publisher are configured.
 - This is still alpha software; APIs, local state formats, marketplace contracts, and memory-retention heuristics may change before a stable release.

akernel_runtime-0.1.4/.github/release-notes/v0.1.2.md

@@ -0,0 +1,30 @@
+# Context Kernel v0.1.2
+
+This release validates the public npm launcher path after the first PyPI releases.
+
+## Install
+
+Python:
+
+```powershell
+python -m pip install --user --upgrade akernel-runtime
+akernel setup
+akernel
+```
+
+npm launcher:
+
+```powershell
+npm install -g @context-akernel/akernel
+akernel setup
+akernel
+```
+
+## Changes
+
+- Renamed the prepared npm launcher scope from `@context-kernel/akernel` to `@context-akernel/akernel`.
+- Keeps `akernel-runtime` as the Python source-of-truth package and `akernel` as the shared CLI command.
+
+## Notes
+
+This is still alpha software. The npm launcher bootstraps the Python package when needed; the Python runtime remains the authoritative implementation.

akernel_runtime-0.1.4/.github/release-notes/v0.1.3.md

@@ -0,0 +1,30 @@
+# Context Kernel v0.1.3
+
+This release aligns public repository metadata with the npm scope and completes the move toward the `akernel` naming surface.
+
+## Install
+
+Python:
+
+```powershell
+python -m pip install --user --upgrade akernel-runtime
+akernel setup
+akernel
+```
+
+npm launcher:
+
+```powershell
+npm install -g @context-akernel/akernel
+akernel setup
+akernel
+```
+
+## Changes
+
+- Updated repository metadata and install links from `context-kernel` to `context-akernel`.
+- Keeps `akernel-runtime` as the Python package and `@context-akernel/akernel` as the npm launcher package.
+
+## Notes
+
+If you use Trusted Publishing, ensure PyPI and npm publisher settings now point to the GitHub repository `huanxin0825-ctrl/context-akernel`.

akernel_runtime-0.1.4/.github/release-notes/v0.1.4.md

@@ -0,0 +1,30 @@
+# Context Kernel v0.1.4
+
+This release verifies the refreshed GitHub repository identity after the public move to `context-akernel`.
+
+## Install
+
+Python:
+
+```powershell
+python -m pip install --user --upgrade akernel-runtime
+akernel setup
+akernel
+```
+
+npm launcher:
+
+```powershell
+npm install -g @context-akernel/akernel
+akernel setup
+akernel
+```
+
+## Changes
+
+- Publishes a clean patch release after updating Trusted Publisher bindings to `huanxin0825-ctrl/context-akernel`.
+- Keeps the package names stable: `akernel-runtime` on PyPI and `@context-akernel/akernel` on npm.
+
+## Notes
+
+Use this version to confirm both package registries now trust the renamed GitHub repository.

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/CHANGELOG.md

@@ -8,6 +8,26 @@ The project follows a pragmatic pre-1.0 changelog: breaking changes may occur, b
 
 No changes yet.
 
+## 0.1.4 - 2026-05-12
+
+### Changed
+
+- Reissued the repository rename release after refreshing package publisher bindings for `context-akernel`.
+
+## 0.1.3 - 2026-05-12
+
+### Changed
+
+- Renamed repository metadata and install links from `context-kernel` to `context-akernel` to align with the npm scope.
+
+## 0.1.2 - 2026-05-12
+
+### Changed
+
+- Renamed the prepared npm launcher scope from `@context-kernel/akernel` to `@context-akernel/akernel`.
+- Renamed project-local provider environment variables from `CONTEXT_KERNEL_OPENAI_*` to `AKERNEL_OPENAI_*` while keeping legacy names as a compatibility fallback.
+- Moved the default user launcher directory from `%USERPROFILE%\.context-kernel\bin` to `%USERPROFILE%\.akernel\bin`.
+
 ## 0.1.1 - 2026-05-12
 
 ### Changed

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: akernel-runtime
-Version: 0.1.1
+Version: 0.1.4
 Summary: Agent Kernel: a CLI-first context-native agent runtime prototype.
 Author: Context Kernel contributors
 License-Expression: Apache-2.0
-Project-URL: Homepage, https://github.com/huanxin0825-ctrl/context-kernel
-Project-URL: Repository, https://github.com/huanxin0825-ctrl/context-kernel
-Project-URL: Issues, https://github.com/huanxin0825-ctrl/context-kernel/issues
-Project-URL: Changelog, https://github.com/huanxin0825-ctrl/context-kernel/blob/main/CHANGELOG.md
+Project-URL: Homepage, https://github.com/huanxin0825-ctrl/context-akernel
+Project-URL: Repository, https://github.com/huanxin0825-ctrl/context-akernel
+Project-URL: Issues, https://github.com/huanxin0825-ctrl/context-akernel/issues
+Project-URL: Changelog, https://github.com/huanxin0825-ctrl/context-akernel/blob/main/CHANGELOG.md
 Keywords: agent,cli,context,llm,token-budget
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
@@ -45,7 +45,7 @@ Package and command names map to the same idea:
 - Python distribution: `akernel-runtime`
 - Python import package: `context_kernel`
 - CLI command: `akernel`
-- npm launcher: `@context-kernel/akernel`
+- npm launcher: `@context-akernel/akernel`
 
 ## Why This Exists
 
@@ -101,7 +101,7 @@ akernel
 
 `setup.cmd` creates `.venv`, installs the local CLI in editable mode, and prepares project-local `.env` if needed. `wake.cmd` activates the environment, loads `.env`, and prints common commands. The `.cmd` wrappers avoid local PowerShell execution-policy friction.
 
-`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.context-kernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
+`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.akernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
 
 ### Manual Python Install
 
@@ -127,22 +127,22 @@ akernel
 Windows users can also install directly from GitHub:
 
 ```powershell
-irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-kernel/main/scripts/install_remote.ps1 | iex
+irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-akernel/main/scripts/install_remote.ps1 | iex
 akernel setup
 akernel
 ```
 
 ### npm Launcher
 
-The npm launcher is prepared for publication. After `@context-kernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
+The npm launcher is prepared for publication. After `@context-akernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
 
 ```powershell
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```
 
-Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-akernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 
@@ -183,12 +183,14 @@ The current deterministic scale snapshot is documented in [Benchmark Evidence](d
 Provider configuration is project-local. Copy `.env.example` to `.env` or use `setup.cmd -ForceEnv`.
 
 ```env
-CONTEXT_KERNEL_OPENAI_API_KEY=replace-with-your-key
-CONTEXT_KERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
-CONTEXT_KERNEL_OPENAI_MODEL=gpt-5.5
-CONTEXT_KERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
+AKERNEL_OPENAI_API_KEY=replace-with-your-key
+AKERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
+AKERNEL_OPENAI_MODEL=gpt-5.5
+AKERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
 ```
 
+Legacy `CONTEXT_KERNEL_OPENAI_*` names are still read as a compatibility fallback, but new projects should use `AKERNEL_OPENAI_*`.
+
 Useful checks:
 
 ```powershell

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/README.md

@@ -18,7 +18,7 @@ Package and command names map to the same idea:
 - Python distribution: `akernel-runtime`
 - Python import package: `context_kernel`
 - CLI command: `akernel`
-- npm launcher: `@context-kernel/akernel`
+- npm launcher: `@context-akernel/akernel`
 
 ## Why This Exists
 
@@ -74,7 +74,7 @@ akernel
 
 `setup.cmd` creates `.venv`, installs the local CLI in editable mode, and prepares project-local `.env` if needed. `wake.cmd` activates the environment, loads `.env`, and prints common commands. The `.cmd` wrappers avoid local PowerShell execution-policy friction.
 
-`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.context-kernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
+`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.akernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
 
 ### Manual Python Install
 
@@ -100,22 +100,22 @@ akernel
 Windows users can also install directly from GitHub:
 
 ```powershell
-irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-kernel/main/scripts/install_remote.ps1 | iex
+irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-akernel/main/scripts/install_remote.ps1 | iex
 akernel setup
 akernel
 ```
 
 ### npm Launcher
 
-The npm launcher is prepared for publication. After `@context-kernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
+The npm launcher is prepared for publication. After `@context-akernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
 
 ```powershell
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```
 
-Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-akernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 
@@ -156,12 +156,14 @@ The current deterministic scale snapshot is documented in [Benchmark Evidence](d
 Provider configuration is project-local. Copy `.env.example` to `.env` or use `setup.cmd -ForceEnv`.
 
 ```env
-CONTEXT_KERNEL_OPENAI_API_KEY=replace-with-your-key
-CONTEXT_KERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
-CONTEXT_KERNEL_OPENAI_MODEL=gpt-5.5
-CONTEXT_KERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
+AKERNEL_OPENAI_API_KEY=replace-with-your-key
+AKERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
+AKERNEL_OPENAI_MODEL=gpt-5.5
+AKERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
 ```
 
+Legacy `CONTEXT_KERNEL_OPENAI_*` names are still read as a compatibility fallback, but new projects should use `AKERNEL_OPENAI_*`.
+
 Useful checks:
 
 ```powershell

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/docs/01-architecture.md

@@ -98,14 +98,14 @@ The model provider is an interface. The CLI includes a mock provider for determi
 
 Provider secrets are loaded from current process environment first, then project-local `.env`. The `.env` file is ignored by git and should stay local to the working copy.
 
-- `CONTEXT_KERNEL_OPENAI_API_KEY`
-- `CONTEXT_KERNEL_OPENAI_BASE_URL`
-- `CONTEXT_KERNEL_OPENAI_MODEL`
-- `CONTEXT_KERNEL_OPENAI_AUX_MODEL`
+- `AKERNEL_OPENAI_API_KEY`
+- `AKERNEL_OPENAI_BASE_URL`
+- `AKERNEL_OPENAI_MODEL`
+- `AKERNEL_OPENAI_AUX_MODEL`
 
 OpenAI-compatible base URLs are normalized to a `/v1` API root, so both `https://host` and `https://host/v1` are accepted.
 
-`CONTEXT_KERNEL_OPENAI_MODEL` is the primary execution model used for high-risk, deep, warning-heavy, or synthesis steps. `CONTEXT_KERNEL_OPENAI_AUX_MODEL` is the auxiliary model role used for low/medium first-step planning in automatic routing and for auxiliary review before primary-model steps. Review traces are saved and their tokens are included in agent cost reports.
+`AKERNEL_OPENAI_MODEL` is the primary execution model used for high-risk, deep, warning-heavy, or synthesis steps. `AKERNEL_OPENAI_AUX_MODEL` is the auxiliary model role used for low/medium first-step planning in automatic routing and for auxiliary review before primary-model steps. Review traces are saved and their tokens are included in agent cost reports.
 
 ### Verifier
 

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/docs/05-local-wake.md

@@ -25,7 +25,7 @@ akernel
 akernel --help
 ```
 
-The launchers live in `%USERPROFILE%\.context-kernel\bin`, and that directory is added to the user PATH. Open a new terminal if the commands are not visible immediately. `akernel` uses the current directory as the workspace, stores state in `.akernel`, and initializes it if needed. Environment lookup prefers the current directory `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` is kept as a compatibility shortcut.
+The launchers live in `%USERPROFILE%\.akernel\bin`, and that directory is added to the user PATH. Open a new terminal if the commands are not visible immediately. `akernel` uses the current directory as the workspace, stores state in `.akernel`, and initializes it if needed. Environment lookup prefers the current directory `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` is kept as a compatibility shortcut.
 
 ## Wake The Project
 

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/docs/07-release-and-ci.md

@@ -94,7 +94,7 @@ akernel
 Until PyPI publishing is enabled, Windows users can install from GitHub with:
 
 ```powershell
-irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-kernel/main/scripts/install_remote.ps1 | iex
+irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-akernel/main/scripts/install_remote.ps1 | iex
 akernel setup
 akernel
 ```
@@ -102,12 +102,12 @@ akernel
 The npm wrapper can be installed globally after publication:
 
 ```powershell
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```
 
-Before PyPI publication, set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` so the npm wrapper bootstraps from GitHub.
+Before PyPI publication, set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-akernel.git` so the npm wrapper bootstraps from GitHub.
 
 `bench gate` also requires the current benchmark report itself to pass its checks. This prevents a bad first run from becoming the new normal just because the relative diff has no regression.
 The release workflow also uploads benchmark evidence as a workflow artifact so release preparation carries a reproducible token-savings snapshot.

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/docs/11-publishing-setup.md

@@ -8,7 +8,7 @@ Do not commit credentials to the repository. Do not paste PyPI or npm tokens int
 
 You need:
 
-- A GitHub account with admin access to `huanxin0825-ctrl/context-kernel`.
+- A GitHub account with admin access to `huanxin0825-ctrl/context-akernel`.
 - A PyPI account with two-factor authentication enabled.
 - An npm account with two-factor authentication enabled.
 - Either an npm organization or user scope that can publish the package name used by `packages/npm/akernel/package.json`.
@@ -30,7 +30,7 @@ Configure a PyPI trusted publisher with these values:
 | --- | --- |
 | PyPI project name | `akernel-runtime` |
 | Owner | `huanxin0825-ctrl` |
-| Repository name | `context-kernel` |
+| Repository name | `context-akernel` |
 | Workflow filename | `release.yml` |
 | Environment name | `pypi` |
 
@@ -48,22 +48,22 @@ No GitHub secret is needed for PyPI when Trusted Publishing is configured.
 The current npm package name is:
 
 ```text
-@context-kernel/akernel
+@context-akernel/akernel
 ```
 
-Before publishing, confirm that the `context-kernel` npm scope is available to you. Usually that means creating an npm organization named `context-kernel`, or changing `packages/npm/akernel/package.json` to use a scope you control.
+Before publishing, confirm that the `context-akernel` npm scope is available to you. Usually that means creating an npm organization named `context-akernel`, or changing `packages/npm/akernel/package.json` to use a scope you control.
 
 Recommended path: use npm Trusted Publishing. It avoids a long-lived npm token and publishes with GitHub OIDC plus provenance.
 
 1. Create or confirm the npm scope.
-2. Create the package or configure a pending trusted publisher for `@context-kernel/akernel`.
+2. Create the package or configure a pending trusted publisher for `@context-akernel/akernel`.
 3. Use these trusted publisher values:
 
 | Field | Value |
 | --- | --- |
-| Package | `@context-kernel/akernel` |
+| Package | `@context-akernel/akernel` |
 | Owner | `huanxin0825-ctrl` |
-| Repository name | `context-kernel` |
+| Repository name | `context-akernel` |
 | Workflow filename | `release.yml` |
 | Environment name | `npm` |
 
@@ -126,7 +126,7 @@ Send only these confirmations:
 
 - PyPI account is ready and Trusted Publisher is configured.
 - GitHub environment `pypi` exists.
-- npm scope decision: keep `@context-kernel/akernel` or change to another scope.
+- npm scope decision: keep `@context-akernel/akernel` or change to another scope.
 - If publishing npm now: npm Trusted Publishing exists, GitHub environment `npm` exists, and `PUBLISH_NPM=true` variable exists.
 - If using the fallback token path: `NPM_TOKEN` secret exists.
 

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/packages/npm/akernel/README.md

@@ -1,11 +1,11 @@
-# @context-kernel/akernel
+# @context-akernel/akernel
 
 This package is a small npm launcher wrapper for the Python Context Kernel runtime.
 
 `akernel` means **Agent Kernel**: the command starts the agent-facing runtime that assembles context, memory, skills, policy, and token budgets before model calls.
 
 ```bash
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```
@@ -18,7 +18,7 @@ python -m pip install --user --upgrade akernel-runtime
 
 Useful environment overrides:
 
-- `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` installs from GitHub instead of PyPI.
+- `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-akernel.git` installs from GitHub instead of PyPI.
 - `AKERNEL_SKIP_BOOTSTRAP=1` disables automatic pip installation.
 
 Python 3.10 or newer is required. The Python package remains the source of truth.

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/packages/npm/akernel/package.json

@@ -1,16 +1,16 @@
 {
-  "name": "@context-kernel/akernel",
-  "version": "0.1.1",
+  "name": "@context-akernel/akernel",
+  "version": "0.1.4",
   "description": "npm launcher wrapper for the Context Kernel akernel CLI.",
   "license": "Apache-2.0",
-  "homepage": "https://github.com/huanxin0825-ctrl/context-kernel#readme",
+  "homepage": "https://github.com/huanxin0825-ctrl/context-akernel#readme",
   "repository": {
     "type": "git",
-    "url": "git+https://github.com/huanxin0825-ctrl/context-kernel.git",
+    "url": "git+https://github.com/huanxin0825-ctrl/context-akernel.git",
     "directory": "packages/npm/akernel"
   },
   "bugs": {
-    "url": "https://github.com/huanxin0825-ctrl/context-kernel/issues"
+    "url": "https://github.com/huanxin0825-ctrl/context-akernel/issues"
   },
   "keywords": [
     "agent",

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "akernel-runtime"
-version = "0.1.1"
+version = "0.1.4"
 description = "Agent Kernel: a CLI-first context-native agent runtime prototype."
 readme = "README.md"
 license = "Apache-2.0"
@@ -26,10 +26,10 @@ classifiers = [
 ]
 
 [project.urls]
-Homepage = "https://github.com/huanxin0825-ctrl/context-kernel"
-Repository = "https://github.com/huanxin0825-ctrl/context-kernel"
-Issues = "https://github.com/huanxin0825-ctrl/context-kernel/issues"
-Changelog = "https://github.com/huanxin0825-ctrl/context-kernel/blob/main/CHANGELOG.md"
+Homepage = "https://github.com/huanxin0825-ctrl/context-akernel"
+Repository = "https://github.com/huanxin0825-ctrl/context-akernel"
+Issues = "https://github.com/huanxin0825-ctrl/context-akernel/issues"
+Changelog = "https://github.com/huanxin0825-ctrl/context-akernel/blob/main/CHANGELOG.md"
 
 [project.optional-dependencies]
 dev = ["build>=1.2", "twine>=5.0"]

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/scripts/install_remote.ps1

@@ -1,6 +1,6 @@
 param(
-  [string]$Source = "git+https://github.com/huanxin0825-ctrl/context-kernel.git",
-  [string]$LauncherDir = "$env:USERPROFILE\.context-kernel\bin"
+  [string]$Source = "git+https://github.com/huanxin0825-ctrl/context-akernel.git",
+  [string]$LauncherDir = "$env:USERPROFILE\.akernel\bin"
 )
 
 $ErrorActionPreference = "Stop"

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/setup.ps1

@@ -13,7 +13,7 @@ $ProjectRoot = Split-Path -Parent $MyInvocation.MyCommand.Path
 $VenvPath = Join-Path $ProjectRoot ".venv"
 $PythonPath = Join-Path $VenvPath "Scripts\python.exe"
 $EnvPath = Join-Path $ProjectRoot ".env"
-$LauncherDir = Join-Path $env:USERPROFILE ".context-kernel\bin"
+$LauncherDir = Join-Path $env:USERPROFILE ".akernel\bin"
 
 function Install-GlobalLaunchers {
     param(
@@ -27,7 +27,7 @@ function Install-GlobalLaunchers {
 $akernel = @"
 @echo off
 setlocal
-set "CONTEXT_KERNEL_PROJECT_ROOT=$ProjectRoot"
+set "AKERNEL_PROJECT_ROOT=$ProjectRoot"
 "$PythonPath" -m context_kernel %*
 exit /b %ERRORLEVEL%
 "@
@@ -36,7 +36,7 @@ exit /b %ERRORLEVEL%
 $chat = @"
 @echo off
 setlocal
-set "CONTEXT_KERNEL_PROJECT_ROOT=$ProjectRoot"
+set "AKERNEL_PROJECT_ROOT=$ProjectRoot"
 "$PythonPath" -m context_kernel chat %*
 exit /b %ERRORLEVEL%
 "@
@@ -76,15 +76,15 @@ if ($ForceEnv -or -not (Test-Path -LiteralPath $EnvPath)) {
         if (Test-Path -LiteralPath $EnvPath) {
             Write-Host "Keeping existing .env because no ApiKey was provided."
         } else {
-            Write-Host "Creating .env from .env.example. Fill in CONTEXT_KERNEL_OPENAI_API_KEY before using openai provider."
+            Write-Host "Creating .env from .env.example. Fill in AKERNEL_OPENAI_API_KEY before using openai provider."
             Copy-Item -LiteralPath (Join-Path $ProjectRoot ".env.example") -Destination $EnvPath
         }
     } else {
         $lines = @(
-            "CONTEXT_KERNEL_OPENAI_API_KEY=$ApiKey",
-            "CONTEXT_KERNEL_OPENAI_BASE_URL=$BaseUrl",
-            "CONTEXT_KERNEL_OPENAI_MODEL=$Model",
-            "CONTEXT_KERNEL_OPENAI_AUX_MODEL=$AuxModel"
+            "AKERNEL_OPENAI_API_KEY=$ApiKey",
+            "AKERNEL_OPENAI_BASE_URL=$BaseUrl",
+            "AKERNEL_OPENAI_MODEL=$Model",
+            "AKERNEL_OPENAI_AUX_MODEL=$AuxModel"
         )
         Set-Content -LiteralPath $EnvPath -Value $lines -Encoding UTF8
         Write-Host "Wrote project-local .env."

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/src/akernel_runtime.egg-info/PKG-INFO

@@ -1,13 +1,13 @@
 Metadata-Version: 2.4
 Name: akernel-runtime
-Version: 0.1.1
+Version: 0.1.4
 Summary: Agent Kernel: a CLI-first context-native agent runtime prototype.
 Author: Context Kernel contributors
 License-Expression: Apache-2.0
-Project-URL: Homepage, https://github.com/huanxin0825-ctrl/context-kernel
-Project-URL: Repository, https://github.com/huanxin0825-ctrl/context-kernel
-Project-URL: Issues, https://github.com/huanxin0825-ctrl/context-kernel/issues
-Project-URL: Changelog, https://github.com/huanxin0825-ctrl/context-kernel/blob/main/CHANGELOG.md
+Project-URL: Homepage, https://github.com/huanxin0825-ctrl/context-akernel
+Project-URL: Repository, https://github.com/huanxin0825-ctrl/context-akernel
+Project-URL: Issues, https://github.com/huanxin0825-ctrl/context-akernel/issues
+Project-URL: Changelog, https://github.com/huanxin0825-ctrl/context-akernel/blob/main/CHANGELOG.md
 Keywords: agent,cli,context,llm,token-budget
 Classifier: Development Status :: 3 - Alpha
 Classifier: Intended Audience :: Developers
@@ -45,7 +45,7 @@ Package and command names map to the same idea:
 - Python distribution: `akernel-runtime`
 - Python import package: `context_kernel`
 - CLI command: `akernel`
-- npm launcher: `@context-kernel/akernel`
+- npm launcher: `@context-akernel/akernel`
 
 ## Why This Exists
 
@@ -101,7 +101,7 @@ akernel
 
 `setup.cmd` creates `.venv`, installs the local CLI in editable mode, and prepares project-local `.env` if needed. `wake.cmd` activates the environment, loads `.env`, and prints common commands. The `.cmd` wrappers avoid local PowerShell execution-policy friction.
 
-`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.context-kernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
+`setup.cmd` also installs user-level launchers in `%USERPROFILE%\.akernel\bin` and adds that directory to the user PATH. After opening a new terminal, `akernel` works from any directory, starts the interactive agent session by default, and uses that current directory as the workspace location. Environment lookup prefers the current project `.env`, then falls back to the installed Context Kernel project `.env`. `akernel-chat` remains as a compatibility shortcut.
 
 ### Manual Python Install
 
@@ -127,22 +127,22 @@ akernel
 Windows users can also install directly from GitHub:
 
 ```powershell
-irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-kernel/main/scripts/install_remote.ps1 | iex
+irm https://raw.githubusercontent.com/huanxin0825-ctrl/context-akernel/main/scripts/install_remote.ps1 | iex
 akernel setup
 akernel
 ```
 
 ### npm Launcher
 
-The npm launcher is prepared for publication. After `@context-kernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
+The npm launcher is prepared for publication. After `@context-akernel/akernel` is published, it will provide a Node-style entrypoint and bootstrap the Python package if it is missing:
 
 ```powershell
-npm install -g @context-kernel/akernel
+npm install -g @context-akernel/akernel
 akernel setup
 akernel
 ```
 
-Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-akernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 
@@ -183,12 +183,14 @@ The current deterministic scale snapshot is documented in [Benchmark Evidence](d
 Provider configuration is project-local. Copy `.env.example` to `.env` or use `setup.cmd -ForceEnv`.
 
 ```env
-CONTEXT_KERNEL_OPENAI_API_KEY=replace-with-your-key
-CONTEXT_KERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
-CONTEXT_KERNEL_OPENAI_MODEL=gpt-5.5
-CONTEXT_KERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
+AKERNEL_OPENAI_API_KEY=replace-with-your-key
+AKERNEL_OPENAI_BASE_URL=https://clarmy.cloud/v1
+AKERNEL_OPENAI_MODEL=gpt-5.5
+AKERNEL_OPENAI_AUX_MODEL=gpt-5.3-codex
 ```
 
+Legacy `CONTEXT_KERNEL_OPENAI_*` names are still read as a compatibility fallback, but new projects should use `AKERNEL_OPENAI_*`.
+
 Useful checks:
 
 ```powershell

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/src/akernel_runtime.egg-info/SOURCES.txt

@@ -17,6 +17,9 @@ wake.ps1
 .github/ISSUE_TEMPLATE/feature_request.md
 .github/release-notes/v0.1.0.md
 .github/release-notes/v0.1.1.md
+.github/release-notes/v0.1.2.md
+.github/release-notes/v0.1.3.md
+.github/release-notes/v0.1.4.md
 .github/workflows/ci.yml
 .github/workflows/release.yml
 docs/00-vision.md

{akernel_runtime-0.1.1 → akernel_runtime-0.1.4}/src/context_kernel/__init__.py

@@ -1,3 +1,3 @@
 """Context Kernel CLI-first agent runtime prototype."""
 
-__version__ = "0.1.1"
+__version__ = "0.1.4"