akernel-runtime 0.1.0__tar.gz → 0.1.2__tar.gz

akernel_runtime-0.1.2/.github/release-notes/v0.1.0.md

@@ -0,0 +1,65 @@
+# Context Kernel v0.1.0
+
+Context Kernel is an alpha CLI release of `akernel`, an **Agent Kernel** for building context-efficient coding-agent workflows.
+
+Most agent systems treat the prompt as the runtime. Context Kernel moves more of that work into an inspectable local runtime: structured memory, scoped skill contracts, policy-gated tools, budget profiles, traces, and benchmark evidence.
+
+## Install
+
+Python users can install the published runtime from PyPI:
+
+```powershell
+python -m pip install --user akernel-runtime
+akernel setup
+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
+akernel setup
+akernel
+```
+
+The npm launcher package is prepared but not yet published in this release:
+
+```powershell
+npm install -g @context-akernel/akernel
+akernel setup
+akernel
+```
+
+## Highlights
+
+- `akernel` starts an interactive Claude Code-style agent session by default.
+- `akernel setup` writes project-local OpenAI-compatible provider configuration.
+- Primary and auxiliary model roles are tracked separately, including automatic routing and optional auxiliary review.
+- Project scanning writes compact `.akernel/project.json` metadata with detected languages, package managers, key files, and likely test/build commands.
+- The bounded agent loop supports policy-gated file reads, writes, patches, batch patches, command execution, and compact responses.
+- Failing-test recovery can inspect simple Python failure output, patch one or more files, and rerun verification.
+- Long task sessions can carry structured milestone plans, active checkpoints, acceptance criteria, and compact resume prompts.
+- Memory pruning and global memory sync support explicit retention, dry-run previews, namespaces, source filters, tags, and provenance.
+- Built-in skill marketplace support includes multi-file bugfix, long-task planning, and context-compaction contracts.
+- A zero-dependency terminal UI provides a cockpit-style dashboard with transcript, model stack, workspace summary, diagnostics, and run timelines.
+
+## Benchmark Evidence
+
+The deterministic scale benchmark snapshot for this release:
+
+- Fixtures: `3`
+- Tasks: `6`
+- Checks: `12/12`
+- Pass rate: `100.0%`
+- Kernel tokens: `1235`
+- Full-load baseline tokens: `2447`
+- Token savings: `1212`
+- Total savings: `49.53%`
+
+These benchmarks are mock-provider deterministic checks. They prove the runtime can produce repeatable token-savings evidence while preserving expected task evidence; they do not yet claim production-wide savings across all real providers.
+
+## Alpha Notice
+
+This is alpha software. The CLI is functional, tested, packaged, and benchmarked locally, but APIs, file formats, marketplace contracts, and memory-retention heuristics may change before a stable release.
+
+Use it for experimentation, early integrations, benchmark-driven iteration, and contributor feedback.

akernel_runtime-0.1.2/.github/release-notes/v0.1.1.md

@@ -0,0 +1,24 @@
+# Context Kernel v0.1.1
+
+This is a release polish update for the first public alpha. It keeps the runtime behavior stable while improving public packaging, release automation, and installation clarity.
+
+## Install
+
+```powershell
+python -m pip install --user --upgrade akernel-runtime
+akernel setup
+akernel
+```
+
+## Changes
+
+- Documented that `akernel` means **Agent Kernel**, and clarified the relationship between the project name, Python distribution, import package, CLI command, and npm launcher.
+- Updated PyPI package metadata to use the Agent Kernel wording.
+- Updated README installation language to reflect that `akernel-runtime` is live on PyPI.
+- Added npm Trusted Publishing guidance, provenance support, and npm-only manual publish support to the release workflow.
+- Added GitHub Release notes and workflow support for automated or manual release page creation.
+
+## Notes
+
+- 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.2/.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.0 → akernel_runtime-0.1.2}/.github/workflows/release.yml

@@ -11,6 +11,20 @@ on:
         options:
           - "false"
           - "true"
