What problem does it solve? Keeping a long-lived downstream fork current with its upstream repository is risky: merges can silently discard product-owned behavior, provenance gets lost, and historical evidence can be overwritten. This Skill provides a guarded, phased workflow that pins exact commits, isolates work in dedicated worktrees, and records append-only evidence for every refresh. ## Core Features & Use Cases - Phased convergence workflow: Orient, isolate, pin, inspect, apply, record, validate, and publish a fork refresh against a pinned upstream commit with full provenance. - Repository-owned policy boundary: Reads a repository adapter manifest (upstream/convergence-policy.json) and delegates conflict, contract, and governance semantics to a repository-local driver with inspect, record, and validate phases. - Safety guardrails: Refuses write phases on dirty worktrees, protected branches, ambiguous refs, mismatched upstream URLs, snapshot overwrites, or unreviewed executable code. - Use Case: A team maintains a fork of an open-source project and must integrate monthly upstream releases. Use this Skill to produce a conflict and residual report by lane, preserve named product contracts, record an evidence snapshot, and open a reviewed PR instead of pushing directly. ## Quick Start Use the upstream-convergence skill to refresh this maintained fork against its canonical upstream and report conflicts, governance changes, and the evidence snapshot.
