agent-lifecycle-kit 1.50.1__tar.gz

agent_lifecycle_kit-1.50.1/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

agent_lifecycle_kit-1.50.1/NOTICE

@@ -0,0 +1,5 @@
+Agent Lifecycle Kit
+Copyright 2026 Agent Lifecycle Kit contributors
+
+This product includes software developed by the Agent Lifecycle Kit
+contributors and distributed under the Apache License, Version 2.0.

agent_lifecycle_kit-1.50.1/PKG-INFO

@@ -0,0 +1,201 @@
+Metadata-Version: 2.4
+Name: agent-lifecycle-kit
+Version: 1.50.1
+Summary: Provider-neutral lifecycle control layer that helps coding agents plan, execute, validate, and prove software tasks to completion.
+Author: Agent Lifecycle Kit contributors
+License: Apache-2.0
+Keywords: adapter-conformance,agent-lifecycle,agent-workflows,agents,ai-agents,audit,coding-agents,lifecycle,model-routing,planning,sdd,software-delivery,task-orchestration,workflow
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Developers
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Typing :: Typed
+Requires-Python: <3.14,>=3.11
+Description-Content-Type: text/markdown
+License-File: LICENSE
+License-File: NOTICE
+Dynamic: license-file
+
+<p align="center">
+  <img src="docs/assets/agent-lifecycle-kit-banner.svg?v=2026-08-02-1" alt="Agent Lifecycle Kit - plan, execute, prove, finish agent work" width="100%">
+</p>
+
+# Agent Lifecycle Kit
+
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-green.svg)](LICENSE)
+[![Release](https://img.shields.io/github/v/release/avksp/agent-lifecycle-kit?label=release)](https://github.com/avksp/agent-lifecycle-kit/releases)
+![Python](https://img.shields.io/badge/python-3.11--3.13-blue.svg)
+
+**Agent Lifecycle Kit (ALK)** gives coding agents one delivery workflow from
+request to verified result. It turns a user task into a reviewed specification,
+an approved plan, bounded implementation work, review, and final proof, so
+agents finish the job instead of stopping at a patch.
+
+The workflow is provider-neutral. Codex, Claude Code, Qwen Code, Goose,
+OpenInterpreter, Pi, Grok Build, or another CLI can follow the same lifecycle,
+while provider commands, model choice, and secret handling stay in adapters or
+host-local profiles.
+
+## Quick start
+
+From a source checkout:
+
+```bash
+python -m pip install -e .
+agent-lifecycle version
+agent-lifecycle diagnose --no-install-plans
+agent-lifecycle adapter validate --descriptor adapters/codex/adapter.descriptor.json
+```
+
+Package install, when available for the release:
+`python -m pip install agent-lifecycle-kit==1.50.1`.
+
+For a short walkthrough, use [Quickstart](docs/guides/quickstart.md) and the [Lifecycle cookbook](docs/guides/lifecycle-cookbook.md). For structure and positioning, see [System architecture](docs/architecture/system-architecture.md) and [Project comparison](docs/reference/project-comparison.md). Russian documentation starts at [Документация на русском](docs/ru/README.md).
+
+## What it gives you
+
+- A finish-oriented lifecycle: plan, execute, review, and prove the result.
+- One process for different CLIs: adapter-specific commands stay outside the
+  core, and new adapters can be added without changing lifecycle schemas.
+- Small-model friendly packets: compact context, clear next actions, and
+  deterministic checks for local or cheaper models.
+- Quality without overengineering: optional profiles turn on only when risk or
+  task type requires them.
+- Usage visibility: tokens, time, and resource counters are native; monetary
+  cost is optional and only used when a metered host reports it.
+- Read-only progress and managed sessions: host UIs can show lifecycle state,
+  attested tokens and Git-style change counters; `adapter task start` accepts
+  task text, Markdown or frozen run requests while preserving review/freeze
+  boundaries.
+
+## Feature areas
+
+### Plan and execute
+
+- Reviewed specification and plan flow before implementation starts.
+- Deterministic task packets for splitting work across agents.
+- Execution records capture completion checks, blockers, retries, and final
+  proof; missing required evidence fails the step.
+- Ready-made task templates cover bug fixes, idea-to-PR flow, PR review,
+  merge-conflict repair, and release-readiness work.
+
+### Quality and proof
+
+- Implementation audits compare results with the frozen plan and acceptance
+  evidence.
+- For explicit bug and regression repair, the optional Bug Forensics profile
+  records reproduction, fingerprint, failure class, hypotheses, minimal patch,
+  regression proof, and reusable recipes.
+- Optional proof-integrity evidence for high-risk final proofs: stable findings,
+  root-cause digests, fix-impact receipts, and hash chains.
+- Cross-checks and runtime-policy receipts are opt-in controls; plans can
+  require proof for an external system update before acceptance.
+- Optional Review Mesh covers leader-draft review, parallel research synthesis
+  and audit panels. The advisor can suggest a mode; `review-mesh prepare`
+  creates local reviewer packets; opted-in plans can require
+  assignment/result/synthesis/quorum receipts, but ALK core does not start hosts.
+
+### Routing and resource control
+
+- Compact context profiles, small-model packets, objective snapshots, and
+  local quality-cost learning help choose the lightest safe mode.
+- Phase resource measurements reuse the usage export envelope for tokens,
+  duration, and resource counters without mandatory monetary accounting.
+- Usage/session exports include tokens, resources, receipt digests, and optional
+  host-reported `cost_usd`.
+
+### Security and containment
+
+- Neutrality filters use host-supplied deny rules to keep local paths, secrets, trust roots, and signing keys out of portable artifacts.
+- Host env files require explicit `--host-env-allow`; receipts store redacted metadata, not secret values or private env-file paths.
+- Imports, diagnostics, and usage exports redact local paths and common secret markers before validation.
+- Sandbox receipts separate runtime filesystem, network, process, and environment containment from git write-scope.
+- Release security gates reject leaked local paths, credentials, and unsupported adapter or production claims.
+
+### Adapters and interop
+
+- Adapter contracts keep host-specific projections separate from lifecycle
+  schemas.
+- New CLI hosts start as adapters: descriptor, command projection, environment
+  boundary, and verification evidence live outside the lifecycle core.
+- Adapter capability checks and progress bridge support compare live receipts
+  and display lifecycle state without automatic maturity changes.
+- Import mappers and issue-to-spec intake treat external workflows, agent
+  dialects, and tickets as untrusted draft inputs.
+- Lightweight episode retrieval over receipt/session summaries keeps digest
+  provenance and explicit `chainVerified` or `chainUnchecked` state.
+
+### Operations
+
+- Runner recovery receipts cover attempt snapshot, restore, abandon, selected
+  attempt, worker lease, and heartbeat state.
+- Read-only diagnostics, event feeds, managed lifecycle steps, progress watch
+  receipts, and change summaries inspect checkout and workflow state without
+  model calls.
+
+## Daily flow
+
+Spec -> frozen plan -> bounded work -> implementation audit -> final proof.
+Core commands cover specification, plan, workflow, audit, adapters, imports, metrics,
+policy, diagnostics, runner state, and adapter task intake. See [CLI reference](docs/reference/cli.md) and [Source of truth](docs/reference/source-of-truth.md).
+
+## Adapter maturity
+
+`EXPERIMENTAL` means offline checks exist; bounded live host conformance and
+usage/resource calibration are still required before `VERIFIED`. The verified
+claim is host-specific and also requires accepted redacted evidence and
+lifecycle final proof for the tested host range. New hosts can be added as
+adapters first and promoted only for the exact CLI/version/provider binding that
+has evidence. Monetary accounting is required only for metered modes.
+
+| Host | Current claim |
+| --- | --- |
+| Codex | `VERIFIED` for Codex CLI 0.145.0. Public Plugins Directory approval is not claimed. |
+| Claude Code | `VERIFIED` for Claude Code 2.1.220. Official directory approval is not claimed. |
+| OpenCode | `VERIFIED` for OpenCode CLI 1.18.9. npm publication is not claimed. |
+| Hermes | `VERIFIED` for Hermes Agent v0.19.0. Public directory approval is not claimed. |
+| Qwen Code | `VERIFIED` for Qwen Code 0.21.0 on the tested host-local provider/model binding. Public package approval is not claimed. |
+| Cursor | `EXPERIMENTAL`; local safe inspection passed, but accepted live receipts are incomplete. |
+| Gemini CLI | `EXPERIMENTAL`; local live canary is blocked by the current Gemini Code Assist tier. |
+| Goose | `VERIFIED` for Goose 1.45.0 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| Kimi Code | `EXPERIMENTAL`; live proof requires a configured provider and model alias. |
+| Grok Build | `VERIFIED` for Grok Build 0.2.117 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| OpenInterpreter | `VERIFIED` for `interpreter` 0.0.34 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| Pi | `VERIFIED` for Pi 0.83.0 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+
+Adapter installation and maturity details live in [Adapter install](docs/adapters/install.md) and [Adapter support matrix](docs/adapters/support-matrix.md).
+
+## Contract map
+
+The public lifecycle surface is schema-backed. Full stable schema ids, compatibility rules, runner recovery, cross-check, Review Mesh, Bug Forensics and usage export details are listed in [Public contracts](docs/reference/public-contracts.md).
+
+## Design boundaries
+
+- The core stays provider-neutral. Concrete host commands and model bindings
+  belong to adapters or host-local profiles.
+- New CLIs are integrated through adapters: descriptor, command projection,
+  environment boundary, and verification evidence. The lifecycle schemas remain
+  stable while host support grows.
+- Small models get compact packets, deterministic checks, and explicit
+  next-action lists instead of long narrative state.
+- Larger models keep the same gates; better reasoning does not bypass evidence.
+- Public release claims are limited to tracked source files and redacted
+  evidence summaries.
+- External dialect imports and retrieved episodes are context aids only; they
+  do not replace reviewed ALK source-of-truth artifacts.
+- Optional cross-check, Review Mesh and runner recovery receipts add evidence
+  only when a task or plan requests them; they are not default multi-model execution.
+
+## Documentation
+
+- Start: [English documentation](docs/README.md), [Русская документация](docs/ru/README.md), [Quickstart](docs/guides/quickstart.md), [Lifecycle cookbook](docs/guides/lifecycle-cookbook.md), and [Code review workflows](docs/guides/code-review-workflows.md).
+- Planning and adapters: [Issue to specification drafts](docs/guides/issue-to-spec.md), [Adapter install](docs/adapters/install.md), and [Adapter support matrix](docs/adapters/support-matrix.md).
+- Reference: [System architecture](docs/architecture/system-architecture.md), [CLI reference](docs/reference/cli.md), [Source of truth](docs/reference/source-of-truth.md), [Managed lifecycle runner](docs/reference/managed-lifecycle-runner.md), [Managed adapter sessions](docs/reference/managed-adapter-sessions.md), [Implementation audit](docs/reference/implementation-audit.md), [Plan completeness](docs/reference/plan-completeness.md), [Public contracts](docs/reference/public-contracts.md), and [Readiness diagnostics](docs/reference/readiness-diagnostics.md).
+- Quality and resources: [Small-model packets](docs/reference/small-model-packets.md), [model routing](docs/reference/model-routing.md), [adaptive policy](docs/reference/adaptive-lifecycle-policy.md), [quality-cost learning](docs/reference/quality-cost-learning.md), [lifecycle cost accounting](docs/reference/lifecycle-cost.md), [Usage export](docs/reference/usage-export.md), and [Evidence integrity](docs/reference/evidence-integrity.md).
+- Profiles and operations: [Read-only status views](docs/reference/read-only-status-view.md), [Adapter progress bridge](docs/reference/automatic-progress-bridge.md), [Sandbox boundaries](docs/reference/sandbox-boundaries.md), [Import mappers](docs/reference/import-mappers.md), [Episode retrieval](docs/reference/episode-retrieval.md), [Runner recovery](docs/reference/runner-recovery.md), [Cross-check profile](docs/reference/cross-check-profile.md), [Review Mesh](docs/reference/review-mesh.md), [Bug Forensics profile](docs/reference/bug-forensics.md), and [Bug Forensics context budget](docs/reference/bug-forensics-context-budget.md).
+- Release assets: [Task templates](templates/tasks/README.md) and [Release security](docs/security/release-security.md).
+
+Apache-2.0. See [LICENSE](LICENSE).

agent_lifecycle_kit-1.50.1/README.md

@@ -0,0 +1,180 @@
+<p align="center">
+  <img src="docs/assets/agent-lifecycle-kit-banner.svg?v=2026-08-02-1" alt="Agent Lifecycle Kit - plan, execute, prove, finish agent work" width="100%">
+</p>
+
+# Agent Lifecycle Kit
+
+[![License: Apache-2.0](https://img.shields.io/badge/license-Apache--2.0-green.svg)](LICENSE)
+[![Release](https://img.shields.io/github/v/release/avksp/agent-lifecycle-kit?label=release)](https://github.com/avksp/agent-lifecycle-kit/releases)
+![Python](https://img.shields.io/badge/python-3.11--3.13-blue.svg)
+
+**Agent Lifecycle Kit (ALK)** gives coding agents one delivery workflow from
+request to verified result. It turns a user task into a reviewed specification,
+an approved plan, bounded implementation work, review, and final proof, so
+agents finish the job instead of stopping at a patch.
+
+The workflow is provider-neutral. Codex, Claude Code, Qwen Code, Goose,
+OpenInterpreter, Pi, Grok Build, or another CLI can follow the same lifecycle,
+while provider commands, model choice, and secret handling stay in adapters or
+host-local profiles.
+
+## Quick start
+
+From a source checkout:
+
+```bash
+python -m pip install -e .
+agent-lifecycle version
+agent-lifecycle diagnose --no-install-plans
+agent-lifecycle adapter validate --descriptor adapters/codex/adapter.descriptor.json
+```
+
+Package install, when available for the release:
+`python -m pip install agent-lifecycle-kit==1.50.1`.
+
+For a short walkthrough, use [Quickstart](docs/guides/quickstart.md) and the [Lifecycle cookbook](docs/guides/lifecycle-cookbook.md). For structure and positioning, see [System architecture](docs/architecture/system-architecture.md) and [Project comparison](docs/reference/project-comparison.md). Russian documentation starts at [Документация на русском](docs/ru/README.md).
+
+## What it gives you
+
+- A finish-oriented lifecycle: plan, execute, review, and prove the result.
+- One process for different CLIs: adapter-specific commands stay outside the
+  core, and new adapters can be added without changing lifecycle schemas.
+- Small-model friendly packets: compact context, clear next actions, and
+  deterministic checks for local or cheaper models.
+- Quality without overengineering: optional profiles turn on only when risk or
+  task type requires them.
+- Usage visibility: tokens, time, and resource counters are native; monetary
+  cost is optional and only used when a metered host reports it.
+- Read-only progress and managed sessions: host UIs can show lifecycle state,
+  attested tokens and Git-style change counters; `adapter task start` accepts
+  task text, Markdown or frozen run requests while preserving review/freeze
+  boundaries.
+
+## Feature areas
+
+### Plan and execute
+
+- Reviewed specification and plan flow before implementation starts.
+- Deterministic task packets for splitting work across agents.
+- Execution records capture completion checks, blockers, retries, and final
+  proof; missing required evidence fails the step.
+- Ready-made task templates cover bug fixes, idea-to-PR flow, PR review,
+  merge-conflict repair, and release-readiness work.
+
+### Quality and proof
+
+- Implementation audits compare results with the frozen plan and acceptance
+  evidence.
+- For explicit bug and regression repair, the optional Bug Forensics profile
+  records reproduction, fingerprint, failure class, hypotheses, minimal patch,
+  regression proof, and reusable recipes.
+- Optional proof-integrity evidence for high-risk final proofs: stable findings,
+  root-cause digests, fix-impact receipts, and hash chains.
+- Cross-checks and runtime-policy receipts are opt-in controls; plans can
+  require proof for an external system update before acceptance.
+- Optional Review Mesh covers leader-draft review, parallel research synthesis
+  and audit panels. The advisor can suggest a mode; `review-mesh prepare`
+  creates local reviewer packets; opted-in plans can require
+  assignment/result/synthesis/quorum receipts, but ALK core does not start hosts.
+
+### Routing and resource control
+
+- Compact context profiles, small-model packets, objective snapshots, and
+  local quality-cost learning help choose the lightest safe mode.
+- Phase resource measurements reuse the usage export envelope for tokens,
+  duration, and resource counters without mandatory monetary accounting.
+- Usage/session exports include tokens, resources, receipt digests, and optional
+  host-reported `cost_usd`.
+
+### Security and containment
+
+- Neutrality filters use host-supplied deny rules to keep local paths, secrets, trust roots, and signing keys out of portable artifacts.
+- Host env files require explicit `--host-env-allow`; receipts store redacted metadata, not secret values or private env-file paths.
+- Imports, diagnostics, and usage exports redact local paths and common secret markers before validation.
+- Sandbox receipts separate runtime filesystem, network, process, and environment containment from git write-scope.
+- Release security gates reject leaked local paths, credentials, and unsupported adapter or production claims.
+
+### Adapters and interop
+
+- Adapter contracts keep host-specific projections separate from lifecycle
+  schemas.
+- New CLI hosts start as adapters: descriptor, command projection, environment
+  boundary, and verification evidence live outside the lifecycle core.
+- Adapter capability checks and progress bridge support compare live receipts
+  and display lifecycle state without automatic maturity changes.
+- Import mappers and issue-to-spec intake treat external workflows, agent
+  dialects, and tickets as untrusted draft inputs.
+- Lightweight episode retrieval over receipt/session summaries keeps digest
+  provenance and explicit `chainVerified` or `chainUnchecked` state.
+
+### Operations
+
+- Runner recovery receipts cover attempt snapshot, restore, abandon, selected
+  attempt, worker lease, and heartbeat state.
+- Read-only diagnostics, event feeds, managed lifecycle steps, progress watch
+  receipts, and change summaries inspect checkout and workflow state without
+  model calls.
+
+## Daily flow
+
+Spec -> frozen plan -> bounded work -> implementation audit -> final proof.
+Core commands cover specification, plan, workflow, audit, adapters, imports, metrics,
+policy, diagnostics, runner state, and adapter task intake. See [CLI reference](docs/reference/cli.md) and [Source of truth](docs/reference/source-of-truth.md).
+
+## Adapter maturity
+
+`EXPERIMENTAL` means offline checks exist; bounded live host conformance and
+usage/resource calibration are still required before `VERIFIED`. The verified
+claim is host-specific and also requires accepted redacted evidence and
+lifecycle final proof for the tested host range. New hosts can be added as
+adapters first and promoted only for the exact CLI/version/provider binding that
+has evidence. Monetary accounting is required only for metered modes.
+
+| Host | Current claim |
+| --- | --- |
+| Codex | `VERIFIED` for Codex CLI 0.145.0. Public Plugins Directory approval is not claimed. |
+| Claude Code | `VERIFIED` for Claude Code 2.1.220. Official directory approval is not claimed. |
+| OpenCode | `VERIFIED` for OpenCode CLI 1.18.9. npm publication is not claimed. |
+| Hermes | `VERIFIED` for Hermes Agent v0.19.0. Public directory approval is not claimed. |
+| Qwen Code | `VERIFIED` for Qwen Code 0.21.0 on the tested host-local provider/model binding. Public package approval is not claimed. |
+| Cursor | `EXPERIMENTAL`; local safe inspection passed, but accepted live receipts are incomplete. |
+| Gemini CLI | `EXPERIMENTAL`; local live canary is blocked by the current Gemini Code Assist tier. |
+| Goose | `VERIFIED` for Goose 1.45.0 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| Kimi Code | `EXPERIMENTAL`; live proof requires a configured provider and model alias. |
+| Grok Build | `VERIFIED` for Grok Build 0.2.117 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| OpenInterpreter | `VERIFIED` for `interpreter` 0.0.34 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+| Pi | `VERIFIED` for Pi 0.83.0 on the tested host-local provider/model binding. Public directory approval is not claimed. |
+
+Adapter installation and maturity details live in [Adapter install](docs/adapters/install.md) and [Adapter support matrix](docs/adapters/support-matrix.md).
+
+## Contract map
+
+The public lifecycle surface is schema-backed. Full stable schema ids, compatibility rules, runner recovery, cross-check, Review Mesh, Bug Forensics and usage export details are listed in [Public contracts](docs/reference/public-contracts.md).
+
+## Design boundaries
+
+- The core stays provider-neutral. Concrete host commands and model bindings
+  belong to adapters or host-local profiles.
+- New CLIs are integrated through adapters: descriptor, command projection,
+  environment boundary, and verification evidence. The lifecycle schemas remain
+  stable while host support grows.
+- Small models get compact packets, deterministic checks, and explicit
+  next-action lists instead of long narrative state.
+- Larger models keep the same gates; better reasoning does not bypass evidence.
+- Public release claims are limited to tracked source files and redacted
+  evidence summaries.
+- External dialect imports and retrieved episodes are context aids only; they
+  do not replace reviewed ALK source-of-truth artifacts.
+- Optional cross-check, Review Mesh and runner recovery receipts add evidence
+  only when a task or plan requests them; they are not default multi-model execution.
+
+## Documentation
+
+- Start: [English documentation](docs/README.md), [Русская документация](docs/ru/README.md), [Quickstart](docs/guides/quickstart.md), [Lifecycle cookbook](docs/guides/lifecycle-cookbook.md), and [Code review workflows](docs/guides/code-review-workflows.md).
+- Planning and adapters: [Issue to specification drafts](docs/guides/issue-to-spec.md), [Adapter install](docs/adapters/install.md), and [Adapter support matrix](docs/adapters/support-matrix.md).
+- Reference: [System architecture](docs/architecture/system-architecture.md), [CLI reference](docs/reference/cli.md), [Source of truth](docs/reference/source-of-truth.md), [Managed lifecycle runner](docs/reference/managed-lifecycle-runner.md), [Managed adapter sessions](docs/reference/managed-adapter-sessions.md), [Implementation audit](docs/reference/implementation-audit.md), [Plan completeness](docs/reference/plan-completeness.md), [Public contracts](docs/reference/public-contracts.md), and [Readiness diagnostics](docs/reference/readiness-diagnostics.md).
+- Quality and resources: [Small-model packets](docs/reference/small-model-packets.md), [model routing](docs/reference/model-routing.md), [adaptive policy](docs/reference/adaptive-lifecycle-policy.md), [quality-cost learning](docs/reference/quality-cost-learning.md), [lifecycle cost accounting](docs/reference/lifecycle-cost.md), [Usage export](docs/reference/usage-export.md), and [Evidence integrity](docs/reference/evidence-integrity.md).
+- Profiles and operations: [Read-only status views](docs/reference/read-only-status-view.md), [Adapter progress bridge](docs/reference/automatic-progress-bridge.md), [Sandbox boundaries](docs/reference/sandbox-boundaries.md), [Import mappers](docs/reference/import-mappers.md), [Episode retrieval](docs/reference/episode-retrieval.md), [Runner recovery](docs/reference/runner-recovery.md), [Cross-check profile](docs/reference/cross-check-profile.md), [Review Mesh](docs/reference/review-mesh.md), [Bug Forensics profile](docs/reference/bug-forensics.md), and [Bug Forensics context budget](docs/reference/bug-forensics-context-budget.md).
+- Release assets: [Task templates](templates/tasks/README.md) and [Release security](docs/security/release-security.md).
+
+Apache-2.0. See [LICENSE](LICENSE).

agent_lifecycle_kit-1.50.1/pyproject.toml

@@ -0,0 +1,49 @@
+[build-system]
+requires = ["setuptools>=70,<81", "wheel>=0.42,<1"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "agent-lifecycle-kit"
+version = "1.50.1"
+description = "Provider-neutral lifecycle control layer that helps coding agents plan, execute, validate, and prove software tasks to completion."
+readme = "README.md"
+requires-python = ">=3.11,<3.14"
+license = { text = "Apache-2.0" }
+authors = [{ name = "Agent Lifecycle Kit contributors" }]
+keywords = [
+  "adapter-conformance",
+  "agent-lifecycle",
+  "agent-workflows",
+  "agents",
+  "ai-agents",
+  "audit",
+  "coding-agents",
+  "lifecycle",
+  "model-routing",
+  "planning",
+  "sdd",
+  "software-delivery",
+  "task-orchestration",
+  "workflow",
+]
+classifiers = [
+  "Development Status :: 5 - Production/Stable",
+  "Intended Audience :: Developers",
+  "License :: OSI Approved :: Apache Software License",
+  "Programming Language :: Python :: 3",
+  "Programming Language :: Python :: 3.11",
+  "Programming Language :: Python :: 3.12",
+  "Programming Language :: Python :: 3.13",
+  "Typing :: Typed",
+]
+dependencies = []
+
+[project.scripts]
+agent-lifecycle = "agent_lifecycle.cli:main"
+agent-lifecycle-neutrality = "agent_lifecycle.neutrality.cli:main"
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+agent_lifecycle = ["py.typed"]

agent_lifecycle_kit-1.50.1/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

agent_lifecycle_kit-1.50.1/src/agent_lifecycle/__init__.py

@@ -0,0 +1,5 @@
+"""Agent Lifecycle Kit public package."""
+
+from ._version import __version__
+
+__all__ = ["__version__"]

agent_lifecycle_kit-1.50.1/src/agent_lifecycle/__main__.py

@@ -0,0 +1,5 @@
+"""python -m agent_lifecycle entry point."""
+
+from agent_lifecycle.cli import main
+
+raise SystemExit(main())