Stability

What a penv 1.0 minor or patch release keeps as it is, what it may change, and the freeze from 1.0.0-rc.1 to 1.0.0.

From 1.0.0, a minor or patch release of penv keeps these as they are. Changing one takes a major version.

Kept	Listed in
Command names, arguments, flags, and the environment variables that alias them	`penv help --json`
Exit codes and error codes	Exit codes, error codes
JSON output, and the manifest versioned by its `schemaVersion`: fields are added, never removed or retyped	`penv help --json`
The `.env.schema` grammar: the @env-spec parts penv reads and the ones it adds	The .env.schema format
`.penv/config.toml` keys and the order value files layer in	Schema and types, environments and precedence
Install paths, release asset names, and the three ways to install	Install the CLI

Not covered

Not covered	Why
Text written for a person	Scripts read the JSON
`penv hook`, `penv lsp`	Their other side is a harness or an editor
The Copilot CLI guard	Experimental: Copilot publishes no schema for its config

1.0.0-rc.1 is 1.0.0 with its behaviour frozen. Until 1.0.0 only fixes land, each listed in the command line changelog.