What's shipping, as of today

Rooms now render in their real finishes with a camera you can stand anywhere with; a project's rooms come together on one floor plan, with ready-made 3, 2 and 1-bedroom floors; kitchens use the same room designer as wardrobes; and every product ends with a short Finish step for the project's name and customer.

Design a room before the furniture: draw its walls, shape it as an L, U or T, add doors, windows, pillars, beams and furnishings, and see every wall. The wardrobe's 2D view is now the drawing you print, and new configurator options add TV wall panels, decorative screens, shaped shelving, stacked carcasses and storage above study tables.

Wardrobes can now turn a corner, stand under an attic ceiling, leave open wall between carcasses, take a study table or dresser between them, or stand free as a dressing island. Kitchen templates start with real cabinets, every product area has templates, and the wardrobe configurator is quicker to use.

Hallway and shoe storage can now be designed in the wardrobe configurator: tilt-out shoe bins, pull-out shoe and trouser racks, coat hooks, an open panel for coats, and lockers inside a compartment. Each is cut and priced. Hardware the library does not hold yet is listed unpriced, never guessed.

A wardrobe can now sit under a staircase or a sloping ceiling: each column steps down to meet the slope, with an angled panel closing the space above it. A piece hung on the wall is drawn off the floor even before its height is set.

Design your own now offers 118 examples to start from, up from 70. The new ones include wardrobes with a loft, ten mandir (pooja) units, crockery units, a bar cabinet and many more, each opening in the configurator ready to change.

The Quote Engine side navigation now has Library and Settings, each opening one page that brings every library or every setting together, and a Back button on every screen. Every product area starts the same way: from a template, fresh, or from your earlier designs.

An open wardrobe column can take a CNC-cut arch face instead of doors, with a jali behind it, for a display, a bookshelf or a mandir. Tall doors suggest straighteners, and a column's light grooves are placed by dragging.

Wardrobe drawers come in standard combinations, inside or on the front, with fronts of their own material. A column's settings open with a double-click, a pillar behind it can be cut round, shelves stop at standard heights, and the plinth can be built with a raised bottom or on a base frame.

Wardrobes can be dragged to size, take a loft that fits the board, keep shelves in one section beside a divider, and be saved as presets. A new project now opens straight on its design; its details are filled in at the end.

A tall wardrobe and a low sideboard can now stand in one run: each column can have its own height. Drawers slide open in the 3D view, and the 3D view can turn 180° or all the way round.

Storage moved to Amazon S3 on 9 October. Documents and files saved before that move would not open; they open again now.

Wardrobes are now designed step by step beside a large live picture you can edit directly. A new Design your own tab starts sideboards, shelving, hallway storage, room dividers and more from 58 ready examples.

Founders Vault is simpler to use. One email code opens it for 8 hours, even if you leave the page, and sensitive actions no longer ask for another code. Vault records now sit in the main database, still encrypted, and uploads open straight away.

Files and documents saved before storage moved to Amazon S3 open again. Also adds a Scheduled emails switch that is off by default, two HR fixes, buttons in link emails, and a simpler wardrobe screen.

Several Inventory lists that could never fill now do, publishing a price list works again, stock and valuation actions ask before they post, and every Inventory write checks your permission. Errors now say why, and money shows in rupees.

Work Management Programs open as cards by default, with a Cards or Table choice remembered per user.

Work Management Portfolios open as cards by default, with a Cards or Table choice remembered per user.

The Application Settings Overview has a new Operations & Security section, so the Operations page and its neighbours can be opened directly instead of only from the Analytics dashboard.

Onboarding invitations whose employee record was deleted can now be cleared from the Onboarding page, and Brands, Price Lists and Work Management Projects open as cards.

Adds a one-time data update that gives the Propulsive ERP installation the Files module, which the new Files workspace needs before it can be switched on. Nothing changes for users until the Files feature is turned on.

Corrective actions gain Five-Why and 8D investigations, and a CAPA can propose an Inspection Plan change that an independent approver turns into a draft plan version. The CAPA screen is rebuilt.

The More menu on module rows is now a panel with a search box, section chips with page counts and a page grid, and HRMS and Accounts get a Simple menu or Full menu switch.

Re-uploading phone-only prospects now applies their real company names. Warehouses open as cards, the Email list columns line up like Gmail, and the Files New menu and Move to folder work.

Six more lists open as cards by default, with a Cards or Table choice remembered per user.

Adds operation-level quality evidence for production inspections, a CNC program lifecycle for machines that need an approved program, and a Training Operations workspace.

Adds the Field Operations foundation: a mobile check-in screen, visit lists, and the attendance, expense and posting checks behind them. Everything is switched off and does nothing until the owner turns it on.

Sales Invoices, Vendor Bills, Estimates and Receipts open as cards by default, with a Cards or Table choice remembered per user.

The IT & Infrastructure app now has a working registry for providers, assets and settings with a renewal workspace, replacing the placeholder screens on all seven Infrastructure pages.

Support Tickets, Purchase Orders and Sales Orders open as cards by default with a Cards or Table choice, and lead cards gain Qualify and Convert to opportunity.

The CRM Service Tickets page opens as cards by default, and the door set configure pricing breakdown shows Not priced for unstated rates instead of a free zero.

Vendors open as cards by default, the Back button returns to the right page even after a refresh, and the Cards or Table toggles on Parties, Contacts and Vendors are large enough to tap.

Leads, Opportunities, Parties and Contacts open as detail cards by default with a Cards or Table choice, Call shows the number in a pop-up, saved Google profiles appear on records, and Party 360, Lead and Opportunity pages gain Edit and Open links.

Fixes a regression where closing certain dialogs with X, Escape or a click outside, then answering Discard changes with keep editing, made the dialog disappear while your typed edits were stuck behind it and it could not be reopened.

The Party Directory now lists real customers by default, you can mark leads, opportunities and prospects as existing customers, move a party back to Lead, Opportunity or the Prospect Pool, and choose a simple or full CRM menu. The search bar gains Edit, Call and Create.

Party Directory rows and the Lead, Contact, Party 360 and Deal pages gain Edit buttons. Quotation documents say Not priced instead of failing when a quote has not been costed. The Product Library and Panel Library match the approved designs, and Purchase and Quote Engine screens ask before consequential actions and protect unsaved work.

The Prospect Pool CSV import can update existing prospects, the Pool hides contacts that have already become a Lead, Opportunity or Party, and Lead, Deal and Party Account pages gain Verify with Google. The Quote Engine Module Library can import kitchen, wardrobe and home review candidates. Also ships the phone-only verification from 1.8.194.

Verifying a Prospect Pool record that has no company name or location now looks it up on Google Places by its phone number, and falls back to the phone when a name search finds nothing. Searching the list also matches phone numbers.

The Design engine workspace gives the canvas the 73px the footer used to take. The CRM command center and territory opportunity map use query forms that production's MongoDB accepts. WhatsApp inline-template creation gains test coverage.

Test connection and Verify Details on Google Places Verification now fall back to Places API (New) when Google refuses the key on the legacy API, and enrichment sends the key the way Google expects. Also ships the Prospect Pool edit button and Add prospect label first cut as 1.8.191.

Every Prospect Pool row now has a visible Edit button that reopens the quick prospect form pre-filled, and the header button reads Add prospect.

Selecting prospects now shows a bar above the table with the selection count, Clear selection and Delete selected; the row action reads Delete prospect. Behaviour and permissions are unchanged.

The Prospect Pool CSV import no longer crashes on load, shows its result after an import, files territories under the right code, and no longer leaves an empty organization behind when a contact is a duplicate. Vendor-bills Close and the recruitment footer badges now respect unsaved edits.

Lands the audited ZCode HRMS (batches 1-3), Sales (batch 2) and Purchase (batch 1) UI programmes: typed work is protected on the purchase routes and ~40 HR routes, raw ids no longer show where a name belongs, consequential writes ask before they happen, and Purchase write buttons now respect permissions on the handler as well as the screen. Audit repairs keep the build green and the guards from misfiring.

Lands the audited 73-host unsaved-changes guard package under its merge condition — the wave-skipped hosts now guarded, four save-then-nag defect fixes, main's richer guards kept on every shared host — plus the Chart of Accounts add-ledger fix (legalEntity stamped server-side, duplicate codes 409 with the code named), and the honest repair of what the package landing had broken: 40 duplicate guard members that broke the build, 27 dropped route wirings, and the Sales-owned billing-settings host.

Completes the platform-wide unsaved-changes programme: every remaining real-gap host from the Phase-0 verified list now carries the shared guard and answers it truthfully — manufacturing, HR, billing/accounts, work-management, CMS/knowledge-base, inventory, library, communication-integrations (typed credential rows guarded by snapshot drift), and the quote-engine shared-projects four-form workspace. Hosts with state beyond reactive forms guard by JSON-snapshot drift or check every bound form. Also lands the CRM-2 polish slice (contact-base regression coverage, toast/analytics/caption fixes) and repairs two route lines the wave-2 wiring had corrupted. No migration.

