Teknium
ef2ae3e48f
fix(file_tools): refresh staleness timestamp after writes ( #4390 )
...
After a successful write_file or patch, update the stored read
timestamp to match the file's new modification time. Without this,
consecutive edits by the same task (read → write → write) would
false-warn on the second write because the stored timestamp still
reflected the original read, not the first write.
Also renames the internal tracker key from 'file_mtimes' to
'read_timestamps' for clarity.
2026-04-01 00:50:08 -07:00
..
2026-03-17 00:16:34 -07:00
2026-03-30 02:45:41 -07:00
2026-03-17 02:33:12 -07:00
2026-03-24 08:19:23 -07:00
2026-03-23 07:43:12 -07:00
2026-03-30 00:02:02 -07:00
2026-03-31 13:38:22 -07:00
2026-03-31 10:40:13 -07:00
2026-03-25 19:47:58 -07:00
2026-03-25 15:02:03 -07:00
2026-03-31 18:52:11 -07:00
2026-03-31 12:16:37 -07:00
2026-03-29 21:29:13 -07:00
2026-02-21 03:53:24 -08:00
2026-03-29 18:21:36 -07:00
2026-03-24 08:19:34 -07:00
2026-03-31 12:47:10 -07:00
2026-04-01 00:50:08 -07:00
2026-03-25 19:47:58 -07:00
2026-03-15 20:21:21 -07:00
2026-03-29 15:55:05 -07:00
2026-03-25 15:02:03 -07:00
2026-02-23 02:11:33 -08:00
2026-03-25 19:47:58 -07:00
2026-03-29 15:52:54 -07:00
2026-03-28 14:55:18 -07:00
2026-03-27 15:28:19 -07:00
2026-03-18 02:55:30 -07:00
2026-03-11 20:02:36 -07:00
2026-03-26 19:38:04 -07:00
2026-03-25 15:02:03 -07:00
2026-03-29 15:52:54 -07:00
2026-03-25 19:47:58 -07:00
2026-03-29 21:29:13 -07:00
2026-03-27 21:27:51 -07:00
2026-03-29 20:08:22 -07:00
2026-03-27 15:28:19 -07:00
2026-03-30 17:34:43 -07:00
2026-03-25 15:54:28 -07:00
2026-03-29 00:33:30 -07:00
2026-03-29 15:15:17 -07:00
2026-03-25 19:47:58 -07:00
2026-03-15 20:21:21 -07:00
2026-03-29 21:27:03 -07:00
2026-03-29 15:15:17 -07:00
2026-03-23 15:40:42 -07:00
2026-03-30 02:59:39 -07:00
2026-03-31 12:13:33 -07:00
2026-03-30 13:37:25 -07:00
2026-03-25 15:54:28 -07:00