2 Commits

Include renames

Author	SHA1	Message	Date
mixandClaude Opus 5.5	bdeb01681d	local-time: the panel in the container's zone, named on Settings ... Agreed by the owner on 2026-10-13 (the local day, no "UTC" beside a time); the zone is the container's TZ in .env and Settings only shows it, his "Да" of 2026-10-17. Mockups c205106. Every time the panel shows is formatted in time.Local and says no zone: the logs' Time and the DMARC Received columns, a message's timeline, Overview's "Updated", Health's certificate and renewal, the filter lists, DMARC reports and windows, the auto limit's last recalculation. Stored instants stay UTC. The days counted are the zone's: delivery_log_days and sender_check_days key their rows by the local date, the sender check cuts downtime at local midnights (byDay), the log filters' days run from local midnight to local midnight. Notification mail and the test message write the zone's abbreviation after a time - they are read away from the panel. DMARC's one-day window label stays the reporter's (UTC) day. Settings box 05, Time zone, read-only: the name (UTC without TZ), its offset, and a TZ the image cannot load said to leave the times in UTC (time/zoneinfo_unix.go, initLocal) rather than named. TZ is passed by the compose file ("${TZ:-}"), in .env.example and the guide's table; tzdata is named in the image (supervisor's python3.13 brings it today). Postfix takes TZ through import_environment, so mail.log's stamps are the same zone, which closes the trap the roadmap wrote down: the tailer has always read them in time.Local. Tests: a TestMain runs view, handlers, store and cmd/panel in UTC whatever the machine's zone (as logtail's); TestSettingsShowsTheTimeZone, TestTimesAreTheContainersZone, TestByDayInTheContainersZone, a Moscow day in TestQueryInboundSpamFilters; envdoc's pattern takes two-letter names. e2e time_zone_is_the_containers recreates the stand with TZ=Europe/Moscow: date says MSK, Settings names the zone and UTC+03:00, a test message's page gives its time and its mail.log lines in Moscow's. go vet + go test (26 packages) and make e2e on the test server for this tree. Docs: guide (§ Settings, the TZ row, the days of Health and the logs), architecture, schema-migrations, help (word for word with the mockup), CHANGELOG [Unreleased] § Added, roadmap row done with the decision. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-17 01:34:28 +03:00
mixandClaude Opus 5.5	2f1ec65b30	panel-redesign: Outbound log, message and the DMARC report pages on the kit ... Stage 2, step 4. Written by Sonnet, reviewed by Opus. - Five pages named after their mockups: out-log, out-message, dmarc, dmarc-domain, dmarc-report, with typed page data (view/outbound_log.go, dmarc.go), fixtures and tests. The engine pages deliveries and delivery are gone with their templates; the three DMARC templates are written anew. All five old names are off legacy_pages.txt. - The log polls its table (GET /outbound/log/fragment, as before); the page count in the box foot follows out of band, and the filter in the head is no longer swapped away while it is being chosen. - Handlers pass typed data; routes, query parameters, filters, paging and authorization are unchanged. - Kit: Foot.ID / Foot.OOB (attributes only, as on Head) and Fact.Small, the mockup's "sp-mono sp-small" value, for a report id and an rua that wrapped mid-word in their column. - test/e2e status scrapers match the new tag markup. Not run: no Docker here. Fixed on the way - The DMARC domain page read a field its source rows do not have and answered 500 as soon as the domain had a source. It builds the rows from the store's rollup now, with a test. Differences from the mockups, for the owner: - the log has no Status filter (the store filters by domain and application only); a refused message is "rejected", a neutral tag as the mockup's "rate-limited" is; - the message history keeps the panel's own wording with full dates and has no "accepted from <IP>" step - the client address is not stored; - dmarc: before the first report the box says "None yet" with what to check; a quiet mailbox is an amber "quiet" tag; - dmarc-domain: the stamp is pass / (pass + fail) rounded down, amber on any failure, red when nothing passed, absent without mail; - dmarc-report: the title has no year; "this relay" marks record rows as well as sources. Known and left as it is (not introduced here): the DMARC hub answers 404 to a domain administrator while the menu shows the entry and the plan gives that role the reports of its own domains. Opening it needs the report list to refuse an empty domain filter first - for the stage-3 security review. Evidence - docs/assets/panel-redesign/evidence/out-log.png, out-message.png, dmarc.png, dmarc-domain.png, dmarc-report.png: 1440 px wide, headless Edge, real templates served locally with their fixtures - NOT from the container (no Docker on this machine). - panel/audit.js on the five pages at 1440 and 1280: 784 texts checked, problems: []. - Polling of the log was exercised in a browser against a local fixture server with document.hidden overridden: four polls, one table and one foot after each, the filter untouched. - go test -count=1 ./internal/web/... ./cmd/panel ok internal/web ok internal/web/auth ok internal/web/handlers ok internal/web/validate ok internal/web/view ok cmd/panel Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>	2026-10-10 01:21:06 +03:00