upgradelisted

# Upgrade GoC `goc upgrade` is deterministic and safe by construction — it never overwrites authored content under `.game-of-cards/`. That guarantee holds for every consumer regardless of whether an agent is present (headless CI runs, scheduled cron, scripted upgrades). But "never overwrite" is not the same as "stay current". Two files under `.game-of-cards/` ship real, evolving content that the upstream template may have changed across versions: - `README.md` — the hook-point catalogue documenting which content stubs and workflow hooks the skills consume, and where. - `config.yaml` — the runtime-neutral closure attestation config (`layer_2_project_dod`, `layer_3_goc_dod`) plus workflow options. If the engine has preserved a *diverged* copy of either, the engine itself has nothing to say about whether real upstream changes need to land in the consumer's local copy. **That is this skill's job.** For the 12 user-owned content stubs and workflow hooks, the engine's "preserved" verdict is the whole story — the templates ship blank by design, so there is nothing to reconcile. This skill confirms that to the user so they know nothing was lost. For the `AGENTS.md` / `CLAUDE.md` GoC marker block, the engine regenerates the goc-owned region wholesale via the marker-bounded merge (`<!-- BEGIN GOC vX.Y.Z -->` ��� `<!-- END GOC -->`). That region is goc-owned, not user-owned, so nothing to reconcile — this skill summarizes what methodology guidance changed across the upgrade so