Record the stale-branch triage and advance TODO.md (closes #71) #95

Merged
clawbot merged 1 commits from fix/triage-stale-remote-branches into main 2026-08-09 10:23:30 +02:00

1 Commits

Author SHA1 Message Date
7e49b483d8 Record the stale-branch triage and advance TODO.md (closes #71)
All checks were successful
check / check (pull_request) Successful in 2m12s
Fourteen of the fifteen stale remote branches are deleted; the
per-branch disposition and its evidence live on issue #71. No product
code changes -- the triage resolved to deletions, so this commit is the
TODO.md Workflow step for the issue.

Two branches were the reason the issue existed, and both turned out to
be closed questions that main had already moved past:

fix/ctime-scanner-population would repopulate a field that no longer
exists. 1c72a37 removed the ctime column, the File.CTime field and
every use (#54/#55). Change detection compares size, mtime, mode, uid
and gid only, matching what ARCHITECTURE.md documents, so ctime never
participated and the silently-skipped-file data-loss risk that made
this a 1.0 item does not exist.

fix/sql-injection-whitelist would revert bfd7334, which deliberately
replaced that allow-list with regex sanitisation on review feedback,
and would break getTableCount("snapshots") because its allow-list omits
that table.

Containment was established with two-dot tip diffs, tree-hash equality
and git cherry rather than three-dot merge-base diffs, which replay
everything that landed on main after a branch diverged and make old
branches look like they hold unlanded work.

feature/daemon-mode is untouched, deferred to #94 pending an owner
decision. The stale TODO.md entry named in the issue needed no fix;
e496aa3 had already removed it.
2026-08-09 08:18:10 +00:00