Upstream synchronization¶
CCB shares history with other Cataclysm-family repositories but is not a mirror. An upstream commit is evidence and source material, not authority over CCB runtime behaviour.
Record provenance before editing¶
- source repository, PR or issue, and exact commit range;
- original authors and applicable license;
- reason for the port and the CCB problem it addresses;
- files and behaviour intentionally omitted or rewritten;
- known CCB divergence and expected conflict areas.
Preserve attribution in commit messages and pull-request notes. Do not collapse several upstream changes into an untraceable patch.
Review the CCB boundaries¶
Compare registrations, data IDs, serialization, mod loading, EOC context, Lua v5 public contracts, UI/input, desktop/Android configuration, and tests. Search for later upstream fixes to the source change, but evaluate them separately. Passing an upstream test suite does not establish CCB compatibility.
Validate and document¶
Run the smallest CCB test that proves the intended behaviour, then expand for shared core, save, data, API, or platform risk. Document intentional divergence in code comments only where it prevents a future incorrect re-port; put the full explanation in CCB-Docs and link the exact source.
A port is ready only when its source is auditable, the final CCB diff is understood, compatibility impact is explicit, and a Responsible human owns the result.