# AUREVIX Nest - Deep QA aur fixes Release: 22 October 2026. Scope: is bundle ke saare 6 Nest plugins. ## Final package | Plugin | Version | |---|---| | Aurevix CoreNest | 0.9.2 | | Aurevix FormNest | 0.9.2 | | Aurevix BookNest | 0.9.2 | | Aurevix CoreNest Pro | 0.4.5 | | Aurevix FormNest Pro | 0.4.5 | | Aurevix BookNest Pro | 0.5.2 | Shared licensing connector: 2.3.1. Existing product slugs, Manager feature choices, assigned licenses aur trial dates retain hain. ## Jo issues resolve kiye | Area | Masla | Corrected behavior | |---|---|---| | Cancellation / reschedule | Purane direct staff API actions late-charge review bypass kar sakte thay. | Dashboard aur legacy endpoints aik hi policy/adjustment flow use karte hain. | | Unscheduled paid booking | Payment approval ke baad time na honay par cancellation/refund record incomplete ho sakta tha. | Cancellation paid credit aur refund due ka record banati hai. | | Reservation expiry | Optional Pro reminders ON hon to default reminder function hold expiry skip kar sakta tha. | Expiry reminder choice se independent chalti hai. | | Duplicate submission | Network retry par saved reservation ko receipt mein reserved nahi bataya jata tha. | Same request ki current hold aur expiry show hoti hai; expired time reserved nahi bataya jata. | | Full forms | 30-field legacy form mein required Voice/Video choice add honay ki jagah nahi bachti thi. | 30 custom fields preserve hoti hain aur required consultation choice safely add hoti hai; migration retry marker updated hai. | | Consultant assignment | Assignment-only custom role ka booking-view scope doctor lock ko bypass kar sakta tha. | Fixed doctor slot ki binding raw booking data se validate hoti hai. | | Google meeting changes | Voice/Video ya consultant change par purani event details/invitation reh sakti thi. | Managed event/link replace hota hai aur attendees current assignment ke mutabiq bante hain. | | Google concurrency | Purana in-flight result nayi meeting choice overwrite kar sakta tha; deleted event ID reuse bhi ho sakti thi. | Worker lease/generation checks aur nayi event identities obsolete updates ko rokti hain; retry idempotent rehta hai. | | Google disconnect | Pending OAuth/refresh result disconnected connection ko dobara active kar sakta tha. | Generation fence aur separate protected token storage old attempts ko invalidate karti hain. | | Pro expiry | Owner disconnect aur old event cleanup Pro expiry ke baad ruk sakti thi. | Owner disconnect aur cancellation/erasure cleanup available rehti hai; new automatic meeting creation active Pro access mangti hai. | | Invoice payment state | Cancelled/change-pending paid booking ka original invoice unpaid dikh sakta tha. | Original verified invoice paid rehti hai. Adjustment apne actual received payment tak unpaid rehti hai. | | Revenue report | Original-status totals late adjustment payments aur recorded refunds ko reflect nahi karte thay. | Received payments + received adjustments - actual recorded refunds; pending refunds alag hain. | | Private record erasure | Optional request messages/notes retain ho sakte thay aur completed meeting ka event cleanup queue nahi hota tha. | Request-linked private tool records remove hote hain aur managed event cleanup queue hoti hai. Unrelated form history preserve hoti hai. | | Pending financial erasure | Open late-charge/refund obligation erase ho sakti thi. | Review, adjustment payment ya pending bank refund settle kiye baghair erasure reject hoti hai. Inactive BookNest ki linked booking pehle activate/review karni hoti hai. | | Update availability | Manager download withhold kare to bhi newer release button appear ho sakta tha. | Withheld package ka update button offer nahi hota; installed feature licensing apni state se control hoti hai. | | Owner recovery | Suspended Normal access mein admin record inspection / SMTP recovery advertised behavior ke mutabiq nahi thi. | Authenticated owner read access, settings/mail repair aur Google disconnect retain karta hai; normal booking writes license enforce karti hain. | | Private downloads | Binary output default WordPress CORS headers se pehle send honay par PHP warnings aa rahi thin; HEAD handling incomplete thi. | Headers pehle finalize hote hain, HEAD file bytes nahi bhejta, aur untrusted origin response credentialed CORS headers nahi rakhta. | | Invoice PDF | Lambi business names ya unbroken bank strings page ke right edge se bahar ja sakti thin. | Actual bundled font widths ke mutabiq wrapping aur multi-page flow verify hai. | | Licensing screens | Nest Pro ko ab bhi empty shell aur purane feature counts ke taur par describe kiya ja raha tha. | Current workflow modules, Google Meet automation aur invoice templates ki descriptions corrected hain. | ## Verification | Check suite | Passed assertions | |---|---:| | Booking / invoice / policy / Google workflow | 139 | | Actual CoreNest Auth with WordPress adapters | 37 | | New regression scenarios | 51 | | Chromium UI, 390px mobile aur Pakistan browser timezone | 34 | | Real WordPress roles, REST routes, data and license behavior | 76 | | Real HTTP multipart proof upload / private file downloads | 15 | | Real WordPress payment, cancellation, refund, revenue and erasure | 29 | | Eight Normal/Pro activation combinations | 44 | | PDF long-text and page-boundary assertions | 6 | | **Total** | **431** | 125 plugin PHP files lint pass hain. 15 JavaScript source files syntax pass hain. Shared runtime, Forms, assets aur connector copies byte-for-byte match hain. Individual plugin ZIPs ki metadata, hashes aur archive integrity verify hai. Environment: PHP 8.3.6, isolated WordPress 7.1.3, MariaDB 10.11.7 aur Chromium 151. SQLite fixtures bhi use hue. Final real WordPress/HTTP run mein PHP warnings/errors log nahi hue. Normal aur stress PDF pages visually inspect hue; lambi strings margins ke andar rehti hain. Har Normal plugin akela, matching Normal + Pro pairs, saare six together, aur BookNest Pro without Normal dependency ka safe behavior check hua. Existing 64 optional module grants aur role restrictions verify hue. Google Calendar HTTP aur Meet browser responses simulated thay. Actual file upload/download tests real PHP temporary uploads aur real WordPress permission checks se hue. ## Live setup ki baqi verification Yeh corrected code package hai. Client ki live website par upload, Manager par releases publish, actual Google OAuth/Calendar invitations, real SMTP/inbox aur do logon ki voice/video call is QA mein execute nahi ki gayi. Koi real customer email, bank payment, refund ya Calendar event generate nahi hua. Client ke exact hosting, theme, cache/security plugins aur existing unrelated plugins ke saath final staging acceptance SETUP-GUIDE-ROMAN-URDU.md ke mutabiq karein. Real Manager ka server-side update restriction aur download policy bhi us environment par check honi chahiye. Yeh ZIP Manager server ko replace nahi karti. Google Meet ke Voice/Video options aur naye slots ki maximum 30-minute duration retain hain. Call ko 30 minutes par automatically end karne aur camera ko remotely force OFF karne ka claim nahi hai. Bank transfers/refunds actual staff operations hain; dashboard unka verified record rakhta hai. ## Install karne ka short tareeqa 1. Website/database backup lein aur staging par update karein. 2. Outer bundle extract karein. WordPress mein plugins/ ke individual installers upload karein aur Replace current with uploaded choose karein. Uninstall/delete se update na karein. 3. Installed Normal Nest plugins ko 0.9.2 par saath update karein. Matching installed Pro installers bhi update karein. 4. Manager mein individual installers unhi product slugs par publish karein. Existing feature switches/license dates reset na karein. 5. Cache clear karke guide ke real-account acceptance steps complete karein.