What: The inverse of #120: serve/write a live .ics feed of scheduled cards (date_scheduled/date_due, estimates as durations, hour-level times once #133 lands) that Google/Apple/Outlook can subscribe to — either a local HTTP endpoint or a periodically regenerated file synced by the user.
Why: 3 👍 on the Full Calendar equivalent and a recurring ask across task ecosystems: scheduling stays vault-native but becomes visible where the rest of life is planned. See documentation/research/feature-ideas-2026-08-21.md.
Related: #120, #133.
What: The inverse of #120: serve/write a live
.icsfeed of scheduled cards (date_scheduled/date_due, estimates as durations, hour-level times once #133 lands) that Google/Apple/Outlook can subscribe to — either a local HTTP endpoint or a periodically regenerated file synced by the user.Why: 3 👍 on the Full Calendar equivalent and a recurring ask across task ecosystems: scheduling stays vault-native but becomes visible where the rest of life is planned. See
documentation/research/feature-ideas-2026-08-21.md.Related: #120, #133.