4 Commits

Include renames

Author	SHA1	Message	Date
Do Siki	a55ce53768	feat(cms): version history panel with diff view and one-click restore ... - GET /versions lists the automatic backups of the selected file (timestamp, size); ?show=<backup> renders a line diff against the current content - POST /restore validates the backup against the content schema and restores it atomically; the pre-restore state gets a fresh backup first, so a restore itself is reversible; audited as version_restored - dependency-free LCS line diff (scripts/cms-diff.js) with add/del highlighting and context trimming; backup names validated against a strict pattern (path traversal impossible) - new 🕘 Verziók entry in the CMS bottom bar - refactor: security/infra helpers extracted to scripts/cms-core.js to keep content-editor.js under the 400-line hard limit - integration test: list, diff, restore + reversibility backup, traversal rejection, CSRF enforcement, auth Closes MITHOME-64	2026-08-18 23:45:39 +02:00
Do Siki	3a5a09c361	feat: expose deploy version (git SHA) on CMS and health endpoint ... 'Is the fix live?' becomes a single check instead of an SSH session: - CMS: git short SHA read at startup, shown in the bottom bar (v<sha>), served by the public GET /version endpoint, recorded in a startup audit entry - Website: deploy.sh exports DEPLOY_VERSION (git SHA), Dockerfile bakes it via build ARG into the runtime env, /api/health reports it as deployVersion, smoke test asserts a non-'unversioned' stamp Closes MITHOME-63	2026-08-18 21:19:43 +02:00
Do Siki	3818859cc5	feat(cms): optimistic locking against stale-tab overwrites ... A Content Editor tab left open across a deploy (or a save from another tab) held the pre-deploy content; one Save would silently overwrite the newer file. The editor page now embeds a SHA-256 fingerprint of the file content at load time, /save requires it back in X-Content-Hash and compares against the current file: mismatch (or a missing header) answers 409 with an explanatory message and writes nothing. The client offers a reload on 409. Integration test covers: matching hash saves, stale hash rejected with the file untouched, missing hash rejected, retry with the fresh hash succeeds. Closes MITHOME-61	2026-08-18 20:57:08 +02:00
Do Siki	5fe36584dd	feat(cms): confirm-before-logout and branded login page ... - logout asks for confirmation, then invalidates the server-side session and navigates to a public /login page (logo, form, error messages) - POST /login validates credentials (timing-safe) and issues an HttpOnly SameSite=Strict session cookie (8h, Secure behind HTTPS); Basic Auth stays valid in parallel for curl/API use - unauthenticated browser navigations redirect to /login; non-browser requests keep the 401 challenge - failed form logins share the auth rate-limit budget with Basic attempts - save/publish redirect to /login when the session expired - refactor: templates and browser script extracted to scripts/cms-pages.js and scripts/cms-editor-client.js, session logic to scripts/cms-session.js (content-editor.js back under the 400-line limit) - user guide updated (login page, confirmation, 8h session) Closes MITHOME-58	2026-08-18 14:01:42 +02:00