@campminder/components 0.7.0 → 0.7.1

package/dist/side-nav/SideNav.d.ts

@@ -85,14 +85,12 @@ export declare class SideNav extends LitElement {
      * `MenuTree` (`../menu-tree`, generic — see that file's move note) instead. Icon binding is the only
      * piece of that pipeline still intrinsic to rendering; see `icon-map.ts`.
      *
-     * Not sorted here. core-js's `sortCategoriesData` sorted by `sort_order` then
-     * name at every level because the base64 fixture arrived unsorted; verified
-     * 2026-09-02 that the committed `campminder.json` categories are already in
-     * `sortOrder` order on disk, and `drift.test.ts` pins that order — so imposing a
-     * second sort here would just be a no-op that could silently start doing
-     * something the day the JSON stops being pre-sorted. If that's ever untrue, the
-     * fix belongs where the JSON is authored, not in a render-time sort this
-     * component would then always pay for.
+     * Not sorted here: the tree arrives in display order. System sorts by `sortOrder`
+     * then name, at every level, on the label the camp actually sees, so the order
+     * depends on each camp's terminology and cannot be fixed in the committed JSON.
+     * The server does it in `getFilteredMenu`, after terms resolve (AB#29742). The
+     * raw tree exported for client use (`CAMPMINDER_TREE`, `loadCampminderTree`) is
+     * neither resolved nor sorted; a host rendering it directly gets on-disk order.
      */
     tree: MenuTree;
     /**

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@campminder/components",
-  "version": "0.7.0",
+  "version": "0.7.1",
   "type": "module",
   "publishConfig": {
     "access": "public"