agent-spec 1.2.0

Intent compiler for AI agent coding: human intent compiles through requirement IR into verifiable task contracts, mechanically verified against the code
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58

# Release Process

agent-spec publishes three Cargo packages from one workspace. Release commits
must keep their dependency versions, changelog, user documentation, and
`Cargo.lock` consistent.

## Version Policy

- `agent-spec` follows stable semantic versioning for the CLI and documented
  machine contracts.
- `rust-atlas` is independently versioned. While it is below 1.0, graph schema
  or public API changes require a minor version bump.
- `agent-spec-code-graph-provider` is independently versioned. Its Cargo API,
  wire schema ids, and provider IR range are separate compatibility gates.
- Atlas graphs, indexes, bindings, and receipts are derived artifacts. Release
  notes must state whether an upgrade requires `agent-spec atlas build --full`.

## Release Gate

From the release PR worktree, run:

```bash
cargo fmt --all -- --check
cargo test --workspace --all-features
cargo clippy --workspace --all-targets --all-features -- -D warnings
cargo package -p agent-spec-code-graph-provider --allow-dirty
cargo package -p rust-atlas --allow-dirty
bash scripts/docs-lint.sh
cargo run -q -- atlas build --code . --graph .agent-spec/graph
cargo run -q -- atlas check --code . --graph .agent-spec/graph
cargo run -q -- lint-knowledge --knowledge knowledge --gate
cargo run -q -- requirements graph --knowledge knowledge --format json --gate
cargo run -q -- wiki check --code . --wiki .agent-spec/wiki
```

Run the active release Task Contracts with `agent-spec lifecycle`. Review the
package file lists so fixtures, runtime state, build output, and secrets are not
included. Use `--allow-dirty` only in the release PR worktree; the merge commit
and tagged checkout must be clean.

## Publish Order

Publish dependencies before the root binary:

1. `cargo publish -p agent-spec-code-graph-provider`
2. Wait until version resolution succeeds from crates.io.
3. `cargo publish -p rust-atlas`
4. Wait until version resolution succeeds from crates.io.
5. `cargo package -p agent-spec`
6. `cargo publish -p agent-spec`

The root package verification can require the newly published dependency
versions. Do not use `--no-verify` to bypass that ordering.

After publication, create and push the signed `v<agent-spec-version>` tag,
publish GitHub release notes from `CHANGELOG.md`, and verify the crates.io and
docs.rs pages. Tags identify the workspace release; the changelog records the
independent crate versions included in it.