{"repo":"NousResearch/hermes-agent","public_id":"105659","display_label":"npm lockfile churn breaking desktop build stamps","summary":"Fixes and a related bug report focused on preventing npm lockfile churn from invalidating desktop build stamps and causing repeated update autostashes, especially on Windows.","subsystem":"hermes_cli","counts":{"members":4,"open_issues":1,"open_issues_distinct":1,"open_prs":2,"closed_issues":0,"merged_prs":0,"attempt_prs":3},"landed_fix":null,"resolution":{"state":"unresolved","by":null},"freshness":{"state":"never_verified","last_verified_at":null,"is_stale":false},"grouping":{"backbone":"STRUCTURAL_SPANNING","link_density":0.5},"fix_edges":[],"members":[{"kind":"issue","number":105659,"title":"hermes update leaves package-lock.json dirty on Windows: desktop build stamp never matches again (stale-build verification failure + endless update autostashes)","url":null,"state":"open"},{"kind":"pr","number":105673,"title":"fix(update): stop npm lockfile churn from invalidating desktop builds","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false},{"kind":"pr","number":105676,"title":"fix(update): preserve lockfile across npm installs","url":null,"state":"closed","close_reason":{"refs":[{"kind":"pr","value":"#105673","number":105673},{"kind":"pr","value":"#105659","number":105659},{"kind":"pr","value":"#105673","number":105673}],"category":"duplicate_of","implication":"duplicate"},"merged":false},{"kind":"pr","number":111994,"title":"fix(desktop): resolve the build stamp at the profile-normalized root","url":null,"state":"open","close_reason":{"category":"uncategorized","implication":"needs_llm"},"merged":false}],"trust":{"default_tier":"verified","includes_suggested":false}}