Update CGP version to v0.8.0-alpha

[soareschen]

AI Overview

This PR is a single-commit release-preparation change that stamps the whole CGP tree as the pre-release of v0.8.0. It touches no source code and changes no public API, no macro behavior, and no wiring — every substantive edit is either a version string, a Cargo.lock regeneration, a publish flag, or a documentation reference. Across 46 files it is 139 insertions and 117 deletions, and the reader should treat it as a bookkeeping commit that declares "this tree is v0.8.0" rather than one that changes what any crate does.

High-level concepts

The core of the change is a lockstep version bump from 0.7.0 to 0.8.0-alpha. CGP keeps every crate on one version, declared once in the root workspace and referenced everywhere with { workspace = true }, so the bump is applied uniformly: the [workspace.dependencies] table in the root Cargo.toml moves every entry to 0.8.0-alpha, each crate's own [package] version follows, the few inter-crate dependencies that name an explicit version (such as the cgp-base-extra dependency inside crates/core/cgp-error/Cargo.toml) are updated to match, and Cargo.lock is regenerated so every recorded package version agrees. The -alpha suffix is deliberate — this tree is the pre-release of v0.8.0, not the final release, so nothing needs a further version edit when v0.8.0 actually ships.

A publishing-hygiene rule is introduced: the test crates are now excluded from cargo publish. The five crates under crates/tests/ each gain a publish = false line in their [package] table, so a workspace publish skips them and pushes only the real library crates to crates.io. This closes a gap where test-only crates could have been published alongside the library.

The documentation is updated to describe the new release status and the publish policy. The repository's AGENTS.md gains a new "Project status" section that states the tree is the upcoming v0.8.0, that the stable crates.io release is still v0.7.0 and is incompatible with this tree because v0.8.0 removed or changed legacy syntax, and that only the library crates are published while the test crates are marked publish = false. The "Conventions specific to this repo" section is revised in the same spirit: the lockstep version is now recorded as 0.8.0-alpha, and the convention note now instructs that a test-only crate also gets publish = false. Alongside this, the CGP agent skill and its reference documents have their standalone "this describes v0.7.0" version markers advanced to v0.8.0.

Overall structural changes

No source files move, are added, or are removed, and no public interface changes. The structural footprint is confined to manifest metadata and prose. In the manifests, the change is the version string in the workspace dependency table, in every crate's [package] block, and throughout Cargo.lock, plus the new publish = false flag on the five test crates. In the documentation, AGENTS.md grows a section and revises another, docs/AGENTS.md updates one version reference, and the skill files under docs/skills/cgp/ each move a lone v0.7.0 mention to v0.8.0. Nothing is renamed or relocated, and there are no test or fixture changes because behavior is unchanged.

Impacts

The change lands as the following concrete impacts, ordered roughly from most to least consequential.

• The workspace now identifies as v0.8.0-alpha. Anyone building or depending on this tree, whether through path dependencies inside the workspace or a future crates.io pre-release, resolves the new version, and the lockfile agrees so builds are reproducible.
• A workspace publish is now safe from leaking test crates. With publish = false on the five crates under crates/tests/, cargo publish --workspace publishes only the library crates and skips the test-only ones, so the release cannot accidentally include internal test scaffolding.
• The incompatibility with the stable line is documented. The new "Project status" note in AGENTS.md tells an agent or contributor explicitly that crates.io v0.7.0 is a separate, older line whose syntax must not be reconciled against this tree, preventing edits that would reintroduce removed legacy forms.
• The documentation and agent skill self-describe as v0.8.0. The skill's version marker and the reference documents now claim v0.8.0, so guidance an agent reads about "the current version" is consistent with the code it is working in.
• No functional impact. Because the PR changes only metadata and prose, there is no behavioral, API, or compilation-surface change for downstream code beyond the version number it resolves.