ai-kit-python 1.4.2__tar.gz → 1.4.3__tar.gz

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/.agents/skills/project-continuity/SKILL.md

@@ -21,14 +21,14 @@ For measurement-led changes, test schema 1/2/3 compatibility, fixed A/B controls
 Resolve temporary fixture roots before deriving paths used by guards, assertions, or injected failures. Test equivalent path spellings; keep cleanup bound to original disposable directories. [Windows CI regression](../../../docs/WINDOWS_CI_FIX.md) records the relevant scenario.
 For reference upgrades, check the actual published tree and old paths left by overlays. Compatibility pointers link to canonical owners; never hide broken legacy links from the checker.
 When editing onboarding docs, verify examples against the actual CLI/defaults and preserve links to policy owners. Keep installation, native discovery, and measured execution claims distinct. For [OpenRouter documentation](../../../README.md#working-with-openrouter), recheck primary API/cache/usage docs; distinguish shipped context manifests from proposed request assembly/runtime, prompt caching from response reuse, and observed usage from assumed savings. Root README and Docker Hub Overview have no size quota; retain scoped instruction budgets and normal link/language checks.
-For [PyPI releases](../../../docs/PYPI.md), verify wheel/sdist metadata, VERSION, licenses, description, resources and private/path exclusions; build the wheel from sdist and smoke-install offline. Quote complete Twine globs; report OS gaps. A JSON 404 does not prove name eligibility; verify publisher registration. Test identity guards without uploads; preserve CI names and existing release tags. Use a new patch when an old tag predates publication support. Trusted Publishing stays manual/build-only by default, with exact version/tag/repository gates, OIDC only in upload jobs and validated same-run artifacts; setup and publication are separate. Keep MCP posture separate from live client activation.
+For [PyPI releases](../../../docs/PYPI.md), verify metadata, VERSION, licenses, description, resources and private/path exclusions; build the wheel from sdist and smoke-install offline. Quote Twine globs; report OS gaps. A JSON 404 does not prove name eligibility. Test release/manual identity guards without uploads; preserve CI names and old tags. Published stable releases prepare PyPI artifacts; manual runs default to validation. Require exact version/tag/repository gates, owner approval and future tag coverage; agents must not approve deployments. OIDC belongs only in upload jobs consuming validated same-run artifacts. Keep setup, upload and live MCP activation separate.
 For repository administration or changes to existing required CI names, consult [repository maintenance](../../../CONTRIBUTING.md#repository-maintenance), verify live protection and emitted names, and keep required checks aligned. New local jobs establish no hosted result or required-check update. Remote changes need explicit authorization; Core governs commits/pushes.
 For every task assess [Docker image impact](../../../docs/DOCKER.md#change-impact-and-image-refresh), including packaged instructions and defaults. Follow canonical [image freshness](../../../template/ai-kit/CONTAINERS.md#image-freshness); rebuild/test affected final sources as ai-kit:dev or record why no rebuild is needed. For the image, verify actual client/daemon, pinned build inputs, VERSION/label identity, closed context, wheel resources, non-root bind permissions, read-only/offline preview and apply, preservation, conflicts, rerun and SIGTERM. Validate the Job schema; distinguish cluster/runtime coverage. Record test cache/volume ownership and size; follow canonical cleanup without shared-builder pruning. Keep image publication separate.
 For [dialogue memory](../../../docs/DIALOGUE_MEMORY.md), test all supported imports, selected ChatGPT branches, omissions, untrusted roles, pending prose, explicit keyed conflicts/resolutions, source-bound review, immutable reruns, both exports and byte limits. Exercise linked/blocked paths, private/team upgrade preservation, Git/build/package exclusions and installed CLI execution. Do not infer semantic agreement from no keyed conflicts or claim live sync/upload from local export. Preserve raw sources and default project context.
 For optional upstream skills, follow [security-audit](../../../docs/SECURITY_AUDIT.md) and [Strix integration](../../../docs/STRIX.md): preserve pinned bytes/license and newline attributes, verify bounded tree coverage/digests and nested-path aliases, explicit-only metadata, absent default/preset payloads, independent persistent choices, local adaptations/conflicts, links, visibility and wheel resources. Exempt only verified external examples from authored model/language/budget checks. Keep installation separate from audits/runtime setup; report unsupported validators. For Strix, check writable copy isolation, explicit full/diff scope, budget/data destination and no implicit cloud fallback; integration tests must start no scan, model or container.
 For [Context7](../../../docs/CONTEXT7.md), check opt-in skill/registry selection, independent persistence, source/native copies, local conflicts and unchanged native MCP configuration. Keep normal skill discovery, version-aware sanitized queries and remote activation separate. Recheck client schemas/authentication against primary docs; a source revision does not pin the hosted service.
 For [Web Design](../../../docs/WEB_DESIGN.md), check whole-module default absence, multi-entry skill selection, independent persistence, created-once project documents, native copies/retirement, local conflicts and linked/blocked paths. Exercise workflow context scope, required design memory above budgets, plain HTML without assumed stack facts, private raw output/team visibility and offline wheel resources. Keep TypeUI/SkillUI setup and real browser/Laravel acceptance separate from installer evidence; adopt external guidance only within the selected stack/visual system.
-For an explicitly requested release version, update VERSION, the root changelog, README release pointer, WIKI and maintainer context together; keep release history out of project templates. Recheck CLI version, kit validation and wheel metadata/install; build in an isolated source copy and exercise preservation across the prior-version baseline. State which behavioral results preceded release labeling; publication/tagging remain separate actions under Core. In release notes, distinguish Web Design instructions from external tools and generated-site acceptance, Context7 setup from installation, and OpenRouter guidance from a live adapter; verify security examples against pinned contracts.
+For a requested release, synchronize VERSION, root changelog, README, WIKI and maintainer context; keep kit history out of templates. Recheck CLI/version, kit, isolated archives, offline installation and prior-version upgrade preservation. Distinguish checks before/after labeling. Follow [the owner-approved release path](../../../docs/V1_4_3.md): preserve tags, wait for hosted build checks and report pending human approval; never approve PyPI for the owner. Git authorization follows Core. Release notes must distinguish installed guidance from external tools, live client/model setup and generated-site acceptance; verify security examples against pinned contracts.
 For every Docker image release, follow the [Docker Hub checklist](../../../CONTRIBUTING.md#docker-hub-releases) and update the complete [Overview](../../../docs/DOCKER_HUB_OVERVIEW.md); synchronize version/features/examples before building and verified publication identity afterward.
 For the current Docker/privacy release, follow [v1.4.1 preparation](../../../docs/V1_4_1.md); keep local image identity distinct from a registry digest and source-bound human review distinct from automatic conversation synchronization. After explicitly authorized publication, read back the registry digest, platform and version/configuration; preserve the prepared image and record later publication-only documentation separately. Do not assign additional tags implicitly.
 Do not bootstrap the reference repository as an application or imply native/runtime checks passed from static validation.

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/.github/workflows/publish-pypi.yml

@@ -1,6 +1,8 @@
 name: Prepare or publish Python package
 
 on:
+  release:
+    types: [published]
   workflow_dispatch:
     inputs:
       destination:
@@ -19,11 +21,15 @@ permissions:
   contents: read
 
 concurrency:
-  group: python-package-${{ github.ref }}-${{ inputs.destination }}
+  group: python-package-${{ github.ref }}-${{ github.event_name == 'release' && 'pypi' || inputs.destination }}
   cancel-in-progress: false
 
 jobs:
   build:
+    if: >-
+      github.event_name == 'workflow_dispatch' ||
+      (github.event_name == 'release' && github.event.action == 'published' &&
+       !github.event.release.draft && !github.event.release.prerelease)
     runs-on: ubuntu-latest
     steps:
       - uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7
@@ -32,13 +38,10 @@ jobs:
       - uses: actions/setup-python@5fda3b95a4ea91299a34e894583c3862153e4b97 # v7
         with:
           python-version: '3.13'
-      - name: Verify explicit release identity before building
-        env:
-          RELEASE_VERSION: ${{ inputs.version }}
-          DESTINATION: ${{ inputs.destination }}
+      - name: Verify release or manual event identity before building
         run: >-
           python scripts/check_distribution.py identity
-          --expected-version "$RELEASE_VERSION" --destination "$DESTINATION"
+          --event-name "$GITHUB_EVENT_NAME" --event-path "$GITHUB_EVENT_PATH"
           --ref "$GITHUB_REF" --repository "$GITHUB_REPOSITORY"
       - name: Validate sources and behavior
         run: |
@@ -65,7 +68,10 @@ jobs:
 
   testpypi:
     needs: build
-    if: inputs.destination == 'testpypi' && github.repository == 'tigusigalpa/ai-kit' && startsWith(github.ref, 'refs/tags/v')
+    if: >-
+      needs.build.result == 'success' && github.event_name == 'workflow_dispatch' &&
+      inputs.destination == 'testpypi' && github.repository == 'tigusigalpa/ai-kit' &&
+      startsWith(github.ref, 'refs/tags/v')
     runs-on: ubuntu-latest
     environment:
       name: testpypi
@@ -87,7 +93,10 @@ jobs:
 
   pypi:
     needs: build
-    if: inputs.destination == 'pypi' && github.repository == 'tigusigalpa/ai-kit' && startsWith(github.ref, 'refs/tags/v')
+    if: >-
+      needs.build.result == 'success' &&
+      (github.event_name == 'release' || inputs.destination == 'pypi') &&
+      github.repository == 'tigusigalpa/ai-kit' && startsWith(github.ref, 'refs/tags/v')
     runs-on: ubuntu-latest
     environment:
       name: pypi

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/CHANGELOG.md

@@ -1,9 +1,16 @@
 # AI-KIT changelog
 
+## v1.4.3 (2026-10-16)
+
+- Added a live PyPI version badge to README.
+- Added stable GitHub Release publication preparation, event/version/repository guards and regression tests; manual validation stays the default. PyPI upload waits for the owner. The live tag policy now accepts v* with reviewer protections preserved. [Procedure](docs/PYPI.md#release-to-pypi-with-owner-approval). Archived v0.13.0 text intact to retain the changelog budget.
+- Added fifteen event regression tests. Before release labeling, 32 hosted CI checks and build-only workflow verification passed; kit checks, 368 packaged Linux tests (two platform skips), archive/privacy/Twine/offline wheel checks and Docker smoke also passed. [Release verification](docs/V1_4_3.md).
+- Verified 1.4.3 CLI/archive/image identity, offline packaging, Docker smoke, 368 Linux tests and preserved private/team upgrades from v1.4.2.
+
 ## v1.4.2 (2026-10-16)
 
 - Verified kit/archive/offline installation, 351 Linux tests (two skips), 23 Windows CLI/archive tests and Docker smoke. [Evidence](docs/V1_4_2.md).
-- Prepared `ai-kit-python` 1.4.2; PyPI publisher/GitHub pypi environment verified. Preserve v1.4.1 Git/Docker. [Status](docs/V1_4_2.md).
+- Published `ai-kit-python` 1.4.2 with verified PyPI hashes and installation. Preserved v1.4.1 Git/Docker; [evidence](docs/V1_4_2.md).
 - Fixed quoted Twine wildcards for Windows CI.
 - Added PyPI metadata, a portable [description](docs/PYPI_DESCRIPTION.md), README guidance and a [release procedure](docs/PYPI.md). Wheel/sdist checks cover metadata, licenses, resources, private files, offline installation and publication identity. Manual Trusted Publishing defaults to validation, requires exact version/tag/repository, and gives OIDC only to upload jobs consuming tested artifacts. Required CI names stay unchanged.
 - Isolated builds inject synthetic private probes; archives exclude private drafts and credential filenames. Added tested `aikit --version`; published Docker 1.4.1 examples use its existing `--help`. Added a README Docker Hub badge.
@@ -46,10 +53,7 @@
 
 ## v0.13.0 (2026-10-11)
 
-- Added Rust, .NET, Java (Maven/Gradle), and Terraform/Helm stack profiles with evidence-based per-module detection: Cargo.toml (rust-version, cargo test/build/clippy), *.csproj/*.fsproj/*.vbproj and global.json (TargetFramework, dotnet test/build), pom.xml/mvnw/build.gradle(.kts)/gradlew (language level, wrapper-aware commands), and .tf files or Chart.yaml (fmt/validate, helm lint). Drafts remain suggestions until bootstrap confirms them.
-- Added rust-work, dotnet-work, java-work, and infra-work skills to the registry; Claude native copies install with the claude agent selection.
-- Benchmark packs accept the new stack names; README, SKILL.md, and WIKI profile lists updated.
-- Verified locally (Windows/Python 3.14.6): 254 tests ran, all passed, 1 runtime skip; kit validation returned zero errors and zero warnings; Python 3.10 grammar verified; end-to-end smoke detected RUST/INFRA with drafted context and installed source/native skills. Real applications of the new stacks remain untrialed.
+[Archived release entry](docs/history/v0.13.0-changelog.md#v0130-2026-10-11).
 
 ## v0.12.0 (2026-10-11)
 

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/CONTRIBUTING.md

@@ -30,7 +30,7 @@ The root README and Docker Hub Overview are user documentation without a size qu
 
 Follow [PyPI preparation and release](docs/PYPI.md) for every package release. Synchronize VERSION, pyproject metadata, [description](docs/PYPI_DESCRIPTION.md) and README; verify license/resource inclusion and local-file exclusions in both sdist and wheel, build the wheel from sdist, run strict Twine checks and offline fresh-venv smoke. Preserve existing CI matrix/job names. Refresh the image when packaging changes affect it.
 
-Trusted Publishing remains manual and build-only by default. Registry uploads require the matching version/tag, canonical repository and the separately configured registry environment/publisher. Build tests have no OIDC permission; upload jobs consume only validated same-run artifacts. Record local, hosted and registry results separately. No upload, publisher/account setup or Git operation is authorized by preparation alone.
+A published stable GitHub Release starts PyPI preparation; manual dispatch defaults to build-only validation. Uploads require matching VERSION/tag, the canonical repository, a configured environment/publisher and the owner's human approval. Agents must not approve or bypass a pending deployment on the owner's behalf. Keep environment reviewer protections when allowing future `v*` tags; validate canonical stable versions separately. Build tests have no OIDC permission; upload jobs consume only validated same-run artifacts. Record local, hosted and registry results separately. Preparation alone authorizes no upload, account setup or Git operation.
 
 ## Repository maintenance
 

{ai_kit_python-1.4.2/ai_kit_python.egg-info → ai_kit_python-1.4.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-kit-python
-Version: 1.4.2
+Version: 1.4.3
 Summary: Offline installer and portable instructions that give AI coding agents project memory, stack rules, guardrails, and adaptive model routing.
 Author: Igor Sazonov
 License-Expression: MIT AND Apache-2.0
@@ -121,6 +121,8 @@ The distribution excludes root maintainer AGENTS.md, PROJECT_CONTEXT.md and WIKI
 
 A separate [Docker image](https://hub.docker.com/r/tigusigalpa/ai-kit) packages the CLI for container use.
 
+Package releases follow GitHub Release, automated checks and owner approval before PyPI upload through Trusted Publishing. Future stable tags must match VERSION; manual runs default to validation. See the [release procedure](https://github.com/tigusigalpa/ai-kit/blob/main/docs/PYPI.md#release-to-pypi-with-owner-approval).
+
 ## Documentation and license
 
 - [Repository and full README](https://github.com/tigusigalpa/ai-kit)

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/README.md

@@ -6,9 +6,10 @@
 
 AI-KIT gives your coding agents persistent project memory, expert stack rules, **Kubernetes-ready** containers, **adaptive model routing**, and native configuration for **11 AI clients**. Add **Cloudflare security-audit** for structured security review and **Strix** for scoped pentesting workflows. One offline installer, zero installer dependencies, changes previewed before you apply them.
 
-**[v1.4.2](CHANGELOG.md#v142-2026-10-16)** prepares the first PyPI release with verified source/wheel packages, a version command and manual Trusted Publishing. Publication is pending; [release status and verification](docs/V1_4_2.md) distinguish local checks from registry availability. The published Docker Hub image remains **1.4.1**, with Docker freshness rules, private-file exclusions, shared dialogue memory and all optional modules.
+**[v1.4.3](CHANGELOG.md#v143-2026-10-16)** adds **GitHub Release → checks → your approval → PyPI**, future release-tag support, fifteen event regression tests and a live PyPI version badge. [Release verification](docs/V1_4_3.md) separates GitHub release preparation from registry publication. The latest verified PyPI package is [ai-kit-python 1.4.2](https://pypi.org/project/ai-kit-python/1.4.2/); the published Docker Hub image remains **1.4.1**. Shared dialogue memory and all optional modules remain available.
 
 [![Python 3.10+](https://img.shields.io/badge/python-3.10%2B-3776AB?logo=python&logoColor=white)](#install)
+[![PyPI version](https://img.shields.io/pypi/v/ai-kit-python?logo=pypi&logoColor=white)](https://pypi.org/project/ai-kit-python/)
 [![Dependencies: none](https://img.shields.io/badge/dependencies-none-2ea44f)](scripts/install.py)
 [![AI clients: 11](https://img.shields.io/badge/AI%20clients-11-7c3aed)](#-works-with-your-ai-clients)
 [![Docker Hub](https://img.shields.io/badge/Docker%20Hub-ai--kit-2496ED?logo=docker&logoColor=white)](https://hub.docker.com/r/tigusigalpa/ai-kit)
@@ -227,19 +228,19 @@ Every command also runs through one CLI: `python aikit_cli.py install|doctor|rou
 
 ### Packaged CLI and PyPI status
 
-AI-KIT includes a portable Python package and a manual Trusted Publishing workflow. **PyPI/TestPyPI publication is prepared, not performed.** The package name is `ai-kit-python`, the executable is `aikit`, and Python 3.10+ is required. PyPI rejected the initial `ai-kit` name as too similar to an existing project; registry activation must finish before the first upload.
+**AI-KIT 1.4.2 is available on [PyPI](https://pypi.org/project/ai-kit-python/1.4.2/).** Install package `ai-kit-python` and run command `aikit`; Python 3.10+ is required with no mandatory runtime dependencies. Publication uses GitHub Trusted Publishing. Uploaded wheel/source hashes and installation directly from PyPI were verified. TestPyPI was not used.
 
-From a reviewed AI-KIT checkout, you can install it now inside a virtual environment:
+Install into a virtual environment:
 
 ~~~powershell
 $cliEnv = Join-Path $env:LOCALAPPDATA 'AI-KIT\venv'
 python -m venv "$cliEnv"
 & "$cliEnv\Scripts\Activate.ps1"
-python -m pip install .
+python -m pip install ai-kit-python
 aikit --version
 ~~~
 
-After a verified PyPI release under that name, installation becomes `pipx install ai-kit-python`, or `python -m pip install ai-kit-python` inside a virtual environment. Updating uses `pipx upgrade ai-kit-python` or `python -m pip install --upgrade ai-kit-python`; installed application instructions are updated separately through preview/apply.
+For an isolated CLI, use `pipx install ai-kit-python`. To install a reviewed source checkout instead, run `python -m pip install .` there. Updating uses `pipx upgrade ai-kit-python` or `python -m pip install --upgrade ai-kit-python`; installed application instructions are updated separately through preview/apply.
 
 ~~~powershell
 aikit install "C:\Projects\my-app" --agent codex --mode private
@@ -249,7 +250,22 @@ aikit doctor "C:\Projects\my-app"
 
 Then open that application in your client and run its bootstrap workflow. The CLI bundles templates and optional integration resources, uses no runtime third-party dependencies and preserves local documents/conflicts. [PyPI description](docs/PYPI_DESCRIPTION.md) contains portable publication copy; the [release guide](docs/PYPI.md) covers local builds, archive/privacy checks, TestPyPI, OIDC publisher fields and later publication.
 
-For maintainers, [publish-pypi.yml](.github/workflows/publish-pypi.yml) runs only by manual dispatch and defaults to build-only `validate`. Upload jobs require an explicit registry, exact version confirmation, a matching release tag and the canonical repository. They use separate `testpypi`/`pypi` environments and receive OIDC permission only in those jobs. Account/environment setup and any actual upload remain separate authorized operations. No permanent registry token is needed.
+For maintainers, [publish-pypi.yml](.github/workflows/publish-pypi.yml) supports **GitHub Release → checks → your approval → PyPI**. Publishing a stable GitHub Release starts production preparation; the upload waits for your review of environment `pypi`. Manual dispatch remains available and defaults to build-only `validate`. No permanent registry token is needed.
+
+#### Publish future releases to PyPI
+
+1. Prepare the new version through the normal reviewed Git workflow. For example, put `1.5.0` in `VERSION`, update release documentation and complete the kit/package checks. Assess Docker impact through the existing image-refresh procedure. The tag's source must contain the updated release workflow and event guard.
+2. Create a new tag such as `v1.5.0` at that prepared commit. **The tag and its committed `VERSION` must match exactly.** Preserve previous tags and published versions.
+3. On GitHub, create and publish a normal Release for that tag. `release: published` starts the workflow automatically. Saving a draft, pushing a tag alone, editing an existing Release or marking it as a prerelease does not request automatic production publication.
+4. Open **Actions → Prepare or publish Python package**. Its `build` job checks the release identity, runs kit validation and behavioral tests, builds a source archive and wheel, validates metadata/resources/privacy and the description, then smoke-installs the wheel. A failed check prevents the upload job from proceeding.
+5. After checks pass, the `pypi` job waits at **Review deployments**. Inspect the tag, commit and successful checks, select environment **pypi**, and click **Approve and deploy**. Required reviewer: repository owner `tigusigalpa`. **This confirmation is a human step; agents must not approve or bypass it on your behalf.** For solo maintenance the owner may approve a run they initiated.
+6. GitHub exchanges its OIDC identity for a short-lived PyPI credential and uploads only the same-run validated artifacts. The upload job builds no code. Verify the new version on [PyPI](https://pypi.org/project/ai-kit-python/), compare its file hashes with the run artifacts, and check installation in a fresh environment. The README PyPI badge then follows the published version automatically.
+
+The live `pypi` deployment policy accepts **tags `v*`**, so future versions do not need a new allowlist entry. Branches are excluded. The event guard separately requires a canonical stable tag of the form `vMAJOR.MINOR.PATCH`, the canonical repository, a published non-draft/non-prerelease Release and matching `VERSION`. Tests and your approval remain required for each production run.
+
+For a manual run, choose **Run workflow**, select the versioned tag, set `destination=pypi`, and type the exact version in `version`. Uploads use the same approval gate. `destination=validate` only builds and tests; `testpypi` is an explicit separate registry with its own environment/publisher setup. Prerelease trials can use that manual route. Republishing the same PyPI version fails rather than replacing or silently skipping files.
+
+The Release path is included in **v1.4.3 and later tagged source**. Existing `v1.4.2` stays unchanged. The complete [release procedure](docs/PYPI.md#release-to-pypi-with-owner-approval) includes activation, recovery and configuration verification. Each stable release still needs your human approval before PyPI upload.
 
 ## Run AI-KIT with Docker
 

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/SKILL.md

@@ -86,7 +86,7 @@ CI and optional integrations stay outside presets. Read the audit, Strix, Contex
 
 ## Unified CLI
 
-`python aikit_cli.py --help` lists commands; pip exposes `aikit`. [Dialogue memory](docs/DIALOGUE_MEMORY.md) imports/merges two dialogues and exports reviewed ChatGPT/OpenRouter references. [Docker](README.md#run-ai-kit-with-docker) mounts an application. [PyPI](docs/PYPI.md) covers package validation and manual Trusted Publishing; preparation uploads nothing. Standalone scripts and Makefile also work.
+`python aikit_cli.py --help` lists commands; pip exposes `aikit`. [Dialogue memory](docs/DIALOGUE_MEMORY.md) imports/merges two dialogues and exports reviewed ChatGPT/OpenRouter references. [Docker](README.md#run-ai-kit-with-docker) mounts an application. [PyPI](docs/PYPI.md) covers checks and owner-approved release publishing; preparation uploads nothing. Standalone scripts and Makefile also work.
 
 ## Maintaining AI-KIT itself
 

ai_kit_python-1.4.3/VERSION

@@ -0,0 +1 @@
+1.4.3

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3/ai_kit_python.egg-info}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: ai-kit-python
-Version: 1.4.2
+Version: 1.4.3
 Summary: Offline installer and portable instructions that give AI coding agents project memory, stack rules, guardrails, and adaptive model routing.
 Author: Igor Sazonov
 License-Expression: MIT AND Apache-2.0
@@ -121,6 +121,8 @@ The distribution excludes root maintainer AGENTS.md, PROJECT_CONTEXT.md and WIKI
 
 A separate [Docker image](https://hub.docker.com/r/tigusigalpa/ai-kit) packages the CLI for container use.
 
+Package releases follow GitHub Release, automated checks and owner approval before PyPI upload through Trusted Publishing. Future stable tags must match VERSION; manual runs default to validation. See the [release procedure](https://github.com/tigusigalpa/ai-kit/blob/main/docs/PYPI.md#release-to-pypi-with-owner-approval).
+
 ## Documentation and license
 
 - [Repository and full README](https://github.com/tigusigalpa/ai-kit)

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/ai_kit_python.egg-info/SOURCES.txt

@@ -79,6 +79,7 @@ pyproject.toml
 ./docs/V1_4_0.md
 ./docs/V1_4_1.md
 ./docs/V1_4_2.md
+./docs/V1_4_3.md
 ./docs/WEB_DESIGN.md
 ./docs/WINDOWS_CI_FIX.md
 ./docs/adr/0000-template.md
@@ -99,6 +100,7 @@ pyproject.toml
 ./docs/history/original-bundle-checks.md
 ./docs/history/v0.1-changelog.txt
 ./docs/history/v0.10-changelog.md
+./docs/history/v0.13.0-changelog.md
 ./docs/history/v0.2-changelog.md
 ./docs/history/v0.3-changelog.md
 ./docs/history/v0.4-changelog.md
@@ -262,6 +264,7 @@ pyproject.toml
 ./tests/test_metrics.py
 ./tests/test_native.py
 ./tests/test_onboarding.py
+./tests/test_pypi_events.py
 ./tests/test_router.py
 ./tests/test_security_audit.py
 ./tests/test_strix.py
@@ -316,6 +319,7 @@ docs/V0_6_4.md
 docs/V1_4_0.md
 docs/V1_4_1.md
 docs/V1_4_2.md
+docs/V1_4_3.md
 docs/WEB_DESIGN.md
 docs/WINDOWS_CI_FIX.md
 docs/adr/0000-template.md
@@ -336,6 +340,7 @@ docs/adr/0014-local-dialogue-memory.md
 docs/history/original-bundle-checks.md
 docs/history/v0.1-changelog.txt
 docs/history/v0.10-changelog.md
+docs/history/v0.13.0-changelog.md
 docs/history/v0.2-changelog.md
 docs/history/v0.3-changelog.md
 docs/history/v0.4-changelog.md
@@ -518,6 +523,7 @@ tests/test_memory.py
 tests/test_metrics.py
 tests/test_native.py
 tests/test_onboarding.py
+tests/test_pypi_events.py
 tests/test_router.py
 tests/test_security_audit.py
 tests/test_strix.py

ai_kit_python-1.4.3/docs/PYPI.md

@@ -0,0 +1,103 @@
+# PyPI package preparation and release
+
+## Status and package identity
+
+Version [1.4.3](V1_4_3.md) includes the owner-approved Release path; publication requires human approval. Release [1.4.2 is published on PyPI](https://pypi.org/project/ai-kit-python/1.4.2/); [evidence](V1_4_2.md) records its workflow, uploaded hashes and clean registry installation. Trusted Publishing uses repository `tigusigalpa/ai-kit`, workflow `publish-pypi.yml`, environment `pypi`. On 2026-10-16 that environment was extended to future `v*` tags with owner review preserved. VERSION is the version source; distribution `ai-kit-python`, import package and executable `aikit`, Python 3.10+, no runtime dependencies. TestPyPI remains unconfigured.
+
+PyPI rejected `ai-kit` and `ai-kit-cli` as too similar to existing projects; the owner selected `ai-kit-python`, whose pending-publisher registration succeeded. A public JSON 404 alone does not establish eligibility, and a pending publisher does not reserve a name. For a rename synchronize pyproject, archive checks, metadata smoke tests, workflow URLs, publisher configuration and install examples before rebuilding.
+
+[pyproject.toml](../pyproject.toml) owns metadata. [PYPI_DESCRIPTION.md](PYPI_DESCRIPTION.md) is the complete Markdown description, with absolute public links and no GitHub-only diagrams. AI-KIT's own code remains MIT; the distribution also bundles Apache-2.0 Strix resources, so its SPDX expression is `MIT AND Apache-2.0`. All three declared license files are included under wheel dist-info/licenses and retained beside their payload resources.
+
+## Install the published package
+
+Use an isolated CLI installation with `pipx install ai-kit-python`, or a Python virtual environment:
+
+~~~powershell
+$cliEnv = Join-Path $env:LOCALAPPDATA 'AI-KIT\venv'
+python -m venv "$cliEnv"
+& "$cliEnv\Scripts\Activate.ps1"
+python -m pip install ai-kit-python
+aikit --version
+~~~
+
+Keep that environment local; it is not an application dependency. For a reviewed checkout, `python -m pip install .` remains available. Update via `pipx upgrade ai-kit-python` or `python -m pip install --upgrade ai-kit-python`. Upgrading the CLI does not rewrite installed project instructions: preview `aikit install TARGET` and apply after review. [Usage](../README.md#packaged-cli-and-pypi-status).
+
+## Build and validate without uploading
+
+Use an isolated checkout/source copy and an output directory outside it. This keeps archive binaries, temporary metadata and private maintainer files away from source validation and test fixture copies. Example from that source copy in PowerShell:
+
+~~~powershell
+$releaseEnv = Join-Path ([System.IO.Path]::GetTempPath()) ('ai-kit-build-env-' + [guid]::NewGuid())
+python -m venv "$releaseEnv"
+& "$releaseEnv\Scripts\Activate.ps1"
+python -m pip install --require-hashes -r docker/build-requirements.txt
+python -m pip install -r docker/pypi-requirements.txt
+
+python scripts/check_kit.py
+python -m unittest discover -s tests -v
+
+$distPath = Join-Path ([System.IO.Path]::GetTempPath()) ('ai-kit-dist-' + [guid]::NewGuid())
+python tests/build_distribution.py "$distPath"
+python scripts/check_distribution.py archives "$distPath"
+python -m twine check --strict "$distPath/*"
+python tests/wheel_smoke.py "$distPath"
+~~~
+
+Use separate commands or stop on each nonzero exit. The build helper copies public source inputs into a disposable directory, injects synthetic private files, runs `build` to create sdist then wheel from sdist, and rejects leaked markers. Output inside the checkout or mixed with old archives refuses. The archive checker inspects paths without extracting, confirms metadata/version, description, CLI, resources, licenses and private-file exclusions, and reports SHA-256. Fresh-venv smoke exercises the installed CLI, optional resources and dialogue pipeline offline. Also check Python 3.10 compatibility and preserve the cross-platform CI matrix. Synthetic probes never read real credentials or conversations.
+
+The source checker and publication identity helper upload nothing:
+
+~~~sh
+python scripts/check_distribution.py identity
+~~~
+
+## Trusted Publishing configuration
+
+[publish-pypi.yml](../.github/workflows/publish-pypi.yml) supports `release: published` for stable releases and `workflow_dispatch` for manual runs. The Release path prepares production PyPI artifacts automatically, then waits for the owner's environment approval. Drafts and prereleases skip automatic production preparation. Pushes, tag pushes and Release edits do not request publication. Manual dispatch defaults to `validate`, which builds/tests/retains artifacts and skips both upload jobs. Existing required CI names remain unchanged.
+
+Configure these account settings separately when publication is authorized. PyPI and TestPyPI are separate services/accounts; use a pending publisher for a new project or add a publisher to an owned project.
+
+| Field | Production | Test registry |
+| --- | --- | --- |
+| Registry | pypi.org | test.pypi.org |
+| Project name | ai-kit-python | ai-kit-python, subject to availability |
+| GitHub owner | tigusigalpa | tigusigalpa |
+| Repository | ai-kit | ai-kit |
+| Workflow filename | publish-pypi.yml | publish-pypi.yml |
+| Environment | pypi | testpypi |
+
+The verified production environment requires reviewer `tigusigalpa` (GitHub user ID 2721390). Its custom deployment policy is **type `tag`, pattern `v*`**; matching branch names are not admitted. The same reviewer and all other environment protections were preserved when replacing the earlier v1.4.2-only policy. Self-review remains allowed so the sole owner can approve a run they started. The required confirmation must be performed by the human owner: agents must not approve or bypass it. [Contribution policy](../CONTRIBUTING.md#python-package-releases).
+
+Keep publisher/environment names identical. No PyPI API token is stored: the pinned PyPA action exchanges GitHub OIDC identity for a short-lived credential after approval. Only upload jobs receive `id-token: write`; build/tests have read-only repository access. Upload jobs consume the validated same-run artifact without checking out or building source. Manual and Release production runs share a per-tag concurrency group and do not cancel each other during approval.
+
+## Release to PyPI with owner approval
+
+1. Review VERSION, metadata, description, README, licenses and changes since the prior release; complete checks and Docker-impact handling. Any Git commit/tag/push needs its own authorization. The reviewed release commit must contain the updated workflow and event guard. Existing tags, including v1.4.2, stay unchanged.
+2. Prepare a new version, for example VERSION `1.5.0`, and a new tag `v1.5.0` at that commit. The automatic path accepts canonical stable `vMAJOR.MINOR.PATCH` tags; release tag, runner ref and the tag's VERSION must agree exactly. The guard also checks the event's repository against the canonical runner repository. Release notes/body are not commands or publication inputs.
+3. Publish a stable GitHub Release for that tag. The workflow first verifies event identity, then validates the kit, runs tests, builds sdist followed by wheel, checks metadata/resources/privacy/licenses/description and smoke-installs offline. A failure stops the upload job.
+4. In **Actions → Prepare or publish Python package**, wait for `build` to succeed. The `pypi` job then pauses at **Review deployments**. The human owner inspects the tag, commit and checks, selects `pypi`, and clicks **Approve and deploy**. Rejecting or leaving it pending uploads nothing. GitHub's required reviewer is the final gate; the agent does not submit this approval.
+5. The approved upload job obtains OIDC credentials and publishes only that run's tested files. Verify the public version, metadata, files, hashes and fresh installation from PyPI; compare downloads against the actual hosted artifacts. Update publication receipts after read-back. The README badge follows PyPI availability, not GitHub Release creation.
+
+### Manual runs and recovery
+
+- **Build only:** use Run workflow with destination `validate`; a branch is allowed. No upload or environment approval occurs.
+- **Manual upload:** select a `vVERSION` tag, choose `pypi` or `testpypi` and enter that exact version. Event inputs are checked before building; production uses the same human approval gate. Explicit manual prerelease trials remain possible.
+- **TestPyPI:** configure its separate environment/publisher before an authorized trial. Install with `--index-url https://test.pypi.org/simple/ --no-deps`; do not mix it with PyPI using an extra index. Production does not automatically upload there.
+- **Failed checks:** fix through the reviewed Git workflow and prepare a new release tag as needed. Do not move a released tag. The release workflow must exist in the tagged source; creating a Release for an older tag does not retrofit this implementation.
+- **Duplicate version:** uploads fail instead of replacing files or silently skipping them. Use a new version for changed packages; check public files and hashes before considering a retry of a partial upload.
+
+Committing these files alone neither creates a GitHub Release nor uploads a package. Keep prepared source, hosted checks, environment approval and registry evidence distinct. No future version is available on PyPI until read-back verifies it.
+
+## Release-chain verification
+
+Verified on 2026-10-16: kit checks returned no errors/warnings; 368 packaged Linux/Python 3.13.16 tests ran with two Windows-only skips. Fifteen new event tests cover future tags, invalid release identities, manual defaults and untrusted payloads. Workflow YAML/security assertions and Python 3.10 grammar passed. Isolated sdist-to-wheel, privacy probes, strict Twine and offline Windows wheel smoke passed. Local ai-kit:dev was rebuilt and passed Docker smoke; ten changed packaged resources matched source. These local runs did not cover macOS or a hosted Release event. No package/image was uploaded. The tested image retains the earlier documentation snapshot preceding this verification receipt.
+
+## Docker and documentation continuity
+
+Packaging metadata, description selection and bundled resource changes affect the CLI image: rebuild/test `ai-kit:dev`, verify new resources/version and preserve published release identities. Docker publication is separate. Follow [image refresh](DOCKER.md#change-impact-and-image-refresh) and the [Docker Hub checklist](../CONTRIBUTING.md#docker-hub-releases) when preparing an image release. Publication receipts alone may retain the tested image snapshot; record that boundary.
+
+For every Python package release, refresh metadata/description/README, run archive checks, strict Twine validation and offline installation, and record unavailable OS/runtime checks. [Contribution rules](../CONTRIBUTING.md#python-package-releases) own the release-maintenance trigger.
+
+Primary sources checked on 2026-10-16: [project metadata](https://packaging.python.org/en/latest/guides/writing-pyproject-toml/), [license expressions](https://packaging.python.org/en/latest/specifications/license-expression/), [PyPI descriptions](https://packaging.python.org/en/latest/guides/making-a-pypi-friendly-readme/), [pending publishers](https://docs.pypi.org/trusted-publishers/creating-a-project-through-oidc/), [OIDC publication](https://docs.pypi.org/trusted-publishers/using-a-publisher/), [PyPA action](https://github.com/pypa/gh-action-pypi-publish).
+
+Release/approval sources checked on 2026-10-16: [release events](https://docs.github.com/en/actions/reference/workflows-and-actions/events-that-trigger-workflows#release), [deployment tag policies](https://docs.github.com/en/rest/deployments/branch-policies), [human deployment review](https://docs.github.com/en/actions/how-tos/deploy/configure-and-manage-deployments/review-deployments).

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/docs/PYPI_DESCRIPTION.md

@@ -92,6 +92,8 @@ The distribution excludes root maintainer AGENTS.md, PROJECT_CONTEXT.md and WIKI
 
 A separate [Docker image](https://hub.docker.com/r/tigusigalpa/ai-kit) packages the CLI for container use.
 
+Package releases follow GitHub Release, automated checks and owner approval before PyPI upload through Trusted Publishing. Future stable tags must match VERSION; manual runs default to validation. See the [release procedure](https://github.com/tigusigalpa/ai-kit/blob/main/docs/PYPI.md#release-to-pypi-with-owner-approval).
+
 ## Documentation and license
 
 - [Repository and full README](https://github.com/tigusigalpa/ai-kit)

{ai_kit_python-1.4.2 → ai_kit_python-1.4.3}/docs/V1_4_2.md

@@ -1,6 +1,6 @@
 # AI-KIT v1.4.2
 
-Release preparation date: 2026-10-16. [CHANGELOG](../CHANGELOG.md#v142-2026-10-16) owns release history; [PyPI procedure](PYPI.md) owns publishing instructions.
+Published on 2026-10-16. [CHANGELOG](../CHANGELOG.md#v142-2026-10-16) owns release history; [PyPI procedure](PYPI.md) owns publishing instructions.
 
 ## Release contents
 
@@ -28,6 +28,21 @@ PyPI rejected `ai-kit` and `ai-kit-cli` as too similar to existing projects. The
 
 The GitHub environment was independently read back: only tag `v1.4.2`, required reviewer `tigusigalpa`, self-review permitted for solo maintenance. TestPyPI remains unconfigured and no TestPyPI upload was requested. A pending publisher does not reserve a project name or establish package availability.
 
-The owner authorized commit/push, PR/merge after required checks, creation/push of v1.4.2 and the production PyPI upload. [PR 1](https://github.com/tigusigalpa/ai-kit/pull/1) contains the release. Its first hosted run exposed incorrect Twine wildcard quoting on Windows; the complete glob is now quoted and passed local PowerShell validation with a space-containing path. Hosted checks must finish before merging. No registry upload or public installation is established yet; record the actual workflow/tag identity, uploaded hashes and fresh installation afterward.
+The first hosted run exposed incorrect Twine wildcard quoting on Windows. The corrected complete glob passed PowerShell validation with a space-containing path. All 32 final push/PR CI checks succeeded, including the required Linux/Windows/macOS matrices and Docker. [PR 1](https://github.com/tigusigalpa/ai-kit/pull/1) was merged without bypassing checks. Tag `v1.4.2` points to `36e804a43f9a8a7912da050e7117821a407904b0`; the existing v1.4.1 tag and Docker Hub image were preserved.
+
+## PyPI publication and read-back
+
+[Publication workflow 38891485311](https://github.com/tigusigalpa/ai-kit/actions/runs/38891485311) completed successfully from that exact tag/commit. The build job validated the source, tests, both archives, description and offline wheel installation. The owner-approved `pypi` environment released only those artifacts through GitHub OIDC; TestPyPI was skipped.
+
+The public [ai-kit-python 1.4.2 page](https://pypi.org/project/ai-kit-python/1.4.2/) and version JSON were read back. Both downloaded files match the SHA-256 values in the same-run GitHub artifacts:
+
+| Published file | SHA-256 |
+| --- | --- |
+| ai_kit_python-1.4.2-py3-none-any.whl | `7bda41d548597ddbba318e0a006eedb886238b89a96168d0ee1514b73881d4f5` |
+| ai_kit_python-1.4.2.tar.gz | `c4a278bcc94945b91363722929e8f1b1f3ec7b28604681348afd85f7b1082174` |
+
+A fresh Windows/Python 3.12.14 environment installed `ai-kit-python==1.4.2` directly from `https://pypi.org/simple`, with the wheel hash required and dependencies/cache disabled. The installed import path belongs to that environment, `aikit --version` returned `aikit 1.4.2`, and the installed kit check reported zero errors/warnings. Complete smoke verification of the downloaded wheel also passed the optional resources and dialogue pipeline.
+
+These are registry receipts, not local preparation hashes. The CLI image remains the tested 1.4.2 development snapshot; descriptive receipts added afterward do not require replacing it. Docker Hub still serves the previously published 1.4.1 image. Raw verification files, downloaded packages and logs are stored outside the repository.
 
 [Core](../template/ai-kit/CORE.md#git-authorization) governs Git authorization. No account secrets belong in source, artifacts or chat. Future image publication remains separate; preserve existing release tags and Docker identities.

ai_kit_python-1.4.3/docs/V1_4_3.md

@@ -0,0 +1,33 @@
+# AI-KIT v1.4.3
+
+Release date: 2026-10-16. [CHANGELOG](../CHANGELOG.md#v143-2026-10-16) owns history; [PyPI procedure](PYPI.md#release-to-pypi-with-owner-approval) owns publishing instructions.
+
+## Release contents
+
+- Published stable GitHub Releases automatically prepare the Python package: verify the event, run source/behavior checks, build sdist and wheel, check metadata/resources/privacy/licenses/description and smoke-install offline.
+- PyPI upload waits for the human owner of environment `pypi`. Agents must not approve or bypass this confirmation. The upload uses OIDC and only the same run's validated artifacts; build jobs receive no OIDC permission.
+- Future canonical `vMAJOR.MINOR.PATCH` tags work with the existing tag-only `v*` environment policy. Release tag, runner ref, committed VERSION and canonical repository must agree. Drafts and prereleases skip automatic production preparation.
+- Manual dispatch stays available and defaults to build-only validation. Explicit manual uploads require an exact version/tag and production still requires owner approval. TestPyPI remains separate and unconfigured.
+- Fifteen event regression tests, a live README PyPI version badge, updated release/recovery instructions and preserved archived changelog text.
+
+VERSION, CLI, package metadata and the local development image advance to 1.4.3. The existing v1.4.2 tag and PyPI files stay unchanged. Docker Hub remains at the separately published 1.4.1 image; this GitHub release does not publish an image there.
+
+## Verification
+
+Before labeling, [PR 3](https://github.com/tigusigalpa/ai-kit/pull/3) passed all 32 push/PR CI checks across Linux, Windows and macOS, including the Python validation/wheel matrices and Docker. [Validate-only run 38897526857](https://github.com/tigusigalpa/ai-kit/actions/runs/38897526857) passed on the merged workflow: 368 tests, source/archive/description/private-probe checks and offline wheel smoke; both upload jobs skipped.
+
+After labeling 1.4.3, verified locally on 2026-10-16:
+
+- Kit validation returned zero errors/warnings; ten Windows/Python 3.12.14 CLI tests passed. The CLI and archive identity guard report 1.4.3.
+- The packaged Linux/Python 3.13.16 image ran 368 tests in 30.323 seconds: 366 passed, two Windows-only skips.
+- Isolated sdist-to-wheel builds, synthetic private-file probes, archive metadata/licenses/resources, strict Twine and offline Windows wheel smoke passed. The package description includes the owner-approved release procedure.
+- Docker smoke passed offline/read-only execution, installation/refusal, all optional modules, preserved files, stable rerun, SIGTERM and the actual context-exclusion engine. The version label is 1.4.3. No test volumes were created; shared cache ownership is unknown, so no pruning was performed.
+- Private/team upgrade fixtures used a Git archive of the actual v1.4.2 tag. README, MCP configuration, project facts, design brief, private dialogue data and settings including a custom extension survived; doctor reported 1.4.3 with no errors, private memory stayed ignored and reruns wrote nothing.
+
+Build binaries, hashes and raw logs remain outside the source checkout. Descriptive verification receipts follow the tested image snapshot. These local runs do not cover macOS; hosted CI is verified separately before release creation. Synthetic tests do not establish live model/client activation, application benchmarks or Kubernetes deployment.
+
+## GitHub Release and owner confirmation
+
+Create the new v1.4.3 tag at the reviewed, checked release commit, preserving old tags. Publishing its stable GitHub Release triggers `publish-pypi.yml`. Wait for `build` to succeed, then the owner selects **Actions -> Review deployments -> pypi -> Approve and deploy**. Rejecting or leaving the request pending uploads nothing.
+
+This record describes release preparation and the approval procedure; it is not a PyPI publication receipt. Verify public files/hashes and a fresh registry installation after the owner's approval before claiming publication. The last verified registry release at preparation was [1.4.2](V1_4_2.md). Descriptive verification/publication receipts added after building may retain the tested image's earlier documentation snapshot.

ai_kit_python-1.4.3/docs/history/v0.13.0-changelog.md

@@ -0,0 +1,8 @@
+# Archived AI-KIT release history
+
+## v0.13.0 (2026-10-11)
+
+- Added Rust, .NET, Java (Maven/Gradle), and Terraform/Helm stack profiles with evidence-based per-module detection: Cargo.toml (rust-version, cargo test/build/clippy), *.csproj/*.fsproj/*.vbproj and global.json (TargetFramework, dotnet test/build), pom.xml/mvnw/build.gradle(.kts)/gradlew (language level, wrapper-aware commands), and .tf files or Chart.yaml (fmt/validate, helm lint). Drafts remain suggestions until bootstrap confirms them.
+- Added rust-work, dotnet-work, java-work, and infra-work skills to the registry; Claude native copies install with the claude agent selection.
+- Benchmark packs accept the new stack names; README, SKILL.md, and WIKI profile lists updated.
+- Verified locally (Windows/Python 3.14.6): 254 tests ran, all passed, 1 runtime skip; kit validation returned zero errors and zero warnings; Python 3.10 grammar verified; end-to-end smoke detected RUST/INFRA with drafted context and installed source/native skills. Real applications of the new stacks remain untrialed.