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

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

@@ -7,8 +7,7 @@ description: Maintain AI-KIT's own context, template boundaries, and installer v
 
 Read [contribution rules](../../../CONTRIBUTING.md). Read optional local `../../../PROJECT_CONTEXT.md`, `../../../AGENTS.md` and `../../../WIKI.md` when present; otherwise verify facts from public source/configuration. These three root files stay local and untracked, outside wheel/Docker payloads; their template counterparts stay public. Check distributions with and without local copies and preserve their on-disk bytes when untracking.
 Keep the root context/history about this kit; keep template project facts uninitialized.
-For a procedure change, update current maintainer commands, this pointer contract, and relevant implementation docs in the same task.
-When verified facts or agreements change, synchronize this skill's scope/procedure/pointers and WIKI with the context; keep actual facts in context.
+Sync commands, this skill, docs, context and WIKI on procedure/fact/agreement changes; keep facts in context.
 Validate templates/links/registry, the agent registry (integrations/agents.json), and behavioral installation scenarios; record root CHANGELOG entries. Keep the root SKILL.md (the repository as a skill) consistent with the CLI, presets, extras, and policies.
 Review explicit semantic acceptance and future-upgrade conflicts whenever installer baseline behavior changes.
 Check candidate draft preservation, state/settings validation, and adapter retirement conflicts when changing installation. Exercise installed Git visibility and portable linked-path refusal; distinguish synthetic fixtures from real application trials. Verify the conditional Docker trigger in installed AGENTS and preserve edited entry points during upgrades.
@@ -16,19 +15,19 @@ Exercise file-versus-directory native rule layouts on both probe and selected-wr
 Exercise manifest-based profile detection and project-fact drafts (version/commands into PROJECT_CONTEXT and project.json), scoped Node/Python ignore rules, the installed-project doctor report, opt-in extras (session-start, guards, CI) including key-level client settings merges, legacy whole-file migration, and hook execution, client detection markers, interactive/check onboarding, the adr/changelog helpers, and the offline router helper (route/configure with provider selection) when installer behavior changes.
 For generated client configuration, exercise private/team settings files and mode switches, owned-entry moves, project.json precedence, secret lists, ignore blocks, every scoped rule format with root modules and skipped paths, presets that turn extras off, and workflow skill copies; recheck client formats against primary docs before changing them.
 For routing, compare the implementation ladder with canonical POLICY, exercise English/Russian operation/risk regressions and override precedence, provider-review status/sources, and distinguish recommendations from executed model controls. For stack profiles, exercise manifest evidence, module scoping, and command drafting; for Filament specifically test Composer dependency/lock evidence and source/native skill lifecycle. For optional metrics, verify failure/recovery accounting, missing-value coverage, duplicate/lock/path guards, private/team journal visibility, schema 1/2 compatibility, experiment/arm/task identity, per-provider analyze output, and upgrade preservation. Exercise context snapshots and doctor warnings for new/removed modules, profile drift, and manifest changes. Exercise adapter reports plus explicit retirement of unchanged files, backups/state updates, and modified-file conflicts. Exercise opaque evaluator pair coverage without task-text persistence. Use the [evaluation protocol](../../../docs/EVALUATION.md) for separately authorized application trials; synthetic fixtures establish no savings.
-Record actual OS/runtime and unavailable checks in the implementation record; keep source visibility checks separate from client activation.
-For measurement-led changes, test schema 1/2/3 compatibility, fixed A/B controls, immutable Git blobs and isolated repeated workspaces, missing/estimated telemetry, semantic-review gates, interrupted runs and idempotent private exports. Exercise resume identity checks, per-unit failure recording and configurable kit-arm agents/presets. Check that worker Git discovery cannot reach the source through parents: a ceiling at cwd itself is ineffective. Keep worker requests separate from observed execution. Exercise routing modes/pins/profiles, distinct-case quality floors, matched history, unsupported controls, immutable proposal history and explicit backed-up restore. Exercise module context scope, duplicate content, critical rules/ADRs above byte budgets and linked paths. Follow [the staged plan](../../../docs/DEVELOPMENT_PLAN.md) and [worker contract](../../../docs/BENCHMARK.md); defer live adapters/orchestration until their mechanisms and total coordination costs are verified.
+Record runtime gaps separately from static/source checks.
+For measurement-led changes, test schema 1/2/3 compatibility, fixed A/B controls, immutable Git blobs and isolated repeated workspaces, missing/estimated telemetry, semantic-review gates, interrupted runs and idempotent private exports. Exercise resume identity checks, per-unit failure recording and configurable kit-arm agents/presets. Check that worker Git discovery cannot reach the source through parents: a ceiling at cwd itself is ineffective. Keep worker requests separate from observed execution. Exercise routing modes/pins/profiles, distinct-case quality floors, matched history, unsupported controls, immutable proposal history and explicit backed-up restore. Exercise module context scope, duplicate content, critical rules/ADRs above byte budgets and linked paths. Follow [the staged plan](../../../docs/DEVELOPMENT_PLAN.md) and [worker contract](../../../docs/BENCHMARK.md); keep native activation and real trials separate. For [optional orchestration](../../../docs/ORCHESTRATION.md), test opt-in/persistence, Codex helper conflicts/retirement, private/team/archive exclusions, bounded inputs/keys/budgets, reservations/locks, unknown billing, source-bound review and reconciliation without replay. Keep native costs separate; tests make no live calls.
 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 reference upgrades verify the published tree and overlay leftovers; preserve canonical links and checker coverage.
