CodePen fork does not reflect updates to the parent Pen

CodePen fork does not reflect updates to the parent Pen

A forked Pen is intended as a point-in-time copy of an original Pen, preserving code, preprocessor settings, and metadata. The goal is to determine whether CodePen documents any mechanism to keep a fork linked to its parent, propagate later edits from the parent, or detect drift between the two.

This assumes current CodePen Pen editor behavior; Projects, Collections, and embedded Pens are out of scope. Forks appear to be immutable snapshots that do not automatically update when the original Pen changes. It is unclear whether privacy settings and preprocessor versions are inherited consistently, or whether a fork can render differently from the parent without manual edits.

Does CodePen provide a documented way to sync a fork with its parent Pen? Is there a supported method to detect drift between a fork and its original? Are fork privacy and preprocessor settings guaranteed to match the parent at fork time?