Verify the current update-issue implementation before changing it

Inspect src/modules/update-issue.js directly and preserve its exact target-restoration semantics. Confirm whether state discovery uses CRAFT_STATE_FILE_PATH or an older version-derived path, and whether updateIssue still consumes inputs. Keep missing state files as a no-op with no issue API calls; when present, fetch the issue and parse the state concurrently, update declared target checkboxes, append undeclared published targets in object-key order, and update the issue body. Also preserve concurrent removal of the accepted label. Do not assume behavior from earlier revisions, and add or review focused tests when these details change.