<feed xmlns='http://www.w3.org/2005/Atom'>
<title>doot.git/docs/superpowers/plans/2026-07-13-multi-day-events.md, branch master</title>
<subtitle>doot — personal productivity web app
</subtitle>
<id>https://git.terst.org/doot.git/atom?h=master</id>
<link rel='self' href='https://git.terst.org/doot.git/atom?h=master'/>
<link rel='alternate' type='text/html' href='https://git.terst.org/doot.git/'/>
<updated>2026-07-16T02:42:31+00:00</updated>
<entry>
<title>docs: fix exclusive all-day end-date bug in multi-day plan's Android task</title>
<updated>2026-07-16T02:42:31+00:00</updated>
<author>
<name>Peter Stone</name>
<email>thepeterstone@gmail.com</email>
</author>
<published>2026-07-13T18:17:06+00:00</published>
<link rel='alternate' type='text/html' href='https://git.terst.org/doot.git/commit/?id=08ded9fc1114c86b7a748c589aa2b6e8d8202c1c'/>
<id>urn:sha1:08ded9fc1114c86b7a748c589aa2b6e8d8202c1c</id>
<content type='text'>
MD-Task 2's review caught that Google Calendar's all-day End.Date is
exclusive (a single-day all-day event's End is one day past its own
day), which isMultiDayEvent/multiDayVariant didn't account for. Task 4
(Android, not yet implemented) had the same flaw copied into its
Kotlin code -- fixed here before dispatching, mirroring the Go-side fix.
</content>
</entry>
<entry>
<title>docs: add multi-day calendar events implementation plan</title>
<updated>2026-07-16T02:42:31+00:00</updated>
<author>
<name>Peter Stone</name>
<email>thepeterstone@gmail.com</email>
</author>
<published>2026-07-13T18:01:41+00:00</published>
<link rel='alternate' type='text/html' href='https://git.terst.org/doot.git/commit/?id=c901a6ea512088991bb2b2d5d1daebb5d90e000e'/>
<id>urn:sha1:c901a6ea512088991bb2b2d5d1daebb5d90e000e</id>
<content type='text'>
</content>
</entry>
</feed>
