[botinc-agent]

Problem

The repository's release contract no longer matched what it ships. AGENTS.md and CLAUDE.md still said 1.0.0, although 1.0.1 was released on 2026-10-29. The README's versioning section still described the pre-1.0 rule ("until 1.0.0, breaking changes bump the minor version") on a 1.x package. The release-please.yml header claimed a person publishes a draft release after approval, contradicting the automatic flow in CONTRIBUTING.md and DESIGN.md section 13: merging the release pull request is the approval, and release-please then tags, releases and starts the NuGet publish.

Solution

• Corrected the release status in AGENTS.md and CLAUDE.md to 1.0.1.
• Rewrote the README versioning sentence so it states normal semantic versioning from 1.0.0 onward.
• Rewrote the stale release-please.yml header comment to describe the shipped automatic flow; no workflow logic changed.

No generated code, public API or package contents changed.

Verification

• dotnet build Didit.sln -c Release: 0 warnings, 0 errors.
• dotnet test on net8.0, net9.0 and net10.0: 897 passed on each.
• python3 codegen/generate.py --check: 1,973 generated files current; 26 codegen tests pass.
• dotnet format --verify-no-changes is clean; both NuGet packages pack.
• Quickstart ran create, decision and webhook verification end to end against a local mock; the Authentication example served /me 401 and a PKCE /login redirect against a local issuer stub.
• Live staging returned the expected typed 401 for an invalid key.

Live session create/retrieve on staging was not run: this checkout has no sandbox API key. Its smoke test covers that path when DIDIT_SANDBOX_API_KEY is set.