3 Commits

Include renames

Author	SHA1	Message	Date
surtic86andClaude Opus 5	4530298398	Cut over-engineering found by a repo-wide audit ... - Config: auth, services, logging, queue and database only repeated the framework's own files and are gone; the others keep only the keys that differ (app version, cache serializable_classes, session cookie name, Markdown mail theme, the shares disk, three Octane values, Livewire's pagination theme and payload guards). - Email verification is removed: User never implemented MustVerifyEmail, so it was never enforced, and SealShare has a single admin and no registration. CreateNewUser goes with it. - FileEncryptionService::encryptFile() and generateSalt() were only used by tests; tests build files with encryptTestFile() in tests/Pest.php. - The expiration options are defined once, as Share::EXPIRATIONS. "30 Days" now lasts 30 days instead of a calendar month, and Admin settings only save a default expiration that is one of the options. - One-caller helpers are inlined, the uploader reads chunk responses with XHR's responseType, and starter-kit leftovers are removed. - Docker: PHP reads the PHP_* limits from the environment itself (${VAR:-default} in uploads.ini); both entrypoints stop writing the ini. docker-compose.yml shares the app and scheduler variables through one anchor. The dev image installs gd for the screenshot publisher and fake test images. - Development runs in Docker only: the composer dev script, concurrently, laravel/pail, laravel/sail, autoprefixer and the shell-quote override are gone. - phpunit.xml forces the test environment with <server> entries, so tests run in the dev container no longer use its real database. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-18 23:14:33 +02:00
Andreas Reinhold / reiniandClaude Opus 5	5853f1f7d6	Give every page the share pages' layout, at one width ... The pages were built five ways: two layouts, seven widths from 28 to 64rem and four heading styles. Every page now looks like the share pages: a centred heading over one 40rem column of outlined cards, with the floating toolbar below. - <x-page> (components/page.blade.php) is the root of every page. It draws the h1 and its line (`brand` takes the site's logo, title and description from Admin settings), an optional `mark` and `navigation` slot, then the content. It has no width prop: every page is the same <x-pane width="narrow">. - The sign-in, password reset, confirm, verify email, two-factor challenge, setup and system password pages move onto layouts/app with the brand heading and their form in a card titled with the task. layouts/auth, auth-header and the settings heading partial are gone, and so is the per-page width CSS. - Settings put their section nav under the heading; the admin pages get a description line each. FileUploader and ShareDownload no longer pass the branding to their views. - The admin dashboard's table needed about 49rem, so its shares are a list: created above the token, which opens the share, then files, size, downloads and expiry on two lines that wrap instead of clipping, and one delete button. A "Sort by" select replaces the column headers (newest, oldest, expiring soonest with never-expiring last, largest, most downloads, most files) and resets the page. The stats stay two by two. table.css and sort-header.css are no longer imported. - Branding hints in Admin settings name every page the title shows on. - Tests: PageTemplateTest renders every page once and checks one page template, one h1 and the width, and the brand heading with its fallbacks. FrameTest measures the page column instead of the auth card and the 64rem main; dashboard tests follow the list and the sort select, including expiry order. .ai/rules/views.md records <x-page>, the CHANGELOG notes the change and the website screenshots are regenerated. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-16 21:42:04 +02:00
Andreas Reinhold / reiniandClaude Opus 5	a88a052d9a	Move onto Livewire Material 2.0.0 and leave Tailwind behind ... Livewire Material 2.0.0 aligns every component with Material 3 Expressive and carries no Tailwind anywhere, so SealShare drops tailwindcss and its Vite plugin and writes its views in the package's vocabulary: layout components (<x-pane>, <x-stack>, <x-row>, <x-grid>, <x-form>) with M3's spacing tokens, the md-type-*/md-ink-* text classes, and --md-sys-* tokens in its own small stylesheet. - resources/css/app.css opens with the package's layer order, imports foundation.css and the stylesheet of each component the views render, then the scheme, regenerated with the 2025 colour rules at M3's three contrast levels. The app's own rules follow, one section per view, on tokens and on M3's breakpoints (600/840/1200/1600px) only. - Every view is rewritten in that vocabulary while SealShare keeps the shape it had: the admin table, the admin settings, the recovery codes, the share options and the download page are cards, and their fields fill them rather than stopping at the 40rem bound a card already bounds. The user settings pages became cards too, to match the admin's, each with the sections that stand apart from its one subject — deleting the account, the recovery codes — in a card beside it. Material 3 decides how a component behaves, not whether a container survives: buttons keep their label's width, a form's actions end it, and each heading level keeps one type role. - The layouts clear the floating toolbar by the --material-bottom-toolbar the package publishes, and the snackbar clears it by itself. - The two-factor setup QR code comes from QrCodeService, so it keeps a white field and quiet zone in the dark theme and still scans. - Browse Files is a real button that opens the file input, reachable and visibly focused from the keyboard. - Tests: the design test scans views, JS, CSS and app/ and checks the CSS entry both ways (no missing, no unused import). New Chromium suites cover the frame, settings and admin, the share flow, and every page at M3's breakpoint edges (599/600, 839/840, 1199/1200, 1600px). The package's renamed data-md-* hooks replace the 1.x ones. - Boost's update brings the material-3 guideline and skill and drops the Tailwind skill. composer.json requires nonameweb/livewire-material ^2.0 from the Gitea repository, resolved at the 2.0.0 tag. The CHANGELOG records the move as 2.1.0. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-09-15 22:30:51 +02:00