Changelog
Co nowego.
Każde ulepszenie platformy, jak to wysyła.
· kamo-internal
Real work orders and subscriptions per market — dispatch, customer accounts, live subscriptions, cancel at period end
Service (work orders): - the grid reads its own market's jobs (plus older jobs with no market), shows the customer, the technician (member chip, never an id), the next visit, and status / priority words from the dictionary; rows keep ?back= - the work order page shows its market, files the job under an account or none (swap beside Customer), dispatches a technician (Choose Technician, arrival and finish, visit notes; a new job becomes Assigned), adds return visits, edits summary / description / trade / priority / address, labels status buttons by what they do (Start Work, Put On Hold, Mark Complete, Mark Invoiced, Cancel Work Order), shows each note's author with photo, and goes Back to its market's tab - no screen shows a job's uid: new jobs are numbered, older ones show a short ref Subscription: - the Agreements sub-tab was fifteen generated agreements whose buttons changed nothing; it now lists the market's live subscriptions (customer with photo, plan, status, seats, MRR, next billing, balance due, overdue, ending) and opens each on its order page - Signups reads the market's orders, names customers by account and member chip (was Member #<id>), offers only the market's plans in the order wizard - the subscription page shows the customer with photo and Open Account, the market, loads its subscription by id (no org-wide account or subscription scan), and cancels a live subscription with a reason, now or at the end of the billing period (Cancel only marked the order before, leaving the subscription billing); cancelling an order asks first - /commerce/agreements/new opens the order wizard for the market instead of a Coming Soon page - Back on agreement and signup pages no longer points at a tab id that never existed Removed the unreachable mortgage mock PipelineCommitmentsTab and /commerce/commitments/[id] (generated data; nothing linked to either). Help: How to Manage a Work Order and How to Manage a Subscription, linked from the grids, the visit window and the cancel window.
· SecurityService
Market-scoped work orders and subscriptions; dispatch and customer endpoints
- GET **************** lists one market's work orders (plus those with no market) - PUT /service-jobs/{uid}/customer files a job under an account or takes it off - POST /service-jobs/{uid}/visits adds a visit; PUT .../visits/{visitUid} schedules it and assigns a technician (409 on a finished visit) - GET /pos/subscription-orders and /pos/subscriptions take ?marketId= - GET **************** takes the market UUID (it was a Long, so every market-scoped request was a 400) and returns only the caller's plans - ServiceJobRightsGateTest covers the three new handlers
· kamo-shared-library
Market on the engagement, job numbers, dispatch, customer accounts, market-scoped lists
Service work orders: - createJob stores the chosen market on Engagement.market (it only picked the engagement type before) and the customer account on Engagement.account - every new job gets a person-readable number (WO-00001…), so no screen falls back to the uid - JobView carries marketId / marketTitle; customerName reads Company (Contact) - listJobs(org, status, marketId): one fetched read (engagement, market, customer, visits) instead of up to four lazy loads per row; a market tab also shows jobs that carry no market - setCustomer: file a job under an account or take it off one (engagement follows) - addVisit / updateVisit: schedule a visit, assign a technician (org-checked in SQL), mark en route / no access / cancelled; assigning someone to a CREATED job moves it to ASSIGNED Subscriptions: - createOrder stores the plan's market and the customer member's account on the engagement (a quote's engagement keeps what it has) - SubscriptionOrderDTO and SubscriptionRecordDTO carry marketId, marketTitle, customerAccountUid and customerAccountName - getOrders / getSubscriptions take a marketId (engagement market, else plan market; none stays in) and read the rows with one fetched query - getPlansForMarket: the market filter on plans took a Long and could never parse a market UUID; it is also limited to the caller's org now
· kamo-internal
Every rental has a renter; cancel, re-date, check out, check in and end; booked dates beside the date picker
- New Rental Request: the Renter (customer account) is required and pre-filled from ?accountId; ?marketId is sent so the rental is filed under the market. Once an asset is chosen, Already Booked lists its booked dates, names a clash, and Create waits for free dates. No assets: a way to the market's Rental Assets. - Rental request: Change Dates (with Charge By and booked dates), Cancel Request (cancel or decoder, with a reason kept on the request), Confirm Booking asks for a renter first; market and the booking's stage shown. - Booking: Check Out, Check In (late fee suggested from the daily rate when it is overdue, damage fee, condition notes, new total), End Rental (nothing handed over), Change Dates (end only once out), Cancel Booking, Open Request; price breakdown, checked out / returned times, overdue warning. - The renter can be changed, never removed; account saves use the record the server answers instead of reloading. - Pipeline lists ask the server for the market's rentals (by the rental's market); Market column when no market is chosen; bookings listed by stage (Reserved, Checked Out, Returned, Cancelled). - Market Rental Assets: Offered switch (switch an asset off instead of deleting it), translated copy, theme tokens, the server's sentence when an asset in use can't be deleted. The unused PipelineRentalAssetsTab (hard-coded English) is removed. - Help: Rentals and Bookings article (commerce/orders) linked from each rental page.
· kamo-internal
Market-filtered lists, line items, approve/reject/withdraw, send/receive/close/cancel, and a real Vendors list
- Procurement tab: Purchase Requests / Vendor Orders / Vendors; lists ask the server for the selected market (plus rows with none), show a Market column, and filter/count in plain words (Waiting for Approval, Rejected, Partly Received…); the "every market shows the same list" caption is gone - New / Change Purchase Request: vendor picker (active, this market's first) with New Vendor on the spot, market, lines with live total (or an estimated amount), notes, optional customer account - Record page: who asked and who decided (with photos), status banner, line table with arrived / still to come, history; Approve, Reject (reason shown to the requester), Change, Withdraw; Mark as Sent, Record Delivery (per line or everything), Close Order, Cancel Order — each confirmed - Vendors: contact person, email and phone through EmailAddress/PhoneNumber, website, notes, market; Active / Inactive with counts; deactivate instead of delete; ids stay strings - Help: "Buying from Your Vendors" help center article, linked from the form and the record page
· SecurityService
ProcurementController — market-filtered lists, change/reject/withdraw a request, send/receive/close/cancel a vendor order, records returned from every change
- purchase requests and vendor orders move out of POSController into ProcurementController (MANAGE_PROCUREMENT to buy and run orders, APPROVE_PURCHASE_REQUESTS to approve or reject) - PUT …/account and …/market answer with the updated record - ProcurementNotifier: a new request tells everyone who can approve it; a decision tells the requester - vendor create/edit/deactivate opens to MANAGE_PROCUREMENT (MANAGE_SUBSCRIPTION_SETTINGS kept)
· kamo-shared-library
Market, lines, approval decisions, and the vendor order lifecycle (send, receive, close, cancel)
ProcurementService owns purchase requests and vendor orders: - the engagement carries the market (chosen Procurement market, else the vendor's); lists filter by market plus rows with none; marketId/marketTitle on both DTOs; PUT market/account return the record - lines (description, quantity, unit cost, received) in the record payload; the total is their sum - reject (outcome REJECTED + reason) and withdraw (CANCELLED) a waiting request; requester and decider recorded; the request is SUBMITTED on create - vendor order: mark sent, receive in parts or whole, close (FULFILLED), cancel before anything arrived (VOIDED); derived stage on the DTO, never stored - EngagementLifecycle: all commitments voided -> CANCELLED, all ended -> FULFILLED - one-query lists (fetch-joined engagement/account/market, vendors and orders batched) - vendors: contact name, email, phone, website, notes, market, active flag (deactivate, never delete) - indexes on org_id / intent_id / commitment_id of the intent and commitment tables (applied by hand)
· KBService
Turn Antivirus scanning on in kbservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· DocsService
Turn Antivirus scanning on in docsservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· MediaService
Turn Antivirus scanning on in mediaservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· ConversionService
Turn Antivirus scanning on in conversionservice
KamoAntivirus is Ready (StatefulSet kamowsantivirus 2/2, /readyz ready, release 2026.11.08.0101); a direct scan from the cluster returns MALICIOUS/TEST_FILE for the standard test string and CLEAN for plain text with this service's internal-auth secret.
· DocsService
Assignment rows say what the member still owes
Adds signableOutstandingCount (signable documents not yet signed) and uploadsOwedCount (required requests with no live file) to each assignment row, so the member's list can label its button by what is actually owed instead of "Continue Signing" on a Quick Request with nothing to sign. Three grouped queries per page; LegalAssignmentCountsParseTest parses them against the real mapping.
· KBService
KBService checks knowledge-base resources and looks up the verdict before signing
- Resource upload writes the raw kb bucket, so it goes through AntivirusUploadGuard (KB) before anything touches storage: 422 ANTIVIRUS_BLOCKED (nothing stored) / 503 ANTIVIRUS_UNAVAILABLE, answered in that shape by the controller. - The content hashes ride on the object as user metadata (kamo-blake3 / kamo-sha3), so every presign site (single URL, batch, library tiles, platform help) looks up the content's global verdict first: a locked or still-checking resource is never signed (423 on the single URL, no URL for a tile). Resources stored before this carry no hashes and are not judged here. - ConfigMap kamo.antivirus.* (enabled: false until KamoAntivirus is Ready); ANTIVIRUS_INTERNAL_AUTH_SECRET from mlos-internal-auth.
· DaemonService
Zaznacz cotygodniowy raport ochrony (co godzinę, lokalny poniedziałek 08:00) i obserwowanie wybuchu (15 min)
· SecurityService
The Antivirus API, platform controls and scheduled endpoints; gate SecurityService's own file paths
/api/antivirus/** (and the /api/security/antivirus twin the console proxy tries first): overview, detections, settings (audited ANTIVIRUS_POLICY_CHANGE), false alarms, verdict lookup. Platform (MANAGE_PLATFORM_ANTIVIRUS): status, signature refresh/rollback, false-alarm review (ALLOWLIST unlocks everywhere + tells people), allowlist, drill, outbreaks. Internal: weekly Protection Report and outbreak check for DaemonService. Raw uploads (avatars incl. SVG, backgrounds, logos, lead imports, disclosures, rate sheets) are screened before anything is written; ImageService paths keep their lib gate and now answer 422/423/503 instead of a 500; vault, loan, patient and picture-frame reads apply the read gate. kamo.antivirus.enabled stays false until the kamowsantivirus StatefulSet is Ready.
· APIService
Route /api/antivirus/** to SecurityService and seal its internal subtree
· KlusterServices
KamoAntivirus mail filter first on inbound smtpd (port 25), tempfail when unreachable
smtpd_milters = { **************** default_action=tempfail }, then rspamd unchanged. Harmful attachments are replaced by a small placeholder part and the message is still delivered; if the filter cannot be reached the sender gets a 4xx and retries. non_smtpd_milters and submission (587) keep rspamd only; postfix-bulk untouched. Milter verified live before this push (milter-protocol client in cluster: test file replaced with the placeholder, clean CSV kept, forged marker stripped).
· EmailService
Antivirus for mail — read gate on every mailbox, milter placeholders, send screening, detections
- Read: every attachment/inline part from any mailbox (Kamo Mail, IMAP providers, Graph; personal and shared routes) is hashed in memory (temp file past 8 MiB, deleted on close), its global verdict looked up and, when unknown, checked by KamoAntivirus (origin MAIL_READ, bytes_stored=false). Harmful = 423 ANTIVIRUS_BLOCKED, not checkable = 423 ANTIVIRUS_CHECKING; reason/family also as X-Kamo-Antivirus-* headers. The SI mail tools read through these routes, so they are gated too. Listing never scans: AttachmentInfo carries **************** only for parts already hashed. - Milter placeholders (X-Kamo-Antivirus-Removed) list under the ORIGINAL name, removed=true, locked; never served or forwarded. X-Kamo-Antivirus message header exposed as EmailMessage.antivirus for the banner. - Send/draft (decision 11): device uploads and pasted images go through AntivirusGate.scanUpload (stored verdicts reused, never rescanned); a forward's parts get the read check. 422 ANTIVIRUS_BLOCKED with fileName, 503 ANTIVIRUS_UNAVAILABLE. - NATS antivirus.detection.mail (queue group antivirus-mail-detections): recipients resolved to members via mailbox holders, personal aliases, shared mailbox readers and alias domains; recorded per member (MAIL_INBOUND, counterparty = sender) so FILE_BLOCKED / THREAT_ALERT go out per org settings. - Notifications: ANTIVIRUS_THREAT_ALERT -> VIEW_ANTIVIRUS (core app, no feature row needed); FILE_BLOCKED/UNLOCKED belong to no app; catalog order. Preview samples for the 4 Antivirus templates. - configmap kamo.antivirus.* (enabled: kamowsantivirus is Ready). Needs kamo-shared-library b6c41d34 (HashUtils BLAKE3 on bcprov 1.70).
· SecurityService
Rental steps, market-filtered lists, and a renter that can move but never be cleared
- GET /rental-requests and /bookings take ?marketId (the caller's own market) and filter by the engagement's market. - POST /rental-requests/{id}/cancel, PUT /rental-requests/{id}/dates, POST /bookings/{id}/check-out | return | cancel, PUT /bookings/{id}/dates (MANAGE_RENTALS), each answering the updated record; a refusal is a 400 with a sentence. - GET /rental-assets/{id}/bookings: the dates an asset is already booked for. - PUT /rental-requests/{id}/account and /bookings/{id}/account refuse a blank account and answer the updated record instead of a bare message. - DELETE /rental-assets/{id} answers 409 with a sentence when the asset has rentals.
· kamo-internal
Orders tab filters by the organization's own markets
Chips and row labels were per line of business, named after its first market, so two Retail markets collapsed into one. Each row now shows its own market (from the server); an older record with no market goes to the only market of its line when there is one, else to a "<Line> — No Market" group. A remembered filter whose market is gone falls back to All.
· DocsService
DocsService wszędzie odrzuca zablokowane dokumenty i sprawdza zapisy edytora
- WOPI PutFile zapisuje raw MinIO, więc zapis przechodzi najpierw przez AntivirusUploadGuard: a harmful save nie zapisuje niczego, zachowuje ostatnią dobrą zawartość dokumentu i odpowiada edytorowi 422 ANTIVIRUS_BLOCKED (503 ANTIVIRUS_UNAVAILABLE więc próbuje ponownie); czyste zapisanie jest oznaczone GetFile odmawia zablokowania/sprawdzania zawartości z wartością 423. - Obrazowanie /download, /stream, konwertowane pliki PDF i miniatury stron wywołują bramkę odczytu przed 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING. UWAGA treść przechodzi, więc jej PDF jest niedostępny Eksport zbiorczy usuwa zablokowane dokumenty, podobnie jak inne wyłączenia. - Wersja do pobrania / pdf / miniatura ocenia własną zawartość wersji. - Kariery CV są sprawdzane jako kariery z kandydatem i aplikacji; kariery Kontrolery odpowiadają na odmowy antywirusowe w kształcie platformy zamiast 500. - Prawne: przesyłanie map odmawia do własnego 422/503, wstrzymane przesyłanie prosi o ponowną próbę (jego PDF Renderowanie byłoby wykonane z niesprawdzonych bajtów), wykonywane pakiety i próbki żądań są Binder albumy ze zdjęciami pozostawiają zablokowane zdjęcia. - Wiersze listy dokumentów/metadanych zawierają scanStatus / scanFamily / scanOutcome. - ConfigMap kamo.antivirus.* (włączone: false dopóki KamoAntivirus nie jest gotowy); Poprawiono błąd 0x0000000E w pliku mlos-internal-auth.
· SecurityService
Każdy wiersz zamówień ma własny rynek
Wiersze przenoszą marketId / marketTitle z ich zaangażowania (jedno zapytanie przez uid), więc organizacja z dwoma rynkami detalicznymi widzi, które Z jednego z nich pochodziło zamówienie zamiast z obu pod nazwą pierwszego rynku. Rekordy dokonane przed śledzeniem rynków pozostają null.
· KlusterServices
Ostrzeżenia antywirusowe (niedziałający skaner, przestarzałe sygnatury, awaria bramki lustrzanej, p95, wzrost liczby wykryć, zaległości)
Nakładany ręcznie (monitoring/ nie jest celem CI).
· kamo-shared-library
A rental needs a renter; market on the engagement; cancel, re-date, check out, return and cancel a booking
- createRentalRequest refuses a missing or foreign customer account, records the market (the asset's, else the chosen one) on the engagement, and validates dates and the rate type. Confirm refuses a request with no account. - setRentalRequestAccount / setBookingAccount move the renter to another account and never clear it; both answer the updated record. - Requests: cancel/decoder (IntentStatus.CANCELLED, reason kept) and new dates (with the availability check). Bookings: check out (the booking's FulfillmentOrder IN_PROGRESS), return or end (COMPLETED; CommitmentStatus.FULFILLED; late and damage fees added to the total; condition notes), cancel (VOIDED, before it goes out), and new dates (only the end while out), each checking the asset's other bookings under a row lock on the asset so two confirms cannot double-book. - EngagementLifecycle: a VOIDED commitment commits nothing; all voided and no order is CANCELLED. - A returned booking no longer holds its dates. The asset's held dates are readable (findRentalAssetBookings) for date pickers. - DTOs: marketId/marketTitle on requests, bookings and assets; booking -> rentalRequestUid, rateType, checkedOutAt, returnedAt, fees, notes, cancel reason; request -> cancelReason, bookingStatus. Lists filter by market and load assets, bookings and hand-overs in one query each instead of per row. - Rental assets: description column; market validated as the org's Rental market and movable on update; negative rates refused; duplicate codes refused on update; an asset with rentals on record cannot be deleted (switch it off instead). - Indexes: **************** by engagement, commitments by rental asset, fulfillments by commitment, rental assets by org and market (applied by hand).
· kamo-internal
Rynki — własne rynki organizacji, pod własnymi nazwami
Rynek jest tym, co definiują członkowie (tytuł + nazwa + nazwa użytkownika) Opis); jego Linia Biznesu jest tylko jego rodzaju. - Opcja nawigacji to Rynki. Z jednym rynkiem jest to rynek, według jego Tytuł (jak wcześniej); z dwoma lub więcej otwiera menu z wierszem na Rynek — jego tytuł, opis poniżej, ikona dla jego linii Każdy z nich otwiera zakładkę danego rynku. Jeden kanał z buforowanej listy Obie nawigacje, launchpad i etykieta, odświeżone na zmiany rynkowe. - Wiersze menu nawigacyjnego mają opcjonalny opis (popover, szyna, górny pasek). - Pole typu formularza rynkowego to "Linia biznesowa"; każdy wybór mówi Co to daje rynkowi, a zablokowany jeden nazywa aplikację, której potrzebuje Pomocnicy nazwy i opisu wyjaśniają, co oznacza nazwa i opis Członkowie zobacz w menu Rynki. - ACCESS_COMMERCE czyta "Dostęp do rynków"; strona pożyczkowa wskazuje na Ustawienia → Linie biznesowe.
· MediaService
MediaService sprawdza załączniki za pomocą antywirusa i odrzuca zablokowane pliki przy każdym odczycie
- Załączniki czatu (członek CHAT, web-chat gość PUBLIC), pliki systemowe-bug, obrazy Growth Hub Są sprawdzane wewnątrz storeContentAddressed z ich kontekstem (członek, konwersacja); Canva Odmowa dociera do klienta w momencie, gdy kształt platformy (422 ANTIVIRUS_BLOCKED {rodzina} / 503 ANTIVIRUS_UNAVAILABLE) zamiast być owinięty w 500. - Tła spotkań (raw MinIO, public bucket) przechodzą najpierw przez AntivirusUploadGuard. - /attachments/link (dedup by hash) odrzuca zawartość Antywirus zablokowany (422); zatrzymany plik może być Jest połączony i pozostaje nieczytelny dopóki nie zostanie zaznaczony. - Załączniki przenoszą skanowanie {status, rodzina, wynik} na odpowiedź upload, wiadomość na żywo Ramka i historia; Oczekiwanie podczas trzymania. - ImagingProxyController (oryginalny i podgląd), pobieranie odwiedzających, pliki systemowe, Obrazy, materiały i odczyty materiałów Canva z Growth Hub wywołują bramkę odczytu: 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING, sprawdzony przed brakującą zawartością 410, więc zatrzymany Serwer proxy sprawdza teraz członkostwo przed stanem zawartości. - ConfigMap kamo.antivirus.* (włączone: false dopóki KamoAntivirus nie jest gotowy); Poprawiono błąd 0x0000000E w pliku mlos-internal-auth.
· ConversionService
ConversionService sprawdza przesyłane pliki za pomocą antywirusa, uzupełnia zatrzymane pliki, ponownie sprawdza nowe podpisy
Zastępuje klienta clamd w usłudze (malware / pakiet, UploadScanGuard, QuarantineStore, Skanowanie wsteczne (retro-scan) z biblioteką współdzieloną - /upload, /replace, /templates/upload są sprawdzane wewnątrz ImageService przed każdym wierszem lub Obiekt jest zapisywany (HOLD dozwolone); odmowy używają kształtów platformy: 422 ANTIVIRUS_BLOCKED {family}, 503 ANTIVIRUS_UNAVAILABLE, 503 HASH_MISMATCH. MALWARE_DETECTED zniknął i nie można go znaleźć Odpowiedzi przenoszą skan {status, rodzina, wynik}; a zatrzymany skan {status, rodzina, wynik} Plik jest PENDING i konwertuje po przechowywaniu. Potok emituje etap 'skanowania'. - /register-existing (dedup przez odniesienie) odrzuca zawartość Antywirus zablokowany (422). - Efekty dźwiękowe (raw MinIO) przechodzą przez AntivirusUploadGuard (bez zatrzymania, 503 w dół). - QuarantineStore nie istnieje już, więc nic nie jest zapisywane do wiadra kwarantanny; nic W nim jest dotknięty. - antivirus.hold.verdict (kolejka antivirus-hold-completer) -> AntivirusHoldCompleter, a następnie Zwykła konwersja dla zwolnionych dokumentów; błąd przechowywania naks dla ponownego dostarczenia. - antivirus.signatures.promoted (kolejka antivirus-recheck) -> AntivirusRecheckService: co flagowany hash, którego bajty są przechowywane (raporty unlock + notify + AUTO_CLEARED) oraz CLEAN zawartość oglądana po raz pierwszy w ciągu ostatnich 14 dni (LOCKED_LATER + alerty), przesyłana z MinIO, Subskrybenci będą próbować ponownie, dopóki nie istnieje strumień ANTIVIRUS. - Mapa konfiguracji: kamo.antivirus.* (włączone: false dopóki KamoAntivirus nie jest gotowy); Poprawiono błąd 0x0000000E w pliku mlos-internal-auth.
· kamo-shared-library
Zaangażowanie należy do rynku zdefiniowanego przez członka
commerce_engagements.market_id (stosowane ręcznie, FK do commerce_markets, Zamówienia detaliczne, zlecenia serwisowe, wynajem i zaopatrzenie (indeksowane za pomocą org_id) Rekordy nie mają własnej kolumny rynkowej; odczytują ją ze swoich Zaangażowanie, w ten sam sposób, w jaki czytają swoje konto klienta.
· kamo-internal
The Antivirus UI — protection seals everywhere a file appears, the Antivirus Center, the platform tab, alerts and help
Design kit (app/components/antivirus): ProtectionSeal with five animated faces (Checking, Protected, Caution, Blocked, Couldn't Check; brand + --av-* tokens, reduced motion honoured), BlockedFileCard / LockedAttachment / LockedOverlay, CautionBanner with Open a Safe Copy, MessageAntivirusBanner, ShieldClip, FalseAlarmDialog ("I think this is a mistake"), AntivirusNotReady. Logic from @kamo/antivirus-core 0.1.0 (seal state, reason parser accepting ANTIVIRUS_BLOCKED / MALWARE_DETECTED / ANTIVIRUS_CHECKING / ANTIVIRUS_UNAVAILABLE / SCAN_UNAVAILABLE). Surfaces: mail reading pane (seals, removed parts locked under their original names, message banner, inline images withheld, Download All skips them, list-row shield clip, body cache v2), composer/chat/SMS/SI trays (Checking + blocked states), chat bubbles for recipients, documents (Checking stage, seals, locked actions, caution gate), and the refusal toast on every upload (KB, avatar, careers, system bugs, sounds, account/patient/application documents, logos). Antivirus Center at **************** (VIEW_ANTIVIRUS; policy needs MANAGE_ANTIVIRUS_POLICY): protection orb, count-up KPIs, trend/origin/family charts, live threat timeline, policy switches with help, false alarms. Platform tab (MANAGE_PLATFORM_ANTIVIRUS): scanner health, releases with refresh/rollback, review queue, allowlist, outbreaks, safety drill. Three notification kinds, the Antivirus guided tour, /api/antivirus BFF, mirrors for ServiceType ANTIVIRUS(41), rights 698-700 and MANAGE_PLATFORM_ANTIVIRUS (shared-lib 332f7275), and seven help center articles. The Protection home widget component is built but not registered: the launchpad needs an ANTIVIRUS_WIDGET right block that the shared library does not have yet.
· KlusterServices
Svc_antivirus logowanie + strumień ANTIVIRUS; konwersja / e-mail może zużywać antywirusa.>
- svc_antivirus: STREAM.INFO/CREATE ANTIVIRUS, publikuje antivirus.> i rt.org.>, Subskrybuj antivirus.> i _INBOX.> (Secret kamo/nats-user-antivirus, SECRETS.md). - svc_conversion: API konsumenckie ANTIVIRUS (zatrzymaj werdykty, ponownie sprawdź promocję), publish/subscribe antivirus.>, publish rt.org.> (zapisane werdykty odświeżają interfejs użytkownika). - svc_email: ANTIVIRUS consumer API (wykrywanie filtrów poczty), antywirus. Przepisy dotyczące zadania ANTIVIRUS (R1, 14d), dzięki czemu konsumenci mogą wiązać się w pierwszej kolejności. Sprawdzono za pomocą nats-server -t na serwerze live.
Twój wszechświat czeka.
Rozpocznij bezpłatnie w kilka minut.Dodaj produkty, kiedy tylko będziesz gotowy — bez migracji, bez nowych logowań.
Bezpłatne na zawsze — nie wymaga karty kredytowej