This release has been yanked by its maintainers, and will be ignored by installers, except when explicitly specified.
Reason given by maintainers: Retired. spec-kitty-runtime was internalised into spec-kitty-cli (ADR 2026-04-25, shared-package-boundary-cutover). This release pins spec-kitty-events==3.3.0 and downgrades spec-kitty-cli when co-installed. Remove it from your environment; nothing replaces it.
spec-kitty-runtime
Canonical mission runtime for Spec Kitty.
Scope (V1)
- YAML mission template loading.
- Deterministic mission discovery with precedence tiers.
- Deterministic step planner and mission
next()execution loop. - Prompt rendering for agent runtimes.
Public API
load_mission_template(path_or_key, context=None)discover_missions(context)start_mission_run(template_key, inputs, policy_snapshot, context=None, run_store=None)next_step(run_ref, agent_id, result="success", policy_snapshot=None, actor_context=None, context=None)render_prompt(decision, format="markdown")
Runtime Event Emitter API (v0.2.0a0)
RuntimeEventEmitter uses canonical payload-object methods aligned to
spec-kitty-events mission-next contracts:
emit_mission_run_started(payload)emit_next_step_issued(payload)emit_next_step_auto_completed(payload)emit_decision_input_requested(payload)emit_decision_input_answered(payload)emit_mission_run_completed(payload)
NullEmitter is the default no-op implementation for local-first/offline flows.
Step Context Contracts (V1)
Mission steps declare their context requirements using step context contracts:
- requires: Contexts that MUST resolve before execution
- optional: Contexts that may enrich but aren't blocking
- emits: Contexts produced/updated on completion
See docs/contracts.md for the complete reference, V1 baseline context types, and integration guide for spec-kitty 2.x.
Mission Pack Layout (YAML-only)
mission-pack.yaml
missions/<mission_key>/mission.yaml
missions/<mission_key>/templates/*.md
missions/<mission_key>/steps/*.yaml # optional
Metadata
Release files for spec-kitty-runtime 0.4.5
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| spec_kitty_runtime-0.4.5.tar.gz | 94.6 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| spec_kitty_runtime-0.4.5-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 137.8 kB
Release files / spec_kitty_runtime-0.4.5.tar.gz
| Download URL | spec_kitty_runtime-0.4.5.tar.gz |
|---|---|
| Size | 94.6 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
becaaca40bf693181d7d704c98acd304b1af9b294d9bdb78bccf7e950e456c65
|
|
BLAKE2b-256 checksum How to use checksums |
f0e423a7df6942d9940569ecab00205af5dba404aa29d8a7bd7149c0887251e7
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 22, 2026.
Transparency logRelease files / spec_kitty_runtime-0.4.5-py3-none-any.whl
| Download URL | spec_kitty_runtime-0.4.5-py3-none-any.whl |
|---|---|
| Size | 43.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
3d02c925146c59244e96a1d89f19da8c7e79a9c3d66cf069fb737f7462a6abfc
|
|
BLAKE2b-256 checksum How to use checksums |
8b61407302855049cb90ff9b3165008ce4ce3d1bb64baebc2692cb889157332e
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.12
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Apr 22, 2026.
Transparency log