The platform-wide unsaved-changes coverage audit's first fix wave: thirteen routes and thirteen hosts wired with truthful guards — the six salary-structure hosts, payroll policy-packs' 28-control version workspace, machines, the roles permission editor (baseline-compare on the permission set), price-lists, routings' steps editor (snapshot-drift), automations, and purchase indents — each with the beforeunload pair and a 17-assertion coverage contract. Also lands the CRM programme's batches 4–5 (quick-company inline workspace, lead slim-down, form sectioning, label/for sweep across 19 templates with the shared phone-input labelForId), the pilot-audit P1 API fix (lead sub-document stripping order), and two one-character regex repairs that had left the spec runner unparseable. No migration.

This number was reserved for the CRM-batches-4+5 release train that stood down mid-cut when a parallel session took the deploy; every change it would have carried (CRM UI batches 4 and 5, the pilot P1 fixes, module-library and email/files work in flight) shipped in 1.8.185 instead. No build with this version number was deployed to any environment.

The owner's follow-up on the module library's still-grey Overview: both the Overview illustration slot and the 2D & 3D tab now render the quote-engine planning (design) screen's own interactive 3D box viewer — the same component, the same drag-to-turn / scroll-to-zoom / right-drag-to-pan interaction — at the module's stated envelope. Nothing is drawn from unstated facts: a generic type-A sample carcass (18 mm board, grooved back, one shelf, no front) is built at the stated width/depth/height, with captions disclosing that the module's own construction, finishes and hardware are not modelled; unstated sizes keep the 2D illustration and a state-the-sizes pointer. Client-side only; no API, RBAC, route or migration change.

Three workstreams land together: the CRM module's owner-approved UI programme completes — unsaved-work protection on 21 routes, RBAC-honest action gates, humans-not-ids rendering, and a shared friendly-error mapper swept across 318 call sites; the ERP Sales Quotations direction-D redesign ships as flag-gated shells (detail journey spine, list KPIs, editor wizard, approval decision cards) behind a fail-closed kill switch pre-seeded off; and every page header that lacked a back button gets the shared one (87 templates), with Product Engine's origin-aware back deliberately preserved. No migration.

The three governed definition libraries were live-routed with no navigation entry anywhere — the Module Library was reachable only through contextual links inside family configure screens, and the Dry Home and Bathroom libraries only by typing their URLs. All three now sit beside Panel Library in the Quote Engine menu, each gated on its own read permission. No migration; data unchanged — the seeded definition rows simply become findable.

The owner-approved Application Settings audit fix across four batches: form labels and feedback semantics module-wide, destructive-action confirmations, unsaved-changes guards, per-page refinements including the email placeholder caret fix and the roles keyboard reorder, and three new saved-credential test buttons (SMTP, AI key, GST lookup) with audited, secret-free probe endpoints. No migration; no permission or payload changes outside the new probes.

Ships the B2B quote workspace v2 journey shell behind a kill switch pre-seeded off, the shared stepper-badge and QR-label kit it needs, dry-home and bathroom reference-library seeds, and the module library's 2D & 3D tab rebuilt on the settings cockpit's own interactive 3D figure. No migration; the one new flag seeds disabled.

The global + New menu's single Quotation item always opened the Quote Engine's furniture workspace for anyone with Quote Engine create rights, so a general (non-furniture) quotation had no top-nav entry. A second item, ERP Quotation, now opens the existing commercial quotation editor and is gated on the same permission trio the ERP list's own New Quotation button checks plus estimation_quotation_v1_enabled — the flag the destination route's guard reads — so it hides rather than bounces wherever the commercial workspace is disabled.

The component library's axonometric view of blind-corner items drew the pre-correction construction (a partial-height blind patch, an open carcass, no filler or door). It now draws the corrected KC-01 construction: a full-height blind panel, the filler, and one door, matching the owner's 2026-10-04 correction to the module image.

Ships the audited agent-work integration of 2026-10-04: the W3 line's production-configuration and module-library drawings measured onto their approved previews, the design workspace v2 shell behind a kill switch seeded off, panel nesting that resolves material names to PlatformMaterial ids and never nests what it cannot resolve, sales-invoice GST heads written by the model, and the audit's own fixes (a build-blocking palette reference, test-fixture pollution of the public release history, and spec syncs for the redrawn figures).

Fixes found walking a purchase from request to production: goods receipts and bills for orders with service lines, blocked stock, closed orders, held work orders, opening stock and plant shift timing.

Turns an accepted Quote Engine quote into a sales order with an advance request, fixes the blockers found walking a sale from estimate to posted invoice, adds a clearer deal page, and fixes room creation and size checks in the Design workspace.

Adds a Today page and a global New button for sales, a table-first Deals list with saved views and bulk actions, a deal page that follows the opportunity type, a compact process-flow band across the app, forgot-password on the login page, and fixes that let a Quote Engine quote be issued and printed cleanly.

Rebuilds many Quote Engine, Design Engine, Product Library and Amendment 03 delivery screens to their approved images, adds the Price Master workbook import and compact engine navigation, and fixes a set of phone layout and pricing-display issues.

Adds one-click record and manifest views to the Manufacturing lists, shows recorded proofs of delivery on a loading plan, seeds product photos for a first batch of Hettich concealed hinges, and fixes a Files switch that was never created on a fresh install.

Adds the shade library editor and search, hardware fitting families and a batch of Design Engine drawing fixes. Panel-definition and rate-builder inputs are now read strictly so a blank is never priced as zero, the personal light or dark choice made in the Design workspace now carries over to the rest of the app, and several tab and control layouts were brought in line with the shared design rules.

Adds the Wall Panelling configure form as the sixth saved-but-unpriced family, restores the dry-home family to the product library so the library seed and its test suites run again, and lands further independent-audit fixes to family settings, saved-family lists and drawer and lift fittings input handling.

Completes the whole-home family bands (office, bathroom, doorsets, uPVC), closes the A03 manufacturing report set, and lands the fixes an independent audit found in the Quote Engine library, import and shade modules. Main's front-end build, which had been failing to compile since 23 September, builds again.

The Quote Engine can now save Door Sets and five furniture families that were not buildable before: Bathroom furniture, Beds, Office workstations, Loose furniture and uPVC openings. Each has its own form opened from the quote's Doorsets tab. These items are saved with their stated sizes and options but are not priced yet, and the quote says so plainly; a quote holding unpriced family items cannot be issued until they are priced or removed. The B2B quote footer now shows the five approved cost buckets and the Production details panel has Cut list, Board plan and Analytics tabs. The planner shows a slope's net and blank front-profile area. Panel CSV import now refuses unreadable numbers, duplicate codes and malformed files.

A full click-through of every HR screen found that filter and "select an employee/department/etc." dropdowns across roughly two dozen HR pages were rendering blank with a stray clear icon instead of their placeholder text ("All statuses", "Select a department..."), because the dropdown's starting value didn't match anything in its own list. Every one of those dropdowns is fixed. A few page breadcrumbs that read "Hr" instead of "HR", and garbled initials on the Organization Chart for names ending in "(Test)", are fixed as well.

A batch of 47 commits landed directly on main over the prior day without going through the normal audit-before-merge pipeline (no PR, no independent review, no release cut). This release is the catch-up: every commit has now been independently re-audited retroactively, two real defects were found and fixed, and one infrastructure blocker was cleared.

Two thin, read-only HTTP seams wiring the already-merged NCR/CAPA renderer (G04-S03 r5, 1.8.161) to routes: GET /nonconformance-reports/:id/record and GET /corrective-actions/:id/record. Each route checks its own surface's read permission. This is the last A03-03 report exposure — every A03-03 report now has an endpoint (R06 stays deliberately gated by design; R07/R08/R09 are all now exposed). Audit independently re-verified the centerpiece claim — that the CAPA integrity-warning path (closed without effectiveness evidence) survives the HTTP boundary byte-identical to the underlying renderer's own output — with an adversarial fixture distinct from the shipped test, plus a negative control confirming the warning is not always-on. No code defects found.

A new read-only "Production closure" card in the work-order detail surface, below the existing Factory-handoff card, consuming the already-merged GET /work-orders/:id/closure projection (G04-S03 r1+r6). Shows the closure-four rows (quality/packages/delivery/actualCost) verbatim from the reconciliation chain with icon+text+colour, a whole-chain reconciled/mismatch banner that teaches the statuses-vs-reconciled distinction explicitly, and a footer distinguishing pending (mid-flight) from not-applicable/not-linked (statements, never passes). Applies the G04-S02-r7 permission-gate lesson structurally: the card frame and the computed denial line render ungated; only the data section branches on load state. Audit independently re-verified every claim live in a dedicated API+Angular instance (including an adversarial mutation test and a direct DOM-state simulation of the restricted-permission path) and found no code defects.

