# Eva-CLI V1.0 Capability Boundary (Historical)

> Language: English
>
> Published default: `docs/en/release/v1.0-known-limitations.md`
>
> Translation: [Simplified Chinese](../../zh-CN/release/V1.0已知限制.md)

Updated: 2026-07-14

Status: historical snapshot of commit `437087c`; not a current limitation inventory.

## Scope

V1.0 was an internal core-CLI capability milestone. It established a narrow, synchronous source-checkout path and the first stable CLI output contracts. The repository has no `v1.0` Git tag, so this document must not be read as evidence of a separately published V1.0 release.

Current implementation gaps are maintained in the [V1.x incomplete feature inventory](../planning/v1.x-incomplete-feature-inventory.md), not in this historical record.

![Eva-CLI release history boundary](../../../assets/release-history-boundary.svg)

## Version Context

| Signal | Meaning |
| --- | --- |
| V1.0 | Internal milestone commit `437087c`; no `v1.0` tag exists |
| V1.4 | Internal lifecycle milestone commit `909ab07`; no `v1.4` tag exists |
| V1.5.0 | Annotated tag `v1.5.0`, resolving to commit `74d85e7da58ac40ef5d30b38e2844dee503a44c0` |
| Current `main` | Cargo and CLI report `1.11.5-alpha`; later V1.12-V1.17 strings are legacy evidence IDs, not release tags |

## Implemented At The V1.0 Milestone

| Area | Historical boundary |
| --- | --- |
| CLI basics | `eva --version`, `eva version --output json`, `doctor`, `config validate`, and `inspect` |
| Basic execution | `eva run --example basic` through the `in_memory_v1.0` composition |
| Task diagnostics | Local `task status`, `task logs`, and `task cancel` records under `.eva/tasks` |
| Public output | Structured success/error envelopes, trace fields, and exit-code mapping |
| Runtime baseline | In-memory EventBus, Scheduler, AgentRuntime, controlled Lua host contract, `config.lint`, dead-letter diagnostics, and basic task logs |

These commands were synchronous and single-process. The basic example was a regression baseline, not a production runtime.

## Outside That Milestone

At commit `437087c`, the following were not implemented end to end:

- durable task/event storage and crash recovery;
- real Lua VM execution and hot reload;
- external Adapter, MCP, Skill, and hardware execution;
- discovery, memory, knowledge, backup, restore, snapshot, and upgrade workflows;
- background service management and packaged distribution.

Several of these areas now have controlled alpha implementations on `main`. Their present boundaries vary between callable behavior, filesystem durability, synthetic fixtures, library/test-only contracts, and missing production integration. This historical list therefore must not be reused as the current backlog.

## Evidence Limits

- The V1.0 milestone proved the source checkout and local regression path only.
- `.eva/tasks` was a local diagnostic format, not a durable public database contract.
- Architecture documents from that period described targets, not guarantees delivered by the milestone.
- Installer, signing, platform service, hardware, and external-provider evidence were not part of this snapshot.

## Related References

- [Current V1.x incomplete feature inventory](../planning/v1.x-incomplete-feature-inventory.md)
- [Current real-runtime implementation plan](../planning/v1.x-real-runtime-implementation-plan.md)
- [Current process upgrade boundary](../operations/process-level-upgrade.md)
- [V1.0.0 release notes record](release-notes-v1.0.0.md)
- [Version management](version-management-plan.md)