project-release-maintainerlisted

# Project Release Maintainer This is a composable project overlay. Add matching implementation guidance when source, build, or automation code changes. Compose with `documenter` when the main artifact is durable release, install, or contributor documentation. For review or planning, inspect and report without changing package contents, manifests, notices, or release state. Apply the workflow as edit instructions only when the user asks for those changes. ## When to use The change affects the shipped or published contract: package contents, install rules, release automation, shipped assets, license and notice files, release checklists, or documentation that must match those artifacts. ## Not for Use `documenter` alone for content-only edits that do not require reconciliation with shipped artifacts. For internal code changes with no release impact, use the matching principle skill and add `project-core-dev` only when repository- specific completion evidence is not concrete. Use `project-config-and-tests` for config contracts. Use `project-vendor-boundary` as primary for vendored source ownership, and compose both overlays when a vendor change also alters shipped metadata. ## Workflow 1. Inventory the existing release contract from package manifests, install rules, shipped assets, release automation, license and notice files, checklists, and public documentation. Identify the source of truth before editing. 2. Trace the requested change across only the affected