Preserved branch: queue/1487-1420-edge-whitespace-normalize — decision needed (merge / cherry-pick / drop) #3535
Description
Preserved branch from the laptop worktree cleanup of 2026-11-01.
- Branch:
queue/1487-1420-edge-whitespace-normalize - Verified HEAD on origin:
fe6c29e8a7fa3956bba4d17bdcdac7f6a9fdd1f7 - Provenance: this branch holds work that existed only in a local worktree on the laptop (unique commits and/or a rescue commit of uncommitted work: "rescue: preserve uncommitted work from worktree cleanup 2026-11-01"). It was pushed so the worktree could be removed without losing the work; the local tree and local branch are gone.
- Decision needed: merge it, cherry-pick from it, or drop the branch. Nothing else references it; this issue is the record of what it holds.
Activity
developing-today commentedon Nov 1, 2026
CODE-1362
dezren39 commentedon Nov 3, 2026
🤖 Agent note · handed off
dezren39 commentedon Nov 3, 2026
🤖 Agent note · done (triage)
ses_e5e5e68546effeeCgySsrpvL3tmain. No cherry-pick and no fresh PR are needed.Findings (verified fresh against current
main@c3c9423, 2026-11-03)efd1d6410fix(id): normalize unmarked text-run edge whitespace at save (#1420)fe6c29e8astyle(id): rustfmt rewrap in is_unmarked_text_json (#1420)7b09ac0bb2444fe58ed9e8f7f1025d1a933142a9(merged 2026-10-28T03:00:35Z), which closed issue id(web): edge whitespace in text runs is written on save but stripped on reopen — a whitespace-only paragraph is deleted outright #1420. PR state is MERGED.931f1771e..fe6c29e8a=pkgs/id/src/web/markdown.rs, 1 file, +195/−8. The squash-merge diff7b09ac0bb^..7b09ac0bbis the same file and the same +195/−8, and the patch bodies match hunk-for-hunk; only line offsets and blob hashes differ becausemainhad advanced.mainstill contains the fix:is_unmarked_text_json,is_whitespace_only_text_json,reaches_line_edgeandnormalize_inline_child_jsonare present atpkgs/id/src/web/markdown.rs:4364+.queue/1487-1420-edge-whitespace-normalizeno longer exists onorigin(not in the branch list,git ls-remotereturns nothing, REST ref returns 404 at 2026-11-03T13:2xZ). I did not delete it. The daily branch-cleanup workflow only deletes branches whose tips are ancestors ofmain, so it would not have removed a squash-merged head; the removal is unexplained but harmless because the content is fully inmain.Blockers
None. Nothing is needed from anyone, and no follow-up task is warranted.
Labels: removing
status/in-progress,queue/queued,queue/claimed,work/assigned; keepingpriority/low.dezren39 commentedon Nov 3, 2026
agent-note:v1 — state: handed off — queue task 7334 launched in bound OpenCode session ses_e5e5e68546effeeCgySsrpvL3t by opencode-claimant.
developing-today commentedon Nov 3, 2026
agent-note:v1
state: reviewed (coverage loop-back)
Coverage pass 2026-11-03, loop-back review: this issue was re-reviewed (drift / overlap / already-handled / stale / blockers / ordering) so every open issue in the four repos is reviewed and in the system. Verdict: still live; in the system as task 8535 (triage, queued, priority 30) in repo-health-code-pilot. Labels audited and synced. If it is already handled at current main, its triage closes it with evidence; if oversized, the triage files the split; blockers belong on this issue.
Found via: coverage loop-back 2026-11-03
dezren39 commentedon Nov 3, 2026
agent-note:v1
event: done
task: 8535
queue: repo-health-code-pilot
lane: code-a
summary: Triage closed as already_done — issue #3535 was closed by dezren39 on 2026-11-03T13:30:19Z with state_reason completed, so the preserved-branch decision it asked for has been resolved outside this task. Queue labels stripped; task completed with outcome already_done.
evidence: gh api repos//issues/3535 -> state=closed, state_reason=completed, closed_by=dezren39