mycogit-release-provenance-reconcilerlisted

# Git Release Provenance Reconciler A comprehensive system for tracking Git lineage and release state in squash-heavy workflows. This skill covers the complete lifecycle from initial configuration through ongoing maintenance of Git-aware release provenance tracking. ## Prerequisites - Working Git repository with release tags and integration branches - Understanding of squash-merge workflows and their impact on commit ancestry - Access to Git subprocesses and ability to parse `git for-each-ref`, `git show`, and patch-ID commands - Database schema support for release state tracking and knowledge graph propagation ## Procedure A: Initial Setup and Git-Aware Defaults Set up release provenance configuration with intelligent defaults inferred from the local Git environment. 1. **Infer GitHub repository information**: ```bash git remote get-url origin # Parse owner/repo from GitHub URL ``` 2. **Configure production release refs**: - Look for project-scoped tag families (e.g., `refs/tags/myco/v*`) - Fall back to standard versioning (`refs/tags/v*`) - **Critical**: Always use fully qualified refs, never bare names 3. **Set up integration refs**: - Resolve `origin/HEAD` to find default branch - Fall back to `origin/main`, `origin/master`, or other common remote branches - **Gotcha**: Writing `main` instead of `origin/main` causes silent reconciliation failures 4. **Populate configuration**: ```yaml production_refs: [refs/tags/myco/v*] i