Focus: Update the library's public documentation to reflect the release: API reference, migration guides for breaking changes, and consumer guidance surfaced from the security review.

Produces: Documentation updates:

• API reference — regenerated or updated to match the released API surface
• Migration guide — if this is a major version with breaking changes, a clear upgrade path
• Changelog link — from the docs site back to the release changelog
• Security guidance — consumer-facing notes from the security review, integrated into relevant sections

Reads: API Surface, changelog, security report.

Anti-patterns (RFC 2119):

• The agent MUST update docs before announcing the release, not after
• The agent MUST NOT ship breaking changes without a migration guide
• The agent MUST integrate security guidance into the relevant API sections, not bury it in a security page consumers won't read

Focus: Publish the library to its target registry with a correct semver version, a complete changelog, and operational release metadata (tags, signed artifacts, provenance). Publishing is one-shot — once a version is out, it's out. Get it right before hitting publish.

Produces: A published release with:

• Version bump — following semver based on API surface changes since the last release
• Changelog entry — user-visible changes grouped by category (added, changed, fixed, security, removed)
• Git tag and release artifacts — signed where the ecosystem supports it
• Registry publish — to npm, PyPI, crates.io, Maven Central, or equivalent

Reads: API Surface (current and prior version), security report, development outputs, prior changelog.

Anti-patterns (RFC 2119):

• The agent MUST NOT publish if the version number doesn't match the semver impact of changes
• The agent MUST NOT skip the changelog entry — consumers depend on it
• The agent MUST NOT publish if the security review has unresolved high-severity findings without consumer guidance
• The agent MUST tag the git commit matching the published artifact