add comment 2a9e1d6e52d025992bc7c8c22fd20474 on issue 20649f4f970201e04ea50e2b460cff17

08f0d7ee7842c439382816d21ec1dea2/description

@@ -35,11 +35,26 @@ or a due date this week.
 
 ## Done last week
 
-I can imagine finding the issues with state=done, running `git log`
-on their state file, finding the datetime of the transition to done,
-and selecting the ones where that datetime is in a particular time window.
+I can imagine finding the issues with state=done, running `git log` on
+their state file, finding the datetime of the transition to done, and
+selecting the ones where that datetime is in a particular time window.
 
-Not sure how to express to ent that that is what i want though.
+This has the drawback that it's hard to lie about...  With taskwarrior
+I often found myself finishing a task on Week X, but forgetting to mark
+it complete.  Then the Monday of Week X+1 i would mark it complete.
+If i didn't override the completion-date the task would look like it
+was completed on Week X+1, not Week X like i wanted.
+
+In git we have `git commit --date=DATE`, but that's only usable at
+commit-time (and awkward to express to ent).  We can rewrite history with
+`git rebase`, but only until we `ent sync`.
+
+Maybe the `state` file should have a date in it, in addition to the
+state word?  Or maybe `completion-date` should be a key in a per-issue
+key-value store?  Is that kv store related to tags?  Idk...
+
+Not sure how to express to ent what completion-dates i want to see.
+Maybe a new filter type?  `ent list finished=2025-07-01..now`?
 
 Maybe we can use git tags in the entomologist-data branch somehow?
 `git log` between tags and look for "state: _ -> done".  But how to

20649f4f970201e04ea50e2b460cff17/comments/2a9e1d6e52d025992bc7c8c22fd20474/description

@@ -0,0 +1,8 @@
+Oops, i stupidly ran: ent new "add `ent sync --dry-run`"
+
+Because i used double-quotes, bash saw the `...` and ran that as a
+command, which failed, but then bash ran the result anyway ("ent new
+"add "), and here we are.
+
+This would be a good time for `ent rm` as suggested by issue
+1ebdee0502937bf934bb0d72256dbdd1.

20649f4f970201e04ea50e2b460cff17/description

@@ -0,0 +1 @@
+add 

20649f4f970201e04ea50e2b460cff17/state

@@ -0,0 +1 @@
+wontdo

ca164f570ea3d62f2ff4a001200e0a00/description

@@ -0,0 +1 @@
+add `ent sync --dry-run`