chore(main): release gh-delta 0.5.0

[gh-delta-release]

🤖 I have created a release beep boop

0.5.0 (2026-08-05)

Features

• add seven neutral delta classes for agent feedback signals (49eba4f)
• explain the new classes in details, text output, and help (e3fe9be)
• extend neutral GitHub signals from the #23 audit (a679688)
• fetch base ref, labels, assignees, and review requests (730ce69)

Bug Fixes

• suppress additive-field detail rows on upgrade ticks (518331f)

Documentation

• catch operator docs up with the new classes and audit notes (0fc4c0c)
• document the new classes and compared fingerprint fields (8af1b84)
• rate-limit budget, unresolvable-reviewer placeholder, GHES opt-in stance (3b4e029)
• showcase review-requests-changed in the example artifacts (f5bb320)

Consumer notes

Everything is additive: report.schemaVersion stays 1.

New delta classes (7): review-requests-changed (pr; co-fires with review-changed when a submitted review satisfies the request), assignees-changed (pr, issue), base-changed (pr; expect mergeable: UNKNOWN churn while GitHub recomputes), became-conflicting (pr; best-effort like became-mergeable — sampling through the UNKNOWN window yields updated instead, gate on observed mergeable), converted-to-draft (pr), comments-removed (pr, issue).

Behavior change to check: relabeled now also fires for PRs (was documented issue-only through 0.4.x). Route on delta.entity, never on the class alone.

New fingerprint fields in from/to: PR base, labels, assignees, reviewRequests (sorted; teams as org/slug; unresolvable reviewers as literal ?); issue assignees. Upgrade-suppressed: old snapshots neither burst on first observation nor emit phantom null -> current detail rows.

New --detail shapes: assignees-changed / review-requests-changed reuse the relabeled set-diff (added/removed); base-changed is a field transition; comments-removed a numeric delta.

Delta ids shift once per item on its first post-upgrade delta (new compared fields enter to). Monitors on different versions emit different ids for the same observation — upgrade co-posting monitors together to keep cross-monitor dedupe intact.

Operational: PR page now costs 7 GraphQL rate-limit points (was 4), issue page 2; a typical tick is ~18 points against 5,000/hour per token — see the contract's Fetch limits section for how to spend less. Older GHES schemas may reject the new reviewRequests selection (fragment on Bot, Team.combinedSlug); github.com verified fine — if hit, the fix ships as an opt-in compat selection, not a default change.

---

This PR was generated with Release Please. See documentation.

[gh-delta-release]

🤖 Created releases:

• gh-delta-v0.5.0

🌻