test(reset): let a personalized profile carry its own ## sections (#676)

* test(reset): let a personalized profile carry its own ## sections

test_full_file_skeletons_keep_the_shipped_headings compares /reset's
skeleton with the ## headings of 01-candidate-profile.md and
02-behavioral-profile.md exactly. On a fork those files are the user's
populated profile, so adding one section of their own (Certifications,
say) fails the suite on the fork's CI and in local runs, though /reset
is fine.

Off upstream (is_upstream_checkout(), as the placeholder and
template-token guards already use) the check now requires every skeleton
heading to appear in the file in order, so a renamed, dropped or
reordered template heading still fails. Upstream keeps the exact
comparison. A new test pins the in-order helper, since the fork branch
never runs in upstream CI.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* changelog: place the #676 entry under [Unreleased]

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
Co-authored-by: Mads Lorentzen <madslorentzen_17@hotmail.com>

CHANGELOG.md

@@ -165,6 +165,13 @@ per-file diff commands.
   path now counts as removed when its nearest ancestor directory exists at the base but not
   in HEAD; a new file or subdirectory under a directory the fork kept is still worth reviewing.
 
+- **The `/reset` skeleton test lets a fork's profile carry its own `##` sections** (#676,
+  `tests/test_reset_command.py`) - it compared `/reset`'s `##` headings with
+  `01-candidate-profile.md` and `02-behavioral-profile.md` exactly, so a fork that added a section
+  to its own profile failed its CI and local runs although `/reset` worked. Off upstream it now
+  requires every shipped heading to appear in order, so an added section passes and a renamed,
+  dropped or reordered one still fails; upstream keeps the exact comparison.
+
 ## [1.7.3] - 2026-10-19
 
 ### Added