+      target:
+        description: "Publish target when publish=true."
+        required: true
+        default: "all"
+        type: choice
+        options:
+          - "all"
+          - "github-release"
+          - "python"
+          - "npm"
+      release_tag:
+        description: "Release tag for manual github-release runs, for example v0.1.0."
+        required: false
+        default: ""
   push:
     tags:
       - "v*"
@@ -67,7 +81,7 @@ jobs:
       - name: Set up Node
         uses: actions/setup-node@v4
         with:
-          node-version: "20"
+          node-version: "24"
 
       - name: Validate npm package
         working-directory: packages/npm/akernel
@@ -112,11 +126,65 @@ jobs:
             .release-bench/benchmark-evidence.md
             .release-bench/benchmarks/*.json
 
+  github-release:
+    name: Create GitHub Release
+    runs-on: ubuntu-latest
+    needs: [python-package, npm-package, benchmark-evidence]
+    if: |
+      startsWith(github.ref, 'refs/tags/v') ||
+      (
+        github.event_name == 'workflow_dispatch' &&
+        github.event.inputs.publish == 'true' &&
+        (
+          github.event.inputs.target == 'all' ||
+          github.event.inputs.target == 'github-release'
+        )
+      )
+    permissions:
+      contents: write
+
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Resolve release notes
+        id: release_notes
+        shell: bash
+        run: |
+          set -euo pipefail
+          tag="${{ github.event.inputs.release_tag || github.ref_name }}"
+          if [ -z "$tag" ] || [ "$tag" = "main" ]; then
+            echo "release_tag must be set for manual GitHub release runs." >&2
+            exit 1
+          fi
+          notes=".github/release-notes/${tag}.md"
+          if [ ! -f "$notes" ]; then
+            echo "Missing release notes: $notes" >&2
+            exit 1
+          fi
+          echo "tag=$tag" >> "$GITHUB_OUTPUT"
+          echo "notes=$notes" >> "$GITHUB_OUTPUT"
+
+      - name: Publish GitHub release
+        uses: softprops/action-gh-release@v2
+        with:
+          tag_name: ${{ steps.release_notes.outputs.tag }}
+          name: Context Kernel ${{ steps.release_notes.outputs.tag }}
+          body_path: ${{ steps.release_notes.outputs.notes }}
+          prerelease: true
+
   publish-pypi:
     name: Publish To PyPI
     runs-on: ubuntu-latest
     needs: [python-package, npm-package, benchmark-evidence]
-    if: startsWith(github.ref, 'refs/tags/v') || (github.event_name == 'workflow_dispatch' && github.event.inputs.publish == 'true')
+    if: |
+      (
+        startsWith(github.ref, 'refs/tags/v') ||
+        (github.event_name == 'workflow_dispatch' && github.event.inputs.publish == 'true')
+      ) && (
+        github.event_name != 'workflow_dispatch' ||
+        github.event.inputs.target != 'npm'
+      )
     permissions:
       id-token: write
       contents: read
@@ -136,9 +204,17 @@ jobs:
     name: Publish npm Launcher
     runs-on: ubuntu-latest
     needs: [python-package, npm-package, benchmark-evidence]
-    if: (startsWith(github.ref, 'refs/tags/v') || (github.event_name == 'workflow_dispatch' && github.event.inputs.publish == 'true')) && vars.PUBLISH_NPM == 'true'
+    if: |
+      (
+        startsWith(github.ref, 'refs/tags/v') ||
+        (github.event_name == 'workflow_dispatch' && github.event.inputs.publish == 'true')
+      ) && (
+        github.event_name != 'workflow_dispatch' ||
+        github.event.inputs.target != 'python'
+      ) && vars.PUBLISH_NPM == 'true'
     permissions:
       contents: read
+      id-token: write
     environment: npm
 
     steps:
@@ -148,11 +224,14 @@ jobs:
       - name: Set up Node
         uses: actions/setup-node@v4
         with:
-          node-version: "20"
+          node-version: "24"
           registry-url: "https://registry.npmjs.org"
 
+      - name: Upgrade npm
+        run: npm install -g npm@latest
+
       - name: Publish npm package
         working-directory: packages/npm/akernel
         env:
           NODE_AUTH_TOKEN: ${{ secrets.NPM_TOKEN }}
-        run: npm publish --access public
+        run: npm publish --access public --provenance

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/CHANGELOG.md

@@ -8,6 +8,21 @@ The project follows a pragmatic pre-1.0 changelog: breaking changes may occur, b
 
 No changes yet.
 
+## 0.1.2 - 2026-05-12
+
+### Changed
+
+- Renamed the prepared npm launcher scope from `@context-kernel/akernel` to `@context-akernel/akernel`.
+
+## 0.1.1 - 2026-05-12
+
+### Changed
+
+- Documented the `akernel` naming convention as Agent Kernel across README, PyPI metadata, and npm launcher docs.
+- Upgraded npm release guidance and workflow support for trusted publishing, provenance, and npm-only manual publishes.
+- Added GitHub Release notes and release workflow support for automated or manual release page creation.
+- Updated README installation wording to reflect the live PyPI package and the pending npm launcher publication.
+
 ## 0.1.0 - 2026-05-12
 
 ### Added

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: akernel-runtime
-Version: 0.1.0
-Summary: A CLI-first context-native agent runtime prototype.
+Version: 0.1.2
+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
@@ -33,6 +33,20 @@ Most agent systems treat the prompt as the runtime. Context Kernel treats the pr
 
 The project is currently an alpha CLI release. It is ready for local experimentation, benchmark-driven iteration, and early contributor feedback.
 
+## Naming
+
+`akernel` means **Agent Kernel**. The project name is Context Kernel because the runtime focuses on context assembly, memory, policy, skills, and token budgets; the executable is `akernel` because users invoke the agent-facing kernel directly from the terminal.
+
+The shorter `kernel` command is intentionally avoided because it is too broad and already carries strong meanings in operating systems, Jupyter, and other AI projects. `akernel` keeps the kernel idea while giving the CLI a distinct, searchable identity.
+
+Package and command names map to the same idea:
+
+- GitHub repository: `context-kernel`
+- Python distribution: `akernel-runtime`
+- Python import package: `context_kernel`
+- CLI command: `akernel`
+- npm launcher: `@context-akernel/akernel`
+
 ## Why This Exists
 
 Modern agent workflows often become expensive for reasons that are hard to see:
@@ -98,9 +112,9 @@ akernel --help
 
 Python 3.10 or newer is required.
 
-### Remote Install
+### PyPI Install
 
-After the package is published, users can install from PyPI:
+The Python runtime is published on PyPI as `akernel-runtime`:
 
 ```powershell
 python -m pip install --user akernel-runtime
@@ -108,6 +122,8 @@ akernel setup
 akernel
 ```
 
+### GitHub Remote Install
+
 Windows users can also install directly from GitHub:
 
 ```powershell
@@ -116,15 +132,17 @@ akernel setup
 akernel
 ```
 
-The npm launcher provides a Node-style entrypoint and can bootstrap the Python package if it is missing:
+### npm Launcher
+
+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 before the PyPI package is available.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/README.md

@@ -6,6 +6,20 @@ Most agent systems treat the prompt as the runtime. Context Kernel treats the pr
 
 The project is currently an alpha CLI release. It is ready for local experimentation, benchmark-driven iteration, and early contributor feedback.
 
+## Naming
+
+`akernel` means **Agent Kernel**. The project name is Context Kernel because the runtime focuses on context assembly, memory, policy, skills, and token budgets; the executable is `akernel` because users invoke the agent-facing kernel directly from the terminal.
+
+The shorter `kernel` command is intentionally avoided because it is too broad and already carries strong meanings in operating systems, Jupyter, and other AI projects. `akernel` keeps the kernel idea while giving the CLI a distinct, searchable identity.
+
+Package and command names map to the same idea:
+
+- GitHub repository: `context-kernel`
+- Python distribution: `akernel-runtime`
+- Python import package: `context_kernel`
+- CLI command: `akernel`
+- npm launcher: `@context-akernel/akernel`
+
 ## Why This Exists
 
 Modern agent workflows often become expensive for reasons that are hard to see:
@@ -71,9 +85,9 @@ akernel --help
 
 Python 3.10 or newer is required.
 
-### Remote Install
+### PyPI Install
 
-After the package is published, users can install from PyPI:
+The Python runtime is published on PyPI as `akernel-runtime`:
 
 ```powershell
 python -m pip install --user akernel-runtime
@@ -81,6 +95,8 @@ akernel setup
 akernel
 ```
 
+### GitHub Remote Install
+
 Windows users can also install directly from GitHub:
 
 ```powershell
@@ -89,15 +105,17 @@ akernel setup
 akernel
 ```
 
-The npm launcher provides a Node-style entrypoint and can bootstrap the Python package if it is missing:
+### npm Launcher
+
+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 before the PyPI package is available.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/docs/07-release-and-ci.md

@@ -102,7 +102,7 @@ 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
 ```

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/docs/11-publishing-setup.md

@@ -48,20 +48,36 @@ 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 first-release path:
+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 an npm automation or granular access token with publish permission.
-3. In GitHub repository settings, add an Actions secret named `NPM_TOKEN`.
-4. In GitHub repository settings, add an Actions variable named `PUBLISH_NPM` with value `true`.
-5. Keep the package public with `npm publish --access public`, which is already what the release workflow uses.
+2. Create the package or configure a pending trusted publisher for `@context-akernel/akernel`.
+3. Use these trusted publisher values:
 
-Alternative future path: npm Trusted Publishing can remove the long-lived npm token once the package and publisher relationship are configured in npm.
+| Field | Value |
+| --- | --- |
+| Package | `@context-akernel/akernel` |
+| Owner | `huanxin0825-ctrl` |
+| Repository name | `context-kernel` |
+| Workflow filename | `release.yml` |
+| Environment name | `npm` |
+
+Then create the matching GitHub environment:
+
+1. Open GitHub repository settings.
+2. Go to `Environments`.
+3. Create an environment named `npm`.
+4. Optional but recommended: add required reviewers so publication requires manual approval.
+5. In GitHub repository settings, add an Actions variable named `PUBLISH_NPM` with value `true`.
+
+No GitHub secret is needed for npm when Trusted Publishing is configured.
+
+Fallback path: if npm Trusted Publishing is unavailable for the account or package, create an npm automation or granular access token with publish permission, add it as an Actions secret named `NPM_TOKEN`, keep `PUBLISH_NPM=true`, and the same workflow can publish with the token. Do not paste the token into chat, issues, pull requests, or docs.
 
 ## Local Release Check
 
@@ -85,13 +101,33 @@ git push origin v0.1.0
 
 The GitHub release workflow will build artifacts, generate benchmark evidence, publish to PyPI through Trusted Publishing, and publish the npm launcher if `NPM_TOKEN` and `PUBLISH_NPM=true` are configured.
 
+To publish only npm for an already-published Python version, open the `Release` workflow manually and run it with:
+
+```text
+publish=true
+target=npm
+```
+
+This avoids trying to republish the same PyPI version.
+
+To create or refresh only the GitHub Release page for an existing tag, open the `Release` workflow manually and run it with:
+
+```text
+publish=true
+target=github-release
+release_tag=v0.1.0
+```
+
+Release notes are read from `.github/release-notes/<tag>.md`.
+
 ## What To Send Back
 
 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.
-- If publishing npm now: `NPM_TOKEN` secret exists and `PUBLISH_NPM=true` variable exists.
+- 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.
 
 Do not send API tokens or passwords.

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/packages/npm/akernel/README.md

@@ -1,9 +1,11 @@
-# @context-kernel/akernel
+# @context-akernel/akernel
 
-This package is a small npm launcher wrapper for the Python `context-kernel` CLI.
+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
 ```

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/packages/npm/akernel/package.json

@@ -1,6 +1,6 @@
 {
-  "name": "@context-kernel/akernel",
-  "version": "0.1.0",
+  "name": "@context-akernel/akernel",
+  "version": "0.1.2",
   "description": "npm launcher wrapper for the Context Kernel akernel CLI.",
   "license": "Apache-2.0",
   "homepage": "https://github.com/huanxin0825-ctrl/context-kernel#readme",
@@ -22,6 +22,10 @@
   "bin": {
     "akernel": "bin/akernel.js"
   },
+  "publishConfig": {
+    "access": "public",
+    "provenance": true
+  },
   "files": [
     "bin",
     "README.md"

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/pyproject.toml

@@ -4,8 +4,8 @@ build-backend = "setuptools.build_meta"
 
 [project]
 name = "akernel-runtime"
-version = "0.1.0"
-description = "A CLI-first context-native agent runtime prototype."
+version = "0.1.2"
+description = "Agent Kernel: a CLI-first context-native agent runtime prototype."
 readme = "README.md"
 license = "Apache-2.0"
 license-files = ["LICENSE", "NOTICE"]

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/src/akernel_runtime.egg-info/PKG-INFO

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: akernel-runtime
-Version: 0.1.0
-Summary: A CLI-first context-native agent runtime prototype.
+Version: 0.1.2
+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
@@ -33,6 +33,20 @@ Most agent systems treat the prompt as the runtime. Context Kernel treats the pr
 
 The project is currently an alpha CLI release. It is ready for local experimentation, benchmark-driven iteration, and early contributor feedback.
 
+## Naming
+
+`akernel` means **Agent Kernel**. The project name is Context Kernel because the runtime focuses on context assembly, memory, policy, skills, and token budgets; the executable is `akernel` because users invoke the agent-facing kernel directly from the terminal.
+
+The shorter `kernel` command is intentionally avoided because it is too broad and already carries strong meanings in operating systems, Jupyter, and other AI projects. `akernel` keeps the kernel idea while giving the CLI a distinct, searchable identity.
+
+Package and command names map to the same idea:
+
+- GitHub repository: `context-kernel`
+- Python distribution: `akernel-runtime`
+- Python import package: `context_kernel`
+- CLI command: `akernel`
+- npm launcher: `@context-akernel/akernel`
+
 ## Why This Exists
 
 Modern agent workflows often become expensive for reasons that are hard to see:
@@ -98,9 +112,9 @@ akernel --help
 
 Python 3.10 or newer is required.
 
-### Remote Install
+### PyPI Install
 
-After the package is published, users can install from PyPI:
+The Python runtime is published on PyPI as `akernel-runtime`:
 
 ```powershell
 python -m pip install --user akernel-runtime
@@ -108,6 +122,8 @@ akernel setup
 akernel
 ```
 
+### GitHub Remote Install
+
 Windows users can also install directly from GitHub:
 
 ```powershell
@@ -116,15 +132,17 @@ akernel setup
 akernel
 ```
 
-The npm launcher provides a Node-style entrypoint and can bootstrap the Python package if it is missing:
+### npm Launcher
+
+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 before the PyPI package is available.
+Set `AKERNEL_PIP_SOURCE=git+https://github.com/huanxin0825-ctrl/context-kernel.git` to make the npm launcher bootstrap from GitHub instead of PyPI.
 
 ## Quick Start
 

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/src/akernel_runtime.egg-info/SOURCES.txt

@@ -15,6 +15,9 @@ wake.ps1
 .github/pull_request_template.md
 .github/ISSUE_TEMPLATE/bug_report.md
 .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/workflows/ci.yml
 .github/workflows/release.yml
 docs/00-vision.md

{akernel_runtime-0.1.0 → akernel_runtime-0.1.2}/src/context_kernel/__init__.py

@@ -1,4 +1,3 @@
 """Context Kernel CLI-first agent runtime prototype."""
 
-__version__ = "0.1.0"
-
+__version__ = "0.1.2"