[vitormattos]

Summary

• Add a read-only maintainer-inbox skill for paginated contributor issue/PR follow-ups, with explicit ownership and coverage limits; distinguish external humans, bots and non-verified AI replies.
• Add a short, evidence-linked task handoff shared by review, CI diagnosis and issue execution so parallel chats can resume at current SHAs without repeating completed work.
• Harden stateful test preflight (database, app configuration, filesystem cleanup and disposable environments) and release handoff (merged versus prepared, finalized, published and reporter-notified), without duplicating the release engine.
• Add regression scenarios, structural assertions and updated plugin catalog/metadata.

Scope and boundaries

No automated publication, GitHub mutation or merge behavior is introduced. maintainer-inbox remains read-only. Release coordination delegates to the target project's existing release tooling. No personal account-specific tools, credentials, private services or identifiers are embedded in the published skills.

Validation

• python3 -m unittest discover -s tests -v: 16 passed
• reuse lint: 54/54 files compliant
• git diff --check: passed
• Two incremental commits, each verified for signature and DCO.

Review focus

• Skill activation boundary versus repository-health and review-pull-request.
• Whether the handoff is sufficiently concise to reduce context costs.
• Whether the stateful-test guidance is strong enough without forcing containers for ordinary unit tests.

No merge requested.