## Summary The README and five docs pages still describe CCC as a beta, or promise a later release. That is already wrong for the release candidates, and it will be wrong for 1.0.0. Releases add no commits, so this must merge before the 1.0.0 tag. Use wording that is true both before and after the tag: describe the release policy from 1.0.0, not the current release. Places: * `README.md:3-6`: "This module is currently in beta. APIs and configuration may change between releases..." * `docs/index.md:16-22`: the heading "## Beta status {#beta-api-stability}" and the same text. * `docs/developers/api-stability.md:19-22`: "While the module is in [beta](../index.md#beta-api-stability), public APIs may still change... Once the module reaches a stable release, the boundaries on this page describe the supported surface." This paragraph links to the anchor above. * `docs/upgrade-policy.md:39-45`: the heading "## Beta status and release line" and "CCC is currently in **beta** on the `1.0.x` branch." * `docs/upgrade-policy.md:69-72`: "Sites **may** upgrade directly to the latest beta or release candidate..." * `docs/upgrade-policy.md:156-160`: "**Before 1.0 stable:** report regressions..." and "discovered after a beta release". * `docs/developers/configuration.md:213-214`: "planned for 1.1" (linked to #3586357+s). The 1.1 scope is being planned again, so do not name a version. * `docs/features/usage_tracking.md:6-8`: the note "Future observability integration" says "AI observability will be integrated later, which will replace the current functionality." The decision is still open in #3567803+s. ## Proposed resolution * `README.md`: replace the paragraph with: "From 1.0.0, public APIs follow the deprecation policy in [API stability](docs/developers/api-stability.md). See the [Upgrade and compatibility policy](docs/upgrade-policy.md) for supported versions and for upgrades from beta and release candidate versions." * `docs/index.md`: rename the heading to "## Release status and API stability {#api-stability}" and use the same text as the README, with links relative to `docs/`. * `docs/developers/api-stability.md:19-22`: replace the paragraph with: "From 1.0.0, the public APIs on this page follow the deprecation policy below. Check the release notes when you upgrade." Update the link to `../index.md#api-stability`, or remove it. * `docs/upgrade-policy.md`: rename the heading to "## Release line" and replace the first sentence with: "CCC releases come from the `1.0.x` branch. Beta and release candidate versions before 1.0.0 could include schema updates, configuration changes and API adjustments." Keep the rest of the section. * `docs/upgrade-policy.md:69-72`: change "the latest beta or release candidate" to "1.0.0 or a later 1.0.x release". Keep the rest of the section about running all pending updates. * `docs/upgrade-policy.md:156-160`: remove the "Before 1.0 stable:" prefix, so the line says to report regressions with the versions and update numbers. Change "after a beta release" to "after a release". * `docs/developers/configuration.md:213-214`: change "planned for 1.1" to "planned", and keep the link to #3586357+s. * `docs/features/usage_tracking.md:6-8`: replace the note with: "Usage tracking is intentionally lightweight. It records which context items consumers select, not full AI request logs." Do not promise a replacement until #3567803+s is decided. * Keep the historical upgrade notes: the "Beta upgrade: ..." sections and the "before the 1.0.0 stable release" notes in `api-stability.md`, the Beta4 import notes in `configuration.md`, and the beta3 and beta5 repair notes in `upgrade-policy.md`. They help sites that upgrade from a beta. ## Remaining tasks * [x] Make the changes above (!349). * [x] Search `README.md` and `docs/` for "currently in beta" and `beta-api-stability`. There must be no results. * [x] Build the docs with MkDocs and check that the changed links work. `mkdocs build --strict` passes; `mkdocs.yml` now also enables `admonition`, so the notes show as note boxes. * [x] No code changes, no tests. > [!note] > Check the one that best describes your usage, or leave all unchecked if AI was not significantly used. > > * [ ] AI **Assisted Issue** \ > _Mainly written by a human; AI used for partial generation under full human supervision._ > > * [x] AI **Generated Issue** \ > _Mainly generated by AI, reviewed and approved by a human before this issue was created._