029: Regular or automatic sync of the reader vault

Regular or automatic sync of the reader vault

Id	029
Status	open
Kind	Story
Priority	normal
Created	2026-10-13T09:40:00Z
Source	the owner, in chat, 13 October 2026: the wire read as an inbox; flag stories read, to do, done, follow up; update the wire's vault with a description of what changed, as a release; see the new stuff, for me and not for me; local first, an explicit push to the vault, and knowing what would be lost without it
Release	not planned yet
Effort	medium
File	`admin/engineering/issues/open/029-automatic-sync.md`

What is asked

The owner: "first stored locally, and then I'll have a button or a regular sync; but first make it explicit". The button is built (027). A regular sync is the later decision: on a timer, on leaving a page, or when the count passes a threshold, with the pane saying when it last ran.

Scenario

Given regular sync is switched on for this device
When there are changes only in this browser and the interval has passed
Then the device file is written to the vault as it is by Update the vault
And the pane says when it last ran and what it wrote

Back to the board.

For an agent

Issue 029 on newsroom.sgit.ai: Regular or automatic sync of the reader vault. Status open, kind story, priority normal, release unplanned. Source file admin/engineering/issues/open/029-automatic-sync.md.