odcs 0.7.0

# Release status

Current release: **0.7.0** (on `main`, ready to publish).

## Version alignment

| Source | Version | Status |
|--------|---------|--------|
| `Cargo.toml` | **0.7.0** | Aligned |
| `pyproject.toml` | **0.7.0** | Aligned |
| `CHANGELOG.md` | **0.7.0** | Release notes present |
| Git tag | *(none yet)* | Push `v0.7.0` to publish |

## Registry status

| Registry | Latest published | After `v0.7.0` tag |
|----------|------------------|---------------------|
| [crates.io](https://crates.io/crates/odcs) | 0.6.0 | 0.7.0 (via release workflow) |
| [PyPI](https://pypi.org/project/pyodcs/) | 0.6.0 | 0.7.0 (via release workflow) |

## Install 0.7.0

### After release (crates.io / PyPI)

```bash
cargo install odcs --version 0.7.0 --locked
pip install pyodcs==0.7.0
```

### From source (before or after tag)

```bash
git clone https://github.com/eddiethedean/odcs.git
cd odcs
cargo install --path . --locked
maturin develop --features python --locked   # Python editable install
```

## Pin in CI

```bash
cargo install odcs --version 0.7.0 --locked
pip install pyodcs==0.7.0
```

See [CI/CD integration](../user/ci-cd.md).

## Publish checklist (maintainers)

Before pushing `v0.7.0`:

- [x] `Cargo.toml` / `pyproject.toml` = `0.7.0`
- [x] `CHANGELOG.md` has 0.7.0 release notes
- [x] Full CI parity passes locally (fmt, clippy, doc, test, pytest, mkdocs, publish dry-run)
- [ ] `main` CI green
- [ ] GitHub secrets `CARGO_REGISTRY_TOKEN` and `PYPI_API_TOKEN` configured
- [ ] No existing `v0.7.0` tag on remote

To publish:

```bash
git tag v0.7.0
git push origin v0.7.0
```

Monitor [Release workflow](../../.github/workflows/release.yml). See [Releasing](../maintainer/releasing.md) for post-release verification.

## What changed in 0.7.0

See [Changelog](../changelog.md). Highlights:

- Structural validation phase: unique `schema[].name` and `servers[].server` values
- `slaProperties[].element` and `slaDefaultElement` must reference existing schema object names (comma-separated tokens supported)
- Diagnostics use `validationPhase: structural` with `odcs:invalid-schema` or `odcs:unresolved-reference`
- Bug fixes: `slaDefaultElement` comma/trim parity, empty `id` dedup, quality no-type validation, Python CLI `phase:` output

## Previous release

**0.6.0** — `validationPhase` metadata on every validation-stage diagnostic (JSON + CLI text).