Removes every README passage about upgrading, downgrading, or data an older build wrote, for #520. Since #519 the schema comes from 001_schema.sql, edited in place before 1.0, so there is no upgrade path to describe.
The Upgrades section is gone: the procedure, the downgrade note and the BIND_ADDRESS upgrade note. The bind address defaults stay documented under Configuration and Running with Docker.
Its description of the SQL schema files moves, word for word, to a new Schema subsection at the end of Database Architecture. The link in the main database paragraph now points there.
The health check command moves into Version stamping.
"Backup, Restore, and Upgrades" becomes "Backup and Restore". Restore step 4 loses its sentence about restored files getting SQL files they lack.
Three sentences now state only what the code does: the session cookie timestamps (the line about older sessions is dropped), file modes (reserveSQLiteFile sets each database and its sidecars to 0600 on every open), and the retention clamp (retentionCutoff clamps every value the reaper reads from the main database).
Judgement call: Version stamping stays where it was, so it now sits under Backup and Restore. The brief kept it in place.
Model: opus-5-5
Removes every README passage about upgrading, downgrading, or data an older build wrote, for https://git.eeqj.de/sneak/webhooker/issues/520. Since https://git.eeqj.de/sneak/webhooker/pulls/519 the schema comes from `001_schema.sql`, edited in place before 1.0, so there is no upgrade path to describe.
- The Upgrades section is gone: the procedure, the downgrade note and the `BIND_ADDRESS` upgrade note. The bind address defaults stay documented under Configuration and Running with Docker.
- Its description of the SQL schema files moves, word for word, to a new Schema subsection at the end of Database Architecture. The link in the main database paragraph now points there.
- The health check command moves into Version stamping.
- "Backup, Restore, and Upgrades" becomes "Backup and Restore". Restore step 4 loses its sentence about restored files getting SQL files they lack.
- Three sentences now state only what the code does: the session cookie timestamps (the line about older sessions is dropped), file modes (`reserveSQLiteFile` sets each database and its sidecars to `0600` on every open), and the retention clamp (`retentionCutoff` clamps every value the reaper reads from the main database).
Judgement call: Version stamping stays where it was, so it now sits under Backup and Restore. The brief kept it in place.
Model: opus-5-5
The schema comes from 001_schema.sql, edited in place before 1.0, so the
README's upgrade procedure, downgrade note, BIND_ADDRESS upgrade note and
remarks about what older builds wrote are removed.
The description of the SQL schema files moves to a new Schema subsection
under Database Architecture, the health check command moves to Version
stamping, and the section is renamed Backup and Restore. The sentences on
session timestamps, file modes and the retention clamp now say only what
the code does.
Model: opus-5-5
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.
Removes every README passage about upgrading, downgrading, or data an older build wrote, for #520. Since #519 the schema comes from
001_schema.sql, edited in place before 1.0, so there is no upgrade path to describe.BIND_ADDRESSupgrade note. The bind address defaults stay documented under Configuration and Running with Docker.reserveSQLiteFilesets each database and its sidecars to0600on every open), and the retention clamp (retentionCutoffclamps every value the reaper reads from the main database).Judgement call: Version stamping stays where it was, so it now sits under Backup and Restore. The brief kept it in place.
Model: opus-5-5
Review passed.
Model: opus-5-5