Nenda kwenye maudhui
KAMOUniverse

Mabadiliko

Nini kipya.

Kila kuboresha jukwaa, kama ni meli.

  1. · 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.

  2. · 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

  3. · 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

  4. · 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.

  5. · 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

  6. · 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)

  7. · 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)

  8. · 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.

  9. · 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.

  10. · 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.

  11. · 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.

  12. · 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.

  13. · 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.

  14. · DaemonService

    Tick ripoti ya kila wiki Ulinzi (kwa saa, org-nyumbani Jumapili 08:00) na watch mlipuko (15 min)

  15. · 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.

  16. · APIService

    Route /api/antivirus/** to SecurityService and seal its internal subtree

  17. · 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).

  18. · 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).

  19. · 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.

  20. · kamo-internal

    Amri tab filters na masoko ya shirika mwenyewe

    Chips na safu labels walikuwa kwa mstari wa biashara, jina baada ya kwanza yake soko, hivyo mbili masoko ya rejareja kuanguka katika moja. Kila safu sasa inaonyesha soko lake mwenyewe (kutoka server); rekodi ya zamani na soko hakuna huenda kwa soko pekee ya mstari wake wakati kuna moja, mwingine kwa "<Line> - Hakuna soko" kundi. Kukumbukwa chujio ambaye soko ni kwenda kuanguka nyuma kwa Wote.

  21. · DocsService

    DocsService anakataa nyaraka kufungwa kila mahali na ukaguzi mhariri anaokoa

    - WOPI PutFile anaandika kavu MinIO, hivyo kuokoa hupita kupitia AntivirusUploadGuard kwanza: a madhara kuokoa huandika kitu chochote, anashikilia maudhui ya hati ya mwisho nzuri na anajibu mhariri 422 ANTIVIRUS_BLOCKED (503 ANTIVIRUS_UNAVAILABLE hivyo retries); safi kuokoa ni alama kuhifadhiwa kwa ajili ya baadaye tena-kuangalia. GetFile anakataa kufungwa / kuangalia maudhui na 423. - Imaging / kupakua, / mtiririko, PDF kubadilishwa na ukurasa thumbnails wito kusoma mlango kabla byte yoyote: 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING. tahadhari maudhui hupita, hivyo PDF yake rendition ni 'nakala salama'. Bulk kuuza nje drops kufungwa nyaraka kama ubaguzi wengine. - Version kupakua / pdf / thumbnail hukumu maudhui ya toleo mwenyewe. - Kazi resumes ni kuangalia kama kazi na mwombaji na maombi; kazi controllers jibu Antivirus kukataa katika sura jukwaa badala ya 500 . - Kisheria: uploads ramani kukataa yao wenyewe 422/503, iliyofanyika kupakua anauliza kujaribu tena (PDF yake rendition itakuwa imefanyika kutoka bytes unchecked), vifurushi kutekelezwa na sampuli ya ombi ni kusoma-gated. Binder albamu ya picha kuacha kufungwa picha nje. - Hati orodha / metadata safu kubeba scanStatus / scanFamily / scanOutcome. - ConfigMap kamo.antivirus * (wezeshwa: uongo mpaka KamoAntivirus ni tayari); Antivirus_Internal_Auth_Secret kutoka mlos-internal-auth.

  22. · SecurityService

    Kila Amri safu majina yake mwenyewe soko

    safu kubeba marketId / marketTitle kutoka ushirikiano wao (moja swali kwa ushiriki uid), hivyo shirika na masoko mawili ya rejareja anaona ambayo moja ili alikuja kutoka badala ya wote chini ya jina la soko la kwanza. Rekodi zilizofanywa kabla ya masoko walikuwa kufuatiliwa kuweka null.

  23. · KlusterServices

    Antivirus tahadhari (scanner chini, saini stale, mirror mlango kushindwa, p95, spike ugunduzi, kushikilia backlog)

    Kutumika kwa mkono (fuatilia / si lengo CI).

  24. · 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).

  25. · kamo-internal

    masoko - masoko ya shirika mwenyewe, kwa majina yao wenyewe

    "Uchumi" ni kwenda. soko ni nini wanachama kufafanua (kichwa + maelezo); Line yake ya Biashara ni tu aina yake. - Nav chaguo ni masoko. Pamoja na soko moja ni kwamba soko, na yake kichwa (kama kabla); na mbili au zaidi inafungua orodha na safu kwa soko — kichwa chake, maelezo yake chini, icon kwa mstari wake ya biashara — kila kufungua tab kwamba soko la. Moja cached orodha feeds wote navs, launchpad na label, refreshed juu ya mabadiliko ya soko. - Nav safu menu kuchukua maelezo ya hiari (popover, reli, juu bar). - sanduku aina ya fomu ya soko ni "Line ya Biashara"; kila uchaguzi anasema nini inatoa soko, na kufungwa moja majina ya programu inahitaji (ilikuwa ngumu-coded Kiingereza). Jina na maelezo wasaidizi kueleza nini wanachama kuona katika orodha ya masoko. - ACCESS_COMMERCE kusoma "Upatikanaji wa masoko"; pointi ukurasa Lending katika Mipangilio → mistari ya Biashara.

  26. · MediaService

    MediaService inaangalia viungo na Antivirus na anakataa faili kufungwa juu ya kila kusoma

    - Chat viungo (Mjumbe CHAT, web-chat mgeni umma), mfumo-bug files, ukuaji Hub picha ni kuangalia ndani storeContentAddressed na mazingira yao (mjumbe, mazungumzo); Canva pato kupitia uploadDocument. kukataa inafikia mteja kama sura jukwaa (422 ANTIVIRUS_BLOCKED {familia} / 503 ANTIVIRUS_UNAVAILABLE) badala ya kuwa kufungwa katika 500. - Mkutano wa backgrounds (raw MinIO, umma bakuli) kwenda kupitia AntivirusUploadGuard kwanza. - / attachments / kiungo (dedup na hash) anakataa maudhui Antivirus kufungwa (422); file iliyofanyika inaweza kuwa kuunganishwa na makazi unreadable mpaka kuthibitishwa. - Attachments kubeba kuchunguza {hali, familia, matokeo} juu ya kupakia jibu, ujumbe kuishi muundo na historia; PENDING wakati uliofanyika. - ImagingProxyController (original na preview), mgeni download, mfumo-bug files, Picha za Growth Hub, vifaa na machapisho ya Canva yanaweza kupatikana kwenye ukurasa wa kusoma: 423 ANTIVIRUS_BLOCKED / ANTIVIRUS_CHECKING, kuangalia kabla ya kukosa-maudhui 410 hivyo kufanyika faili anasema 'hata hivyo ni kuchunguza'. proxy sasa inachunguza uanachama kabla ya maudhui hali. - ConfigMap kamo.antivirus * (wezeshwa: uongo mpaka KamoAntivirus ni tayari); Antivirus_Internal_Auth_Secret kutoka mlos-internal-auth.

  27. · ConversionService

    ConversionService huchunguza uploads na Antivirus, hukamilisha faili zilizofanyika, tena huchunguza saini mpya

    Inachukua nafasi ya katika-huduma clamd mteja (malware / mfuko, UploadScanGuard, QuarantineStore, retro-Scan) na Antivirus kushirikiana-makumbusho: - / kupakia, / kubadili, / templates / kupakia ni kuangalia ndani ImageService kabla ya safu yoyote au kitu ni kuandikwa (HOLD kuruhusiwa); kukataa kutumia maumbo jukwaa: 422 ANTIVIRUS_BLOCKED {familia}, 503 ANTIVIRUS_UNAVAILABLE, 503 HASH_MISMATCH. MALWARE_DETECTED ni kwenda na hakuna saini jina ni milele kurudi. Majibu kubeba scan {hali, familia, matokeo}; iliyofanyika faili ni PENDING na kubadilishwa mara moja kuhifadhiwa. bomba hutoa 'kuchunguza' hatua. - / usajili-kuwepo (dedup na rejea) anakataa maudhui Antivirus kufungwa (422). - Matokeo ya sauti (kwa ajili ya MinIO) kwenda kupitia AntivirusUploadGuard (hakuna kushikilia, 503 wakati chini). - QuarantineStore haipo tena, hivyo hakuna kilichoandikwa kwa bakuli karantini; hakuna ndani yake ni kugusa. - antivirus.hold.verdict (mstari antivirus-kushikilia-completer) -> AntivirusHoldCompleter, kisha uongofu wa kawaida kwa ajili ya nyaraka kutolewa; kushindwa kuhifadhi naks kwa redelivery. - antivirus.signatures.promoted (kusubiri antivirus-recheck) -> AntivirusRecheckService: kila flagged hash ambao bytes ni kuhifadhiwa (kufungua + kutoa taarifa + ripoti AUTO_CLEARED) na CLEAN maudhui kwanza kuonekana katika siku za mwisho 14 (LOCKED_LATER + tahadhari), streamed kutoka MinIO, moja kwa wakati, throttled. Subscribes kujaribu tena hadi mkondo wa Antivirus ipo. - ConfigMap: kamo.antivirus.* (wezeshwa: uongo mpaka KamoAntivirus ni tayari); Antivirus_Internal_Auth_Secret kutoka mlos-internal-auth.

  28. · kamo-shared-library

    kushirikiana ni mali ya mwanachama defined soko

    commerce_engagements.market_id (kutumika kwa mkono, FK kwa commerce_markets, indexed na org_id). Retail amri, kazi ya huduma, kodi na ununuzi rekodi hawana soko safu ya wenyewe; wao kusoma kutoka yao kushirikiana, njia hiyo hiyo wanasoma akaunti yao ya mteja.

  29. · 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.

  30. · KlusterServices

    Svc_antivirus kuingia + ANTIVIRUS mtiririko; ubadilishaji / barua pepe inaweza kula antivirus.>

    - svc_antivirus: STREAM.INFO/KUTOA antivirus, kuchapisha antivirus.> na rt.org.>, Kujiunga antivirus.> na _INBOX.> (Siri kamo/nats-mtumiaji-antivirus, SECRETS.md). - svc_conversion: ANTIVIRUS watumiaji API (kushikilia verdicts, recheck juu ya kukuza), kuchapisha / kujiunga antivirus.>, kuchapisha rt.org.> (hukumu kumbukumbu refresh UI). - svc_email: ANTIVIRUS watumiaji API (detections barua pepe-chujio), antivirus.>. - mkondo-bootstrap Kazi masharti Antivirus (R1, 14d) ili wateja wanaweza kushikamana kwanza. Kuthibitishwa na nats-server -t dhidi ya kuishi server.

Ulimwengu wako unasubiri.

Kuanza bure katika dakika. Ongeza bidhaa wakati wowote wewe ni tayari - hakuna uhamiaji, hakuna logins mpya.

Bure milele - hakuna kadi ya mkopo inahitajika