mycorelease-provenance-settingslisted

# Release Provenance Settings Configuration and Lifecycle Myco's release provenance system tracks which commits are included in each release by comparing Git refs. Configuring it correctly requires touching three layers: the ref settings (what counts as a release boundary), the GitHub credential (how Myco authenticates to enrich commit data), and the daemon config routes (how settings are scoped per-project). This skill covers the full configuration lifecycle. **Scope boundary:** This skill covers the *settings/configuration* side of release provenance. For the Git snapshot capture algorithm and the two-tier reconciliation logic, see `myco:git-release-provenance-reconciler`. --- ## Prerequisites - You understand Myco's three-tier config model (project, machine, Grove). See `myco:three-tier-config-architecture` if not. - The target Grove or project is already registered in the daemon. - For monorepo mapping: you know the package directories and the Git tag naming convention used for each package. - For config route work: you are working in `packages/myco/src/daemon/` and understand that `req.requestContext` carries per-request vault scoping. --- ## Procedure A: Select a Release Provenance Preset and Configure Refs Release provenance is defined by two Git refs — `productionRef` (marks shipped releases) and `integrationRef` (marks the integration branch, e.g., main). Standard presets pre-fill both: | Preset | productionRef | integrationRef | |---|---|---| | `tag-based`