100 Commits

This Branch

This Branch

All Branches

Author	SHA1	Message	Date
Do SikiandClaude Sonnet 5	02a73b3702	sync: mark MITHOME-120 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-12 00:05:06 +02:00
Do SikiandClaude Sonnet 5	74e40329a0	feat(cms): admin quick-search across all content (MITHOME-120) ... Adds a search box to the top of every Payload admin page (admin.components.header) that searches by text across every field of every Global and Collection, in both locales — something Payload has no built-in equivalent for: collection list views only search their own title/slug fields, and Globals have no list view at all. Implementation is deliberately client-side and index-free rather than @payloadcms/plugin-search (a server-side search collection kept in sync via hooks): this project's entire content is 5 Globals + 2 small Collections, so a plugin-managed search index would be disproportionate maintenance for the actual data volume — the same reasoning already applied to the logo editor (MITHOME-118). On first use, the component fetches every Global/Collection doc in both locales via the existing REST API (same-origin, admin session cookie), recursively flattens every field to (path, value) pairs client-side, and filters by case-insensitive substring as the user types. Each result links straight to the right edit view (global or collection/id). New: src/components/admin/QuickSearch.tsx. Registered via payload.config.ts admin.components.header, which required a generate:importmap run — the useful gotcha this surfaced: Payload resolves component paths against admin.importMap.baseDir, which defaults to process.cwd() (the proto/ the CLI is run from), not dirname(payload.config.ts) — so the path needed to be './src/components/admin/QuickSearch#QuickSearch', not './components/admin/QuickSearch#QuickSearch'. Documented inline. Verified live in the browser (not just tsc/lint): search finds matches in both a Global (Home hero.cta.secondary.text / services description) and a Collection (Partners name/url), shows source + field path + locale + a snippet per result, clicking a result navigates to the correct edit view, and the search state persists across client-side admin navigation since the header component doesn't remount. Zero console errors in a fresh tab. Full gate green: tsc, lint, unit tests (51 passed), production build. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-12 00:03:13 +02:00
Do SikiandClaude Sonnet 5	3f72d714df	sync: add cms.stage.llmdev.mozdit.hu nginx vhost log entry to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 23:33:33 +02:00
Do SikiandClaude Sonnet 5	265b656df9	docs: document the cms.stage.llmdev.mozdit.hu nginx vhost (MITHOME-97 follow-up) ... Server-side nginx config isn't tracked anywhere in this repo, which is exactly how an orphaned vhost went unnoticed: it used to reverse-proxy to the old CMS (content-editor.js, port 4001), retired in MITHOME-93. After that service was stopped/disabled, the vhost silently kept serving its still-valid TLS cert as nginx's apparent fallback for any unmatched *.mozdit.hu subdomain — which is what produced a real-looking (but harmless) Firefox "this site may be impersonating" warning when the user mistyped a URL. Repointed the vhost (server-side, not in this repo) to reverse-proxy /admin, /api/ and /_next/ to the same staging app container Payload already runs on (127.0.0.1:8081) — same backend as stage.mozdit.hu, just a friendlier admin-specific URL. Root redirects straight to /admin; anything else redirects to the canonical stage.mozdit.hu to avoid serving the public site twice. Reused the existing Let's Encrypt cert (no new certbot run needed). This commit only adds docs/nginx-vhosts.md, documenting what's live on the server and why, since nginx config itself isn't part of this repo's source of truth. Verified live: TLS cert now matches cms.stage.llmdev.mozdit.hu (no more mismatch warning), GET / redirects to /admin (302), GET /admin returns 200 with correctly loaded assets (checked in a real browser, zero console errors), GET /rolunk redirects to stage.mozdit.hu, GET /api/health proxies through correctly, and POST /api/users/login with the real staging admin credentials returns 200 through this domain too. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 23:33:01 +02:00
Do SikiandClaude Sonnet 5	00d2b82877	sync: add MITHOME-97 admin-seed follow-up log entry to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 23:21:17 +02:00
Do SikiandClaude Sonnet 5	729268a3fe	feat(deploy): auto-seed a known Payload admin user on every deploy ... Follow-up to MITHOME-97: after every deploy, a brand-new database (first-ever deploy, or a volume wipe) leaves the Payload admin behind the "Create first user" screen — someone has to notice and fill it in by hand, which means environments can silently end up with no known admin credentials, or with whatever a random person happened to type in at the time. deploy.sh now calls Payload's built-in `POST /api/users/first-register` REST endpoint right after the healthcheck passes, using ADMIN_EMAIL / ADMIN_PASSWORD from the environment's .env file. That endpoint only succeeds when the `users` collection is completely empty (throws 403 Forbidden otherwise) — which makes this naturally idempotent: the first deploy against a fresh database creates the known admin, every later deploy gets a harmless 403 and skips it. It never overwrites an existing user's password. Missing ADMIN_EMAIL/ADMIN_PASSWORD in the env file just skips the step with a warning, it doesn't fail the deploy. Documented the new variables in .env.staging.example and .env.production.example (next to the existing PAYLOAD_SECRET instructions), and the new deploy.sh step 4 in .agent/workflows/deploy.md. Also dropped a stale "Content Editor is staging feliratot kap" line from the same doc (that behavior belonged to the CMS retired in MITHOME-93 and no longer exists). Verified locally against real Payload instances (not just reading the code): a fresh, empty MongoDB returns 200 and creates the user; a second call against the same now-non-empty database returns 403 and changes nothing; a database that already had a different user (the existing dev DB) also correctly returns 403. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 23:12:12 +02:00
Do SikiandClaude Sonnet 5	94647d5293	sync: mark MITHOME-97 done, add MITHOME-92/93/97 log entries to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 22:52:53 +02:00
Do SikiandClaude Sonnet 5	d8cccc1a65	fix(deploy): drop stale content-editor systemd restart from staging script ... scripts/deploy_to_stage_on_local.sh restarted a "mozdit-content-editor.service" systemd unit after every staging deploy — the old custom CMS's own service (content-editor.js, retired in MITHOME-93). Left in place, the next staging deploy would pull the commit that deletes content-editor.js and then try to restart a service pointing at a now-missing script. Removed the restart from the deploy script; the server-side systemd unit itself (if still installed) needs a manual stop/disable — out of reach from here (no SSH access in this session), flagging it to the user instead. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 22:13:47 +02:00
Do SikiandClaude Sonnet 5	1b3ae07811	feat(deploy): staging/production Docker deploy for Payload (MITHOME-97) ... Fixes a real, previously-undiscovered build failure and a bigger architectural gap found while testing an actual `docker build` of proto/Dockerfile for the first time since the Payload migration: 1. Docker build failure: the (frontend)/[locale] pages use generateStaticParams, so `next build` fully prerenders them (SSG) — which calls the Payload Local API during the build. With no MONGODB_URI/PAYLOAD_SECRET reachable in the build stage, `docker build` failed outright ("missing secret key"). 2. Bigger problem underneath: even if the build could reach a DB, full SSG means a Payload admin edit would NOT appear on the public site until a full rebuild + redeploy — directly undermining the project's whole reason for migrating to Payload (self-service content editing for the client). Fix (user-confirmed direction: force-dynamic): dropped generateStaticParams from (frontend)/[locale]/layout.tsx and [locale]/[slug]/page.tsx, added `export const dynamic = 'force-dynamic'` to layout.tsx + both page.tsx files. Every request now reads Payload live — publishing in the admin is visible immediately, and the Docker build no longer needs any DB connectivity at all (verified: a full `docker build --target builder` now succeeds with zero env vars set). Docker/Compose changes: - docker-compose.staging.yml / docker-compose.prod.yml: wired PAYLOAD_SECRET through to the app container (was documented in .env.*.example since MITHOME-86 but never actually passed to the container — Payload would have refused to start). No fallback, same fail-loudly pattern as MONGODB_URI. - Same two files: added a named `media_data_{staging,prod}` volume mounted at /app/media — Payload's local upload storage (Media.ts) writes there at the container's runtime cwd; without a volume, `deploy.sh`'s `--force-recreate` would silently wipe every uploaded logo/image on each deploy. - docker-compose.dev.yml: was missing PAYLOAD_SECRET entirely (only discovered because the same "missing secret key" error reproduces there too) — added a dev-only literal value. Media persistence already works there via the existing `./proto:/app` bind mount, no volume needed. Also dropped the obsolete `version: '3.8'` key (compose warns it's ignored). - DOCKER.md: one-paragraph note on the new PAYLOAD_SECRET requirement and where the admin account gets created. Verified: - `docker build --target builder` succeeds from a clean context with zero environment variables (previously failed). - `docker build --target runner` + `docker run` against the real dev MongoDB (PAYLOAD_SECRET + MONGODB_URI supplied at runtime only): /hu, /admin and /api/health all return 200 inside the container; confirmed live in the browser that Payload content renders correctly end-to-end through the production Next.js server, not just `next dev`. - `docker compose -f docker-compose.{staging,prod,dev}.yml config` parses cleanly. - Full gate green: tsc, lint, proto unit tests (51 passed), scripts/pre-deploy-tests.sh (proto tests, tsc, lint, content schema, plane-sync — all pass). deploy.sh itself needs no changes: it already just runs `docker compose up --build`, and that now works without any build-time DB wiring. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 22:12:01 +02:00
Do SikiandClaude Sonnet 5	19622d9703	sync: mark MITHOME-93 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 21:50:00 +02:00
Do SikiandClaude Sonnet 5	12b2711168	chore: retire legacy custom CMS (content-editor.js) (MITHOME-93) ... Removes the standalone, git-push-based content editor that predates Payload CMS: content-editor.js, its scripts/cms-*.js modules, its scripts/test-content-editor-*.js + scripts/test-cms-publish.js test suite, scripts/markdown-render.js (only used by the editor's guide renderer), the proto-side test doubles (cms-editor-client.test.ts, cms-editor-shortcuts.test.ts), and the editor's own user guide (docs/felhasznaloi-utmutato.md). Kept: proto/src/content/*.json (still the source for migrate-content-to-payload.ts and test fixtures for Header/Footer, per MITHOME-96), proto/src/content/schema.js + scripts/test-content-schema.js (still validate those JSON files), and docs/content-editor-recovery.md (historical incident record, not user-facing tool docs). Safety net before deletion (per user request): added proto/scripts/export-content-snapshot.ts, a reusable Payload Local API exporter, and ran it to produce docs/backups/payload-content-snapshot-*.json — a full hu/en snapshot of every Global + LegalPages + Partners document at the moment of retirement. Also confirmed no data-loss risk otherwise: .content-backups/ (the editor's own gitignored backup dir) tops out at 2026-08-23, well before today's fresh migration run, and every JSON edit ever made through the editor already exists as its own git commit ("content: frissítve a CMS-ből"). Updated dangling references: pre-deploy-tests.sh and .agent/steering/testing.md (dropped the CMS test block), .agent/workflows/deploy.md (publish flow is now Payload draft/publish, not git push), CLAUDE.md + .agent/AGENTS.md (dropped the /cms-feature workflow, deleted alongside it), README.md (stack description), .agent/steering/development-rules.md (the guide-maintenance rule no longer has a guide to maintain). Verified: tsc, lint, proto unit tests (51 passed), root test-content-schema.js, plane-sync unit tests, production build all green after the deletion. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 21:48:50 +02:00
Do SikiandClaude Sonnet 5	21a0d73639	sync: mark MITHOME-92 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 21:36:49 +02:00
Do SikiandClaude Sonnet 5	d445f0f31a	feat(cms): enable draft/publish + version history on Globals/Collections (MITHOME-92) ... Adds versions.drafts to all content-bearing Globals (Home, About, Services, Contact, Common) and Collections (LegalPages, Partners) via shared config in src/lib/payload-versions.ts. Media and Users are deliberately excluded (no draft workflow needed for uploads/auth). This is the direct successor to the old custom CMS's "Verziók panel" (MITHOME-64): the Payload admin now shows Save Draft / Publish changes and a Versions tab with history/diff/restore per document. Fixes a real bug found during manual verification: Payload's `_status` field defaults to 'draft' when a create/update call's data omits it, and that value is preserved on subsequent updates rather than being overwritten. Since migrate-content-to-payload.ts never passed `_status`, every migrated document ended up in draft status, which would have broken public pages once combined with any future explicit draft read. Fixed by explicitly setting `_status: 'published'` on every write in the migration script. Verified live in the browser: - Payload admin: Home global shows Status: Published, Save Draft / Publish changes buttons, Versions tab with history (draft -> current). - Saving a draft edit (title change, not published) does NOT change what /hu and /en render — confirmed by reloading the public page before publishing. - Publishing the change updates the public page as expected. - Full gate green: tsc, lint, tests (58 passed), production build. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-11 21:36:03 +02:00
Do SikiandClaude Sonnet 5	b5590175b7	sync: mark MITHOME-91 + MITHOME-114 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 16:16:47 +02:00
Do SikiandClaude Sonnet 5	d6f3dda9e5	feat(frontend): Payload Local API + hu/en locale routing (MITHOME-91/114) ... Replaces the JSON content system with Payload's Local API across every frontend page, and introduces symmetric locale-prefixed routing (/hu/..., /en/...) with per-locale translated slugs — supersedes the earlier "hu unprefixed" decision (see chat 2026-09-10). Routing structure: - src/app/(frontend)/layout.tsx: now a minimal shell (html/body, theme script, ThemeProvider) — no longer locale-aware. - src/app/(frontend)/page.tsx: redirects bare "/" to the default locale (/hu). - src/app/(frontend)/not-found.tsx: explicit 404 for the (frontend) group — without it, Next's built-in fallback collided with the (payload) group's own root and reproduced the "double html / script tag" symptom from MITHOME-87, but only on notFound() paths. Verified fixed in both dev and a real production (standalone) server; the remaining "script tag" console warning on invalid routes turned out to be Turbopack dev-mode-only noise (zero console errors in production) — confirmed by building and running .next/standalone directly. - src/app/(frontend)/[locale]/layout.tsx: validates the locale segment (generateStaticParams hu/en, notFound() otherwise), fetches Common + Home via Payload, renders Header/Footer/staging-banner. - src/app/(frontend)/[locale]/page.tsx: home, fetches Home global + Partners collection. - src/app/(frontend)/[locale]/[slug]/page.tsx: catch-all for about/ services/contact/privacy/terms — resolves slug -> PageKey via src/lib/i18n.ts's PAGE_SLUGS map (generateStaticParams pre-renders all 10 locale×slug combinations), generateMetadata per page. New lib layer: - src/lib/i18n.ts: Locale/PageKey types, PAGE_SLUGS (translated slugs per locale), localePath()/resolvePageKey()/switchLocalePath() helpers (the last one already shaped for MITHOME-115). - src/lib/payload-content.ts: Local API getters that also unwrap Payload's `{ value: string }[]` array-field shape back into plain string[] (see src/globals/fields/stringArray.ts) — keeps the page JSX consuming the exact shape the old content/types.ts had, so the migration is a data-source swap, not a markup rewrite. Presentational split: page bodies moved to src/components/views/ (HomeView, AboutView, ServicesView, ContactView, LegalPageView — the last one shared by both legal pages, identical shape) as prop-driven components; the app-router page.tsx files became thin server-side fetch + render wrappers. Header/Footer converted from importing content directly to accepting nav/locale/content props, since they're 'use client' and can't call the Payload Local API themselves — config/site.ts's navigation arrays became getMainNavigation(locale)/ getFooterNavigation(locale)/getFooterLegalLinks(locale) functions. Two real, pre-existing bugs fixed along the way (not introduced by this migration): - Services and Contact pages' "Webmail belépés" links used the primary CTA's href (/kapcsolat) with target="_blank" instead of the actual webmail URL (home.hero.cta.secondary.href) — now correct. - The GDPR checkbox link pointed to "/adatkezelesi-tajekoztato", which never matched the real privacy page route under any past URL scheme. contact.json's gdpr.label now carries a {privacyHref} placeholder that ContactView replaces with the locale-correct path — also fixes the adatvedelem page's own <title> tag, which previously read "Adatvédelmi Tájékoztató | Szolgáltatás jellemzők:" (a copy-paste bug using common.labels.features instead of the site name). Known, accepted limitation: the outer shell layout hardcodes <html lang="hu"> because it sits above the [locale] segment and can't read the param — every [locale]/[slug] page's own generateMetadata is locale-correct, but the initial lang attribute isn't. Documented as a MITHOME-116 (SEO/hreflang) follow-up rather than restructured now. Verified end to end in a real browser: /hu matches the https://stage.mozdit.hu visual baseline (MITHOME-117) exactly; /en renders with English nav/metadata (content body still Hungarian-only, as expected — MITHOME-111/113 not done yet); /hu/kapcsolat's GDPR link resolves to /hu/adatvedelem; dark mode still works; invalid locale (/fr/about) and invalid slug (/hu/nemletezo-oldal) both 404 correctly; bare "/" redirects to /hu. build/lint/tsc/test (58 passed) all clean, including a clean production standalone-server run. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 16:15:09 +02:00
Do SikiandClaude Sonnet 5	594865ea9a	sync: mark MITHOME-90 done, add MITHOME-119 (MFA prep) to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:28:57 +02:00
Do SikiandClaude Sonnet 5	8407b45367	feat(cms): Users access control + lockout policy (MITHOME-90) ... Explicit, documented decisions instead of relying on implicit Payload defaults: - auth.maxLoginAttempts: 5, lockTime: 10 min — codifies the lockout policy rather than leaving it as an unstated library default. - auth.cookies: { secure: NODE_ENV === 'production', sameSite: 'Lax' } — secure cookies once behind HTTPS (MITHOME-15), harmless over plain HTTP in local dev. - access.{create,read,update,delete,unlock}: explicit requireAuthenticatedUser (== Payload's defaultAccess, Boolean(user)). Investigated the known open advisory flagged in MITHOME-86 (GHSA-jg8r-5jh2-v2xj — any authenticated user can unlock any other account) by reading Payload's unlock operation source: the gap only matters when a less-privileged authenticated identity exists that needs protecting from a more-privileged one. This project's single "admin" role model (no role hierarchy — MITHOME-85 epic decision) has no such identity, so the default is accepted as-is, with the reasoning and a MITHOME-46 (central IDM/SSO) revisit trigger written into the code comment rather than left implicit. - Added an optional `name` field for a nicer admin identity than a bare email (audit trail, header display). Verified live: existing dev@mozdit.hu user unaffected (name column shows "<No Name>", backward compatible). Reproduced the lockout for real — 5 wrong POST /api/users/login attempts, 6th attempt with the *correct* password still rejected ("locked due to too many failed login attempts"), unlocked via Local API (overrideAccess), then the correct password logged in successfully. build/lint/tsc/test (58 passed) all clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:26:41 +02:00
Do SikiandClaude Sonnet 5	71ab1e08ac	sync: mark MITHOME-118 cancelled in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:17:00 +02:00
Do SikiandClaude Sonnet 5	fb11eff18b	docs(cms): note the manual pre-processing workflow on the Partners logo field ... Following the MITHOME-118 scope decision (cancelled — see Plane comment): partner logos are prepared with a free external tool (e.g. remove.bg) before upload, not edited inside Payload admin. Surface that expectation right on the field so an editor isn't looking for a crop/transparency tool that doesn't exist. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:16:14 +02:00
Do SikiandClaude Sonnet 5	30f271651a	sync: mark MITHOME-110 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:08:07 +02:00
Do SikiandClaude Sonnet 5	6589289878	feat(cms): enable Payload localization — hu default + en (MITHOME-110) ... payload.config.ts: localization: { locales: ['hu','en'], defaultLocale: 'hu', fallback: true }. URL/routing side is separate (MITHOME-114). Proved the mechanism on a real field rather than a throwaway one: Common.buttons.* (contact/learnMore/webmail/sendMessage) marked localized: true — these are genuinely translatable UI labels, so this doubles as a first, correct slice of the full MITHOME-111 retrofit instead of being disposable test scaffolding. Gotcha discovered and documented in the migration script: marking an existing field `localized: true` after data was already written non- localized makes that value unreadable via `locale: defaultLocale` (the storage shape changed) — the migration script must be re-run so it gets rewritten under the localized shape. This will matter again for the full MITHOME-111/112 retrofit. Verified: Local API round-trip (set en, defaultLocale/hu re-seeded via re-running the migration script) — hu reads "Kapcsolatfelvétel", en reads "Contact". Real browser: admin UI locale switcher (hu/en) in the top bar, fields show "— hu"/"— en" per-locale labels, switching locale swaps the visible value correctly on the Common global editor. build/lint/tsc/test (58 passed) all clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 13:07:36 +02:00
Do SikiandClaude Sonnet 5	1b587ac373	sync: mark MITHOME-89 done, add MITHOME-118 to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:34:25 +02:00
Do SikiandClaude Sonnet 5	776fa66bc8	feat(cms): Partners + Media collection MVP (MITHOME-89) ... Payload built-in upload collection (Media) + a Partners collection (name, url, logo -> Media relationship) mirroring home.json's partners.items. Scope decision (see Plane MITHOME-89/118): the old logo editor (crop/rotate/transparent-background — MITHOME-76/84) is entirely client-side canvas logic (scripts/cms-logo-client.js, 345 lines), not server-side processing. Porting that UX into the Payload admin is a real custom React field component, split into its own ticket (MITHOME-118) rather than bundled here. This ticket covers plain upload only. - src/collections/Media.ts, src/collections/Partners.ts, registered in payload.config.ts. - migrate-content-to-payload.ts: upsertPartner() uploads the existing processed logo file (filePath) into Media (idempotent — matched by `alt` == partner name) and upserts the Partner document (matched by `name`). - .gitignore: Payload's default local upload storage lands at proto/media/ (not proto/public/) — runtime data, not source, needs a persistent volume in staging/production (flagged for MITHOME-97). Also ignored the generated src/payload-types.ts. Verified: migration run twice against the real dev MongoDB produced exactly 1 Media doc + 1 Partner doc (no duplicates, confirmed via mongosh) with the correct file size (12289 bytes, matching the source PNG). Real browser: logged into /admin, Partners list shows the migrated entry, and the document editor renders the logo thumbnail (270x80, 12KB) correctly. build/lint/tsc/test (58 passed) all clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:33:34 +02:00
Do SikiandClaude Sonnet 5	928439bc7b	sync: add MITHOME-117 visual design-protection ticket ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:25:18 +02:00
Do SikiandClaude Sonnet 5	1c9e231a16	sync: add localization epic (MITHOME-109..116) to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:22:08 +02:00
Do SikiandClaude Sonnet 5	329269aeb1	sync: mark MITHOME-88 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:16:35 +02:00
Do SikiandClaude Sonnet 5	17c6d63ae3	feat(cms): LegalPages collection + migration (MITHOME-88) ... Slug-based collection mirroring LegalPageContent (proto/src/content/ types.ts) for the two legal pages (adatvedelem, hasznalati-feltetelek). - src/collections/LegalPages.ts: slug (unique), title, lastUpdated, sections[] (id/title/content). `content` stays a plain textarea, not lexical richText — the current frontend (src/app/(frontend)/adatvedelem/page.tsx) renders it through a hand-rolled "•"/"**bold**" regex converter, not a real Markdown/ richText parser, matching the same bootstrap-scope call made for Contact.gdpr.label in MITHOME-87. - Registered in payload.config.ts. - migrate-content-to-payload.ts: added an idempotent upsertLegalPage helper (find-by-slug, then update or create — Collections don't have Globals' fixed-slug updateGlobal) and seeded both legal pages from their existing JSON. Verified: migration run twice against the real dev MongoDB produced exactly 2 documents (no duplicates) — confirmed via mongosh. Real browser: logged into /admin, Legal Pages list shows both entries with correct titles/slugs, opened the adatvedelem document and the slug/ title/body fields all show the migrated content correctly. build/lint/ tsc/test (58 passed) all clean. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:16:09 +02:00
Do SikiandClaude Sonnet 5	570f4b45e5	docs: add program-hid-update skill for the Program Híd artifact ... Project-scoped Claude Code skill that re-queries the MITHOME and PLATFM Plane projects, recomputes the roadmap-phase/bridge/epic-progress data, and republishes the same Program Híd artifact (claude.ai/code/artifact/95d7def2-c648-4fb7-a3f3-0d172b1c21ab) in place. Includes the canonical artifact source (source.html) so future runs edit a versioned file instead of a session-local scratchpad copy. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 12:05:23 +02:00
Do SikiandClaude Sonnet 5	91a9d97a59	docs: note PLATFM-1 program-level convergence map in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 11:52:54 +02:00
Do SikiandClaude Sonnet 5	72a5a10476	sync: reconcile Hermes epic with PLATFM-10/PLATFM-12 ... MITHOME-99 (Hermes Agent EPIC) and its 6 pure-AI-pilot subtasks (MITHOME-100/101/104/106/107/108) duplicated work already planned under PLATFM-10 (managed AI features pilot). Cancelled them in Plane, linked to PLATFM-10 and the new PLATFM-12 engine-choice ADR. The genuine MITHOME-side responsibility (the website's own event source) survives as MITHOME-102/103/105, reparented under the Payload epic (MITHOME-85) and reworded to target a PLATFM-2-compatible event schema (idempotencyKey, eventType, data) instead of a Hermes-specific webhook. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 11:44:26 +02:00
Do SikiandClaude Sonnet 5	c4e3d91640	sync: add Hermes Agent epic (MITHOME-99..108) to TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 11:03:37 +02:00
Do SikiandClaude Sonnet 5	a3d7e9ce75	chore(cms): disable Payload's anonymous telemetry ... Payload sends anonymous usage telemetry to its own servers by default. The site is self-hosted specifically so the client's data never leaves our own infrastructure (see the legal/GDPR discussion in chat) — that reasoning extends to Payload's own runtime telemetry too, so opt out via telemetry: false in payload.config.ts. Verified: build and dev server produce no telemetry notice, and the admin dashboard's network requests (checked in a real browser) are all to localhost — no outbound telemetry calls. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 10:52:54 +02:00
Do SikiandClaude Sonnet 5	db2f38743f	sync: mark MITHOME-98 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 10:39:58 +02:00
Do SikiandClaude Sonnet 5	4c54c639e5	fix(docker): authenticate the dev app's MongoDB URI (MITHOME-98) ... docker-compose.dev.yml's mongodb service sets MONGO_INITDB_ROOT_USERNAME/ PASSWORD, which makes the official mongo image enable --auth — but the app service's MONGODB_URI was unauthenticated (mongodb://mongodb:27017/mozdit). Same bug class as MITHOME-32 (staging/production), but that ticket covers docker-compose.staging.yml /docker-compose.prod.yml specifically, not this dev file — hence the separate MITHOME-98. Why /api/health never caught it: that route is a pure liveness check and never touches MongoDB. Only an endpoint that actually performs a DB operation exercises the bug. Verified live (docker compose -f docker-compose.dev.yml up --build): - Reproduced the failure first: inside the running app container, a plain `mongodb://mongodb:27017/mozdit` connection's findOne() throws "Command find requires authentication" — confirms the hypothesis that the app fails only on a real query, not at startup. - With the fix in place: POST /api/contact returns 200 with a submissionId, and the document is actually present in contact_submissions (checked via mongosh) — a real, previously- broken write path now works end to end. - npm test: 58/58 passed (unaffected, as expected for a docker-compose/doc-only change). Also fixed the same stale unauthenticated example in DOCKER.md. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 10:39:29 +02:00
Do SikiandClaude Sonnet 5	018a1f2767	sync: mark MITHOME-87 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:42:12 +02:00
Do SikiandClaude Sonnet 5	3132fcb8eb	feat(cms): Home/About/Services/Contact/Common Globals + JSON migration (MITHOME-87) ... Payload Global configs mirroring proto/src/content/types.ts: - src/globals/{Home,About,Services,Contact,Common}.ts - src/globals/fields/stringArray.ts — shared helper: Payload has no native string[] field, so every plain string array from the old content types (trustBullets, paragraphs, features, spec items, …) becomes an array of one-field { value } objects. - home.partners is intentionally NOT included — that becomes its own Partners collection (logo -> Media upload) in MITHOME-89, to avoid two disagreeing sources for the same data. - contact.form.fields.gdpr.label stays a plain textarea (not lexical richText): the JSON source is a hand-written HTML string with an <a> tag; richText's node-tree serialization would need its own migration/render logic, out of scope for this bootstrap pass. scripts/migrate-content-to-payload.ts: one-shot, idempotent Local API migration reading the existing JSON files and calling updateGlobal — does not touch or delete the JSON files. Run via the new `npm run migrate:content` script. Registered the five Globals in payload.config.ts. Also included here (belongs with the previous "resolve double-root- layout conflict" commit but didn't actually get staged there — verified only now by diffing HEAD against the working tree): (frontend)/layout.tsx's relative imports corrected to ../../ instead of ../ (one directory deeper than the original src/app/layout.tsx). Verified: - npm run build / lint, tsc --noEmit, npm test (58 passed) all clean - npm run migrate:content against the real dev MongoDB container, then read back via payload.findGlobal() — hero.title, trustBullets, services.items[0].features, footer.address, faq.items.length all match the JSON source - Real browser: logged into /admin, opened the Home global editor — Hero/Trust bullets group renders and shows the migrated Hungarian content correctly (see screenshot shared in chat) Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:41:03 +02:00
Do SikiandClaude Sonnet 5	3183098926	chore(deps): pin tsx 4.23.13 and add migrate:content script ... tsx 4.22.4 (the version resolved before this was an explicit dependency) fails on Node v25.6.1 with "T.registerHooks is not a function" — its CommonJS-require hook feature-detection finds node:module's registerHooks but calls it with a shape that version of Node no longer accepts. This broke both the `payload` CLI (needed for `generate:importmap`, see next commit) and would have broken `npm run migrate:content` (MITHOME-87) the same way. 4.23.13 fixes it. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:40:24 +02:00
Do SikiandClaude Sonnet 5	a661739844	fix(cms): resolve double-root-layout conflict between the site and Payload admin ... Next.js 16 requires either one shared root layout for every route, or each top-level route group to be fully self-contained (no ancestor layout.tsx above it). MITHOME-86 added (payload)/layout.tsx — which itself renders Payload's own <html>/<body> via <RootLayout> — while src/app/layout.tsx still existed as a shared ancestor and did the same. The result was two React trees fighting over <html>/<body>/<head>, surfacing in the browser as hydration failures and "You are mounting a new html component" errors on /admin (invisible to curl-based checks in the MITHOME-86 verification, since they only exercise SSR, not client hydration — that verification's "confirmed live" claim was therefore incomplete; caught now with an actual browser). Fix, per Payload's documented multi-root pattern: move every existing site route (page.tsx, globals.css, kapcsolat/szolgaltatasok/rolunk/ adatvedelem/felhasznalasi-feltetelek) into a new (frontend) route group with its own layout.tsx (renamed from src/app/layout.tsx, with relative imports adjusted one level deeper), as a sibling of (payload). No shared layout.tsx remains directly under src/app/. Verified in a real browser (not just curl): /admin/login and the dashboard now render and hydrate cleanly, and all site routes (/, /rolunk, /szolgaltatasok, /kapcsolat, /adatvedelem, /felhasznalasi-feltetelek) are unaffected — same output, just moved. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:40:00 +02:00
Do SikiandClaude Sonnet 5	2a4f33172b	sync: mark MITHOME-86 done in TODO.md ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:21:32 +02:00
Do SikiandClaude Sonnet 5	849acf4c34	fix(config): disable Next.js 16 auto-generated agent-rules files ... \`next dev\` (Next.js 16) writes proto/AGENTS.md and proto/CLAUDE.md on every run to brief AI agents on framework changes. This project already has its own agent instruction system (root CLAUDE.md -> .agent/) — a second, unrelated proto/CLAUDE.md stub would conflict with/shadow it for anyone working inside proto/. Disabled via agentRules: false. Verified live: MITHOME-86's admin route renders end-to-end against a real MongoDB (docker-compose.dev.yml mongodb service) — GET /admin 200 with the create-first-user flow, GET /api/users correctly 403s for an anonymous request, /api/health unaffected. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:19:25 +02:00
Do SikiandClaude Sonnet 5	1600d99c5d	feat(cms): Payload CMS bootstrap — config, MongoDB adapter, admin routes (MITHOME-86) ... Alapinstalláció a Payload CMS-re való áttéréshez (EPIC MITHOME-85): - payload@3.88.0, @payloadcms/next, @payloadcms/db-mongodb, @payloadcms/richtext-lexical, graphql, sharp telepítve - src/payload.config.ts: mongooseAdapter a meglévő MONGODB_URI-ra (ugyanaz az adatbázis, mint a Mongoose/mongodb rétegnek), lexical editor, PAYLOAD_SECRET env-ből - src/collections/Users.ts: minimális auth collection — Payload nem tud admin felületet renderelni auth collection nélkül. Ez csak a bootstraphez kell; a valódi access control/jelszó-politika MITHOME-90 feladata. - App Router route group (src/app/(payload)/): admin UI ([[...segments]]), REST (api/[...slug]), GraphQL + playground route-ok, root layout — a szokásos Payload v3 Next.js integrációs minta szerint - next.config.ts: withPayload() wrapper a route handler bundling-hoz - tsconfig.json: @payload-config path alias -> src/payload.config.ts (ez oldja fel a webpack/turbopack importot is, nem csak a type-checket) - PAYLOAD_SECRET env var: generált dev érték a .env.local-ban (gitignore-olt), changeme placeholder + generálási megjegyzés a staging/production .env példafájlokban, dokumentálva a CLAUDE.md env-lista részében Ismert, még nem javított biztonsági advisory a felvett payload@3.88.0-ban (GHSA-jg8r-5jh2-v2xj, moderate, CWE-307: az admin account-unlock alapból más fiókok lockoutját is felold hitelesített usernek) — nincs újabb patch-elt verzió jelenleg, nyomon követve MITHOME-90 alatt. Ellenőrizve ezen a commiton: npm run build, npm run lint, tsc --noEmit, npm test (58 passed) — mind zöld. Az admin bejelentkezés/DB-kapcsolat élő tesztje MongoDB-t igényel (jelen környezetben Docker daemon nem fut, ez lokálisan `docker compose -f docker-compose.dev.yml up -d mongodb` után `npm run dev` + http://localhost:3000/admin-mal ellenőrizhető). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:14:51 +02:00
Do SikiandClaude Sonnet 5	30364fcab7	sync: update TODO.md with Payload CMS epic (MITHOME-85..97) ... Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:14:31 +02:00
Do SikiandClaude Sonnet 5	6cb99f603a	chore(deps): upgrade Next.js to 16.3.4 for Payload CMS compatibility ... Payload 3.88.0's peer range for `next` is >=15.2.9 <15.3.0 || >=15.3.9 <15.4.0 || >=15.4.11 <15.5.0 || >=16.2.6 <17.0.0 — the project's previous 15.5.23 fell in the unsupported gap between the 15.4.x and 16.2.x ranges. Upgrading to 16.3.4 (React 19.1.0 stays compatible) unblocks MITHOME-86. - next.config.ts: drop the removed `eslint.ignoreDuringBuilds` option (Next 16 no longer runs ESLint during `next build`) - eslint.config.mjs: import eslint-config-next's native flat-config arrays directly instead of bridging through FlatCompat, which threw "Converting circular structure to JSON" under ESLint 9 with the upgraded config - tsconfig.json: Next 16's own migration set `jsx: react-jsx` and added `.next/dev/types/**/*.ts` to `include` - ThemeProvider.tsx: suppress two react-hooks/set-state-in-effect false positives (new rule shipped with eslint-config-next 16) — these effects intentionally sync state from localStorage/DOM on mount, there is no subscription to move the setState into Verified: npm run build, npm run lint, tsc --noEmit, npm test (58 passed) all clean on this change alone, before installing Payload. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>	2026-09-10 03:04:54 +02:00
Do Siki	38be6c0450	sync: update TODO.md with MITHOME-84 (make-transparent)	2026-08-23 11:47:25 +02:00
Do Siki	b56b81b2ba	feat(cms): make-transparent (remove white background) in the logo editor ... Adds a ⚪ Háttér átlátszóvá (fehér) button to the canvas editor. Pixels above a luminance threshold become fully transparent; a soft ramp just below keeps edges smooth. Lets white-background partner/site logos sit on any page background. Closes MITHOME-84	2026-08-23 11:46:29 +02:00
Do Siki	f6846ad217	test(cms): partner-logo test uses unique names and only cleans its own files ... The previous cleanup emptied proto/public/partners/ entirely, deleting real committed partner logos during the pre-deploy run. Now the test uploads to unique run-specific filenames and removes only those.	2026-08-23 11:42:24 +02:00
Do Siki	4b48f27302	content: add Angele Pihenőház partner (logo + URL)	2026-08-23 11:41:13 +02:00
Do Siki	1b565af4d5	sync: update TODO.md with MITHOME-83 (partners section)	2026-08-23 10:24:52 +02:00
Do Siki	611e229af9	test(cms): clean up all partner-logo test artifacts	2026-08-23 10:23:00 +02:00
Do Siki	f65c22987f	feat: partners section on the homepage (logo + URL, CMS upload) ... - home.json gains a partners block (title/subtitle/items: name, url, logo), rendered on the homepage under the services section (next/image logos linking out with rel=noopener) - CMS: partner logos uploadable from the 🎨 Logó page via POST /partner-logo (PNG, 1 MiB cap, filename sanitized to a slug, written to public/partners/) - schema + types extended; guide updated Closes MITHOME-83	2026-08-23 10:22:22 +02:00
Do Siki	410b4a2e2f	docs: refresh all documentation to the current state ... - agent docs: Linear (ZEE-*) → Plane (MITHOME-*) everywhere (task tracking, commit examples, workflows, env vars) - testing steering: replace the obsolete Gherkin/Linear reporting with the pre-deploy suite and the CMS test scripts - README: rewrite to Next.js 15, local deploy, Plane, CMS, security monitoring - DOCKER/proto docs: correct dev-stack ports (app 8080, mongo 27018) and Next.js 15 - content-editor-recovery: mark the old 'next steps' as done - mark clearly-obsolete Linear/GitHub-era guides as deprecated (banner) — LINEAR-SYNC, GITHUB-CICD/INTEGRATION, TEST-MANAGEMENT/REPORTING, traceability, sync-status analysis, requirements docs	2026-08-22 19:41:50 +02:00
Do Siki	8ee5befe10	fix(security): real newlines in alert details for the ntfy body ... The \n in the accumulated alert text was a literal backslash-n, so the details would have rendered as one garbled line. printf -v now appends real newlines; the notification body joins header + details with a real line break.	2026-08-22 14:37:46 +02:00
Do Siki	164b19cdb8	fix(security): filter docker exec errors and include finding details in ntfy body ... - a container stopping mid-scan produced 'cannot exec in a stopped state' as a false-positive finding; such exec errors are now filtered out - the ntfy notification body now carries the actual alert lines, not just a counter	2026-08-22 14:33:06 +02:00
Do Siki	8903ec9562	fix(security): use project-specific ntfy topic st_limidev_security	2026-08-22 14:04:50 +02:00
Do Siki	de0bd2fc07	feat(security): push scan alerts to the local ntfy server ... On findings the scan now POSTs a high-priority notification to topic st_security on the host ntfy (127.0.0.1:2586), authenticated with the si_17t_pro token read from /etc/ntfy/credentials/auth.env (never logged). Topic/cred/URL overridable via env for testing.	2026-08-22 13:43:59 +02:00
Do Siki	00d6cf9786	sync: update TODO.md with MITHOME-82 (security scan)	2026-08-22 13:40:26 +02:00
Do Siki	28778aef88	feat(security): lightweight cryptominer/backdoor detection script ... Periodic host+container sweep for the exact indicators seen in the staging miner incident: decoy process names (redis-server/kworkerd/xmrig/ssl_client/ init.sh), /tmp/.kworkerd and .redis-server.pid artifacts, and high-CPU containers. Findings are logged and exit 1 for cron MAILTO alerting. Closes MITHOME-82	2026-08-22 13:39:46 +02:00
Do Siki	c73cdd3b2f	sync: update TODO.md with MITHOME-78/79/80/81 (review fixes)	2026-08-22 12:39:20 +02:00
Do Siki	d908f6b1b4	chore(quality): type-check and lint gates in pre-deploy, clean lint/tsc ... - pre-deploy suite now runs tsc --noEmit and eslint; any failure aborts the release - fix all TypeScript errors (FooterConfig.copyright removed after the CMS move; test guards/casts) - fix all ESLint errors: <a>→<Link> and <img>→<Image> in Header/Footer, remove unused imports and explicit any in src - eslint config relaxes no-explicit-any/no-require-imports/no-unused-vars for test and CommonJS config files (legitimate usage) Closes MITHOME-81	2026-08-22 12:37:22 +02:00
Do Siki	162e5782e9	refactor(cms): split oversized modules below the 400-line limit ... - content-editor.js: extract the /save handler to scripts/cms-save.js - cms-logo-page.js: inline the ~280-line canvas editor script to scripts/cms-logo-client.js (page is now the HTML/CSS shell only) - cms-editor-client.js: move the keyboard-shortcut section to scripts/cms-editor-shortcuts.js, inlined after the main client All modules now under the hard limit; full pre-deploy suite green. Closes MITHOME-80	2026-08-22 12:31:28 +02:00
Do Siki	15529c7705	fix: contact length limits + logger/next.config nitpicks + dep updates ... - /api/contact enforces per-field length caps (name/email/subject/message) before sanitization/persistence; over-long message returns 400 without touching Mongo (test added) - logger: crypto-based request id (randomUUID) instead of Math.random().substr; defaultMeta.version prefers DEPLOY_VERSION over npm_package_version - next.config: move Turbopack svg rule from deprecated experimental.turbo to top-level turbopack - deps: bump next 15.5.2 → 15.5.23; npm audit fix (19 → 3, remaining are transitive sharp/libvips DoS advisories, not exploitable for static images) Closes MITHOME-78, MITHOME-79	2026-08-22 12:22:27 +02:00
Do Siki	b8f9e8cfdf	sync: update TODO.md with MITHOME-77 (web hygiene)	2026-08-22 12:14:42 +02:00
Do Siki	9f1fb349c2	fix(web): hygiene — OG image/metadataBase, Header a11y text + nav flag, dead code ... - siteConfig.ogImage pointed to an existing asset; metadataBase added so relative OG/Twitter URLs resolve against the real origin instead of localhost - Header sr-only menu label moved to common.json (a11y.openMenu/closeMenu); navigation primary styling driven by a NavigationItem.primary flag instead of brittle 'Kapcsolat' string comparisons - remove dead code: lib/site-config.ts (unused hybrid config) and the unused, schema-divergent siteConfig.contact.form - ContactConfig type cleaned up (address/form removed) Closes MITHOME-77	2026-08-22 12:12:48 +02:00
Do Siki	4c2913e131	feat(cms): add interactive canvas logo editor modal ... Closes MITHOME-76: - Interactive Canvas-based modal for logo editing in CMS - Crop with presets (1:1, 3:1, 4:1, 16:9, free) - Drag-to-pan positioning and wheel/slider zoom - 90 deg rotation and horizontal/vertical flip - Configurable padding/margins around logo - Brightness, contrast, and color invert filters - Direct high-DPI (2x retina) PNG export and atomic save	2026-08-20 11:53:23 +02:00
Do Siki	c5d5198fbf	fix(cms): implement v2 security and stability review findings ... Resolves: - CSRF false positive checked (global POST protection) - Publish mutex to prevent git lock / double deploy - Basic Auth rate limit checked before credential evaluation - Memory leak in rate limiter (added GC interval) - XSS in Toast messages - XSS in data-path attribute - CI healthcheck port mismatch (3000 -> 8080) - Added security headers (X-Frame-Options, X-Content-Type-Options)	2026-08-20 11:35:01 +02:00
Do Siki	768297031d	sync: update TODO.md with MITHOME-75 (keyboard shortcuts)	2026-08-19 22:53:54 +02:00
Do Siki	6030c48abb	feat(cms): keyboard shortcuts — Ctrl+S save, Ctrl+P publish, ? help ... - Ctrl/Cmd+S saves (native browser save dialog suppressed) - Ctrl/Cmd+P publishes; Ctrl/Cmd+Shift+V opens the Versions panel - '?' toggles a shortcuts overlay (Esc/click closes) - plain typing in inputs never triggers actions (modifiers required; '?' only outside editing targets) - jsdom regression tests run the real client script with dispatched KeyboardEvents; the client is evaluated once per suite because each eval would stack another keydown listener on the shared document Closes MITHOME-75	2026-08-19 22:52:09 +02:00
Do Siki	db0e898ac4	sync: update TODO.md with MITHOME-74 (publish deploy cwd fix)	2026-08-19 17:41:52 +02:00
Do Siki	02d6755874	test(footer): assert address from common.json instead of hardcoded city ... The footer address is CMS-editable now; the test must follow the single source instead of a fixed city.	2026-08-19 17:37:36 +02:00
Do Siki	42533ec0aa	fix(cms): deploy exec was missing cwd — landed on / and never ran ... Root cause of publishes not rebuilding the site: the deploy exec child started in the process working directory (repo root), so 'cd ../../../' resolved to the filesystem root, where creating deploy.log failed with Permission denied. The git publish command already used cwd: CONTENT_DIR; the deploy child now does too (caught via live cwd/touch diagnostics in the service context). Closes MITHOME-74	2026-08-19 17:14:02 +02:00
Do Siki	1fb787413f	sync: update TODO.md with MITHOME-73 (CMS-editable address)	2026-08-19 16:56:19 +02:00
Do Siki	9365c0f1ee	feat(footer): CMS-editable company address (common.json footer.address) ... 'Budapest, Magyarország' lived hardcoded in site.ts. It now lives in common.json (footer.address), editable via the Közös szövegek tab, and both consumers (Footer, Kapcsolat page) read it from there — single source. Schema and types extended; site.ts keeps only the email. Closes MITHOME-73	2026-08-19 16:53:16 +02:00
Do Siki	9c7dc1d35e	sync: update TODO.md with MITHOME-72 (publish deploy reliability)	2026-08-19 15:34:55 +02:00
Do Siki	068e148da1	fix(cms): run publish deploy as direct child — detached spawn died under systemd ... Root-caused with systemd-run repros: under the unit's hardening flags the backgrounded grandchild ('cmd &' / setsid) died silently, so a CMS publish committed+pushed but never rebuilt the site (stale content, no deploy.log, no trace). A direct (non-detached) exec child provably survives the same flags; the response is sent first, output goes to deploy.log, and the callback's audit entry now reports real deploy completion (ok/error). Closes MITHOME-72	2026-08-19 15:27:51 +02:00
Do Siki	a29a1f461b	fix(cms): detach and audit the publish-triggered deploy (systemd-safe) ... A CMS publish's background deploy silently never ran under systemd (naive 'cmd &' child died with the spawning shell; no log, no trace — the site kept serving stale content). The spawn now uses setsid+nohup+stdin-null so it survives any parent exit, and writes deploy_spawned / deploy_exec_exit audit entries so a failed spawn can never be silent again. Closes MITHOME-72	2026-08-19 15:16:19 +02:00
Do Siki	b0cd270dc5	sync: update TODO.md with MITHOME-71 (fresh version tag)	2026-08-19 14:41:19 +02:00
Do Siki	14a72a3ffe	fix(cms): keep version tag fresh — deploy restarts CMS, editor page no-store ... The version tag is the git SHA read at CMS startup, but the deploy script only rebuilt the website container, leaving the tag stale (v8838304 shown after aa8d926 was live). The local deploy script now restarts the CMS service after the server-side deploy (the CMS publish flow is unaffected — it calls deploy.sh directly and never restarts itself). The editor main page also gains Cache-Control: no-store so browsers stop caching it. Closes MITHOME-71	2026-08-19 14:38:40 +02:00
Do Siki	aa8d92646c	test(cms): run-unique markers so a crashed run cannot poison the next ... The versions integration test asserted against fixed marker strings; if a run crashed before restoring contact.json, the next run read the polluted file as its baseline and its expectations collapsed. Markers now carry a per-run timestamp.	2026-08-19 14:30:58 +02:00
Do Siki	c0579198f8	sync: update TODO.md with MITHOME-70 (pre-deploy test suite)	2026-08-19 14:16:04 +02:00
Do Siki	5db71998eb	feat(test): comprehensive pre-deploy test suite as single entry point ... scripts/pre-deploy-tests.sh runs every local test group before a deploy: proto unit (jest), content schema validation, all CMS integration suites (security, serializer, save, optimistic lock, versions, logo, login, logout, guide, bottom bar), publish command/integration and plane sync unit tests. Per-group PASS/FAIL summary; non-zero exit on any failure. deploy_to_stage_on_local.sh now runs the full suite as step 1 — a failing group aborts the release before push. Deploy workflow docs updated. Closes MITHOME-70	2026-08-19 14:15:33 +02:00
Do Siki	067b15c50e	sync: update TODO.md with MITHOME-68/69 (409 UX + stable bottom bar)	2026-08-19 14:05:54 +02:00
Do Siki	88383049d5	fix(cms): stable bottom bar and self-save no longer trips the 409 lock ... MITHOME-68: the optimistic-lock fingerprint was frozen at page load, so the user's own second save 409'd. /save now returns the hash of the written content and the client refreshes CONTENT_HASH on success — 409 only fires for genuine external changes (deploy, other tab, restore). Also: successful logins no longer consume the auth failure budget (only failed attempts do). MITHOME-69: bottom bar items no longer shift while saving/publishing — the status message occupies a constant flex slot (visibility instead of display), the publish button locks its width while running and restores its env-specific label, auto margins removed. Layout guard test added. Test markers are now run-unique so a crashed run can never poison the next one's expectations.	2026-08-19 14:04:49 +02:00
Do Siki	41a2259ede	sync: update TODO.md with MITHOME-67 (delete/reindex fix)	2026-08-19 13:31:56 +02:00
Do Siki	5d2141ec88	fix(cms): capture array container before node removal so reindex runs ... The ❌ delete buttons called wrap.closest('.array-items') AFTER remove(); a detached node has no ancestors, so closest() returned null and reindexItems() silently skipped. Remaining items kept their old indices, collect() produced sparse arrays (null holes) and saves failed schema validation, e.g. '$.details.services[1].specs.items[0]: string érték szükséges'. Capture the container before remove() for both str-item and obj-card delete handlers. Regression test runs the real browser script in jsdom and clicks the actual delete buttons (nested string array + object card reindexing). Closes MITHOME-67	2026-08-19 13:30:53 +02:00
Do Siki	19f2fdfece	refactor(cms): extract /versions and /restore route handling to cms-versions.js ... Companion to the cms-logo.js extraction: keeps content-editor.js under the 400-line hard limit. No behavior change — covered by test-content-editor-versions.js.	2026-08-19 12:47:24 +02:00
Do Siki	d2ee13bb91	feat(cms): logo upload with preview, backup and audit ... - 🎨 Logó page in the CMS bottom bar: replace the website header logo and the CMS login icon with a PNG upload (magic-byte validation, 1 MiB cap) - the replaced logo gets a timestamped backup in .content-backups; every upload is audited (logo_updated) - /logo.png?variant=header serves the header variant for the preview - publish stages proto/public too, so logo changes ride the same commit+deploy pipeline as content - route handling extracted to scripts/cms-logo.js to stay under the 400-line limit - integration test: upload+replace+backup, variant preview, 415/413/400, CSRF, auth Closes MITHOME-65	2026-08-19 12:46:55 +02:00
Do Siki	fe4a6a1e92	feat(footer): CMS-editable copyright with 2002–current year range ... The copyright text lived in site.ts with a build-time year and was not CMS-editable. It now lives in common.json (footer.copyright, editable via the Közös szövegek tab) with a {year} placeholder that resolves to the current year at render: '© 2002–{year} mozdIT Bt. Minden jog fenntartva.' Schema and types extended; site.ts keeps only the footer links. Closes MITHOME-66	2026-08-19 12:44:48 +02:00
Do Siki	03615d5959	sync: update TODO.md with MITHOME-64 (versions panel)	2026-08-18 23:46:13 +02:00
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	d15cc05c36	sync: update TODO.md with MITHOME-63 (deploy versioning)	2026-08-18 21:24:23 +02:00
Do Siki	e2a8ac13eb	fix(deploy): declare DEPLOY_VERSION ARG in the runner stage ... ENV does not carry across build stages: the value set in the builder never reached the running container, so /api/health reported deployVersion: null and SMOKE-01 failed. Re-declare the ARG in the runner stage.	2026-08-18 21:22:40 +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	edd2e46ae3	sync: update TODO.md with MITHOME-62 (Safari-compatible auth)	2026-08-18 21:14:45 +02:00
Do Siki	a7b1a2cab2	fix(cms): Safari-compatible authentication ... Safari-specific deviations fixed: 1. Safari shows its native auth dialog on fetch() calls answered with a 401 + WWW-Authenticate challenge (e.g. save with an expired session). All CMS 401 responses now omit WWW-Authenticate; browsers use the styled /login page instead. 2. Safari caches Basic credentials and resends them automatically, which made logout ineffective (a navigation after logout went straight back into the editor). Browser navigations (GET + text/html) now authenticate ONLY via the session cookie; Basic Auth remains valid for non-browser clients (curl, API). 3. /login and redirects send Cache-Control: no-store so Safari does not cache the login page or the 302. Closes MITHOME-62	2026-08-18 21:14:12 +02:00
Do Siki	27b84cb87c	sync: update TODO.md with MITHOME-61 (optimistic locking)	2026-08-18 20:57:35 +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	bdf9aac4d0	content: apply copy review — concrete, credible claims and CTAs ... - hero: state the actual offering (hosting, mail, domains) instead of a mission statement - security USP: list concrete measures instead of 'maximális teljesítmény' promise - hosting: replace '99% uptime garancia' with the 99.9% availability goal (excluding planned maintenance) — no absolute guarantee claim without SLA backing - email: encrypted webmail/IMAP access wording; domain: registration, renewal and DNS in one place; SPF/DKIM/DMARC explained by purpose - per-service CTA texts instead of the generic 'További információk' - main CTA: 'Kérjen személyre szabott konzultációt' (smoke test updated to match) - bottom CTA asks the visitor to describe their need briefly	2026-08-18 20:39:24 +02:00
Do Siki	fff834a48a	sync: update TODO.md with MITHOME-60 (publish hardening)	2026-08-18 20:25:45 +02:00
Do Siki	c4c89f644e	fix(cms): deploy only on real changes, abort failed rebases, test publish ... Review follow-up on MITHOME-59: - no-op publish no longer triggers a background deploy (deploy moved behind a deterministic hadChanges flag) - replace output-regex classification ('Already up to date.' also appears on real publishes when the remote did not move, which misclassified them as no_changes) with an explicit __NO_CONTENT_CHANGES__ marker echoed by the shell skip-branch - failed git pull --rebase is aborted immediately so the repo is never left mid-rebase; the error is reported and nothing is pushed or deployed - command + interpretation extracted to scripts/cms-publish.js - CONTENT_EDITOR_CONTENT_DIR / CONTENT_EDITOR_DEPLOY_CMD env overrides enable an integration test against throwaway git repos covering: no-change skip, real publish + deploy, rebase conflict abort - .gitignore: drop patterns already covered by .env.* - user guide: new no-changes message Closes MITHOME-60	2026-08-18 20:25:12 +02:00
Do Siki	8afc4e6899	sync: update TODO.md with MITHOME-59 (CMS publish fix)	2026-08-18 20:17:46 +02:00