Three thin, read-only HTTP seams wiring already-merged, already-audited services to routes: GET /work-orders/:id/closure (JSON closure-four projection, the Task 2 closure panel's future data source), GET /packages/:id/manifest (A03-R08 manifest HTML), GET /proof-of-delivery/:id/record (A03-R09 POD record HTML). Each route checks its own surface's read permission, deliberately not a shared dashboard permission. Audit independently completed the 3x3 cross-permission matrix (the shipped suite covered 3 of 6 cross pairs) and confirmed all 9 cells behave correctly. No code defects found.

A pure, read-only HTML renderer over the real NonconformanceReport and PlatformCorrectiveActionReport documents implementing REPORT-CONTRACTS.md §A03-R07. Status prints as the recorded service state, never inferred from closedAt. A CAPA whose status says closed while carrying zero effectiveness reviews renders a loud INTEGRITY WARNING instead of silently choosing a side; open actions on an otherwise-closed CAPA are counted and shown, not hidden. Cost fields are omitted with 'cost not recorded' rather than printing a fabricated zero. Closes out Task 4's full report set (R06 stays deliberately gated).

A pure, read-only HTML renderer for the signed PlatformProofOfDelivery record (REPORT-CONTRACTS.md A03-R09): every field verbatim, the recorded outcome never recomputed, the delivery challan a link only (never a substitute for POD detail), evidence rows by reference only, and a banner stating a correction is a new POD, never an edit. Unknown id throws ApiError(404). No route or UI ships in this release.

A pure, read-only HTML renderer over the real PlatformPackage document implementing the A03-R08 package manifest contract. Only verified package content lines render as manifest content; unverified lines are named and excluded, never printed as if shipped. A package with zero verified content renders as a package RECORD carrying a "NOT A DISPATCHABLE MANIFEST" banner. Dimensions and weight print only when actually recorded, distinguishing a genuinely recorded zero from an unset field. The package number carries an explicit identity note stating it is not an SSCC and naming the GS1 Company Prefix / allocation requirement this system does not have. No route or UI ships in this release.

A pure, read-only planner returning the three draft-only inspection candidates (incoming/in-process/final) with every required characteristic fact (method, target, tolerance, sample policy, instrument, responsible role) left null/unresolved and named in a per-candidate unresolved list. No InspectionPlan document is ever created, and the advisory qualityTrigger evaluator is untouched (complete non-interference). No route or UI ships in this release.

A read-only "Factory handoff" card in the Work Order detail screen: which immutable design release the order's BOM traces to (recorded vs reconstructed vs unlinked), BOM coverage, the pinned routing revision, label status, live readiness, and a "Route traveller" button that previews the already-merged A03-R05 route traveller in the app's own preview modal. Consumes only already-merged endpoints; no new backend behaviour ships in this release.

A read-only, four-fact view of the reconciliation chain (quality, packages, delivery, actual cost) for screens that need exactly those closure facts, without the whole thirteen-link report. Every value is copied verbatim from the existing reconciliation chain, never re-derived, and reads nothing new — no route or UI ships in this release.

Exposes the already-merged A03-R05 route traveller renderer (1.8.153) as a real, RBAC-gated GET endpoint on the work order. No renderer logic changed.

Developer documentation and an acceptance-evidence record for the release-control work merged across the last several releases (correlation, gates, seed planning, the release packet, and the workspace card). No code changes, no behavior changes.

renderWorkOrderTraveller(workOrderId) is a pure HTML render (writes nothing) of the REPORT-CONTRACTS.md #A03-R05 factory-floor route traveller: a full traveller only when the work order's routing carries a PINNED RoutingRevision that resolves, is 'released', and has steps; otherwise a review/unavailable state naming every unmet condition (including a draft revision, which is explicitly not a qualified routing standard) plus source ids, never a fabricated route. A real defect was found and fixed during audit: the renderer's blank-CNC-machine-profile check tested only for object PRESENCE (machine.postProcessorProfile && machine.postProcessorProfile.workingEnvelope), but Machine.model.js schema-defaults both fields to a present-but-empty object for every machine -- so the safety flag never fired for any machine created through the real Mongoose model/API, only for the shipped test's own raw-collection-insert fixture (which happens to omit the field entirely). Fixed by extracting and reusing machineEnvelope.util.js's already-authoritative per-field isDeclared() logic (the module the sibling release-packet/isoGcodePost renderer already relies on) via a new exported hasAnyDeclaredEnvelopeDimension(machine) helper, closing the exact 'independently re-derives a fact another module owns' drift risk this audit was primed to look for.

Test-only follow-up to the G04-S02 r3 audit (1.8.151): the r3 audit hardened a03-routing-candidate-plan.test.js's mechanically-read-only source-scan forbidden-verb list (it was missing .insertOne(, .replaceOne(, .remove(, .findOneAndDelete(, .findOneAndReplace() and flagged the identical gap in five already-merged sibling suites as a coordinated back-port opportunity. This is that back-port: one line changed per file, no production code touched.

planRoutingCandidates() is a pure dry-run planner for the A03-RTG-PANEL/A03-RTG-ASSEMBLY review-candidate routings: no RoutingRevision document is ever created, and the two candidates it returns stay status:'draft' by construction (the field is assigned once, unconditionally -- no code path can emit anything else, so the unresolved.length > 0 => status !== 'released' invariant holds structurally, not just by test coverage). operationIds are resolved against the real A03-OPS-001 operation catalogue using the seeder's own findOne({name}) rule; a missing or inactive named operation is reported in unresolved with what would fix it, never substituted or defaulted. All owner facts (work-centre qualification, times/yield/capabilities/skill/subcontract lead, and the finished item each candidate routes FOR) stay unresolved with a stated reason.

GET /api/v1/platform-manufacturing/factory-handoff/:workOrderId exposes r1's factoryHandoffProjection(workOrderId) (1.8.148) over real HTTP, gated by platform_manufacturing.design_links.read. The handler adds only request shaping and a 404 translation for an unknown work order; every rule stays in r1's projection service, which this revision does not touch. RBAC proven by construction over real HTTP (real app boot, real PlatformEmployee/Role fixtures, real JWTs, supertest over loopback): unauthenticated to 401, no permissions to 403, and -- the interesting case -- a role holding only design_links.repair (not read) also gets 403, confirmed independently against the permission engine's roleGrants() (exact-key / '*' / 'module.*' / 'module.resource.*' matching only, no action-level implication), not just the shipped test.

The Manufacturing Release Workspace gains a release-control card showing whether a work order's factory release chain is ready, with each gate (quote verification, BOM/product release, design bridge, release approval) named individually rather than blended into one status, plus a button to preview the release packet in-app.

A new read-only service, factoryHandoffProjection(workOrderId), answers one question about a work order in one shape -- linkageKind, coveragePercent, skippedLines, bomId, routingId, labelStatus, readiness, reasons, generatedAt -- composed entirely from four already-existing authorities rather than reimplementing any of their logic: the design<->manufacturing bridge's own resolveForWorkOrder for linkage/coverage/skipped-line/ambiguity facts, the work order's pinned WorkOrderRouting.routingRevision for routingId, productionReconciliation.reconcileWorkOrder's own labels link row for labelStatus, and manufacturingReadiness.assessWorkOrder's own live summary for readiness. It performs no reconstruct/repair/issue/schedule/release call of any kind and writes nothing. This is Task 1 of a five-task phase plan; HTTP wiring, UI surfaces, and the acceptance-time evidence file are explicitly out of scope for this revision and are not present.

A new read-only GET endpoint renders the manufacturing release candidate's seven-section release packet as HTML, gated on stored evidence rather than the state enum alone: a full packet requires the candidate to be released AND its stored assessment to carry zero unoverridden blockers AND recorded source revisions, and anything short of that renders with a visible 'REVIEW COPY — NOT FOR FABRICATION' banner naming the exact unmet conditions. Everything is HTML-escaped; the renderer writes nothing and does not depend on the r1/r2 correlation endpoint (it reads the candidate document directly). One real defect was found and fixed during audit: the approvals section's own staleness check compared each approval's checksum against the wrong stored field, causing it to under-report staleness for any candidate approved without ever calling assess() (a reachable path, since approveState() never touches the stored assessment snapshot) — fixed to use the same field the packet's own header already labels 'Live scope checksum', and pinned with a new regression test.

A read-only correlation adapter now answers, for any work order built from a legacy BOM, which production package (if any) it is correlated with through the recorded design-to-manufacturing bridge, naming the exact missing edge whenever it cannot answer 'correlated'. A new GET endpoint projects that correlation into a release-control gate view (quote verification, released BOM/product, recorded/complete design bridge, current release approval) behind a three-permission RBAC AND. A companion dry-run planner reports what a governed operational seed WOULD do for five A03 requirements, never touching a database. Foundation only: nothing here grants a release, seeds anything live, or changes any existing route's behavior.

The loose-furniture family's product vocabulary is extended from storage-only to the full A02-P06 set (storage, sofa, armchair, dining-chair, coffee-table, side-table, console), and a new reconciliation pass classifies every real catalogue record for this family plus three deliberately cross-referenced upholstered-bed records, with an upholstery/mechanism safeguard: any record naming a lift kit, entrapment control, fabric/foam fact, or a bare stability/structural fact, is held for owner review rather than silently treated as a normal reusable template. The register also carries a purchased-vs-custom identity split (A04-02's bought-out identity vs A04-03/04's custom manufacturing) and names all four original roadmap IDs (A02-P06, A04-02, A04-03, A04-04) on one cross-map. The family stays not delivery-accepted with no planner dispatch.

The upvc-doors-windows family's product vocabulary is extended from empty to the A02-P07 set (casement window, sliding window, uPVC door), and a new reconciliation pass classifies all 17 real catalogue P07 records. P07 is the sharpest boundary of any family so far: uPVC is system-led (manufacturer profile/reinforcement/glazing/hardware facts, never defaulted) and structurally independent from the furniture aluminium/profile solver — verified by construction, not just documented, by showing the planning product-list accessor (calc/planning/productLists.js) recognises only families with a non-null planner (kitchen, wardrobe, b2b-cabinetry), so no container exists for a uPVC product to reach the assembly/layout pipeline. An audit defect in the manufacturer-system-qualification hold regex (6 of 17 records, 35%, escaping owner review) was found and fixed before this release. This closes the G03 whole-home family-foundations band: all seven A02 families now have their registry vocabulary, settings-readiness contract and reconciliation register.

The door-sets family's product vocabulary is extended from empty to the full A02-P05 set (doorset, partition, wall-panelling), and a new reconciliation pass classifies every real catalogue record for this family with an installation-interface safeguard: any record naming a survey opening, handing, gap, approved joint detail, substrate condition or fire/acoustic performance concern is held for owner review rather than silently treated as a normal reusable template. Door Sets already has real, working quoting on main (specProductType 'doorset'); this slice adds a library-identity layer alongside it without touching, wrapping or replacing that pricing path, and the family stays not delivery-accepted with no planner dispatch.

The beds family's product vocabulary is extended from empty to the full A02-P04 set (bed-frame, storage-bed, headboard, bedside-table), and a new reconciliation pass classifies every real catalogue record for this family with a load-path/mechanism safeguard: any record naming a mattress load-path, lift/gas-strut mechanism, bracing, joint, structural member, support schedule, stability or actuator concern is held for owner review rather than silently treated as a normal reusable template. One implementation discharges both A02-P04 and the A04-R01 bed-rendering scope (cross-map carried on the reconciliation output).

The office-furniture family's product vocabulary is extended from empty to the full office/retail P03 set (desk, pedestal, office-storage, meeting-table, reception, retail-counter), and a new reconciliation pass classifies every real catalogue record for this family with a structural/load safeguard: any record naming a worksurface-load, support-span, clear-knee-space or stability concern is held for owner review rather than silently treated as a normal reusable template. One implementation discharges both A02-P03 and A04-01 (cross-map carried on the reconciliation output).

The bathroom-furniture family's product vocabulary is extended from vanity-only to the full bathroom/utility set (vanity, mirror-storage, utility-cabinet, laundry-unit, wc-overhead), and a new reconciliation pass classifies every real catalogue record for this family with a wet-interface safeguard: any record naming a moisture/plumbing/wet-zone concern is held for owner review rather than silently treated as a normal reusable template.

Rebased onto 1.8.138 (G03.1-S01, the dry-home family registry, PR #592, merged during this audit) after an identical-version collision -- re-cut from 1.8.138 to 1.8.139, same content otherwise. Adds api/src/services/quoteEngine/calc/dryHomeLibraryReconciliation.js, a pure module that reads the A02 seed-catalogue (370 sourceRecords, an untracked shared-checkout file) and classifies its P01 (dry-home) records into reuse-inherited / extend-reviewed-record / new-template / planned-separate-system / hold-owner, each with a reason quoting the record's own qualification/configuration text. No DB writes, no seed application, no library rows. Audited on a clean worktree off origin/main (base worktree D:/ww-g38 was still present; both changed files verified byte-exact by sha256 against the slice's SNAPSHOT-MANIFEST.json before porting). The audit found and fixed a severe defect in the P01 partition boundary: the original code identified 'P01 dry-home records' with a regex over each record's free-text name/browsePath/group (matching words like storage, study, TV), and on the real catalogue that pulled in 25 records the catalogue's own crosswalk[].phase tags as P02 (bathroom-furniture), P03 (office-furniture), P04 (beds) and P06 (loose-furniture) -- e.g. a 'Bathroom tall storage unit' and a 'Drawer-storage bed' matched on the word 'storage' -- while missing all 14 genuine P01 BC-xx trade-pack records outright. The claimed 33-record / 14-extend / 11-reuse breakdown was internally consistent but computed against the wrong record set; independently re-deriving the true P01 set from the catalogue's own authoritative crosswalk[].phase field gives 22 records (14 BC-xx + 8 TV-xx), of which today only 1 (TV-01) holds (owner-gated split supply) and the remaining 21 fall to planned-separate-system -- zero reuse-inherited, zero extend-reviewed-record, zero new-template, because the real P00 ancestor pool has no record of a matching kind (supply-package / panel-component-template) anywhere in the catalogue yet. Fixed by reading crosswalk[].phase directly rather than re-deriving phase membership from prose; every other part of the classifier (ancestor-priority guard, hold-pattern matching, blocker surfacing) was independently verified correct and left unchanged. Also fixed: summary.complete was a hardcoded constant (always false) despite HANDOFF documentation describing it as conditional on blocker resolution -- it could never become true even once every blocker resolved and every row settled. Replaced with a derived fact (no blockers AND no row left in hold-owner/planned-separate-system), verified with a synthetic fixture to actually flip true when warranted while still reading false on today's real, still-unsettled data. TDD: 8/8 (the original suite's ancestor-inheritance assertion was softened to match honest real-data behavior -- today's real P01 set has no ancestors to honour yet -- and two new synthetic-fixture tests were added: the UNIQUE-LIBRARY-POLICY trap (a record with a real P00 ancestor and a new-template-hinting name must never disposition to new-template, verified against both the trapped case and a genuinely-new-template control case with no ancestor) and the complete-flag derivation (flips true only once every row is settled and every blocker is resolved). Both new tests were confirmed RED against the original code and GREEN against the fix. Fresh lint: Syntax OK (5615 files). Data-provenance note: the real catalogue is read from an untracked, session-local shared-checkout path (default D:/projects/woodworkingERP, overridable via A02_SHARED_CHECKOUT) with no digest or count pinning -- six of the eight tests depend on whatever that shared file currently contains, so a concurrent session editing it could change those tests' pass/fail independent of any code change; the three ID/count assertions in the first test were made self-consistent (deriving expected values from the same catalogue at test time) but hardcoded IDs (TV-01, SH-01) still assume specific records persist. Not imported anywhere yet (confirmed by a repo-wide grep of api/ and app/); this release carries zero behavioral change on any running path.

Adds the 'dry-home' row to the Quote Engine's single-source-of-truth family registry (api/src/services/quoteEngine/calc/families.js) -- label 'Dry Home Storage', status 'researched', deliveryAccepted false, planner null -- covering the A02-P01 storage vocabulary (TV/media, shoe, crockery, display, pooja, study, dressing-table, storage-cabinet units), with read-time aliases home-storage/dry-storage. Every downstream projection (ProductTemplate's PRODUCT_FAMILIES/schema enum, PRODUCT_WORKSPACES menu order at position 9 with uPVC renumbered to 10, QuoteEngineLibraryItem's stored FAMILIES/schema enum, calc SCOPE_TYPES) is a live require()-time projection of this one table, so the row change alone propagates everywhere except the Angular component library's own familyOptions copy, which was updated to match and is pinned by a golden regression test. Adds familySettingsReadiness.js: a pure, derived contract giving data/calculation/price/2D/3D/manufacturing/release readiness as seven separate facts (never one blanket 'supported' bit), each defaulting NOT ready with null evidence for a researched family, each carrying its own owning role, and deriving real (true) readiness for delivery-accepted families (kitchen, wardrobe) from the existing modules -- verified directly, not just asserted. Audited independently on a clean worktree off origin/main (base worktree D:/ww-g36 was still present, so the true source was recovered directly rather than via the zcode CLI artifact store); all six changed/added files verified byte-exact (sha256) against the slice's SNAPSHOT-MANIFEST.json before porting. The two most safety-critical claims were verified by construction, not by reading code: (1) dispatch gating -- planningLists()/productLists.LIST_KEYS genuinely exclude 'dry-home' (its planner is null), productLists.descriptor('dry-home') throws 'Unknown planning product list: dry-home', and a planning block carrying a stray 'dry-home' array is silently ignored by products()/cabinetOwners() -- there is no generic-cabinet fallback because the calculation/planning engine is keyed structurally on the kitchens/wardrobes/cabinetries/frameUnits list names, and QuoteEngineProductTemplate rows (where 'dry-home' is now a valid productFamily) are catalogue/review records that no calculation path reads, by the service's own documented contract; (2) the drift guard -- temporarily broke the Angular familyOptions array (removed one option) and confirmed the registry test's 'drift guard' subtest genuinely fails, then restored it and reverified byte-exact; separately reproduced the exact workspace-order collision (dry-home at order 5, colliding with beds) the slice's HANDOFF says its own TDD loop caught, confirming the golden PRODUCT_WORKSPACES test genuinely fails on that collision. Alias resolution (home-storage/dry-storage -> dry-home) was verified end-to-end through the real quoteEngineLibraryItem.service.js libraryFilter(), and confirmed that unrelated garbage family names ('dryhome', 'DRY-HOME', 'random-garbage-family') are never coerced to dry-home. Audit defect found and fixed: familySettingsReadiness.js's derived facts were only Object.freeze()'d, so the claimed 'writes throw' contract silently failed to hold for any caller module that does not itself carry 'use strict' -- constructed a genuinely sloppy-mode write (via the Function constructor, which is not lexically strict) and confirmed the pre-fix code let it through as a silent no-op (Object.freeze under sloppy-mode assignment does not throw; it just doesn't apply). Fixed by wrapping every derived fact and the readiness record itself in a Proxy whose set/defineProperty/deleteProperty/setPrototypeOf traps throw unconditionally, independent of the caller's strict mode; added a new regression test (readiness facts refuse a write even from a genuinely sloppy-mode caller) that reproduces the gap and is confirmed failing against the pre-fix code and passing after. Confirmed workspace order has no other collisions across the full eleven-family list (orders 0-10, all unique). Full suites run fresh in the ported worktree: dry-home registry test 8/8 (7 original + 1 new regression), family-registry golden suite 14/14, FE component-library view-model spec 13/13 (via app/scripts/run-specs-bounded.cjs), ng build platform exit 0 with zero errors or warnings on the touched component, backend lint Syntax OK (5615 files, +2 for the two new test/source files added by this slice). This is registry identity plus an honest readiness vocabulary only -- no dry-home settings editors, seeds, planning dispatch, or previews exist yet, matching the slice's own stated scope.

Adds api/src/services/quoteEngine/calc/mepServicePoints.js, a pure calc module coordinating electrical/plumbing/technology service points (room/host, position with an explicit datum, direction, responsibility, confidence, access envelope) across plan/elevation/3D/schedule views bound by one canonical digest. Coordination only: sizing facts a caller sends (loadAmpere, pipeDiameterMm, circuitBreakerAmpere, wireCrossSectionMm2) are dropped, not modelled, and certification is always null. Reproduces and never repeats the 'y || default zero-height' suspicion -- an unstated height carries heightUnstated: true with y staying null, while a genuinely-stated 0 is a real fact and is not flagged. Audited independently on a clean worktree off origin/main (base worktree D:/ww-g35 was still present, so the true source was recovered directly rather than via the zcode CLI artifact store); both changed files verified byte-exact (sha256) against the slice's SNAPSHOT-MANIFEST.json before porting. Audit found and fixed one real defect before release: the responsibility field (builder/electrician/plumber/technology-contractor/other) was never actually checked against its own exported enum the way kind and confidence are -- an unrecognised responsibility value was silently accepted (ok: true) with the point's responsibility field literally set to the string 'INVALID', flowing straight into the schedule output with no error and no review flag. Fixed by adding the missing enum-membership check, mirroring the kind/confidence pattern exactly; a RED-first regression test was added and confirmed to fail before the fix and pass after. This module is not imported anywhere yet (confirmed by a repo-wide grep of api/ and app/); shipping it is zero behavioral change on any running path.

A new pure calculation module represents a wall-hosted dado band as its own object, with variable per-span heights (no universal default), typed cut-outs that only deduct when policy says so, and a disclosed reconciliation with the countertop upstand so an overlapping region is never double-charged. Not yet wired into any quote or extras flow.

Adds api/src/migrations/086_quote_engine_profile_system_code_version_unique.js, the follow-up G01-S06 flagged: the (code, version) unique index the publish-race fix relies on only gets created automatically where Mongoose autoIndex is on (tests) -- pilot and production run with autoIndex off, so the index, and the duplicate-key-catch race guard that depends on it, do not exist on either host yet. This migration creates it explicitly, first refusing loudly (naming every conflicting row) if any legacy duplicate (code, version) pair already exists, so duplicates are resolved by human review rather than silently skipped or partially indexed. This release ships the migration FILE only. It has not been run against pilot, production, or any real database of any kind -- applying it to a host is a separate, owner-gated step per this repo's standing migration rules, to be done only after `node scripts/migrate.js --status` is checked on that host.

A new pure calculation module represents a stone countertop run as its own quoted object, keeping net geometric area, whole-slab purchasable area and the seller's chargeable basis as three genuinely distinct facts instead of one blended number, with joints adding no phantom material and no invented rates. Not yet wired into any quote or extras flow.

A new pure module, finishSurfaceSlots.js, gives the finish-asset system a named slot vocabulary (front-face, body-face, back-face, edge, elevation-view), each declaring which asset types (sample/elevation/render) may legally occupy it. An attachment {slot, finishCode, assetType, assetSha256} pins the selected asset version by digest, never by a mutable pointer. Preview -> Discard/Apply: a preview never touches applied state, only one preview exists at a time, and Apply is the only writer. renderSignature(state) folds every APPLIED attachment through canonical key-sorted serialization so any applied change invalidates the render while a preview never does. Cost-ready/verified stay read-only derived facts, recomputed from caller-supplied evidence, never stored on the attachment. Zero importers by construction -- no regression surface.

A new, bounded-core data contract and service for machining designs (decorative-front and cnc-handle purposes, filtered from ONE append-only versioned registry, never two collections): draft -> technically-complete -> published -> revoked, with a Production-Manager digest-confirmation gate. Additive only, zero importers anywhere in the app or API (grep-confirmed) -- no regression surface by construction. An audit fix closes a real self-confirmation gap in the confirmation gate before release.

A tall cabinet's front-row split now records who authored it: splitDatum labels each row as 'stated' or 'derived-fill', frontAlignment persists an alignment to a verified wall/appliance reference (a bare offset with no reference does not persist), and frontSplitPreset persists an owner-approved preset key verbatim. The preset registry is empty by design; an unknown preset key is refused rather than guessed into dimensions.

The edge-tape bill of materials now scopes by the revision's supply scope (complete/cabinets/shutters-only), matching the commercial total, cut list and panel schedule, which were already scope-correct. Audit found and fixed three real defects beyond the slice's own claims: the scoped ORDER length (not just net length) silently reverted to the unscoped total whenever a tape-order purchase allowance was configured; the per-collection shade attribution misattributed metres between collections on a partial-scope order; and every decorative drawer front was misclassified as carcass instead of shutter tape because the split read the wrong internal role variable.

A shutter leaf can now state a finished size directly (gaps already adjusted) as a second, explicitly persisted input mode alongside the existing cabinet/opening-derived width. The two modes are mutually exclusive per leaf and refused loudly, before the layout changes, wherever a leaf is written.

The Profile System master's save path silently dropped two fields the profile-shutter calculation actually reads (per-member handle/hinge-stile/rail profile facts, and the rail-deduction fallback), so authored values could never reach the calc regardless of what an operator entered. Both now persist through create and every subsequent version. Also closes a related gap: a door-system hardware preset could not be saved at all because its family was missing from the model's enum.

A new pure, dependency-free evaluator (evaluateDimensionConstraints, classifySelectionMm, separateDimensionFacts) implements the dimension-constraint contract from DIMENSION-CONSTRAINT-PLAN.md, so the Design Library resolver, the quote-local dimension-selection service and the definition validator will all share one answer instead of independently re-implementing the rules. This release adds only the evaluator itself — nothing in the running app calls it yet, so there is no user-visible or behavioral change.

A new read-only directory screen at Application Settings > Engine Configuration gives admins one place to see setup status, jump to configuration areas, and check import/activity surfaces for the Design and Quote Engines — discoverable from the Application Settings hub, which previously had no such link wired to render.

Five previously-recorded Panel Library contract gaps, each re-audited against current code before being credited: two processing-rate field mismatches that made a save fail, a handle-profile Save/Adopt permission gate that relied on a raw 403, and a profile-system publish race that could silently write two rows for the same version. A fifth recorded gap (an AIR-pocket location hint) was found already resolved by concurrent work and closed as a recheck, not a re-fix.

Two persisted, whitelisted Design Library construction-system fields (Edge treatment policy and Calculation strategy key) could be silently changed on a published construction system via a direct API call, bypassing the version-on-publish rule every other field already enforces. Both are now visible in the editor and locked exactly like the rest of the form once published.

The Columns menu's thickness entry now says "Finished" exactly when the rendered table heading does, and a load-sequencing token closes a stale-response race on rapid archived-status toggles.

Picking the material a panel's body, back or panel sheet is cut from now shows only eligible board SKUs, instead of an arbitrary first catalog page. The same eligibility is enforced on save.

Parity 2, drop 2 of 2. The Quote Engine screens (form previews, the approved Phase 2 screens, bundle visuals) and the customer quotation documents now follow the approved references: the Quote Engine's own side menu, the kitchen and B2B tab layouts, the quotation letterhead and layout, and per-component pricing. Issued quotations from before this release still print exactly as issued.

A new Doors & Millwork workspace in the Quote Engine takes a door or millwork job from site measurement to production. Frames, leaves, architraves, glazing, sliding and entrance doors, trims and panelling are engineered from one calculation, which produces the drawings, cutting lists, stock plans, BOM, release, labels and packing.

Parity 2, drop 1. The Design Engine workspace and its proposal drawing sheets now follow the approved concept screens and the proposal PDF: its own side menu, the 3D workspace with labels, fitting callouts and an exploded view, per-unit notes, and proposal sheets laid out like the approved pages. The Quote Engine rebuild follows in the next release.

Amendment 01. The Design Engine gets focused-room editing, a top band with the four design outcomes, true drawer positions, site and corner detail, door operation notation, a technical 3D mode, fitting picks from the hardware library, and complete drawing sheets with schedules. The Quote Engine gets a separate wardrobe bottom panel, sliding track lengths, OEM documents, handle finish, profile + glass shutters priced per door, and richer optimizer and retail quotation output.

Every full-page form now puts its title in the app's main header and its Save/Cancel in the main footer, the Email screen gets the approved Gmail-style layout on top of all its phase 1–5 features, and the Quote Engine gains shade pickers on the wardrobe and B2B screens, the full Ebco price list and working part-rule functions.

Production's release line (1.8.109–1.8.112) and main are one line again, so nothing live is lost: the opportunity detail redesign, email phases 1–5, honest margin figures, CRM single create, the scoped reporting period and payslip PDFs stay, and main's work since 1.8.108 arrives with them — the Hardware Library search workspace, Files (behind its flag), WhatsApp support, Meet links for CRM and the contract-audit fixes.

Quote Engine hardware (Gola, door systems, straighteners, profile doors) now prices from the maker price lists in the Item library; Phase 2 B2B cabinetry and the editable hardware library land; Files, the Gmail-style Email workspace, WhatsApp support and Meet links for CRM arrive; contract-audit fixes across Sales, Purchase, HR, CRM and Files.

Numbers nobody measured are no longer shown as facts, creating a lead or contact takes one button and fewer fields, and the reporting period only appears on screens that use it.

The Quote Engine's B2B cabinetry work arrives in full, processing is priced instead of silently costing nothing, and a backlog of stock, manufacturing and sign-in fixes lands with it.

The opportunity page shows each fact once, only what someone actually entered, and one clear next action. Email gains privacy-safe images, real conversation threads, folders, sorting and keyboard shortcuts. Dashboard figures read correctly.

Every tool in the Tools menu is now real: a Files browser with Save to Drive, WhatsApp in the CRM inbox, Meet links on appointments and Website Chat. Email gains search, party search and rich-text compose; To-Do is rebuilt around correct due dates; staff can download payslips.

Staff can sign in with any email address as typed; the Prospect Pool shows only prospects, not existing customers; Email gains print, download, headers and per-message actions; screens that were failing now load; permission and approval checks are tighter.

The app update strip names version and build and links to Version & changelog; CRM prospect verification settings compile for pilot/production builds.

Same-path ?tab= navigation reloads the route; CRM Settings reads tab from hash when router query lags.

Business module Linked settings use erpHashLink so the Angular router runs the destination, not only a hash URL change.

CRM Settings cards, picklist tabs, and the CRM header Settings menu use erpHashLink so native hash navigation is confirmed including ?tab= switches; hard assign runs when the hash did not change.

Open links use routerLink + queryParams like the working wizard control, with confirmRouteTargetNavigation hard fallback after SW mismatch.

Open links rely on native hash navigation instead of click handlers that blocked the browser when the router silently no-opped.

Linked settings fall back to location.assign when the router refuses navigation after a service-worker chunk mismatch.

Open links call navigateByUrl with a location.hash fallback instead of relying on routerLink under the service worker.

Route targets use one absolute path command so Linked settings Open links navigate under hash routing.

Linked settings Open links use single-path routerLink commands like Run setup wizard, not hash-only anchors.

Business Module and CRM settings Open links use hash href anchors only; no routerLink or click interceptors.

Business Module and CRM settings links use routerLink plus Router.navigate with queryParams instead of navigateByUrl on combined URLs.

Linked settings and module settings Open links route reliably under hash routing via navigateByUrl.

Linked settings Open links navigate via hash hrefs; route targets use single-path router commands.

Module detail Linked Settings Open links use Angular router links with query params for reliable tab deep links.

Lifecycle uniqueness, issue and party/GST guards, decision ledger, export artifact audit trail, and pilot library qualification on the Quote Engine API.

CRM Settings cards and sidebar links open the right tab; child settings routes match; Back respects returnTo.

CRM business-module policy fields are editable on Application Settings and enforced on staff lead create and lead conversion.

Setup wizard and linked settings preserve return navigation; keyboard users can open linked settings with Enter; wizard fix actions match module detail resolution targets.

New estimates are built in a dedicated workspace with prospect-scoped CRM data, rich terms and templates; CRM module configuration separates required setup from optional enhancements and names every fix action.

The link in the personal-email verification email now opens a page that confirms the address.

Every report and document can be previewed before downloading, sales documents follow the new professional layouts, command centers and maps match the approved designs, and opportunities move forward from one simple stage bar.

Application Settings is now a guided settings workspace, command centers show real monthly trends and a shared India map, and Purchase and CRM gain new home views.

Tools → Email and other tool workspaces fill the routed column, remaining shell chrome uses mapped Material icons with wrapping labels, and Pilot also ships the Purchase Command Center and print-paper tokens already on main.

Pilot HR onboarding and performance collectors now fail closed on missing evidence, search dropdowns line up with the text boxes beside them, and module More menus close when you click away.

Pilot module homes now use the approved contextual icon treatment across KPI cards, section views and analytics panels instead of generic or text-only card chrome.

Pilot module homes now expose their approved operational hierarchy, certified queues and honest unavailable states instead of sparse, fragmented or duplicate navigation views.

Pilot navigation, command centers, governed CRM capture and API request handling now match the approved app-wide UAT contract under sustained authenticated use.

The remaining approved module, CRM, territory, location, return-navigation, report and onboarding requirements are reconciled for Pilot validation.

Inventory, Knowledge Base, Library and Site Survey now open dedicated, full-width command centers with authoritative module-wide data and the approved analytical composition.

Week view now exposes the same complete, actionable calendar-item treatment as Month and Day, grouped by date without capping or hiding records.

CRM day-calendar entries now open the approved communication-notes and next-follow-up form for both lead and deal commitments, closing the final live Pilot mismatch found during the app-wide acceptance replay.

The approved app-wide tabbed interface now reaches the operational pages, calendars, shared quick actions, location-aware CRM records and full-width command centers required for Pilot acceptance.

Operational overviews now match the approved resource hierarchy with centered workspaces, prominent semantic KPI icons, denser ledgers and reliable module-tab ownership.

Module workspaces now use the approved tabbed navigation and consistent controls, while legacy imported CRM references no longer break sales command-center views.

Support Chat inbox aggregation now uses the MongoDB stage supported by the deployed Pilot server while preserving the same unread and activity projections.

Founders and sole proprietors can now use the same isolated, email-verified private Vault as eligible directors without being treated as employee-directors for payroll.

The Pilot UAT graph now keeps its opening stock in one warehouse and presents the issue-adjusted ledger balance as the current quantity.

Pilot UAT seed snapshots now protect the complete database against drift without loading every business record into memory.

Revenue KPIs now rely on posted billing evidence, and managerial employment drafts can be corrected through a crash-safe, Pilot-only policy repair.

Salary-advance and Fleet decisions now require immutable evidence, and Pilot-to-Production HR conflicts can be resolved only through an exact reviewed, rollback-capable merge plan.

Managed performance actuals now stay evidence-backed, HR promotion previews verify typed dependencies and role authority, and the Production deploy path has stronger isolation and identity checks.

Pilot can now retire only the exact duplicate reminders left by the legacy Perfex manifest while preserving every business record and retaining complete disposition evidence.

Commercial modules now use the approved icon-led tab shell, CRM follows the prospect-first lifecycle, locations share one governed authority, and customer reports retain their approved print geometry.

Onboarding, employee payments and Propulsive KPI evidence now use one governed launch boundary, with permanent Pilot scoring exclusions and an encrypted HR promotion manifest.

Propulsive's approved L1-L7 pay-band corrections can now be applied safely to Pilot's standalone MongoDB with protected recovery evidence.

Employee performance, fleet logging, privacy controls, the Pilot order-to-cash rehearsal and Quote Engine Phase 2 now use clearer workspaces and stronger audit evidence.

Onboarding audit rows, attendance provenance, movement locks, privacy retention and final-settlement dues now remain reliable across the complete employee lifecycle.

The Onboarding page keeps its shared enterprise table mounted during asynchronous loading so returned employee rows render without waiting for content projection to be recreated.

Attendance breaks, inactivity locks, onboarding, Digital IDs, resignation terms and employee documents now enforce their authority at the API boundary and retain reviewable audit evidence.

Offer letters, payroll payments, TA reimbursements, RACI, session controls, attendance and operational KPI actuals now share stronger authority, audit and retry guarantees.

CRM now matches the approved compact hierarchy with six direct daily-work tabs and grouped access to every other destination.

CRM now uses a single icon-led tab workspace across every route, with module administration kept in a permission-gated Settings area at the upper right.

CRM now supports clean contact-to-customer progression, territory-scoped work, historical prospect qualification, compact capture, and the imported Perfex pilot dataset.

Salary advances now post from an approved funding account, recover only from available pay, carry unpaid balances forward, and remain traceable through payroll and employee self-service.

Commercial terms, addresses and payment details are easier to read across sales and purchase documents.

Estimate authors now add itemised and special discounts explicitly, while zero-discount records keep those controls and report fields hidden.

Employees can open a focused salary-advance workspace from their profile, while HR device and inactivity policies now reach already-open sessions safely.

The Sales estimate detail now reloads the selected record on every route change, so itemised and special discounts from a prior estimate cannot remain visible on a zero-discount estimate.

Estimate details now reload the selected record whenever its route changes, preventing commercial columns and totals from a prior estimate from remaining on screen.

Estimate and Proforma outputs hide unapplied discounts, render authored terms cleanly, and present part payments as a complete final audit table.

Pilot TA receipts now resolve against one valid public origin even when the configured browser allowlist contains several comma-separated URLs.

Employment Documents keeps its heading and guidance readable at phone widths while actions wrap into their own row.

Historical probation metadata can prepare a confirmation draft while a missing canonical Employment History event remains visibly blocked for independent resolution.

HR can reconstruct, approve, issue and acknowledge appointment letters, probation confirmations and professional-service agreements with controlled numbers and immutable issued records.

All report ribbons are removed. Status appears as plain document metadata, and branding previews open at the top with accurate page sizing.

Commercial documents follow the approved report skeletons with printable corner ribbons, consistent branding, safe continuation pages, and a responsive preview. Party Directory and Customer 360 now expose onboarding email actions.

HR can issue controlled disciplinary and recognition documents, employees can see proposal-only KPI evidence on Home, and customer reports show discount columns only when positive persisted discount money exists.

Branding now renders the selected commercial report skeleton in the dedicated right preview pane, at a usable scale and with the same header, discount, transaction, payment and footer structure as generated PDFs.

New-hire probation, confidential offer delivery, structured employee designations and performance evidence now share enforceable source and approval controls without inventing production scores.

Commercial PDFs now follow the approved estimate, proforma, sales-order and delivery-challan structures, with governed branding, color or monochrome output, conditional discount evidence and safe multipage pagination.

Estimate discounts now appear only when backed by positive persisted money, while HR identity, Digital ID, RACI, multi-establishment policy and employee-lifecycle controls are hardened for the pilot rollout.

The Professional GST Proforma now uses even A4 page margins and keeps the receiving-bank, payment-status and signatory details as the final report block after commercial terms and notes.

The proforma uses a more compact header with source evidence in the document body, and estimate/proforma detail tables show item discount percentages only when at least one line has an applied discount.

Leads can be captured quickly in a centered modal, calendar follow-ups can be completed and rescheduled in place, parties are searchable across connected modules, and commercial reports now follow the approved structures with installation-wide branding and conditional discount evidence.

Large CRM forms now show a clear selected section boundary, controls follow one size and focus contract, record actions open in centered dialogs or full workspaces, and tab and view choices carry relevant icons with accessible selected states.

The guarded pilot import now preserves lead and follow-up ownership for staff who have one verified active employee match by email, phone or exact name, while leaving unresolved identities unassigned for review.

Tab navigation now follows one shared Analytics-style pattern throughout the app, with relevant icons, clearer selected state, keyboard movement and mobile overflow guidance.

The registered Propulsive vehicle now has a guarded, reversible pilot data pack for Parvesh-to-Rajni trip, fuel and maintenance approval testing, including genuine synthetic refill-slip files without changing the vehicle master or odometer.

Fresh Propulsive deployments now create the Haryana salary-policy establishment after verified organization facts are available, allowing the State/UT policy interface to open without inventing registrations, contribution coverage or Aadhaar data.

Organization setup now records legal constitution and planned legal-employer transitions, while governed payroll policy packs can target every Indian State and Union Territory, legal-entity type and establishment context without treating unverified rules as certified. Offer negotiation also supports managerial notice defaults and complete probation-assessment terms.

Application Settings now controls eight approved report-header layouts across compatible reports, with Banner layout C selected by default for Propulsive. Offer terms include a governed information-security and data-breach schedule, and employee attendance history uses a compact month view with monthly insights.

HR can review a branded A4 offer with governed company identity, personal-email status, salary components, notice and increment policy before applying the approved format to other employee documents.

A guarded pilot pack can validate a complete CRM-to-cash flow with linked commercial and finance records while protecting background jobs and enforcing published enterprise receipt formats.

HR can seed truthful employee lifecycle records without treating proprietor drawings as salary, while performance setup repairs only provably stale baseline roll-ups.

HR can rehearse employee entry-to-exit workflows, manage role-specific KRA and KPI plans, and use consistently sized, validated forms without exposing internal server failures.

HR can populate July and August pilot attendance and exercise leave, travel, advance and movement workflows with clearly marked synthetic evidence and a governed cleanup path.

Employees can review their approved role duties and active process ownership, while HR sees a conventional process-by-person RACI matrix.

Paid Leave and Earned Leave have been retired from Propulsive's operating policy, and prior pilot availability is reversed through auditable ledger entries.

Current employee roles can be recorded from the ERP start date without falsely treating the latest designation or manager as the employee's original joining record.

Attendance, leave and shift records now follow the 1 September 2026 operating baseline, with policy corrections retained as auditable ledger adjustments.

Thirteen effective-dated RACI processes now document responsibility and accountability across Propulsive's current HR, customer, finance, purchasing, fleet, IT and operating workflows.

The production-safe performance seed now gives every governed department a measurable, editable plan without inventing achievements or ratings.

HR can classify a training-stipend engagement as Trainee across employee records, JDs, requisitions, postings and employment history.

HR can classify each employee and hiring role against the live L1-L7 Salary Structure ladder while payroll continues to use the employee's effective Salary Revision.

HR can maintain one reusable job description for a role without forcing it into a legacy pay grade. Employee compensation continues to come from each employee's effective salary revision, including professional-service engagements that have no employee grade.

Eligible employees can submit travel allowance bills with owned receipt evidence. Each bill follows reporting-manager review, independent HR approval, and a separate Finance reimbursement record with a payment reference.

Approved attendance punch corrections now recalculate gross time, actual break deductions, personal move-out deductions, net working hours and the configured shortfall status before the corrected record reaches monthly reporting or payroll.

Attendance actions now use full-width cards. Active tea and lunch breaks show live progress against the scheduled allowance, while temporary move-outs show progress from departure to the employee's expected return time on both the attendance card and the locked return screen.

HR can now decide whether an employee may use one, two, or three active devices, choose whether a new login replaces the oldest device or is blocked, and end one or all sessions. Employee activity uses the existing business and security audit trails, with configurable retention, deletion previews and legal holds. The attendance card also reliably applies the 10/40/10 break policy to legacy shifts and locks every permitted device during an active tea or lunch break.

Salary advances now move through request, independent approval, disbursement and payroll recovery. Fleet evidence follows the reporting line, HR can publish versioned RACI ownership, selected employees can use audited inactivity controls, and attendance now locks the ERP during governed tea and lunch breaks while enforcing an eight-hour review policy.

A quotation's tax now splits the way the law expects: CGST and SGST when the site is in your own state, IGST when it is not, decided from the site on the quote and printed as separate lines on the proforma. The total is unchanged either way — only its composition. Elsewhere this release is about a quote telling you what it could not work out: a sliding wardrobe with no track chosen, a panel with no collection, a mechanism your library does not stock now say so on the results screen and on the hardware schedule, instead of quietly leaving the item out of the price.

Your staff can now raise and track support requests from their own profile, and your support team has a full desk to answer them with private notes, replies and resolution history. The Quote Engine gains wardrobes end to end: a unit library, all four door types including sliding, named internal layouts, lofts and their hardware on the schedule. Areas can carry their own charge and discount, optional supply lines come from the catalogue instead of being typed, and printed proposals no longer break a page straight after a heading.

A project is now one quote divided into areas — a kitchen, a study, a bedroom — each included or left out. It prints as a premium proposal the customer can sign, with your standard terms, a bill of quantities cabinet by cabinet, and optional appendices: drawings to scale, a complete hardware schedule and 3D views. Website content for the three sites is now edited, reviewed and released through the CMS.

A B2B cabinetry enquiry is now built from its carcass and shutter definitions and a grouped library of kitchen boxes, priced at the quote's channel level and printed as a proforma invoice. Each box can be divided into drawers and doors, given a handle, fitted from the hardware library, and seen in 3D.

HR can now invite a new joinee with just their personal email address; the joinee enters their own name and details through the secure link, and HR completes employment setup after approving them. Customer and supplier onboarding keeps approved records stable, stores uploaded evidence privately, applies stricter review controls, and supports refunds to the original payment method and recorded bank exceptions.

Customers, suppliers and software subscribers can now be invited to a secure onboarding page to confirm their company details, contacts, bank account and documents, and one organization can be a supplier, a customer and a subscriber under a single verified record. HR gets the same kind of secure page for new joiners and for existing employees whose records need completing. In both cases the person confirms their email with a one-time code, and nothing they enter reaches your records until someone on your team approves it.

A cabinet placed on a Quote Engine room plan can now use a technical definition, so its panels are calculated at the size it is actually built and the same panels reach the price, the cut list, the drawings and the SVG, DXF and PDF exports. This release also carries the owner's construction decisions for corner, drawer and top panels, and fixes a set of planning problems found while working through complete kitchen and wardrobe quotes.

Forms that hold a list of rows, such as document lines, addresses, discount tiers, salary slabs and workflow transitions, now keep every edit with the row it was made in. Before this release, an edit could be dropped without any message when you saved: after switching to another record while the form was still open, after removing a row from the middle of a list, or after moving a row up or down.

The process band on every module now follows the approved design: completed stages are a pale tint of the brand colour with a check, the current stage is filled, and upcoming stages are plain tiles with an empty circle. Module Process Flow pages show bold, clearly separated stages instead of a thin strip. On an opportunity, stages carry their real names, the band ends in a single Won / Lost stage, stages ahead are shown as upcoming, and a stage the opportunity actually moved on from shows as completed with the date it did.

Every module now has a Process Flow page that explains how its work moves from stage to stage, and an opportunity shows how far its own work has actually progressed, built from the quotations, orders, projects, surveys, deliveries and invoices saved against it rather than from its pipeline stage alone. Projects can start from ten reviewed milestone templates, with a preview of the plan against working days and holidays before anything is created. Customers now carry an explicit GST registration declaration and an individual or business identity, instead of both being guessed from whether a GSTIN happens to be recorded.

The Digital Employee ID has had a card design, a printable PDF, a scannable code and a public verification page for some time — and no way to issue one, so every employee's Workspace read "No Digital ID has been issued for you yet — ask HR to issue one" and HR had nowhere to do it. HR can now issue, reissue, suspend, reinstate and revoke a Digital ID from an employee's record, which makes the rest of it reachable for the first time. Alongside that: three of the four attendance card formats on Home carried no identity at all, and choosing a format did nothing until the page was reloaded; the calendar and the organization chart stopped short of the space they were given; and the Lead and Opportunity forms now follow the same sectioned pattern as the Employee form.

Opportunities opens on the board view, and a card on that board offered only an edit pencil — so clicking an opportunity opened the edit form, and the opportunity’s own page was reachable only from the table view, and only if you knew to switch first. The card title is now a link, so the record opens from the view that actually opens. Alongside that, three things on the record page that were visibly wrong have been corrected: the progress stages had a grey groove between them instead of meeting cleanly, the pipeline drew a dangling branch for “Lost” that the approved design does not have, and the GST panel was overlapping its own text inside the narrow side column.

The opportunity screen has been taken through the approved design one element at a time rather than in outline. It now opens with a single heading naming the record, its customer and its reference — “OPP-0142 · Asha Mehta — Kitchen renovation” — over the line of context the design shows, instead of two competing titles. Its fields sit in two labelled columns, each value in its own box, as drawn. Activity is a dated table with the person who logged each entry. The GST check sits inside the readiness card where the design puts it, rather than beside it, and the next agreed action carries the page’s one filled button.

The opportunity record page kept three of its four sections behind tabs, so opening an opportunity showed you a quarter of it — and the part it hid worst was the activity history, which sat out of sight of the readiness check a few inches away that grades whether the record has any activity at all. The page is now a single column of cards you scroll, in the order the approved design shows: the opportunity’s own details, the site surveys raised against it, then its activity. The Process Flow page has been brought to the same chrome, with the process picker where the design puts it.

Two things the owner asked for after looking at the running system. The application had been calling the same record a “deal” in some places and an “opportunity” in others, sometimes on the same screen — the record page was headed “Opportunity details” under a breadcrumb reading “Deals”. It is now called an opportunity everywhere a person can read it. Separately, thirty screens — every module overview, dashboard and command centre — carried a strip of process stages above their figures. That strip describes a process rather than reporting on any particular record, so it was grey on every one of them, and it has been taken off. It remains where it means something: on a record, showing that record’s progress, and on the module’s own Process Flow page.

Quote Engine was drawing its icons from a different icon set than the rest of the product — different shapes and weights on every button, list row and panel, on every screen. Beside it in the same menu sat the older commercial quotation screens, which were on the correct set, so the newer workspace was the one that looked out of place. Every Quote Engine icon now comes from the same set as the rest of the application. The menu has also been reduced to the Quote Engine itself: the older commercial quotation and commercial masters screens no longer appear in it.

Opening an opportunity from the deals list showed a progress band, a readiness checklist and a set of tabs, and nowhere on the screen did it say who the opportunity was for. The list row beside it showed the company and the contact; the record page showed neither. The cause was in the API: the list query asked for those names and the single-record query did not, so the page was sent two identifiers and had nothing to display. With the names arriving, the page now leads with an Opportunity details card carrying the record’s own facts, and the next agreed action moves to the side panel where it sits beside the check that grades it.

The Quote Engine’s own screens — its Command Center, quote list, calculation coverage and quote progress board — were missing the process band that every other module carries at the top of its landing and list screens, and their summary figures were plain unclickable panels. Opening Quote Engine therefore looked like arriving in an older, separate product, whatever the screens further in looked like. The band is now there, and each figure on the Command Center is a real card: it says what the number means and where it came from, and clicking it opens the records behind it.

Twelve modules had a record screen — the page showing one support case, one work order, one purchase order, one asset — and nothing in the application linked to any of them. They were built and they worked; there was simply no way to open one. The only process flow anyone could reach was the module guide page, which explains a process rather than tracking a record, so every stage there reads as not yet started and the whole band is deliberately grey. That is why the flow looked colourless: not a broken palette, but the correct rendering of the only page that could be opened. Each list now opens its record from the identifier in the row.

The CAD planning and drawing screens that arrived in 1.5.0 worked, but they were laid out like a standard record page — a heading, a row of summary tiles, then stacked notices — rather than like the drawing workspace they were designed as. This rebuilds them on the layout the design review approved: the quote’s name and status at the top with its key facts on one line, the process band beneath it, a row of sections, and then a single framed workspace holding the list of views, the drawing itself with its own toolbar, and a properties panel beside it. Nothing about the drawings, the calculation or the exports changed — only where things sit and how the screen reads.

The corporate site’s homepage lived in the website source, so changing a headline meant a developer and a rebuild. This release moves that page into the CMS: the homepage is imported as a governed draft, edited and published through the normal page workflow, and the website reads it from the published feed. Publishing a page still does not make a hidden site readable — the public feed checks that the site itself is published, not just the page.

The Quote Engine could price a kitchen but never place one. It calculated parts — a width, a height, a thickness and a quantity — with nothing to record which drawer sat in which cabinet or how high a shelf landed, so no drawing could be derived from a quote and the two were kept in step by hand. This release adds a planning workspace where cabinets and wardrobe bays are placed against measured walls, and produces the plans, elevations and sections from the same saved calculation the quote is issued from — so a drawing cannot describe a different kitchen from the one being priced. Alongside it: the HR onboarding flow, process-flow status on 22 of 23 modules, and several dropdowns that were being clipped by the panels they sat in.

The calendar that arrived in 1.3.0 showed the right work in the wrong shape: everything sat at the top of its hour, a fifteen-minute call and a three-hour installation drew the same block, two meetings in one hour covered each other up, and the panel beside the grid was usually empty. This rebuilds the workspace around a continuous time grid where an event sits at the minute it starts and is as tall as it actually lasts. There is a Day view, a small month navigator for jumping around, a list of your calendars you can switch on and off, and event details that open where you clicked instead of in a permanent side panel. Times are now shown in your organisation's timezone throughout — the toolbar said one thing and the grid did another.