759 commits

This branch

This branch

All branches

Author	SHA1	Message	Date
andodeki	97f03fd2bd	docs(nigig-site): record SITE-03 publication	2026-09-26 03:18:57 +03:00
andodeki	834755205b	feat(site-03): site-scoped versioned aggregates and explicit context ... - New opaque id newtypes (ids.rs) and SiteContext with no-fallback selection, pagination and revision CAS (site_context.rs). - New aggregates.rs: per-site versioned split (16 MiB cap), envelope site binding, shared supplier quarantine, device-local preferences excluded from replication, per-aggregate revision ledger with CAS. - store.rs: mutate_scoped and all site queries take &SiteContext; scoped_context() binds selection at the durable revision; stale base revisions fail compare-and-swap; ledger bumps only mutated scopes. Queries without context no longer compile. - Screens and scheduler converted; multi-site compilation takes an explicit site list. No selected_or_first fallback remains. - Migration: legacy whole store splits by site_id with quarantine report; original bytes untouched. Verified: check --all-targets, lib 83 green (19 new SITE-03 tests), integration jobs, clippy -D warnings, fmt --check.	2026-09-26 03:17:42 +03:00
andodeki	9b07b8f7d5	docs(site): SITE-14 scanner-owned OCR design plus SITE-20-32 product scope ... - SITE-14 revised: engine owned by nigig_doc_scanner/ocr, site consumes buffer API only, no pdf dependency; nigig-ocr app noted as parallel OS-provider effort with Linux-fallback delegation. - New feature tranches SITE-20-32 with R1-R5 roadmap, FR traceability, product budgets and gates, out-of-scope v1 and open decisions from construction-site-app-scope.md and construction-site-app-scope2.md.	2026-09-25 22:41:42 +03:00
andodeki	f535296b43	feat(scanner-ocr): on-device recognition behind ocr feature; gate pdf seam ... nigig_doc_scanner splits the app shell (Makepad UI, nigig-core/uikit, device location) from a new ocr feature: pure-Rust TemplateOcr (Otsu plus 8-connected components plus embedded 5x7 templates for 0-9A-Z, confidence floor 0.80 plus runner-up margin, checked budgets) with field suggestions and a deterministic fixture renderer shared with downstream crates. Downstream device crates enable nigig_doc_scanner/ocr with default-features=false (dep tree proven free of UI/location crates). Binary requires app. nigig-pdf-document gates its engine-free ocr seam behind an ocr cargo feature (default on); recognition must not pull the document/signing stack. Verified: scanner ocr-only check plus 11 lib tests green; pdf-document check green with default and --no-default-features; pdf ocr tests 5/5. Pre-existing xmp.rs unused_mut warning untouched.	2026-09-25 22:41:38 +03:00
andodeki	b3a9005795	feat(pdf): image ink colorants + downsample/pixels + shading/interpreter ports	2026-09-14 09:46:52 +03:00
Arena Agent	75ec2f9f20	fix(nigig-site): harden macOS native evidence	2026-09-14 06:31:57 +00:00
Arena Agent	41259b096a	ci(nigig-site): budget clean native builds honestly	2026-09-13 16:26:31 +00:00
Arena Agent	3c9dc7943a	classify Site schema versions before decoding	2026-09-13 07:22:38 +00:00
Arena Agent	bbce8fb015	harden SITE-02 repository and native vault contracts	2026-09-13 06:51:39 +00:00
Arena Agent	92f1508325	site: verify native vault and production dependency trust	2026-09-12 23:03:56 +00:00
Arena Agent	c568a99948	site: exercise abrupt SITE-02 publication exits	2026-09-12 22:21:22 +00:00
Arena Agent	8c786ae163	site: define blocked SITE-02 key lifecycle review	2026-09-12 22:18:22 +00:00
Arena Agent	6d6f887ba6	site: harden SITE-02 process and scope boundaries	2026-09-12 22:11:59 +00:00
Arena Agent	a7a057f44a	site: gate SITE-02 runtime and security review	2026-09-12 21:54:30 +00:00
Arena Agent	aa10b06d9b	site: prove locked legacy migration contracts	2026-09-12 21:47:35 +00:00
Arena Agent	8dbfae8f72	site: add SITE-02 encrypted repository candidate	2026-09-12 21:44:00 +00:00
Arena Agent	1cb6ad289b	docs(nigig-site): record SITE-00 and SITE-01 publication	2026-09-12 15:50:05 +00:00
Arena Agent	5d2d890f70	feat(nigig-site): enforce SITE-01 fail-closed containment ... Contain production capabilities, remove the production sync surface, and keep legacy media/export/transport implementations test-only. Require authenticated existing-key storage with preservation-first recovery and sticky write disablement, backed by deterministic fault and concurrency tests plus dependency and workflow contracts.	2026-09-12 15:46:30 +00:00
Arena Agent	f49d8b16ac	ci(nigig-site): establish truthful SITE-00 gates	2026-09-12 09:08:22 +00:00
Arena Agent	672fdd54b7	style(nigig-site): establish SITE-00 formatting baseline	2026-09-12 09:04:00 +00:00
Arena Agent	bae671f357	docs(nigig-traffic): add correctness remediation execution plan	2026-09-12 07:59:51 +00:00
Arena Agent	16a98334f1	docs(nigig-site): add security remediation execution plan	2026-09-12 07:59:51 +00:00
Arena Agent	5297c94180	docs(nigig-build): add audited remediation execution plan	2026-09-12 07:59:51 +00:00
Arena Agent	4665973b57	docs(cad-ui): add audited remediation execution plan	2026-09-12 07:59:51 +00:00
Arena Agent	3666c6ce3a	docs(cad-core): add audited remediation execution plan	2026-09-12 07:59:51 +00:00
andodeki	e899a271c6	feat(pdf): shading port test (12 passed) + function updates	2026-09-12 09:22:48 +03:00
andodeki	cea969cce5	feat(pdf): function module updates	2026-09-12 09:14:08 +03:00
andodeki	c66a8ec9db	docs+test(site,pdf): assessment update + font_info port cases ... Verified: font_info_port 22 passed.	2026-09-12 08:55:20 +03:00
andodeki	5614121eae	feat(site+pdf): report editor video + font ports ... - nigig-site: video module, report editor WYSIWYG updates. - pdf-graphics: colorant_raster, font_text, unicode_names modules + colorant raster port test; font + font_info test updates. Verified: nigig-site + pdf-graphics check clean; pdf-graphics tests all pass (20 suites, 0 failures).	2026-09-12 08:45:35 +03:00
andodeki	2142e1834b	fix(nigig-site): report editor WYSIWYG wiring for new makepad API ... - Use WidgetRef::borrow_mut/borrow directly for the DocEditor host (new Widget derive: borrow has no generics on refs, as_* only on WidgetRefExt; WidgetExt blanket impl covers View lookups). - Semicolon fix for RefMut temporary lifetime in set_rich_mode.	2026-09-12 08:22:43 +03:00
andodeki	a620609ff9	feat(cad-ui): sun position controls	2026-09-12 07:21:51 +03:00
andodeki	ac8f8aa002	chore: sync full working tree to gitdab ... Whole-tree sync: cad-core/cad-ui split sources, nigig-build construction_frame migration, pdf port progress, mpesa/pay/uikit/doc updates, workspace members/profiles/lock, CI workflows and reviews. See individual file history for details.	2026-09-12 07:15:24 +03:00
andodeki	338b8c818f	fix(android): enable cad-ui on mobile + new-API fixes ... - nigig-build: cad-ui + construction_frame back on unconditionally. The host-only gate is dropped: cad-ui now compiles for aarch64, and pageflipnav mobile needs ConstructionScreen / BuildProjectsPage (CAD/Docs/Spreadsheet buttons) — gating produced the white screen. - cad-ui: ScriptVmHost for standalone eval (no more vm.std / () host), std::thread workers (Cx::spawn_thread removed upstream). - viewport: same worker fix + section_state helper for the CPU cull path. - script_bindings: new script/geometry binding module. - spreadsheet grid + invoice Walk literals: ..Default::default() for new aspect/cell/deferred fields; explicit style::CellAlign import (makepad added its own CellAlign). Verified: pageflipnav aarch64 release links with 0 errors; APK built, installed (54M) and running with home screen drawing.	2026-09-12 00:26:43 +03:00
andodeki	5ae5d5a84c	fix(android): gate cad-ui host-only + port map to new makepad API ... - nigig-build: cad-ui + construction_frame host-only (DO NOT enable unconditionally: CadViewport Script derive fails ScriptApply for aarch64 and breaks every pageflipnav android build). - map: vendor TagThreadPool (removed upstream with the task-pool scheduler) into thread_pool.rs; Walk literals gain ..Default::default() for new aspect/cell/deferred fields. Verified by pageflipnav aarch64 release rust build (0 errors).	2026-09-11 08:46:05 +03:00
andodeki	b1045d79d4	feat(pdf): graphics/document port progress + android gates ... - pdf-graphics: new cff, truetype, cjk_cmap, disk_cache, document_ai, path, reflow, text_diff modules + port tests (all green); syntax/type fixes for the aarch64 build (stray brace, &u8 derefs, f2dot14 assign). - pdf-document: ocr, pdf_a, xmp modules + roundtrip tests; annotation editor updates. - pdf-makepad: handle RenderCommand::SetOverprint (report via TransparencyError per ADR 0009, no silent drop); renderer/page_view updates for the new recording ops. - matrix_client: nimanyatta native module (ungated; the aarch64 wrapper needs it unconditionally). - pageflipnav home_screen: project_store sync is host-only until cad-ui's Widget Script derive is fixed for aarch64. Verified: cargo check on all four crates clean at fork 66cc4f15f; nigig-pdf-graphics tests pass; pageflipnav aarch64 release links.	2026-09-11 05:09:11 +03:00
andodeki	f177df8d43	chore(deps): bump makepad fork rev to 66cc4f15f (fix broken widgets merge) ... b9a083c26 carried an upstream merge that dropped enter_isolate / leave_isolate / IsolateEntry from widget_async while lib.rs and apps/flow-ui + apps/wm still use them, breaking makepad-widgets. 66cc4f15f restores them (verified: makepad-widgets, makepad-app-flow-ui, makepad-wm check clean). Urgent follow-up to c901f1d which pinned the broken rev.	2026-09-10 19:21:21 +03:00
andodeki	c901f1d4f1	chore(deps): bump makepad fork rev to b9a083c26 + workspace updates ... Fork nigig-makepad-test-android now at b9a083c26 (upstream merge + robot secondary-dex bundling + app_main wrapper fix, on top of the game-libs/arcade port). All 16 workspace makepad revs follow. Also takes the in-tree workspace updates: exclude nested crates/nimanyatta workspace, add crates/apps/nigig-site member, and PERF-OPS Phase 1 profile tuning (thin LTO + engine opt-level 3). cad-core/cad-ui split and nigig-traffic members stay WIP.	2026-09-10 16:36:11 +03:00
andodeki	12dff81b05	fix(build): make cad-ui host-only for Android ... cad-ui's Widget Script derive (CadViewport) needs LiveHook fix for aarch64; until then, gate it behind cfg(not(target_os="android")) in nigig-build so pageflipnav's aarch64 wrapper (which pulls nigig-build) can link without cad-ui. Host builds still include cad-ui. Unblocks pageflipnav aarch64 release.	2026-09-08 22:28:11 +03:00
andodeki	075d775e9f	fix(robius-ussd): fix Android JNI getPackageName handling for new jni crate ... JString::from(JObject) + get_string borrowing was incorrect for aarch64 android target (jni 0.21): JavaStr doesn't impl Display and temporary JObject dropped while borrowed. Store package_obj in local and use JString::from(package_obj). Fixes pageflipnav android build which pulls robius-ussd via pageflipnav -> nigig-build -> cad-ui.	2026-09-07 03:50:53 +03:00
andodeki	366b80dd16	refactor(pageflipnav): use AndroidManifest.xml.template and dedup robius java ... - Rename resources/android/AndroidManifest.xml -> AndroidManifest.xml.template so the current cargo-makepad (template-based, not --manifest flag) picks up the custom manifest with permissions/services (ussd, sms, trigger). Old --manifest flag was removed in makepad's android/mod.rs; template is now the supported override. - Remove duplicate java at resources/android/java/robius/{sms,trigger,ussd} (7 files). These are now compiled via their owning crates' build.rs (robius-sms/src/sys/android/*.java, robius-trigger/src/android/*.java, robius-ussd/src/sys/android/*.java) producing secondary dex that cargo-makepad bundles. Keeping them in the app caused duplicate sources and is not needed; java belongs in the respective crates.	2026-09-07 03:02:06 +03:00
andodeki	f1eecd3c97	chore(deps): bump makepad fork rev to 435135ed5 (port game libs + arcade) ... Fork nigig-makepad-test-android now at 435135ed5: reintroduces libs/game (assets, audio, blocks, coedit, gen, net, pkg, render, script, session) + apps/arcade reconciled to fork's libs/sim + splash_storage jail model; arcade AI rewritten to makepad-ai-hub ChatProvider worker (CAD pattern). nigig-build verifies. Includes makepad-game-* workspace deps at new rev (traffic WIP gated on this merge). cad-core/cad-ui split remains WIP.	2026-09-06 03:12:48 +03:00
andodeki	95b89cf8d3	chore(deps): bump makepad fork rev to 531114e84 (rebase onto latest kerja/dev via 493d23a76)	2026-09-03 11:47:02 +03:00
andodeki	212abe6e8b	refactor(cad): port AI subsystem from makepad-ai Agent API to makepad-ai-hub worker-thread ChatProvider model (adopt upstream example/cad), bump makepad fork rev to 7bddebb	2026-09-03 08:39:07 +03:00
andodeki	560116189c	fix(cad-build): land CAD workspace on project dashboard, not a blank editor ... The CAD dashboard's CadDashboard node never realized as a widget, so tapping 'CAD Workspace' opened to a blank/editor-only sheet. Empirical device dumps showed the first child after the root realizes reliably while a sibling placed after the editor AdaptiveView does not, and a root ':=' widget child alone never realizes here. - Place dashboard_layer as the FIRST direct child of CadWorkspaceBase, wrapping mod.widgets.CadDashboard so it is a reliably-realizable, togglable View layer (matching the working doc workspace pattern). - Wrap the editor AdaptiveView in editor_layer (a plain View) and toggle editor_layer/dashboard_layer visibility from apply_dashboard_visibility instead of toggling the AdaptiveView variants, which always draw their active variant regardless of visible. - Add use mod.widgets.* to the CadDashboard script_mod (matches the CadEditorSheet registration that realizes inside this workspace). - Add regression test candlands_on_dashboard asserting the dashboard title and + New Project button land when opening the workspace.	2026-09-02 09:06:20 +03:00
andodeki	3a3db4efa6	feat(robius-notification): iOS via UNUserNotificationCenter, and the Apple/Windows logic comes out of the cfg blocks ... Two gaps remained on the Apple and Windows side after the last commit, and they are different in kind. The first was a missing backend. iOS returned PermanentlyUnavailable with a note saying it was not implemented. It now uses UNUserNotificationCenter -- the only option there, since every iOS process is bundled, so the Objective-C exception that rules that API out on macOS cannot occur. The objc2-user-notifications bindings are real and fetchable, so this type-checks for aarch64-apple-ios against the actual framework, and the module was confirmed genuinely reachable by injecting a type error and watching the target build fail. Its is_available() returns a constant false, and that is a limit worth naming rather than burying. The real answer comes from getNotificationSettingsWithCompletionHandler:, which is asynchronous -- it hands the settings to a block on an arbitrary queue. A synchronous is_available() could only produce that by blocking on a completion handler, which on the main thread is a deadlock rather than a delay. Returning false errs toward telling the user delivery is unverified; the alternative is claiming an availability the platform never confirmed, which is the whole failure this crate was written to remove. A correct answer needs an async entry point, which is a change to the public API rather than a bug fix, so it is recorded in the ADR instead of being quietly wrong. The second gap is subtler and, I think, the more valuable fix. The Apple and Windows backends contain pure logic -- XML escaping, tag clamping -- that was sitting inside #[cfg(target_os = "windows")], where cargo test on the only available machine could never reach it. Those functions had zero tests and no prospect of any. They now live in src/payload.rs, which is cfg-free and runs on every target. Eleven tests cover them, and they cover exactly the rules a compiler cannot: an unescaped `&` in a merchant name makes the toast XML malformed and Windows discards the whole notification rather than showing a mangled character, and the Binance P2P book is full of `&`. A byte-wise truncation of the 64-character tag limit panics outright on the full-width names that book also contains -- so the clamp cuts on character boundaries, pinned by a test that would panic if anyone changed it back. One test pins something deliberately counter-intuitive: escaping is not idempotent, and escape_xml("&") is "&". That is correct, and the test exists so nobody "fixes" double-escaping by teaching the function to detect already-escaped input, which is precisely how escaping filters grow holes. The distinction this commit is really about: the last one made the Apple and Windows backends *compile*, which catches wrong selectors -- it found CreateToastNotifier(&HSTRING), which does not exist. It could not catch wrong behaviour. Extracting the logic is what makes the behaviour testable on a machine that will never run either platform. 62 tests, up from 51. Clippy clean with -D warnings on all five targets: linux-gnu, linux-android, apple-darwin, apple-ios, windows-msvc. p2p-intel unchanged at 225.	2026-09-01 20:10:50 +00:00
andodeki	3ef182414e	feat(robius-notification): real macOS and Windows backends, type-checked against the actual frameworks ... The previous commit refused to write these two, on the grounds that code no compiler has ever seen is not an implementation -- it is plausible-looking text that would sit in the same crate as tested code and be read as equally finished. That reasoning holds. The premise behind it did not. `cargo check` needs the *target's standard library*, not a linker or a platform SDK. `rustup target add x86_64-pc-windows-msvc aarch64-apple-darwin` puts the real `windows` and `objc2` crates -- genuine WinRT metadata, genuine Objective-C class definitions -- in front of the type checker on a Linux host. So both backends are now written and both compile against the frameworks they call. Compile-checking earned its place immediately. The Windows backend was written against `ToastNotificationManager::CreateToastNotifier(&HSTRING)`, which does not exist: the AUMID overload is `CreateToastNotifierWithId`. Nothing short of a compiler holding the real metadata would have caught that, and it would have shipped looking entirely correct. Because a cfg-gated module can silently compile to nothing -- leaving a green check that proves only that the module was skipped -- each backend was verified to be genuinely reachable by injecting a type error and confirming the target build failed. Both macOS and Windows were checked this way, then restored. Two platform decisions worth recording. macOS uses NSUserNotification, not UNUserNotificationCenter, and that is a deliberate downgrade to a deprecated API. `UNUserNotificationCenter.current()` raises an Objective-C exception when the process has no bundle identifier; that unwinds through Rust frames and aborts. A plain `cargo run` host has no bundle, so the modern API would crash the caller instead of reporting unavailable -- which is worse than deprecated. The nil check on `defaultUserNotificationCenter` is there for the same reason: msg_send on nil returns zero rather than crashing, so every later call would silently do nothing, which is precisely the failure this crate exists to remove. Windows requires the host to supply an AppUserModelID, because a library cannot invent one. It comes from an MSIX manifest or a Start Menu shortcut, and a fabricated id produces a notifier that constructs happily and then fails at Show. `set_app_user_model_id` is therefore public, a no-op off Windows so portable hosts call it unconditionally, and `is_available()` is false with a reason naming exactly what is missing until it is called. Toast payloads are XML, so text is escaped -- the same bug class as the Telegram MarkdownV2 escaping p2p-intel needed before it dropped Telegram, and a merchant nickname containing `&` is not hypothetical. The support table now has two columns, "compiles" and "executed", because they are different claims. All four backends compile; only Linux has posted a notification. iOS remains unavailable by design: it needs UN* with a bundle and an entitlement, which is an app-packaging concern rather than something this crate can satisfy. Off Windows the module defines no entry points at all rather than stubs. Clippy was right to call them dead: sys/mod.rs dispatches elsewhere, so they existed only to satisfy a symmetry nothing needs. CI gains a step that clippies all four cross-targets with -D warnings, so a cfg-gated backend cannot rot unnoticed -- which is exactly how the CreateToastNotifier mistake would have survived. 51 tests, clippy clean on five targets, p2p-intel still at 225.	2026-09-01 18:54:57 +00:00
andodeki	e16d1d1d44	feat(robius-notification): a zero-dependency D-Bus notifier, and p2p-intel's last limit closes on Linux ... ADR 0035 left one of p2p-intel's four limits open: no OS notification backend, so alerts stopped when the window closed. The seam existed with one implementation that truthfully did nothing. This is the crate that fills it. Posting a notification on Linux is one D-Bus method call. Three ways to make it were measured rather than assumed: notify-rust with libdbus is twelve crates but a C library, which needs pkg-config and breaks the Android and iOS cross-compile this crate family keeps clean; notify-rust with zbus is pure Rust and 169 crates including an async executor; writing the wire format out is about 250 lines and nothing at all. robius-sms deleted polkit and gio for exactly this reason -- its E9 note records they were the sole source of two RUSTSEC advisories and an LGPL question for every consumer -- so pulling a 169-crate tree back into the same family for one method call would reverse that decision for a worse reason. The cost of hand-rolling is that the protocol has to be exactly right, and a mistake makes the daemon disconnect with no diagnostic. That cost was paid in tests: the suite starts a private dbus-daemon per test and talks to it. This matters more than it sounds. The marshaller and the parser were written from the same reading of the specification, so them agreeing with each other proves only that I was consistently wrong or consistently right; only a third party can say which. It found three bugs no unit test would have. The first is the one worth dwelling on. Every error reply parsed as success. The header-field walk assumed all fields were strings, but REPLY_SERIAL is a u32, and reading its four bytes as a string length desynchronised the cursor so ERROR_NAME was never reached. `post` returned Ok against a bus with no notification service running. That is precisely the bug this crate was written to eliminate -- a notifier that reports success and delivers nothing -- reintroduced by accident inside its own parser. I cannot think of a stronger argument for testing against something you did not write. Second, is_available() was true on a bare bus, because NameHasOwner *succeeds* and answers false in its body; checking only for an error reported a working notifier on a machine with no notification daemon. Third, replies were not correlated. The bus sends NameAcquired unprompted right after Hello, so "read the next message" consumed a signal and treated it as the answer. Replies are now matched on REPLY_SERIAL, and a single read carrying several messages is walked rather than truncated. The suite also serialises every test that mutates DBUS_SESSION_BUS_ADDRESS behind a mutex. The variable is process-wide and cargo runs tests in parallel threads; three consecutive parallel runs are now green. --test-threads=1 would have made the failures go away too, and would have hidden a real hazard from whoever reads the file next. On the four platforms, honestly. Linux is implemented and tested. Android is implemented and *compiles* -- cargo check and clippy both pass for aarch64-linux-android -- but has never run on a device, and the module says so in its first paragraph. It handles the two things Android drops silently, missing POST_NOTIFICATIONS on API 33+ and a missing channel on API 26+, because both are the same accepted-and-discarded failure this crate exists to remove. Apple and Windows are deliberately not written. Neither could be compiled here -- no macOS or Windows toolchain and no way to add one -- and objc2 message sends or WinRT calls that no compiler has ever seen are not an implementation. They are plausible-looking text that would sit in the same crate as tested code and be read as equally finished. Both return PermanentlyUnavailable with a reason naming ADR 0036, and their module docs record the call sequence so the next person starts from a design rather than a blank file. The support table says "written" and "verified" in separate columns for the same reason. p2p-intel's dashboard now uses SystemNotifications instead of UnavailableNotifications. The latter stays: on a platform with no backend it is still the truthful answer, and a test needs something that reliably cannot deliver. Alerts are tagged per fiat so a market replaces its own previous notification rather than stacking -- a 30-second poll would otherwise fill the shade, and a full shade is what makes someone turn notifications off for the app entirely, which costs more than the feature is worth. Two new tests pin the invariant that a sink must never report delivery it did not achieve. CI gains a notifications job that installs dbus and sets ROBIUS_NOTIFICATION_REQUIRE_DBUS=1. The bus-backed tests skip when dbus-daemon is absent so the suite stays green on a bare machine, but a silent skip in CI would mean the integration tests quietly stopped running while the build stayed green. I verified the guard fails by hiding dbus-daemon behind a stub that exits 127. 50 tests in the new crate, 225 in p2p-intel, clippy clean on host and Android, and the app still starts under Xvfb.	2026-09-01 18:43:07 +00:00
andodeki	da326142bf	fix(pay-ui): stop re-setting ussd/phone-perm toggles on refresh so manual user state is preserved	2026-09-01 21:40:49 +03:00
andodeki	1d8b3a6053	merge(local): reapply local WIP onto merged main -- cad dashboard/explode/script_parts/xray merged with remote Phase-5 LOD, plus doc-ui extraction, spreadsheet xls-import, android ussd, camera and test work	2026-09-01 21:13:52 +03:00
andodeki	159f3c7fee	Merge remote-tracking branch 'origin/main'	2026-09-01 20:31:44 +03:00