Remove get_reputation and release 2.7.0

[vvillait88]

Summary

GET /v1/reputation was retired on 2026-09-30 along with the transaction pipeline, and the API now answers 404 on it. This removes get_reputation() / aget_reputation() and the types only they returned, and releases 2.7.0.

• get_reputation() and aget_reputation() are removed.
• The reputation response types are removed from agentscore.types and the package exports: ReputationResponse, Reputation, Score, ChainScore, ChainEntry, Classification, RedactedClassification, Subject, Identity, Activity, EvidenceSummary, OperatorScore, AgentSummary, Grade, EntityType, ReputationStatus. AssessResponse is unchanged.
• The create_session docstrings no longer call it "an assessment session for deferred scoring".
• README, .claude/CLAUDE.md and the package keywords no longer describe a reputation lookup.
• Dependencies: ruff 0.16.10, python-dotenv 1.2.4, lefthook 2.1.16. Workflows move to uv 0.12.22.

Versioned as a minor on purpose: the method has returned 404 since the endpoint was retired, so no working call changes behavior. Code that still references it raises AttributeError after upgrading.

Type of change

• Bug fix (no breaking change)
• New feature (no breaking change)
• Breaking change (existing callers must update)
• Docs, tests, or internal maintenance only

Public API

AgentScore.get_reputation(), AgentScore.aget_reputation() and the reputation types listed above are removed. Migration: drop the call. The endpoint behind it no longer exists, so there is no replacement; assess() / aassess() remain the identity and compliance check.

Test plan

• The generic request tests (error mapping, context managers, concurrency, retries) used get_reputation as their vehicle and now run through list_credentials() / alist_credentials(), so that coverage is kept.
• The assess and session-poll fixtures now carry the shapes the API returns, not score and chain bodies. A policy test that sent a nonexistent min_score key now sends require_kyc.
• A new test pins that both methods are absent from the client.
• uv run pytest (177 passed, 2 integration skipped without credentials, 99.8% coverage), ruff check, ruff format --check, ty check and vulture all pass locally. The OSV scan of uv.lock is clean.

Worked with Varun.

Checklist

• Tests cover the new behavior, and the suite passes locally
• Lint, format, and type checks pass
• Docs and README examples updated if the public surface changed
• No secrets, credentials, or personal data in the diff or the tests