What is the SQLite table/entity shape (via Doctrine DBAL + hand-defined typed PHP entities/DTOs, per this map's Notes) for caching calendar accounts, events, and tasks — including a source_type discriminator generic enough that RSS/Diun rows can later fit the same tables (per docs/research/smart-tablet-screen-additions.md, though not implemented now), a last_synced_at/staleness column per account, and — depending on the webhook-support ticket's findings — any columns needed for webhook subscription state (subscription id, expiry, renewal)?
Part of #1
Blocked by: #2
## Question
What is the SQLite table/entity shape (via Doctrine DBAL + hand-defined typed PHP entities/DTOs, per this map's Notes) for caching calendar accounts, events, and tasks — including a source_type discriminator generic enough that RSS/Diun rows can later fit the same tables (per docs/research/smart-tablet-screen-additions.md, though not implemented now), a last_synced_at/staleness column per account, and — depending on the webhook-support ticket's findings — any columns needed for webhook subscription state (subscription id, expiry, renewal)?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Part of #1
Blocked by: #2
Question
What is the SQLite table/entity shape (via Doctrine DBAL + hand-defined typed PHP entities/DTOs, per this map's Notes) for caching calendar accounts, events, and tasks — including a source_type discriminator generic enough that RSS/Diun rows can later fit the same tables (per docs/research/smart-tablet-screen-additions.md, though not implemented now), a last_synced_at/staleness column per account, and — depending on the webhook-support ticket's findings — any columns needed for webhook subscription state (subscription id, expiry, renewal)?