comparison · c_76e946cb1d07 (tommy-mor) vs c_db279f012399 (tommy-mor)
Side A performs a coherent semantic rename (canonical -> item/wire) across multiple modules and files, clarifying that ItemId is not a URL-canonicalization concept, along with doc comment improvements and test renames—this is real, lasting clarity work. Side B is a narrow CI/workflow tweak (npm OIDC publishing setup) that is useful but small, environment-specific, and not core project logic, making it lower lasting value to the codebase itself.
B makes a real CI/security change: OIDC trusted npm publishing (Node 22, newer npm, drop NODE_AUTH_TOKEN secrets). A is almost entirely terminology renames (canonical→item/wire, function/field renames, comment tweaks) plus removing a thin tilde_http_tail wrapper, with no meaningful behavior or design improvement.
Side B makes a functional CI/release change by updating the npm publishing workflow for OIDC trusted publishing: it moves to Node 22, upgrades npm to a version supporting OIDC, and removes reliance on repository NPM tokens during publish steps. Side A is primarily a terminology cleanup and API renaming (e.g. `pick_random_distinct_canonical` to `pick_random_distinct_item_pair`, `canonical` to `item`), with minor documentation edits and removal of an unused helper, which has much less lasting behavioral impact.
comparison · c_db279f012399 (tommy-mor) vs c_fc17a4aa31e6 (tommy-mor)
Side B is a real functional/UI fix that reworks post_header_meta to consolidate delete button placement, adjusts CSS flex layout in two themes, and refactors call sites—concrete, testable product code. Side A is a small CI workflow tweak (npm OIDC publishing config) which is useful infra maintenance but lower in lasting code value and scope compared to B's cross-cutting UI/logic change.
A modernizes the npm release path for OIDC trusted publishing (Node 22, npm upgrade, drop NODE_AUTH_TOKEN secrets), a lasting security/ops improvement to how packages ship. B only relocates the delete control into post header meta and adjusts flex CSS—useful UI polish, but a small layout refactor with less project-wide impact.
Side A updates the release workflow toward npm OIDC trusted publishing by moving to Node 22, upgrading npm to a version that supports trusted publishing, and removing reliance on injected NPM auth tokens in the publish steps. Side B is a clean UI refactor that relocates the delete button into the post metadata and adjusts CSS layout, but it primarily changes presentation rather than project infrastructure or release behavior.