Complete post-v1.0 release closure

[ElvinMorales]

Goal

Close the loop on the agent-librarian v1.0 release candidate.

Type

release / docs

Priority

P1

Taxonomy bucket(s)

• Knowledge and resources
• Evaluation and observability
• Runtime and deployment
• Learning and iteration

Why this matters

The repo now presents a mature v1.0 posture, but release-prep artifacts still separate repo readiness from maintainer-only release actions. This issue prevents ambiguity between “release-ready” and “actually tagged/released.”

Proposed change

Confirm whether v1.0.0 has been tagged and published. If yes, update release language as needed and capture any portfolio follow-up separately. If no, complete the manual release checklist before public communication.

Files likely affected

• docs/releases/v1.0.0-release-checklist.md
• CHANGELOG.md
• README.md
• possible follow-up issue in the profile repo

Acceptance criteria

• Maintainer confirms tag and GitHub Release state.
• Release checklist reflects the actual release state.
• README stays clear about what the project does and does not claim.
• Any portfolio follow-up is captured separately.
• No unexpected generated outputs are added.

Validation checks

python -m pytest --basetemp=.tmp/pytest-basetemp -o cache_dir=.tmp/pytest-cache
python scripts/check_packages.py
python scripts/check_source_snapshot.py examples/source-snapshots/synthetic-team-space
agent-librarian --version
git diff --check

Public-safety notes

Keep release language public-safe and avoid adding private examples, private generated outputs, live integration details, or sensitive configuration.

Suggested labels

release, docs, v1.0.0

Suggested branch name

release/v1-post-release-closure

Suggested commit message

release: close v1.0 release checklist