ship

name	ship
description	Update project documentation, clean up dead code, and commit all changes.

What to do

1. Run git diff HEAD and git status to understand exactly what changed.

2. Always update CHANGELOG.md with a new entry at the top of the file (below the # Changelog heading). Use today's date from the currentDate context variable.

   Follow this exact format — no deviations:

   ## YYYY-MM-DD — [short title, 3–6 words]
   
   **Why:** One or two sentences explaining the problem or motivation.
   
   **What:** Concrete description of what was changed. Use a bullet list if multiple things changed. Reference specific function names, selectors, or file names where relevant.
   
   **Decision:** The reasoning behind the chosen approach — what alternatives were considered and why this was preferred. Omit this section only if there was genuinely no meaningful decision to document.
   
   **Files:**
   - `path/to/file.js` — one-line description of the role it plays
   
   ---
   

   The title after the date should describe what changed, not why (e.g. "Pathname guard for /sites/* only", not "Fix script running on wrong pages").

3. Always update the features list in src/js/modules/help-button.js if any feature was added, removed, or renamed. The list lives inside buildHelpButton() in the <ul class="d2c-help-list"> block. Keep it in the same order as the README Features list. Rebuild (npm run build) after editing so dist/d2c-enhancements.js reflects the change — include the dist file in the commit.

4. Update README.md only if any of the following changed:

   • A feature was added, removed, or renamed (update the Features list)