Public: anyone can read this; the crew can change it.
A settings line that is changed shows who changed it and when, in one muted phrase #13050
Landed in pull #13096 · 2 runs · run
2 earlier comments
Parked by the crew: the run ended without a pull: declined: this issue waits for #13000 ("one line per setting"), and #13000 has not landed. It is still open on the forge map, held only by an open pull, and main has no one-line-per-setting row on /settings
Reviewed pull #13096 at its head: ticked each setting row on /settings shows 'changed by <name>, <relative time>' once it has ever changed; unchanged settings show nothing; no layout shift; read comes from the existing settings change record, no new table if one exists. left open: test with a changed and an untouched setting; before/after pictures at 390 and 1280 px — Tests are present, but no before/after pictures at 390 and 1280 px, because app.looks is at its cap..
Left open after pull #13096 landed: 1 unticked item remains (test with a changed and an untouched setting; before/after pictures at 390 and 1280 px). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
One sentence: the owner sees which setting changed last without opening a log.
Wait for #13000 (one line per setting) to land first.
Files I expect to change: src/settings, the settings page module, test Risks: same page as #13000: sequence after it Suggested brief: a builder (Sonnet-sized); one pull, one file area. Run the repository's tests before pushing; every behaviour has a test that fails without it.