4 Commits

Author	SHA1	Message	Date
admin	7f3e58ff0a	The app page as one column — the approved mockup ... v0.315.0 worked and looked, in the operator's words, messy: boxes of different widths stacked down the page, with the same card shape around things you act on and things you only read. The mockup approved on 2026-10-15 replaces it, and each of its three rules has a reason: ONE COLUMN OF ONE WIDTH (820px). Differing widths read as a page assembled by accident. SECTIONS ARE HAIRLINES, NOT CARDS. A card says "this is a thing you act on"; most of an app page is a thing you READ, so a card there is a promise the content cannot keep. A BOX MEANS SOMETHING. Exactly two remain: blue when the app is waiting for the household, amber when something is risky. The exception-colour principle applied to shape as well. What moved: - the hero loses its box: a 64px logo tile, the name at 26px, the tagline, then hairline chips (state, lifecycle, update) and meta text (the address, the last automatic update); - the tabs are links with a 2px blue underline under the open one — no pills, no fills; - sections are `padding: 28px 0` with a bottom hairline; rows are a 200px label column so every value on the page starts at the same x, and stack under 720px; - the after-start callout is now the FIRST thing on Beallitasok. A household opening a Plex that wants its claim code should meet the code box, not a Restart button; - "2. mentes beallitasa — <app>" and "<app> — Exportalas" are gone: they were the headings of pages that no longer exist, on a tab that already says which app this is; - the settings tab gains "Cim es kulcsok" with one address row, and the disabled subdomain input that said the same thing is skipped for an installed app (the install wizard still asks); - the "this app is already installed, the settings are read-only" BANNER becomes the hint under the fields it is about; - the install wizard gets the same back link, hero and column, so pressing Telepites does not land the household on a page that looks like a different product. THE AUTO-UPDATE SUCCESS BANNER IS GONE. It was a full-width blue box above the tabs, level with "the update failed" and "your files are missing". A success that asked nothing of the household is a date, and it is now meta text in the hero. Every banner that DOES need a decision — a failed update, a hold, lost files, a missing drive, an interrupted install — is untouched, above the tabs, exactly where R-571 puts it. Tests: TestAppPage_OneColumnLayout (one column, one aria-current, no card-shaped section, no success banner), TestAppPage_AutoUpdateSuccessIsMetaNotBanner, TestAppPage_CalloutsOnlyForAskAndWarn (one blue callout on a waiting app and it comes first; one amber on a same-disk backup; none on the good case). Four red-proofs recorded in REPORT. app_row_dedup_gate convicted `.app-row`, correctly: that class already means "a row in the app list". The app page's label/value row is `.app-field-row`. Restoring the list's own rule after an over-broad rename was part of the fix. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y	2026-10-15 20:29:56 +02:00
admin	db52f5a4cf	v0.315.0: close the log tab's <script> — the live poller was dead, and a test now says so ... FOUND IN A BROWSER. The log tab's body was lifted out of the old logs.html by line range and the range stopped one line short, so the closing </script> never came with it. Everything downstream agreed the page was fine: - html/template parsed it, - the page rendered and looked right, - TestAppPage_EachTabRendersItsOwnContent found `setInterval(window.fetchLogs` exactly where it expected it, because the TEXT was there. Chrome refused the whole block with "SyntaxError: Unexpected token '<'" at the `</div>` that followed, so the live log never refreshed. A marker proves a string is present; it does not prove the browser will execute it. TestAppPage_ScriptTagsAreBalanced now counts <script> against </script> on all seven app-page URLs and checks the last block is closed. Red-proved by removing the tag again: it fails naming the logs tab, 3 opened and 2 closed. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y	2026-10-15 19:27:21 +02:00
admin	fe0228c877	v0.315.0: style the app page's tab bar, and reuse the hero classes that already have rules ... FOUND IN A BROWSER, and findable no other way. Every endpoint-level marker passed and the page was unusable: the tab bar rendered as four bare underlined links run together, and the app logo filled a third of the screen. The shell had been written with new class names — app-hero, app-hero-logo, app-tabs — and only the first two of those had any CSS at all, under the names the design system already uses. - the shell now reuses .app-info-hero / .app-info-logo / .app-info-hero-text, which carry the 80px logo box, the hairline border and the 2px radius. Inventing a parallel name is what left the logo unsized; REUSE.md's first rule, learned again. - .app-tabs / .app-tab / .app-tab-active are genuinely new and are now styled to design system v2: 2px radius, hairline --line border, no shadow, --text-2 for an inactive tab and --blue-bright only for the one the household is on (blue marks where you are, not a deviation), the active tab sitting on the bar's own line, and a narrower gutter under 640px. - .after-start-card gets a blue left hairline — it is a request, not a fault, so no amber. - .app-faq gets its dt/dd rules. TestAppPage_DeployedDefaultsToSettings sliced the header at `class="app-hero"`; it now slices at the reused class and fails loudly if either marker is gone, instead of slicing on -1. The 36 app-page parity fixtures are recaptured — and no other fixture moved, which is the evidence that the shell change reaches only the app page. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y	2026-10-15 19:04:57 +02:00
admin	e66d4669d6	v0.315.0: one app page with four tabs; the guide the catalog can carry; no Raspberry Pi badge ... An app was six pages — details, install/settings, logs, export, the per-app backup panel and a details card for moving data — and every "Vissza" on them went to the app LIST, so there was no way back to the app you were looking at. It is now ONE page with four tab URLs under /apps/{slug}/, one shared header and one set of banners. settings Mukodes (Start/Restart/Stop, Stop confirms) + the cards that want something from the household + the install-time and optional settings. The default for an installed app, RENDERED at the bare URL and never redirected to. data the data folders, move to another drive, the nightly copy, the 2nd-copy setting, export guide tagline, screenshots, use cases, first steps, the catalog's guide, the FAQ, the docs link — and the WHOLE page for an app that is not installed logs the log, and the only tab whose poller runs The tabs are links, not panels: a link in an alert has to land ON a tab, and the log poller must not run on the other three. Start/Restart/Stop left the page header, where they read as menu buttons. The old /stacks/{name}/{deploy,logs,export,backup} GETs answer 302 — never 301, which a browser caches beyond anyone's reach — to the tab that now holds them, query string carried through, with name->slug resolved through the stack list rather than assumed equal. Every POST on those paths is untouched: the backup form, the app-email toggle and the reveal endpoints keep their URLs. A value asked AFTER the app starts is now generic (D2). The catalog marks a field `after_start: true` and supplies its label; the ACTION is Go, in a registry keyed by slug + env var. The catalog can never declare what runs — a declared field with no registered action renders nothing, POSTs 404 and logs one WARN with the env var KEY, never the value. A red-proof found the second half of that guard unpinned: deleting the "the catalog must have DECLARED this field" check left the suite green, and a POST for an undeclared field then reached Plex and opened the setup gate. TestAfterStart_RegistryAloneIsNotAnInvitation pins it. New catalog block app_info.guide (sections + faq + checked_version), parsed, localised field by field and rendered with the household's own address filled in. It renders only when checked_version names the image tag its author clicked through. No template carries one yet. The Pi and "csak x86" badges are gone; PiCompatible and the catalog key stay this release, or a box on 0.314.0 would read "csak x86" on every app (R-1067). template_id_gate.py now follows {{template}} includes, with a scope decoy proving the walk did not become vacuous. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_0117kRTSgs3rJWUFGxyoWN6Y	2026-10-15 18:37:50 +02:00