+Verify [Windows](../../../README.md#windows-installation-and-troubleshooting) examples and CLI defaults; report actual client activation. 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 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.
+Assess [Docker impact](../../../docs/DOCKER.md#change-impact-and-image-refresh) on every task, including installed guidance. Rebuild/test affected final sources as ai-kit:dev or record a descriptive-only exception. Verify client/daemon, pins, VERSION/labels, closed context, wheel resources, non-root mounts, offline/read-only preview/apply, preservation, reruns, signals and Job schema. Follow [canonical cleanup](../../../template/ai-kit/CONTAINERS.md#post-test-docker-cleanup): no threshold, zero eligible disposable resources, dedicated-builder cache, protected persistent/unrelated data and separately measured RAM/disk reclamation. Check actual backend, VHDX identity and idle maintenance scope; never infer compaction from prune. Upgrade tests must preserve adapted container rules/AGENTS through candidates. Record actual runtime gaps; publication needs its authorization.
 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 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 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 release path](../../../docs/V1_4_5.md#pypi-publication-status): 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.
+For Docker releases, follow [image verification](../../../docs/V1_4_5.md#docker-hub-publication); 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 this kit as an application or infer runtime success from static checks.

{ai_kit_python-1.4.3 → ai_kit_python-1.4.5}/.dockerignore

@@ -82,6 +82,8 @@ ai-kit/.metrics
 ai-kit/.metrics/**
 ai-kit/.memory
 ai-kit/.memory/**
+ai-kit/.orchestration
+ai-kit/.orchestration/**
 ai-kit/.upstream-cache
 ai-kit/.upstream-cache/**
 ai-kit/.design

{ai_kit_python-1.4.3 → ai_kit_python-1.4.5}/.gitignore

@@ -58,3 +58,5 @@ build/
 .DS_Store
 Thumbs.db
 Desktop.ini
+
+/ai-kit/.orchestration/

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

@@ -1,11 +1,27 @@
 # AI-KIT changelog
 
+## Unreleased
+
+## v1.4.5 (2026-10-30)
+
+- Require maximum disposable Docker cleanup after every build/test/debug task, without a size/age threshold; include containers, volumes, networks, unnecessary test images and dedicated-builder cache.
+- Require separate host RAM/disk reclamation, supported WSL2 settings and offline compaction; preserve persistent data, unrelated workloads and reviewed retention scope.
+- Updated installed AGENTS/docs; tested private/team upgrades and conflicts; published Docker Hub 1.4.5. PyPI follows owner approval. [Release record](docs/V1_4_5.md).
+- Added a detailed Windows README guide covering setup, inherited/stale PATH, persistent user PATH, isolated CLI, common errors and project updates.
+
+## v1.4.4 (2026-10-18)
+
+- Added opt-in Codex helpers and a bounded OpenRouter executor with capped-key preflight, reservations, private accounting, source-bound review and billing reconciliation; preserved installer defaults/edits and added tests, packaging and instructions.
+- Published and verified Docker Hub/PyPI 1.4.4, exact hosted hashes, registry installation and image behavior; refreshed README/Overview. [Complete entry and evidence](docs/V1_4_4.md).
+
 ## 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).
+- Added stable GitHub Release checks and owner-approved PyPI uploads, event/version/repository guards, future v* tags and manual validation. [Procedure](docs/PYPI.md#release-to-pypi-with-owner-approval). Archived v0.13.0 text intact.
+- Added fifteen event regression tests. Before labeling, 32 hosted checks and build-only verification passed, plus kit, 368 Linux tests (two skips), archive/privacy/Twine/offline wheel and Docker checks. [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.
+- Verified PyPI 1.4.3 publication, matching hosted hashes and fresh registry installation; [receipt](docs/V1_4_3.md#pypi-publication-and-read-back).
+- Published Docker Hub 1.4.3 with verified image/digest and refreshed README/Overview; [receipt](docs/V1_4_3.md#docker-hub-143).
 
 ## v1.4.2 (2026-10-16)
 
@@ -57,12 +73,7 @@
 
 ## v0.12.0 (2026-10-11)
 
-- Benchmark packs accept optional `kit_agents`/`kit_preset` (default codex/minimal), so kit arms install the client's real adapter set and preset instead of a hard-coded arm; both are validated against the installer registry.
-- Benchmark task paths are now probed against the benchmark project instead of the process working directory.
-- Interrupted benchmark runs are resumable: re-running `benchmark run` with the identical pack skips completed units and continues missing ones, and a changed pack is refused against the existing run. Per-unit infrastructure failures are recorded as explicit failed units, so one bad unit neither aborts the run nor hides as an executed attempt; failed units still block savings and cannot be reviewed as correct.
-- The unified `aikit` dispatcher now prefers installed `aikit.scripts.*` package modules over bare script-path imports, avoiding duplicate module objects inside the wheel.
-- The checker document budgets are named constants; the root README budget rises to 22000 bytes (human onboarding that never enters project context), other documents keep 12000.
-- Verified locally (Windows/Python 3.14.6): 252 tests ran, all passed, 1 runtime skip; kit validation returned zero errors and zero warnings; Python 3.10 grammar was verified for the changed sources. Live workers, native client activation and hosted CI remain unverified.
+[Full preserved entry](docs/changelog/v0.12.0.md).
 
 ## v0.11.0 (2026-10-11)
 

{ai_kit_python-1.4.3 → ai_kit_python-1.4.5}/MANIFEST.in

@@ -6,6 +6,7 @@ include pyproject.toml Makefile MANIFEST.in
 recursive-include ai-kit *.md
 prune ai-kit/.metrics
 prune ai-kit/.memory
+prune ai-kit/.orchestration
 prune ai-kit/.upstream-cache
 prune ai-kit/.design
 recursive-include .agents *

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

@@ -1,7 +1,7 @@
 Metadata-Version: 2.4
 Name: ai-kit-python
-Version: 1.4.3
-Summary: Offline installer and portable instructions that give AI coding agents project memory, stack rules, guardrails, and adaptive model routing.
+Version: 1.4.5
+Summary: Portable instructions and installer for AI coding agents: project memory, stack rules, model routing, and optional budgeted orchestration.
 Author: Igor Sazonov
 License-Expression: MIT AND Apache-2.0
 Project-URL: Homepage, https://github.com/tigusigalpa/ai-kit
@@ -82,7 +82,7 @@ Open the application in your AI client and invoke `$ai-kit-bootstrap` in Codex o
 - **Conservative upgrades:** existing documents, settings and local adaptations are preserved; conflicts remain reviewable.
 - **Engineering workflows:** plan, implement, test, review and document, with explicit Git authorization.
 - **Routing and measurement:** offline recommendations, context selection, metrics and benchmark scaffolding. Live execution needs a separately configured worker.
-- **Container guidance:** non-root execution, lifecycle, image freshness, mounts and Kubernetes readiness appropriate to the workload.
+- **Container guidance:** Kubernetes readiness, image freshness and mandatory maximum disposable cleanup without a size threshold, including separate host RAM/disk reclamation. Persistent data and unrelated workloads remain protected; installation starts no cleanup or compaction process.
 
 ## Optional integrations
 
@@ -132,3 +132,7 @@ Package releases follow GitHub Release, automated checks and owner approval befo
 - [Issues](https://github.com/tigusigalpa/ai-kit/issues)
 
 AI-KIT's own code and instructions are MIT licensed. Bundled Cloudflare references retain MIT; bundled Strix references retain Apache-2.0. The complete distribution declares `MIT AND Apache-2.0` and includes the corresponding license texts. External runtimes and application dependencies keep their own licenses.
+
+## Optional orchestration (v1.4.4)
+
+Install with `--with-orchestration` to add scoped Codex helpers and disabled-by-default OpenRouter configuration. `aikit orchestrate` previews selected text tasks, executes only on explicit apply, enforces local admission and capped-key preflight, and retains private observed usage/cost, review and billing reconciliation. It never executes model output. Native helper billing is separate; real trials and savings are unverified. See the [complete guide](https://github.com/tigusigalpa/ai-kit#optional-orchestration).