## Latest verified source — Checkpoint473 (2026-11-15)

**153/164 DONE (93.3%)**,3 PARTIAL,1 MISSING,7 BLOCKED. Actual scouting run/source controls accepted12native+2live; backend371/frontend120 pass. Three tenant lifecycle stories remain for95.1%. Published release93 passed: public manual/demo93.3%, bridge49 installed, real sign-in15API probes200; backup and rollback images retained. See [Checkpoint473](build-engine/CHECKPOINT_473.md).

## Latest verified source — Checkpoint472 (2026-11-14)

**152/164 DONE (92.7%)**,3 PARTIAL,2 MISSING,7 BLOCKED. Finance-reviewed closeout accepted24native+2live; contact layout revalidated17native+2live. Backend366/366 and frontend120/120 pass. Four more stories remain for95.1%. Published release92 passed: public manual/demo92.7%, bridge48 installed,14 authenticated API probes200; backup/rollback retained. See [Checkpoint472](build-engine/CHECKPOINT_472.md).

## Latest verified source — Checkpoint471 (2026-11-14)

**151/164 DONE (92.1%)**,4 PARTIAL,2 MISSING,7 BLOCKED. BE-030 human-contact/consent accepted with17native+2live checks; backend364/364 passes. Five further stories remain for95.1%. Public manual/runtime remains90.2% pending release. See [Checkpoint471](build-engine/CHECKPOINT_471.md).

## Latest verified source — Checkpoint470 (2026-11-14)

**150/164 DONE (91.5%)**,4 PARTIAL,2 MISSING,8 BLOCKED. BE-076 stock prevention and BE-126 PDF/DXF preview are accepted; six further stories remain for95.1%. Public manual/runtime remains90.2% pending verified release. See [Checkpoint470](build-engine/CHECKPOINT_470.md) for evidence and limits.

## Current milestone — Checkpoint 469 (2026-11-12)

Verified source **148/164 DONE (90.2%)**,4 PARTIAL,2 MISSING,10 BLOCKED. Backend355/355 and frontend120/120 pass. Full story-specific native/live acceptance, skip reasons and practical limits are recorded in [Checkpoint469](build-engine/CHECKPOINT_469.md). Eight accepted stories since85.4%: BE-013/046/121/032/113/072/080/160. Release90 and PUBLIC_MANUAL_PROGRESS_LATEST passed: the public manual main card/story-progress chapter and demo show90.2% (148/164). Real authenticated login and11 affected APIs return200. Verified backup and rollback images retained.

## Checkpoint 465 — 75% acceptance coverage (2026-11-07)

**123/164 DONE (75.0%), 29 PARTIAL, 2 MISSING, 10 BLOCKED.** BE-011/035/133/138/139/147 now meet their supplied criteria through React, authenticated BFF routes and authoritative Odoo operations. Workflow native 9/9, broader native regression 22/22 and live bilingual browser 2/2; CRM native 16/16 and live bilingual browser 3/3; timesheet native 3/3 plus date-filter checks and live Arabic workbook 1/1. Backend 340/340 and React 117/117 pass. See [Checkpoint 465](build-engine/CHECKPOINT_465.md) and [traceability](REQUIREMENTS_TRACEABILITY.md). Source acceptance was isolated; local rollout evidence is separate. Remaining module-wide parity, production policies and model accuracy are explicitly outside these verified slices.

## Checkpoint 463 — BE-038 isolated live acceptance (2026-11-06)

- Current-source Odoo native AI suite: **18/18 passed**. Authenticated React→BFF→Odoo browser journey: **1/1 passed**. Graph regression suite: **5/5 passed**; backend full unit suite: **335/335 passed**; React full unit suite: **117/117 passed**; mocked receipt browser test: **1/1 passed**.
- Exact Odoo audit run UUID matched each BFF approve/reject run. Reopened receipt, foreign customer denial, no-send/stage, no-write rejection, draft-only approval, role/company isolation, unchanged CRM/mail and audit immutability all verified. Temporary resources were removed; source unchanged.
- BE-038 is DONE. Totals: **117 DONE (71.3%), 35 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. Six more verified stories remain for 75%. See [Checkpoint 463](build-engine/CHECKPOINT_463.md) and [evidence](build-engine/evidence/BE-038_LIVE_ACCEPTANCE_FOLLOWUP_20261106.json).

## Checkpoint 462 — BE-150 live workflow QA (2026-11-06)

- Focused native current-source tests: **2/2 passed**. Authenticated React→BFF→Odoo browser cases: **2/2 passed**.
- Verified authorized draft generation, estimator edit, save/reopen provenance and actor/time/project/company readback; invalid input, same-company reader and foreign project were denied without writes/disclosure.
- Deterministic model/drawing fixtures verify the workflow boundary only, not takeoff accuracy. BE-150 remains PARTIAL; story counts do not change. Clone/services/image/backup were removed; source database unchanged. See [Checkpoint 462](build-engine/CHECKPOINT_462.md) and [QA evidence](build-engine/evidence/BE-150_AI_BOQ_LIVE_QA.json).

## Checkpoint 461 — BE-038 audit receipt and run correlation fix (2026-11-06)

- Backend full unit suite: **335/335 passed**. The previously inconsistent BOQ-import test now correctly asserts that an unauthenticated commit makes no additional Odoo call after preview.
- LangGraph approval regression: **5/5 passed**, including exact BFF `run_id` preservation through approval resume and Odoo audit receipt retention. React unit suite: **117/117 passed**; production build passed with the existing large-chunk advisory. Mocked AI review receipt browser test: **1/1 passed**, including all visible audit fields. The screenshot is labelled synthetic in the offline manual.
- BE-038 live follow-up is still required for the new React receipt and exact UUID readback. Story stays PARTIAL; overall counts stay **116 DONE (70.7%), 36 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. See [Checkpoint 461](build-engine/CHECKPOINT_461.md).

## Checkpoint 460 — BE-038 native pass; live Sales login blocked (2026-11-06)

- Current-source Odoo `be_ai:TestBeAi`: **18/18 passed** on a disposable clone with HTTP disabled.
- Live browser run stopped at synthetic Sales sign-in: Access Denied before an AI run or business action. A retry stopped before auth preflight when Odoo shell could not initialize the clone registry; no fixture users were created in that attempt. No live guardrail/role/company result is claimed; BE-038 remains PARTIAL.
- Clone, UUID agent DB, temporary containers/processes/ports and raw browser artifacts were removed. Source DB/shared Odoo configuration were unchanged.
- Totals unchanged: **116 DONE / 164 (70.7%)**, 36 PARTIAL, 2 MISSING, 10 BLOCKED. Seven verified stories remain for 75%.
- See [Checkpoint 460](build-engine/CHECKPOINT_460.md) and [attempt evidence](build-engine/evidence/BE-038_LIVE_ACCEPTANCE_ATTEMPT_20261106.json).

## Checkpoint 459 — BE-004 company identity acceptance (2026-11-06)

- Native current-source suite: **4/4 passed**. Authenticated React→BFF→Odoo live browser tests: **2/2 passed**.
- Owner branding save/reopen, authoritative identity actor/time, quotation letterhead/footer, field validation with no partial write, Sales write denial, and foreign-company isolation were verified on a disposable clone.
- The clone was dropped and shared `namaa_ksa` was unchanged. Auxiliary post-run shell readback is recorded INCOMPLETE due to a missing import; the live identity and native template assertions passed before that diagnostic error.
- BE-004 is DONE. Story totals: **116 DONE / 164 (70.7%)**, 36 PARTIAL, 2 MISSING, 10 BLOCKED. Seven additional verified stories remain for 75%.
- See [Checkpoint 459](build-engine/CHECKPOINT_459.md) and [QA evidence](build-engine/evidence/BE-004_IDENTITY_LIVE_QA.json).

## Checkpoint 458 — Arabic React copy and timesheet export (2026-11-06)

- React full unit suite: **116/116 passed**; focused language/localization: **11/11 passed**; production frontend build passed.
- Backend timesheet-export route test: **1/1 passed** in the backend container using a temporary test copy; the copy was removed. React timesheet export URL tests: **2/2 passed**.
- Export filters within the Odoo reader before the row limit; matches over 200 return 422. Arabic RTL workbook, formula-safe text, and omission of cost/rate data are covered.
- Native Odoo date-filter regression and authenticated live role/company export acceptance were not run. BE-147 remains PARTIAL; story totals unchanged at **115 DONE / 164 (70.1%)**.
- See [Checkpoint 458](build-engine/CHECKPOINT_458.md).

## Checkpoint 457 — BE-038 AI guardrail current-source recheck (2026-11-06)

- Full isolated current-source Odoo `be_ai:TestBeAi`: **18/18 passed** after correcting a test fixture to give its runtime user an accessible same-company lead. Clone was dropped; source DB unchanged.
- Sales-specific native lifecycle tests: draft-only approval, immutable rationale events, rejected request creates no quote, no email/stage change, foreign-company denial.
- Existing graph guards **5/5**, mocked authenticated API boundary **1/1**, synthetic React browser review flows **2/2** passed. These groups are not summed.
- Authenticated live React→BFF→Odoo acceptance did not run: a temporary orchestrator failed syntax validation before clone/service creation. BE-038 remains PARTIAL. Overall story counts remain **115 DONE (70.1%), 37 PARTIAL, 2 MISSING, 10 BLOCKED**.
- See [Checkpoint 457](build-engine/CHECKPOINT_457.md) and [QA record](build-engine/evidence/BE-038_SALES_AI_GUARDRAILS_QA.json).

## Checkpoint 456 — React guide, language and Western digit checks (2026-11-06)

- React unit suite **113/113 passed**, including source-wide rejection of Arabic-Indic/Persian numeral glyphs, Arabic timestamp Western-digit formatting, and bilingual source checks.
- Focused guide browser journeys **3/3 passed** in English, Arabic, and Arabic 390px phone layout; onboarding Arabic preview **1/1 passed**. Five audited Arabic error paths now use localized fallbacks.
- Production build passed. The refreshed bundle is deployed locally and through the public React ngrok endpoint; both return HTTP 200. Complete screen-by-screen professional translation review remains open.
- No story status changed: **115 DONE / 164 (70.1%)**, 37 PARTIAL, 2 MISSING, 10 BLOCKED. Professional translation review across all screens remains in progress.

## Checkpoint 455 — React bilingual guide and language cleanup (2026-11-06)

- React unit suite **107/107 passed**; traceability-generated manual index contains all 164 unique story IDs across DONE/PARTIAL/MISSING/BLOCKED.
- Focused Playwright manual journeys **2/2 passed** in English and Arabic: navigation, story count, localized Arabic title, bilingual search, Accounting route/how-to, and DONE status filtering. Arabic 390px navigation/overflow check **1/1 passed**. Arabic onboarding preview **1/1 passed** for localized synthetic company/checklist/actor/project content.
- Production build passed. Local frontend container serves the refreshed bundle at HTTP 200. `git diff --check` passed.
- The public URL initially returned `ERR_NGROK_3200`; a separate React ngrok session was started alongside the existing UAT tunnel. Public HTTP check now returns 200 and the deployed bundle contains the bilingual guide.
- No story status changed; totals remain **115 DONE / 164 (70.1%)**.

## Checkpoint 449 — BE-090 attendance review (2026-11-05)

- Native Odoo **4/4**, backend/API **3/3** plus 9 validation subtests, React Playwright **3/3**, production build passed. Disposable clone/filestore removed; source DB unchanged.
- Five supplied criteria verified: authoritative submit/review, invalid/no-partial, actor/time/project/company readback, unauthorized/foreign denial and immutable approval/rejection with no early state change.
- Totals: **115 DONE / 164 (70.1%)**; 8 more verified stories to reach 75%. Evidence: [QA](build-engine/evidence/BE-090_ATTENDANCE_REVIEW_QA_20261105.json), [checkpoint](build-engine/CHECKPOINT_449.md).

## Checkpoint 454 — BE-057 BOQ cost/quantity comparison (2026-11-05)

- Comparison helper **2/2**, mocked React BOQ journey **1/1**, production build passed. No native Odoo changes or database writes.
- Story remains PARTIAL for stock/site reconciliation, role/company acceptance and DEC-18. Counts unchanged at **115 DONE / 164 (70.1%)**.
- Evidence: [QA](build-engine/evidence/BE-057_BOQ_CONSUMPTION_COST_COMPARISON_QA.json), [checkpoint](build-engine/CHECKPOINT_454.md).

## Checkpoint 453 — BE-140 offline-ready snapshot (2026-11-05)

- PWA production build passed; offline E2E **3/3** passed for authenticated snapshot, offline read, atomic failed-refresh preservation and credential isolation.
- Mocked platform pull; no live Odoo/assignment acceptance and no database changes. BE-140 remains PARTIAL.
- Counts unchanged at **115 DONE / 164 (70.1%)**. Evidence: [QA](build-engine/evidence/BE-140_OFFLINE_PACKAGE_QA_20261105.json), [checkpoint](build-engine/CHECKPOINT_453.md).

## Checkpoint 452 — BE-063 landed-price comparison (2026-11-05)

- Comparison helper **3/3**, backend document route **1/1**, live React→BFF→Odoo comparison **1/1**, production build passed.
- Current-source native role/document test passed 1/1 after correcting a Python datetime assertion; clone removed.
- BE-063 remains PARTIAL; totals unchanged at **115 DONE / 164 (70.1%)**. Evidence: [QA](build-engine/evidence/BE-063_REACT_LANDED_COMPARISON_QA.json), [checkpoint](build-engine/CHECKPOINT_452.md).

## Checkpoint 451 — BE-113 offline conflict resolution (2026-11-05)

- Queue unit **4/4**, mocked React conflict/reconnect **2/2**, BFF route **1/1**, production build passed. No native code/database changed; prior native/live evidence is referenced in the QA artifact.
- BE-113 remains PARTIAL: offline auth/device/retention and live verification of both conflict choices remain. Counts unchanged at **115 DONE / 164 (70.1%)**.
- Evidence: [QA](build-engine/evidence/BE-113_OFFLINE_CONFLICT_QA_20261105.json), [checkpoint](build-engine/CHECKPOINT_451.md).

## Checkpoint 450 — BE-147 purchase receipt Excel export increment (2026-11-05)

- Native Odoo receipt role/company matrix **1/1**, backend/API **1/1**, mocked React download **1/1**, and live React→BFF→Odoo workbook download **1/1** passed. The downloaded workbook was reopened and matched the seeded Odoo receipt/supplier/product/quantity.
- Disposable DB, BFF/image and workbook removed. BE-147 remains PARTIAL because other operational registers and full per-source role/company acceptance remain. Read-only downloads do not create a record to reopen.
- Evidence: [Checkpoint 450](build-engine/CHECKPOINT_450.md), [API/React QA](build-engine/evidence/BE-147_PURCHASE_RECEIPTS_EXPORT_QA.json), [live QA](build-engine/evidence/BE-147_PURCHASE_RECEIPTS_EXPORT_LIVE_QA.json).

## Checkpoint 448 — BE-088 staff onboarding/offboarding (2026-11-05)

- Native Odoo **7/7**, backend/API **4/4**, React Playwright **1/1**, production build passed. Clone DB and filestore removed; source DB unchanged.
- Four supplied criteria verified: authoritative lifecycle changes, invalid/no-partial, audit/reopen, HR/company boundary. Browser API is mocked.
- Totals: **114 DONE / 164 (69.5%)**; 9 more verified stories to reach 75%. Evidence: [QA](build-engine/evidence/BE-088_EMPLOYEE_OFFBOARDING_QA.json), [checkpoint](build-engine/CHECKPOINT_448.md).

## Checkpoint 447 — BE-147 purchasing receipt Excel export (2026-11-05)

- Added authenticated, filter-aware React Excel export for Odoo purchase receipts, with Arabic RTL headers, formula-safe text, and read-only semantics.
- Backend/API test **1/1** and React download test **1/1** passed. Native role-matrix test did not reach ACL assertions because its purchase-order fixture lacks the required independent Owner approval; disposable clone removed.
- BE-147 remains PARTIAL. Other register exports and broader native role/company acceptance remain. Evidence: [checkpoint](build-engine/CHECKPOINT_447.md), [QA](build-engine/evidence/BE-147_PURCHASE_RECEIPTS_EXPORT_QA.json).

## Checkpoint 446 — BE-087 employee records and assignments (2026-11-05)

- Native Odoo **4/4**, backend/API **3/3**, React Playwright **1/1**, production build passed. Clone DB and filestore removed; source DB unchanged.
- Four supplied criteria verified: native persistence, invalid/no-write, audit/readback, HR/company boundary. Browser API is mocked.
- Totals: **113 DONE / 164 (68.9%)**; 10 more verified stories to reach 75%. Evidence: [QA](build-engine/evidence/BE-087_EMPLOYEE_PROJECT_ASSIGNMENTS_QA.json), [checkpoint](build-engine/CHECKPOINT_446.md).

## Checkpoint 446 — BE-087 employee records and assignments (2026-11-05)

- Native Odoo **4/4**, backend/API **3/3**, React Playwright **1/1**, production build passed. Clone DB and filestore removed; source DB unchanged.
- Four supplied criteria verified: native persistence, invalid/no-write, audit/readback, HR/company boundary. Browser API is mocked.
- Totals: **113 DONE / 164 (68.9%)**; 10 more verified stories to reach 75%. Evidence: [QA](build-engine/evidence/BE-087_EMPLOYEE_PROJECT_ASSIGNMENTS_QA.json), [checkpoint](build-engine/CHECKPOINT_446.md).

## Checkpoint 445 — BE-052 AI BOQ draft (2026-11-05)

- Current-source native Odoo tests **2/2**, backend AI/schema/API/security **11/11** (8 subtests), React Playwright review/save/reopen **1/1**.
- Disposable Odoo clones were removed; source databases unchanged. Browser journey uses deterministic synthetic model/API fixtures.
- All five supplied criteria verified. QS accuracy evaluation and live local-model/role integration remain follow-up, outside supplied criteria. Evidence: [QA](build-engine/evidence/BE-052_AI_BOQ_DRAFT_QA.json), [checkpoint](build-engine/CHECKPOINT_445.md).
- Totals: **112 DONE / 164 (68.3%)**; 11 more verified stories to reach 75%.

## Checkpoint 444 — BE-003 company mandate (2026-11-05)
- Current-source native mandate/lead tests: **2/2 passed** on disposable clone.
- Backend HTTP 422 field-error/no-call test: **1/1 passed**. Live React→BFF→Odoo Owner journey: **1/1 passed**. Mocked React journey: **1/1 passed**.
- Four supplied AC verified: persisted company settings and lead codes, invalid/no-write, actor/time/company reopen, and Owner/foreign-company authorization. All disposable DB/services removed. Evidence: [QA](build-engine/evidence/BE-003_OWNER_COMPANY_ACCEPTANCE.json), [checkpoint](build-engine/CHECKPOINT_444.md).
- Totals: **111 DONE / 164 (67.7%)**; 12 more verified stories to reach 75%. Benchmark/feed integrations remain separate extensions.

## Previous — Checkpoint 443 — BE-127 drawing revision links (2026-11-05)
- Current-source native Odoo drawing/correspondence suite: **39/39 passed** on disposable clone after clone-only dependency upgrade; clone dropped.
- Backend APIs: **4/4 passed**. React drawing journeys: **2/2**; submittal drawing-link/readback: **1/1**. Production build passed.
- Four supplied criteria verified: task/submittal revision links, validation/no-partial-write, actor/time/project/company readback, and cross-company/role denials. Browser APIs are mocked. Evidence: [QA](build-engine/evidence/BE-127_DRAWING_SUBMITTAL_LINK_QA.json), [checkpoint](build-engine/CHECKPOINT_443.md).
- Totals: **110 DONE / 164 (67.1%)**; 13 more verified stories to reach 75%.

## Previous — Checkpoint 442 — BE-036 approved proposal PDF archive (2026-11-05)
- Current-source native Odoo archive/approval suite: **11/11 passed** after clone-only schema upgrades; clone dropped.
- Focused API tests: **3/3 passed**. React internal review/archive journey: **1/1 passed** (synthetic API fixtures). Direct ORM QA generated/reopened a real `%PDF-` QWeb output and verified private immutable checksum-backed attachment.
- All five supplied criteria verified, including approval gate, invalid/stale no-record, role/company denial and audit readback. Evidence: [QA](build-engine/evidence/BE-036_TECHNICAL_PROPOSAL_ARCHIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_442.md).
- Totals: **109 DONE / 164 (66.5%)**; 14 more verified stories to reach 75%. Customer release remains separate under DEC-26.

## Previous — Checkpoint 441 — BE-125 drawing upload/version (2026-11-05)
- Current-source native Odoo drawing/file-policy/project-ACL suite: **12 selected tests passed** on disposable clone; DB and filestore dropped.
- Backend tests: **4/4 passed**. React upload/revision browser flows: **2/2 passed** (mock API). Production build, Python compile, JSON and diff checks passed.
- Four supplied criteria verified: authorized upload/version, invalid file no-partial-write, actor/time/project/company readback, and unauthorized/foreign-scope denial. Evidence: [QA](build-engine/evidence/BE-125_DRAWING_UPLOAD_VERSION_QA.json), [checkpoint](build-engine/CHECKPOINT_441.md).
- Totals: **108 DONE / 164 (65.9%)**; 15 more verified stories to reach 75%. Preview conversion/licensing remains in BE-126.

## Previous — Checkpoint 440 — BE-078 milestone customer invoice (2026-11-05)
- Current-source native Odoo progress-billing approval/invoice tests: **7/7 passed** on a disposable clone, dropped afterward.
- Focused BFF validation/ACL test: **1/1 passed**. React Owner approve/reject/reopen + accountant draft-invoice flow: **1/1 passed** (mock endpoints). Production build passed.
- Five criteria verified, including immutable Owner rationale, no self-approval, invoice blocked before approval, rejection creates no invoice, and draft-only accountant invoice after approval. A live browser retry stopped at sign-in/configuration before any write. Evidence: [QA](build-engine/evidence/BE-078_MILESTONE_REVIEW_QA_20261105.json), [checkpoint](build-engine/CHECKPOINT_440.md).
- Totals: **107 DONE / 164 (65.2%)**; 16 more verified stories to reach 75%. Retention/advance and accountant UAT remain rollout work.

## Previous — Checkpoint 439 — BE-123 ticket resolution evidence (2026-11-05)
- Current-source native Odoo tests: **2/2 passed** on a disposable clone; database and filestore dropped.
- Backend API tests: **2/2 passed**. React resolution evidence/reopen journey: **1/1 passed** (mocked endpoints). Production build, Python compile and diff check passed.
- All four criteria verified, including immutable evidence, atomic native Done transition, invalid-file rollback and role/company access denial. Evidence: [QA artifact](build-engine/evidence/BE-123_TICKET_RESOLUTION_EVIDENCE_QA.json), [checkpoint](build-engine/CHECKPOINT_439.md).
- Totals: **106 DONE / 164 (64.6%)**; 17 more verified stories to reach 75%.

## Previous — Checkpoint 438 — BE-156 AI suggestion feedback (2026-11-05)
- Current-source native Odoo feedback/immutability/access test: **1/1 passed** on a disposable clone, dropped after run.
- Focused API validation test: **1/1 passed**. React edit → approve → reopen journey: **1/1 passed** (mocked BFF). Production build, Python compile and diff check passed.
- Five supplied criteria verified, including rationale audit and unchanged official state/target. Evidence: [QA artifact](build-engine/evidence/BE-156_AI_SUGGESTION_FEEDBACK_QA.json), [checkpoint](build-engine/CHECKPOINT_438.md).
- Totals: **105 DONE / 164 (64.0%)**; 18 more verified stories to reach 75%.

## Previous — Checkpoint 437 — BE-120 internal defect/blocked-task tickets (2026-11-05)
- Current-source native OCA Helpdesk role/company tests on disposable clone: **2/2 passed**; clone dropped and shared DB unchanged.
- BFF/API test: **1/1 passed**. React internal ticket create/list/reopen journey: **1/1 passed** (mock endpoints). Production build, Python compile and diff check passed.
- Four supplied criteria verified: persistence/readback, invalid-input no-create, actor/time/company/project, and unauthorized/foreign-company denial. OCA Helpdesk was not installed on shared demo database. Evidence: [QA artifact](build-engine/evidence/BE-120_INTERNAL_HELPDESK_QA.json), [checkpoint](build-engine/CHECKPOINT_437.md).
- Totals: **104 DONE / 164 (63.4%)**; 19 more verified stories to reach 75%. Client portal/resolution/SLA are separate remaining stories.

## Previous — Checkpoint 436 — BE-007 language and timezone preferences (2026-11-05)
- Current-source Odoo user-profile test on disposable DB: **1/1 passed**; the clone was dropped.
- Focused API/session validation test: **1/1 passed**. React save → fresh sign-in → reopen and timezone-rendering journey: **1/1 passed** (mocked API). Production build, Python compile and diff check passed.
- Four supplied criteria verified, including session-bound user ID, invalid-input no-call, audit/company readback and another-user write denial. Evidence: [QA artifact](build-engine/evidence/BE-007-USER-PREFERENCES-QA-20261105.json), [checkpoint](build-engine/CHECKPOINT_436.md).
- Totals: **103 DONE / 164 (62.8%)**; 20 more verified stories to reach 75%.

## Previous — Checkpoint 435 — BE-065 approval before purchase commitment (2026-11-05)
- Current-source focused native Odoo lifecycle/security tests: **2 passed**, with no failures/errors; both temporary databases dropped.
- FastAPI route validation/ACL test: **1 passed**. React request → independent Owner approval → close/reopen history journey: **1 passed** (mocked API roles). Production build, Python compile and diff check passed.
- Five supplied acceptance criteria mapped, including no confirmation without approval, append-only decision rationale, rejected RFQ remains draft, and changed order invalidates approval. Evidence: [QA artifact](build-engine/evidence/BE-065_PURCHASE_COMMITMENT_QA.json), [checkpoint](build-engine/CHECKPOINT_435.md).
- The wider `be_supplier` suite has one unrelated fixture error because `res.company.namaa_supplier_list` is absent; focused BE-065 tests pass. Totals: **102 DONE / 164 (62.2%)**; 21 more verified stories to reach 75%.

## Previous — Checkpoint 434 — BE-033 tenant logo and letterhead (2026-11-05)
- Current-source native Odoo role/company/validation tests on disposable clone: **3/3 passed**; clone dropped, source unchanged.
- Backend API tests: **2/2 passed**. React branding browser journey: **1/1 passed** (mock API). Production build passed with the existing large-chunk warning.
- Branding identity values, actor/timestamp, stale revision, invalid input/no-write, Sales write denial, and foreign-company read denial were verified. No PDF was visually rendered. Evidence: [QA artifact](build-engine/evidence/BE-033_IDENTITY_BRANDING_QA.json), [checkpoint](build-engine/CHECKPOINT_434.md).
- Totals: **101 DONE / 164 (61.6%)**; 22 more verified stories to reach 75%.

## Previous — Checkpoint 433 — BE-077 project analytic cost-center assignment (2026-11-05)
- Current-source native Odoo test on a disposable clone: **1/1 passed**, including persisted assignment, invalid ID/no-write, project/company/actor/time, unauthorized reader and foreign-company denial. Clone dropped; source snapshot unchanged.
- Focused BFF field-validation test: **1 passed**. React cost-center browser journey: **1 passed** (mock API; persistence and authorization verified separately in Odoo).
- Python compilation and `git diff --check` passed. Evidence: [QA artifact](build-engine/evidence/BE-077_COST_CENTER_ASSIGNMENT_QA.json), [checkpoint](build-engine/CHECKPOINT_433.md).
- Totals: **100 DONE / 164 (61.0%)**; 23 more verified stories to reach 75%.

## Previous — Checkpoint 432 — BE-084 customer and supplier credit/debit notes (2026-11-05)
- Current-source native Odoo credit/debit note regression: **1 passed** across customer and supplier source documents.
- Authenticated accountant React → BFF → Odoo browser journey: **1 passed** across four note variants; invalid reason and persisted source/company/actor/time were verified.
- Same-company non-accounting reader and foreign-company accountant were denied; retries are native-tested.
- Disposable clone, temporary BFF/proxy/Odoo process and image removed; source database unchanged. Evidence: [QA artifact](build-engine/BE084_ACCOUNTING_NOTES_ACCEPTANCE_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_432.md).
- Totals: **99 DONE / 164 (60.4%)**; 24 more verified stories to reach 75% (123 DONE).

- Current-source native routing, classification, validation and access tests: **3 passed**.
- Authenticated React → BFF → Qwen → Odoo Owner journey: **1 passed**; cited draft, review audit, source/company context and unchanged CRM records verified.
- Disposable QA clone and temporary services removed; source unchanged. Evidence: [QA artifact](build-engine/CRM_SCOUTING_AI_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_430.md).
- Totals: **97 DONE / 164 (59.1%)**; two more verified stories to reach 60%.

- Current-source native duplicate/validation/company regressions: **3 passed**.
- Authenticated React → BFF → Qwen → Odoo review journey: **1 passed**; source citation, reviewer/audit and Odoo readback verified.
- Disposable clone and temporary services removed; `namaa_ksa` unchanged. Evidence: [QA artifact](build-engine/CRM_SCOUTING_AI_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_429.md).
- Totals: **95 DONE / 164 (57.9%)**; four more verified stories to reach 60%.

- Current-source isolated native project-plan/security tests: **3 passed**.
- Authenticated React → BFF → Odoo Gantt drag/resize/role journey: **1 passed**; native readback confirmed task dates, actor/time and company.
- Disposable clone dropped; source unchanged. Evidence: [QA artifact](build-engine/PROJECT_PLAN_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_428.md).
- Totals: **94 DONE / 164 (57.3%)**; five more verified stories to reach 60%.

- Current-source isolated native Odoo tests: **11 passed, 0 failures/errors**.
- Authenticated React → BFF → Qwen 3.8 27B → Odoo browser journey: **1 passed**; persisted draft reopened and business records were unchanged.
- Disposable clone dropped; source unchanged. Evidence: [QA artifact](build-engine/CRM_TECHNICAL_PROPOSAL_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_427.md).
- Totals: **93 DONE / 164 (56.7%)**; six more verified stories to reach 60%.


- Current-source isolated Odoo BOQ and bridge suite: **27 passed, 0 failures/errors**.
- Authenticated React → BFF → Odoo import browser journey: **1/1 passed**.
- Verified valid XLSX persistence and reopen, imported row and audit provenance, validation/no-write for invalid input, same-company reader denial, and foreign-company QS denial.
- Disposable clone dropped; source database unchanged. Evidence: [QA artifact](build-engine/BE050_BOQ_IMPORT_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_426.md).
- Totals: **92 DONE / 164 (56.1%)**; seven more verified stories to reach 60%.

## Checkpoint 425 — BE-054 BOQ baseline approval DONE (2026-11-04)

- Current-source isolated Odoo focused suite: **4/4 passed**, including independent baseline approval, no requester self-approval, foreign-company Owner denial without state change, Odoo audit, and BOQ snapshot locking.
- Authenticated live React → BFF → Odoo browser journey: **1/1 passed**. PM created/submitted the BOQ; a separate Owner approved with rationale; the approved actor/time and state reopened in React. Invalid rationale returned 422.
- Disposable clone and temporary BFF removed. `namaa_ksa` and shared QA source databases were unchanged. See [QA artifact](build-engine/BOQ_BASELINE_OWNER_APPROVAL_LIVE_QA.json) and [Checkpoint 425](build-engine/CHECKPOINT_425.md).

# Verification refresh — Checkpoint 424 (2026-11-04)

- Contract native Odoo/bridge tests: **4/4 passed** on a disposable clone; includes create/reopen audit, duplicate-follower regression, invalid no-write, unauthorized read denial, foreign-project denial, and key-date reminder scheduling.
- Live React → BFF → Odoo contract journey passed: created a project/company-linked contract, reopened its audit fields and critical expiry date, verified native reminder deadline `2027-01-01` for a `2027-01-15` key date, and confirmed invalid create returned 422 without a write.
- Clone and temporary BFF were removed; source database unchanged. See [Checkpoint 424](build-engine/CHECKPOINT_424.md) and [QA JSON](build-engine/CONTRACT_CLAUSE_REVIEW_LIVE_QA.json).

## BE-054 follow-up attempt (2026-11-04) — not accepted

- Current-source disposable clone upgrade passed **4/4** focused native BOQ baseline and security tests after including the purchase addon that owns its schema fields.
- The live React run did not produce a clean acceptance result. Earlier retry reached the Owner approval response but failed on an ambiguous UI locator; latest retry failed before sign-in because the app page was blank. Keep BE-054 **PARTIAL** until React browser startup and full journey pass.
- Every disposable clone and temporary BFF was removed. Shared demo databases were not modified. See [QA artifact](build-engine/BOQ_BASELINE_OWNER_APPROVAL_LIVE_QA.json), [runner](../scripts/run_boq_baseline_live_qa.py), and [current traceability](REQUIREMENTS_TRACEABILITY.md).

# Verification refresh — 2026-11-04

- React workspace Playwright suite: **26/26 passed** (run sequentially to avoid shared Playwright artifact races).
- Offline React/Odoo user manual: **351/351 embedded screenshots decoded**; Arabic and English desktop/mobile layouts have no horizontal overflow; navigation, screenshot search, enlargement and filtering passed.
- Progress demo and manual served locally on port 3200 with HTTP 200; the public ngrok `/demo.html` endpoint also returned HTTP 200.
- Checkpoint 423 current-source live dashboard QA remains green (Owner/company aggregate, PM denial, foreign-company isolation); frontend production build passed in that checkpoint.
- The Checkpoint 423 rechecks themselves changed no story status; Checkpoint 425 subsequently raises the current total to **91 DONE / 164 (55.5%)**.

# Latest — Checkpoint 423: Executive construction portfolio roll-up (2026-11-04)

The Owner dashboard's company-scoped construction portfolio fields passed a current-source Odoo regression **1/1** and authenticated live React → BFF → Odoo owner/PM/foreign-company journey **1/1**. Live totals include the persisted project's planned/actual BOQ costs; PM data is restricted and foreign-company isolation holds. React preview regression **1/1** and production build passed. QA clone and worker removed; source database unchanged. See [Checkpoint 423](build-engine/CHECKPOINT_423.md), [live QA JSON](build-engine/BE162_PROJECT_RISKS_LIVE_QA.json), and [traceability](REQUIREMENTS_TRACEABILITY.md).

# Latest — Checkpoint 418: maintenance planning schema repair (2026-11-03)

Fixed the reported `maintenance_equipment.be_source_receipt_line_id` missing-column error. The live `namaa_ksa` module schema was behind the mounted addon; a verified 0600 backup was created, an isolated clone upgrade passed **27/27 native equipment tests**, then `be_equipment` was upgraded to **20.0.1.0.4** in the demo database. SQL readback confirmed the column. Authenticated React read-only smoke passed: Maintenance planning rendered; `/api/maintenance/options` and `/api/maintenance/plans` returned 200; no page errors or business mutations. Odoo and React are healthy. Story totals remain **82 DONE (50.0%), 70 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. Requested next target: **123 DONE (75.0%)**, 41 more stories. See [Checkpoint 418](build-engine/CHECKPOINT_418.md) and [QA evidence](build-engine/MAINTENANCE_SCHEMA_LIVE_QA.json). A separate quality-template QA rerun was blocked by an orphaned product-tracking reference in the old QA snapshot and a stale `127.0.0.1:18081` runner dependency; both test clones were dropped and no story status changed.

# Latest — Checkpoint 417: live variation acceptance (2026-11-03)

- Authenticated live React → BFF → local Qwen → Odoo journey: **1/1 passed** on a disposable QA clone. The PM created a variation in React and reopened its pending source-cited impact advice; the advice remained non-mutating.
- Independent Owner approval and rejection of separate requests both saved immutable rationale, actor and timestamp. Requester self-approval returned 403; underlength rationale returned 422 with no state change. Direct Odoo readback verified applied BOQ quantity/baseline for approval and no BOQ change for rejection. Same-company reader and foreign-company PM could not list variations or access advisory records.
- Native impact bridge: **4/4**; clean-database native variation lifecycle/approval suite: **21/21**; mocked React contract journey: **1/1**. Python/JavaScript syntax checks passed.
- QA clone and temporary BFF/image removed; source database unchanged. Status: **BE-055 and BE-056 DONE**. Totals: **82/164 DONE (50.0%), 70 PARTIAL, 2 MISSING, 10 BLOCKED**. See [Checkpoint 417](build-engine/CHECKPOINT_417.md) and [QA evidence](build-engine/VARIATION_IMPACT_LIVE_QA.json).

# Latest — Checkpoint 416: BE-099 equipment disposal acceptance (2026-11-03)

- Authenticated React → BFF → Odoo Owner/requester/Finance-only journey: **1/1 passed** on a disposable clone of `namaa_ksa`.
- Owner approval posted the Odoo disposal move, closed the linked accounting asset and archived the equipment. Invalid reason returned 422/no-write; requester self-approval and Finance-only decision returned 403; foreign-company read was denied without disclosure.
- Fresh-session readback showed company, requester/approver, timestamps and disposal move; Arabic RTL review passed; direct Odoo postconditions matched.
- Current-source module-upgrade/native tests were **not run** because a pre-existing dangling `product.mail` tracking reference blocks the module upgrade. No native test pass is claimed. Disposable DB, Odoo runtime, BFF and image removed; `namaa_ksa` unchanged.
- Story totals: **80 DONE (48.8%), 72 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. Two more verified stories reach 50%. See [Checkpoint 416](build-engine/CHECKPOINT_416.md) and [QA evidence](build-engine/EQUIPMENT_RETIREMENT_BE099_LIVE_QA.json).

- Authenticated React → BFF → Odoo lifecycle template journey: **1/1 passed** on a disposable clone. Valid stages/transitions/approvers, publish/version, project-type assignment and readback passed; malformed condition syntax returned 422 without a record.
- PM configuration denial and foreign-company Owner list/version denial passed without disclosing the target template. Native readback confirmed company scope and assignment. Clone and temporary BFF removed; source unchanged.
- Native module upgrade was not run because the isolated snapshot has a pre-existing dangling mail-tracking product reference. BE-044 is DONE against its acceptance criteria. Totals: **79/164 DONE (48.2%), 73 PARTIAL, 2 MISSING, 10 BLOCKED**. Three more verified stories are required for 50%. See [Checkpoint 415](build-engine/CHECKPOINT_415.md) and [live evidence](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

# Latest — Checkpoint 414: BE-059 supplier qualification DONE (2026-11-03)

- Native Odoo supplier qualification tests: **7/7 passed**. Authenticated React → BFF → Odoo live journey: **1/1 passed** on a disposable clone.
- Procurement submitted a qualification; an independent Owner reviewed it with rationale. The requester, an Owner who submitted their own request, and a Purchase Manager were denied review. Approved/rejected decision events retained immutable reviewer/time/rationale. Missing required scope was rejected without a write; foreign-company records stayed hidden.
- Clone and temporary services were removed; `namaa_ksa` unchanged. BE-059 is DONE. Totals: **78/164 DONE (47.6%), 74 PARTIAL, 2 MISSING, 10 BLOCKED**. Four more DONE stories are needed for 50%. See [Checkpoint 414](build-engine/CHECKPOINT_414.md) and [live QA](build-engine/SUPPLIER_QUALIFICATION_LIVE_QA.json).

# Latest — Checkpoint 413: authenticated BOQ Excel export and role boundaries

- BE-049 remained DONE; this run strengthens BE-147 export evidence but does not add a newly completed story. Authenticated Owner React → BFF → Odoo downloads were verified in English and Arabic (RTL); same-company non-QS export returned 403 and foreign-company QS export omitted the target BOQ/project.
- Focused Odoo upgrade suite: **31/31 passed**. Authenticated live Playwright journeys: **3/3 passed**. English workbook values matched the BOQ at export time; Arabic workbook headers/RTL were verified.
- Invalid line validation, stale-version rejection, reopen audit fields, reader/foreign-company boundaries and unauthorized-create no-write checks passed. Disposable clone, services and backup were removed; source database unchanged.
- BE-147 remains PARTIAL because more operational exports and full role/company acceptance remain. Totals unchanged: **77/164 DONE (47.0%), 75 PARTIAL, 2 MISSING, 10 BLOCKED**; five more DONE stories are required for 50%. See [Checkpoint 413](build-engine/CHECKPOINT_413.md) and [live evidence](build-engine/BOQ_DRAFT_REVISION_LIVE_QA.json).

# Latest — Checkpoint 412: workflow validation before publication

- BE-134/135/137 authenticated React→BFF→Odoo lifecycle journey: **1/1 passed** on disposable QA clone `be_workflow_template_qa_4d2ec367`. Invalid condition syntax returned 422 and left no template row. A regular Owner saved a valid graph and condition with role/group/user approvers, published immutable v1, made editable v2 and assigned the published version to a project type. Same-company PM read was allowed and create denied (403). Native readback passed. Clone and temporary BFF removed; source unchanged.
- Native module-upgrade tests remain unrun because older fixtures fail on unrelated dangling mail-tracking data.
- Requirements: **77/164 DONE (47.0%), 75 PARTIAL, 2 MISSING, 10 BLOCKED**. Five verified stories remain to reach 50%. See [Checkpoint 412](build-engine/CHECKPOINT_412.md) and [QA evidence](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

# Previous — Checkpoint 411: transition conditions and permissions

- BE-134/135 authenticated React→BFF→Odoo lifecycle editor: **1/1 passed** on disposable QA clone `be_workflow_template_qa_97829305`. Normal Owner configured a three-stage transition graph, condition expression and role/group/user approval settings; publication/versioning and project-type assignment persisted; same-company PM read succeeded and create/configuration returned 403. Native readback matched condition, approvals, versions, creator and company. Clone and temporary BFF removed; source unchanged.
- Native module-upgrade tests remain unrun because an older fixture has unrelated dangling mail-tracking product data. DEC-06 operational approver policy remains open.
- Requirements: **76/164 DONE (46.3%), 76 PARTIAL, 2 MISSING, 10 BLOCKED**. Six verified stories remain to reach 50%. See [Checkpoint 411](build-engine/CHECKPOINT_411.md) and [QA evidence](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

# Previous — Checkpoint 410: visual lifecycle editor acceptance

- BE-134 authenticated React→BFF→Odoo lifecycle editor journey: **1/1 passed** on disposable clone `be_workflow_template_qa_7d0def96`. Verified ordinary Owner create/publish/version/assignment, graph stages/transitions and three approval types; PM read and denied create; native readback verified creator/company, versions and project inheritance. Clone and temporary BFF removed; source unchanged.
- Native module-upgrade tests were not run. An earlier attempt against the prior demo clone failed during Odoo flush on dangling `product.product(154)` mail-tracking data. Rerun native upgrade coverage against a clean fixture.
- Requirements: **75/164 DONE (45.7%), 77 PARTIAL, 2 MISSING, 10 BLOCKED**. Seven verified DONE stories remain to reach 50%. See [Checkpoint 410](build-engine/CHECKPOINT_410.md) and [QA evidence](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

# Previous — Checkpoint 409: baseline and vendor metrics acceptance

- BE-047: current-source Odoo project-plan/baseline suite **3/3 passed**; authenticated React→BFF→Odoo browser **1/1 passed**. Owner-only decisions, same-company PM denial, invalid-input/no-write, actor/time/company snapshot and foreign-company denial verified.
- BE-068: native derived-metric tests **2/2**, bridge **2/2**, BFF **5/5**, React metrics **4/4**, bilingual preview **2/2**; current-source authenticated role/company browser **1/1 passed**.
- Disposable Odoo clones and temporary BFF services removed.
- Requirements: **74/164 DONE (45.1%), 78 PARTIAL, 2 MISSING, 10 BLOCKED**. See [Checkpoint 409](build-engine/CHECKPOINT_409.md) and the linked QA artifacts.

# Latest — Checkpoint 408: BE-147 authenticated Site report export

- Live React → BFF → Odoo Site-role browser journey: **1/1 passed**.
- Offline daily-report sync and readback, exact replay idempotency and changed-payload HTTP 422 passed.
- Filtered report export returned XLSX MIME type/signature (PK ZIP), >1 KB; synthetic user/project/report were removed. `namaa_ksa` unchanged.
- See [QA artifact](build-engine/SITE_DAILY_REPORT_EXPORT_LIVE_QA.json). Story remains PARTIAL; counts unchanged at 72/164 (43.9%).

# Previous — Checkpoint 407: BE-043 live resource conflict acceptance

- Native Odoo project-plan/security/conflict tests: **3/3 passed**.
- Authenticated React → BFF → Odoo browser journey: **1/1 passed**, showing an overlapping crew assignment and crane booking from a second same-company project.
- Invalid task input returned 422/no-write; foreign-company project-plan access was denied.
- Disposable clone and temporary BFF removed; source database unchanged. Conflict detection remains advisory.

Story totals: **72 DONE (43.9%), 80 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. See [Checkpoint 407](build-engine/CHECKPOINT_407.md), [QA evidence](build-engine/PROJECT_PLAN_LIVE_QA.json), and [traceability](REQUIREMENTS_TRACEABILITY.md).

# Latest — Checkpoint 406: BE-154 Arabic project status report

- Native Odoo project-report suite: **7/7 passed** on a disposable clone.
- Authenticated React → BFF → Qwen → Odoo journeys: **3/3 passed**. Arabic status draft was reopened by a separate Owner and reviewed with rationale.
- Invalid reversed dates returned 422 with no write; same-company reader and foreign-company PM read/create attempts returned 403 without disclosure. Odoo verified source IDs, company/project, actors/times, review audit and unchanged project data.
- QA clone, temporary BFF and isolated Odoo registry removed; shared source unchanged.

Story totals: **71 DONE (43.3%), 69 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. See [Checkpoint 406](build-engine/CHECKPOINT_406.md), [QA evidence](build-engine/PROJECT_REPORTS_LIVE_QA.json), and [traceability](REQUIREMENTS_TRACEABILITY.md).

# Latest — Checkpoint 405: Drawing-linked submittal revision acceptance

- Isolated current-source native Odoo `be_correspondence` tests: **29/29 passed**.
- Authenticated React → BFF → Odoo live role journeys: **2/2 passed**. The PM requested a revision; the Site author resubmitted a drawing-linked second revision; a PM approved it with rationale. The unauthorized reader received 403 for project log and Excel export.
- Odoo readback verified current drawing, company/project, actors/timestamps, both immutable revisions and attachment snapshots, and event order. Invalid required fields returned 422 without a partial write.
- Disposable clone and temporary services removed; shared database unchanged. `git diff --check`, Python compile, JS syntax and production React build passed.

Story totals: **70 DONE (42.7%), 82 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. See [Checkpoint 405](build-engine/CHECKPOINT_405.md), [QA evidence](build-engine/RFI_LIVE_QA.json), and [traceability](REQUIREMENTS_TRACEABILITY.md).

# Latest — Checkpoint 404: Project correspondence XLSX export

- Backend correspondence route and XLSX export regressions: **2/2 passed**. Workbook content, filters, Arabic RTL, audit history, formula-like label safety and 403/422 paths were checked.
- React Playwright correspondence download flow: **1/1 passed**, verifying filtered CSV and Excel downloads and filter forwarding.
- Isolated native Odoo role/lifecycle suite: **29/29 passed**; live React → BFF → Odoo role journeys: **2/2 passed**. The Project Manager Excel download returned a real workbook; unauthorized same-company reader received 403 on both correspondence read and export without disclosure. Clone/services removed; source database unchanged.
- Frontend production build passed (Vite 8.2.1). Existing large-JS-chunk warning remains (1.41 MB minified).
- Python compile, JavaScript syntax check and `git diff --check` passed.
- Export is read-only. BE-147 remains PARTIAL pending broader export coverage and live role/company acceptance.
- The portable bilingual user manual was regenerated with the correspondence CSV/XLSX workflow and 341 embedded screenshots.

See [Checkpoint 404](build-engine/CHECKPOINT_404.md) and [traceability](REQUIREMENTS_TRACEABILITY.md).

# Latest — Checkpoint 403: React BOQ Excel export slice

- Focused backend BOQ/site-report API/workbook tests: **2/2 passed**. They checked XLSX structure/content, Arabic RTL layout, formula-like text safety, filtered Odoo calls and invalid-filter 422/no-call.
- React BOQ and site-report Playwright download journeys: **2/2 passed**, verifying attachment names and active query filters.
- Read-only export does not create or modify Odoo records. BE-147 remains PARTIAL while operational report exports and live role/company download acceptance are open.

See [Checkpoint 403](build-engine/CHECKPOINT_403.md), [traceability](REQUIREMENTS_TRACEABILITY.md), and [BOQ export route](../backend/app/main.py).

# Previous — Checkpoint 402: BE-148 charter drafting acceptance

- Focused native Odoo charter AI suite: **5/5 passed**, including saved-draft fresh-read regression, project/company scope, task snapshot, validation and role checks.
- Authenticated isolated React → BFF → Qwen → Odoo browser journey: **1/1 passed**. It verified English/Arabic pending drafts, fresh login/reopen, invalid language 422/no-write, same-company reader sees no AI drafts and cannot create, and foreign-company PM denial without disclosure.
- Odoo readback confirmed both drafts pending under the PM/company with source IDs, baseline task assignment and unchanged project/task write dates; no official charter was created.
- Disposable QA clone and temporary BFF removed; source database unchanged, Odoo restarted healthy, and shared frontend dependency symlink restored.

See [QA artifact](build-engine/PROJECT_CHARTER_AI_ACCEPTANCE_LIVE_QA.json), [Checkpoint 402](build-engine/CHECKPOINT_402.md), and [Arabic screenshot](build-engine/frontend/screenshots/live-project-charter-ai-ar-acceptance.png).

# Previous — Checkpoint 401: BE-153 change-impact acceptance

- Focused native Odoo variation-impact lifecycle/security tests: **4/4 passed**.
- Focused backend variation-impact generator and BFF/API regression tests: **6 passed, 232 deselected**.
- Authenticated React → BFF → Qwen 3.8 27B → Odoo browser journey: **1/1 passed**, including the English and Arabic UI and model drafts, invalid-language 422/no-write, same-company read-only denial, foreign-company PM denial, and separate PM/Owner review flow.
- Postconditions verified two pending source-bound drafts; independent human approval applied the SAR 750 variation exactly once and appended a BOQ baseline while preserving the original.
- Disposable clone dropped, source database unchanged, Odoo healthy and original frontend dependency symlink restored.
- No deployment was performed.

See [QA artifact](build-engine/VARIATION_IMPACT_LIVE_QA.json), [Checkpoint 401](build-engine/CHECKPOINT_401.md), and [Arabic screenshot](build-engine/frontend/screenshots/live-variation-impact-arabic-draft.png).

# Latest — Checkpoint 399: BE-029 account research acceptance

- Backend account-research generator suite: **5/5 passed**, including a regression proving missing Odoo country/industry, false, null and blank values are omitted from the LLM payload.
- Current-source disposable clone native Odoo acceptance: **4/4 passed**.
- Authenticated React → BFF → Qwen → Odoo Playwright journey: **1/1 passed**. Unsupported language returned a field-level 422 and saved no suggestion; reopened English/Arabic drafts showed actor, timestamp, company, project and cited CRM sources. Same-company non-Sales reader and foreign-company requests were denied without disclosure. Drafts remained pending and unsent; the lead, messages and activities were unchanged.
- The refreshed Arabic screenshot includes the full draft and uncertainty. Root reviewed the text as understandable and appropriately cautious; no false/null sentinel appears.
- QA clone dropped, BFF removed, source fingerprint unchanged, Odoo healthy and original Playwright dependency link restored. No deployment was performed. See [QA artifact](build-engine/CRM_ACCOUNT_RESEARCH_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-crm-account-research-arabic-draft.png), and [Checkpoint 399](build-engine/CHECKPOINT_399.md).

# Latest — Checkpoint 398

BE-162 current-source isolated acceptance: focused native Odoo test **1/1 passed**; focused backend invalid-filter test **1/1 passed**; preview and authenticated React → BFF → dedicated Odoo worker browser journeys **2/2 passed**; React unit suite **96/96 passed**; production build **passed** (existing chunk-size warning). Direct BFF JSON and browser assertions verified source IDs, project/company, responsible actor and timestamp where available. Invalid page-size returned field-level 422 without an Odoo call or writes; same-company PM denial and foreign-company data scoping passed. Odoo readback confirmed source rows and unchanged business counts. A3 write audit is N/A for this read-only drilldown. Clone and worker were removed, clone port returned HTTP 000, shared source DB remained unchanged and Odoo remained healthy. Story totals: **64 DONE, 88 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (39.0% DONE)**. See [BE-162 QA](build-engine/BE162_PROJECT_RISKS_LIVE_QA.json) and [Checkpoint 398](build-engine/CHECKPOINT_398.md).

# Latest — Checkpoint 397

BE-124 isolated current-source acceptance: native Odoo tests **3 passed, 1 conditional skip**; focused backend provision-route test **1/1 passed**; authenticated React live journey **1/1 passed**. The test verified folder root and six standard subfolders, creator/time/project/company visible after fresh login, invalid project ID field-level 422/no-write, same-company reader denial and foreign-company PM denial. Odoo postconditions verified all six folders and their root belong to the target project/company and were created by the PM. Clone/temp services removed; source unchanged. See [folder QA](build-engine/PROJECT_DOCUMENT_FOLDERS_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_397.md).

# Latest — Checkpoint 396

BE-027 current-source isolated acceptance: native Odoo tests **2/2 passed**, backend/API tests **240/240 passed**, authenticated live browser **1/1 passed**. Invalid prompt produced 422/no-write; saved two-turn Qwen transcript reopened with project/company/actor/time, citations and uncertainty; AI remained draft-only. Clone/temp services removed; source unchanged. See [QA](build-engine/CRM_SCOUTING_AI_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_396.md).

# Latest — Checkpoint 395

BE-130 current-source isolated acceptance: native Odoo tests **4/4 passed**; authenticated React live journey **1/1 passed**. PM provisioning/upload/fresh-login history, invalid directory 422/no-write, same-company reader/DMS-group denial and foreign-company denial passed. Clone/temp services removed; source DB unchanged. See [QA](build-engine/PROJECT_DOCUMENTS_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_395.md).

# Latest — Checkpoint 394

BE-157 current-source isolated acceptance: native bridge tests **7/7 passed**; authenticated React live journey **1/1 passed**. Missing `period_end` returned 422/no-write; AI closeout lessons showed citations and uncertainty, required separate Owner review, reopened with audit after fresh login, and were not applied/sent. Same-company reader and foreign-company PM were denied. Odoo readback passed; clone/temp services removed, source unchanged. See [QA](build-engine/PROJECT_REPORTS_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_394.md).

# Latest — Checkpoint 393

BE-132 current-source isolated acceptance: native lifecycle/security check **1/1 passed**; authenticated React live journey **1/1 passed**, including invalid export rationale/no-write, valid ZIP integrity and exclusions, fresh-login audit reopen, reader and foreign-company denials. Clone and temporary services removed; source DB unchanged. See [QA](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_393.md).

# Latest — Checkpoint 392

BE-061 isolated acceptance: native Odoo alternative test **1/1 passed**; authenticated React live journey **1/1 passed**, including invalid supplier selection/no-write, persisted draft audit, same-company reader denial and foreign-company Procurement denial. Clone and temporary services removed; source DB unchanged. See [QA](build-engine/PURCHASE_ALTERNATIVES_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_392.md).

# Latest — Checkpoint 391

BE-128 current-source isolated acceptance: native archive/export lifecycle **1/1 passed**; authenticated React live journey **1/1 passed**, including short-rationale 422/no-write, missing-approved-source denial/no-write, fresh-login reopen, PDF integrity, reader and foreign-company boundaries. Clone cleanup and source integrity verified. See [QA](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_391.md).

# Latest — Checkpoint 390

BE-050 current-source isolated QA: native Odoo BOQ/bridge suite **27/27 passed**; authenticated React import Playwright journey **1/1 passed**; preceding BE-053 BOQ validation browser journeys **2/2 passed**. Clone cleanup, unchanged source fingerprint and Odoo health verified. See [QA artifact](build-engine/BE050_BOQ_IMPORT_LIVE_QA.json) and [checkpoint](build-engine/CHECKPOINT_390.md).

# Checkpoint 387 — BE-098 equipment utilization DONE (2026-10-31)

- Current-source isolated Odoo role/lifecycle test: **1/1 passed**. It verified immutable company-scoped snapshot create/reopen, creator/time, active project at period end, role and foreign-company denial, and invalid-period no-write.
- Current-source authenticated React → BFF → Odoo Site-role browser journey: **1/1 passed**. The live report returned 240 available, 216 checked-out, 24 idle calendar hours and 90% utilization, with the project visible. Arabic RTL at 390px had no horizontal overflow.
- Disposable clone and temporary services removed; shared database unchanged. Original dependency symlink restored. Manual verification: **335/335 screenshots decoded**, English/Arabic desktop and phone no overflow, no external requests. See [checkpoint](build-engine/CHECKPOINT_387.md) and [live QA](build-engine/EQUIPMENT_UTILIZATION_LIVE_QA.json).
- Story totals: **53 DONE, 99 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (32.3% DONE)**; five more verified stories are needed for 35%.

# Checkpoint 379 — BE-034 PDF preview DONE

- Current-source native Odoo tests **4/4 passed**; authenticated Sales React→BFF→Odoo live browser **3/3 passed**.
- Invalid language returned field-level 422/no write; private PDF create/download/reopen, audit and company/project metadata, same-company non-Sales denial, and foreign-company create/download denial passed. Accounting move count stayed at baseline **6**.
- Sales BOQ read permissions are limited to linked lines/parents on their own confirmed orders in allowed companies; native access regression passed. Clone+filestore removed; source fingerprint unchanged; Odoo healthy. Evidence: [live QA](build-engine/BE034_FINANCIAL_PDF_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/be034-live-financial-pdf-preview.png), [checkpoint](build-engine/CHECKPOINT_379.md). Totals: **46 DONE, 106 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (28.0% DONE)**.

# Checkpoint 378 — BE-053 BOQ validation DONE

- Native Odoo BOQ/bridge tests: **26/26 passed**.
- Authenticated live React→BFF→Odoo browser: **2/2 passed**; invalid zero quantity and UOM made no writes, valid fractional lines persisted/reopened, currency rounding matched Odoo (SAR 0.21), and same-company/foreign-company access denials passed.
- Clone removed; source fingerprint unchanged; Odoo healthy. Evidence: [live QA](build-engine/BE053_BOQ_VALIDATION_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_378.md). Totals: **45 DONE, 107 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (27.4% DONE)**.

## Historical candidate check — BE-029 stayed PARTIAL before Checkpoint 399 (2026-10-30)

The isolated live runner could not load the clone registry: Odoo hit a stale `product.product(154)` reference while upgrading `namaa_ai_bridge`, before native tests or browser acceptance. The clone was dropped, no BFF was started, the source fingerprint stayed identical, and Odoo is healthy. No Arabic draft was generated or reviewed. Evidence: [runner report](build-engine/CRM_ACCOUNT_RESEARCH_LIVE_QA.json). This is an environment/clone blocker, not acceptance evidence; BE-029 remains PARTIAL.

# Checkpoint 377 — BE-037 daily follow-up draft DONE (2026-10-30)

- Native follow-up tests **2/2**; authenticated React→BFF→Qwen→Odoo browser acceptance passed on an isolated current-source clone.
- Pending draft reopened with author/company/Riyadh date-time, citations and uncertainty. Source activity stayed open. No-role read/create was denied; foreign-company data stayed isolated; company override returned 422/no write.
- Clone dropped; source unchanged. Counts: **44 DONE, 108 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (26.8% DONE)**. See [Checkpoint 377](build-engine/CHECKPOINT_377.md) and [live QA](build-engine/TASK_FOLLOWUP_LIVE_QA.json).

# Checkpoint 372 — BE-104 nonconformance workflow DONE (2026-10-30)

- Native Odoo tests **2/2**; authenticated React→BFF→Odoo acceptance **1/1**; separate live GET-only timestamp check **1/1**.
- Quality/Safety user created and reopened a finding; blank description returned field-level 422/no record; state, reporter, time, project and company were shown. Non-reporter and foreign-company requests returned 403 without disclosure.
- React date/time formatter renders non-midnight `detected_at` with Asia/Riyadh date and HH:mm against an existing finding; zero mutation requests were sent in this check. Clone and temporary services removed; source unchanged; Odoo healthy. All supplied criteria passed.
- Counts: **39 DONE, 113 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (23.8% DONE)**; two more verified stories are needed for 25%. See [Checkpoint 372](build-engine/CHECKPOINT_372.md), [acceptance QA](build-engine/NONCONFORMANCE_ACCEPTANCE_LIVE_QA.json), and [timestamp QA](build-engine/NONCONFORMANCE_TIMESTAMP_LIVE_QA.json).

# Checkpoint 371 — BE-016 Sales bid evidence DONE (2026-10-30)

- Current-source native tests **2/2**; authenticated Sales React→BFF→Odoo browser journey **1/1**.
- Tender-owning Sales user uploaded/reopened sanitized evidence without bidder identity, amount or filename; missing required evidence made no partial write; actor/time/company/project audit was visible; non-owner Sales and foreign-company attempts were denied without disclosure. Procurement retains its full view.
- Native postcondition confirmed published tender, evidence filename, Sales actor and timestamp. Clone/temp services removed; source unchanged; Odoo healthy. All four supplied criteria passed.
- Counts: **38 DONE, 114 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (23.2% DONE)**; three more verified stories are needed for 25%. See [Checkpoint 371](build-engine/CHECKPOINT_371.md) and [Sales live QA](build-engine/TENDER_SALES_EVIDENCE_LIVE_QA.json).

# Checkpoint 370 — BE-164 owner dashboard export DONE (2026-10-30)

- Current-source native dashboard tests **17/17**; owner React→BFF→Odoo browser journey **1/1**; frontend unit 95/95, mobile E2E 2/2 and focused BFF auth tests 2/2 passed.
- Owner created/reopened an audited export and downloaded a valid protected XLSX. Separate PM direct export returned 403; foreign owner saw no history and protected download returned 404. Company/project/exporter/time/outbox linkage verified.
- The generic invalid-input criterion is N/A because the export action has no required user-supplied parameters. Clone removed; source unchanged; Odoo healthy. All applicable criteria passed.
- Counts: **37 DONE, 115 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (22.6% DONE)**; four more verified stories are needed for 25%. See [Checkpoint 370](build-engine/CHECKPOINT_370.md) and [live QA](build-engine/BE164_OWNER_EXPORT_LIVE_QA.json).

# Checkpoint 369 — BE-016 Procurement evidence workflow (PARTIAL, 2026-10-30)

- Current-source native Odoo tests passed **2/2**; authenticated React→BFF→Odoo browser journey passed **1/1**.
- Procurement uploaded and reopened evidence for a published tender. Missing required evidence returned field-level validation without a partial write; completed line showed actor/time/project/company. No-role and foreign-company create/update attempts returned 403 without sensitive data.
- Native postcondition confirmed published tender, completed checklist line, evidence filename and actor/time. Clone and temporary BFF removed; source unchanged; Odoo healthy.
- BE-016 remains PARTIAL because the supplied persona is Sales Representative while the current ACL denies Sales users checklist evidence access. Role reconciliation and Sales-persona acceptance remain.
- Counts remain **36 DONE, 116 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (22.0% DONE)**; five more verified stories are needed for 25%. See [Checkpoint 369](build-engine/CHECKPOINT_369.md) and [live QA](build-engine/TENDER_EVIDENCE_LIVE_QA.json).

# Checkpoint 368 — BE-097 repair cost recording DONE (2026-10-30)

- Current-source native Odoo suite **26/26**; backend tests **4 passed + 5 subtests**; React unit suite **95/95**; authenticated React→BFF→Odoo browser journey passed.
- Authorized PM recorded/reopened a corrective repair with SAR 125.75 and allocated SAR 300 from a posted same-project vendor bill without another journal entry. Invalid cost returned field-level 422/no write; unauthorized reader and foreign-company breakdown were denied without cost disclosure.
- Workflow generated no AI content; the generic AI-review acceptance is not applicable. Clone/temp services removed; source DB unchanged. All supplied criteria passed.
- Counts: **36 DONE, 116 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (22.0% DONE)**; five more verified stories are needed for 25%. See [Checkpoint 368](build-engine/CHECKPOINT_368.md) and [live QA](build-engine/MAINTENANCE_BE097_LIVE_QA.json).

# Checkpoint 367 — BE-067 schedule shortage detection DONE (2026-10-30)

- Backend tests **3/3**, mocked Playwright **1/1**, current-source native checks and authenticated React→BFF→Odoo journey passed.
- Dated project-location inventory forecast compared against task allocation; invalid cross-project location returned field-level 422/no snapshot; authorized user saved and reopened review; native readback confirmed actor/time/company/project and 10 required, 5 forecast, 5 shortage. BOQ over-allocation rejected; no-role and foreign-company attempts denied.
- Clone and temporary BFF/image removed; source unchanged. All four supplied criteria passed.
- Counts: **35 DONE, 117 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (21.3% DONE)**; six more verified stories are needed for 25%. See [Checkpoint 367](build-engine/CHECKPOINT_367.md) and [live QA](build-engine/SCHEDULE_SHORTAGE_LIVE_QA.json).

# Checkpoint 366 — BE-164 protected dashboard XLSX export slice (2026-10-30)

- Current-source disposable clone native dashboard suite passed **15/15**.
- Owner export persisted XLSX bytes on an owner-protected record with company, projects, actor/time and outbox linkage. Owner download returned **200** and a valid ZIP/XLSX signature; separate PM session received **404** and no XLSX. Foreign-company export denied; cash values redacted without journal-item ACL.
- Clone and temporary addon removed; Odoo healthy; `namaa_ksa` unchanged. BE-164 remains PARTIAL pending remaining dashboard report families and React export coverage. Totals remain **34 DONE, 118 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (20.7% DONE)**; seven more verified stories are needed for 25%. See [Checkpoint 366](build-engine/CHECKPOINT_366.md) and [QA evidence](build-engine/BE164_OWNER_EXPORT_LIVE_QA.json).

## BE-067 schedule shortage review — partial verification (2026-10-30)

- Backend shortage API tests **3/3**, mocked Playwright journey **1/1**, production build, Python compilation and `git diff --check` passed.
- Disposable-clone live checks verified wrong-project location rejection as field-level 422/no write, valid React→BFF→Odoo save/readback, and native no-role/foreign-company denial.
- Fresh-session React reopen did not finish because the Arabic login page was asserted in English. A corrected locale order is prepared, but no final live retry ran because another isolated QA run was in progress. Clone/temp BFF/image removed; Odoo healthy; source unchanged. BE-067 remains PARTIAL. See [live QA](build-engine/SCHEDULE_SHORTAGE_LIVE_QA.json) and [Checkpoint BE067](build-engine/CHECKPOINT_BE067_20261030.md).

# Checkpoint 365 — BE-015 tender checklist DONE (2026-10-30)

- Current-source disposable clone native tests passed **2/2**; authenticated React→BFF→Odoo browser journey passed **1/1**.
- Sales user created/reopened a tender and checklist; invalid mandatory checklist input was rejected; reopened record displayed actor/time/company/project; no-role and foreign-company create/detail requests were denied with no tender/project/marker data. Same-operation retry was idempotent.
- The optional post-browser native postcondition collector hit a report-only f-string formatting error after Playwright passed. Clone and temporary BFF were removed; Odoo healthy; source snapshot unchanged.
- Counts: **34 DONE, 118 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (20.7% DONE)**; seven more verified stories are needed for 25%. See [Checkpoint 365](build-engine/CHECKPOINT_365.md) and [live QA](build-engine/TENDER_CREATE_LIVE_QA.json).

# Checkpoint 364 — BE-014 pipeline stage/probability DONE (2026-10-30)

- Current-source disposable clone native test passed **1/1**. Authenticated React→BFF→Odoo browser journey passed **1/1**.
- Sales user updated New/25% → Qualified/67%; fresh read verified persistence/audit/project/company. Invalid probability 101 and stale revision returned 422 without writes. Reopened UI showed state, actor/time, project and company. CRM-reader and foreign-company user received 403 without record-name disclosure.
- Clone and temporary services removed; source DB unchanged. All four supplied BE-014 acceptance criteria passed.
- Counts: **33 DONE, 119 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (20.1% DONE)**; eight more verified stories are needed for 25%. See [Checkpoint 364](build-engine/CHECKPOINT_364.md) and [live QA](build-engine/CRM_PIPELINE_LIVE_QA.json).

# Checkpoint 363 — BE-064 quote anomaly human review DONE (2026-10-30)

- Current-source disposable clone native Odoo Hoot test passed **1/1**, with direct Odoo permission/privacy checks.
- Authenticated React → BFF → Odoo browser journey passed: authorized quote buyer created and reopened a human-review record; invalid/short reasons returned inline field errors and API 422 with no Odoo write; reopened record showed state, actor/time/project/company; same-company reader and foreign-company buyer were denied without sensitive source data or mutation.
- Clone and temporary BFF/image removed; source snapshot unchanged. All four supplied BE-064 acceptance criteria passed.
- Counts: **32 DONE, 120 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (19.5% DONE)**; nine more verified stories are needed for 25%. See [Checkpoint 363](build-engine/CHECKPOINT_363.md), [live QA](build-engine/QUOTE_ANOMALY_LIVE_QA.json), and [native QA](build-engine/QUOTE_ANOMALY_NATIVE_QA.json).

# Checkpoint 362 — BE-094 equipment assignment DONE (2026-10-30)

- Current-source disposable clone native equipment tests **26/26 passed**.
- Authenticated React Site-role journey assigned equipment to a project, reopened the movement/audit state, then returned the equipment.
- Missing project returned field-level **422** with no movement; foreign-company and unauthorized reads/writes were denied without disclosure. Native postcondition preserved company/project, actor and movement timestamps.
- Clone, temporary BFF and image removed; shared source database unchanged. BE-094 now meets its four supplied acceptance criteria; yard/tool stock and acquisition flows are extensions, not acceptance criteria for this story. Counts: **31 DONE, 121 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (18.9% DONE)**; 10 more verified stories are needed to reach 25%. See [live QA](build-engine/EQUIPMENT_ASSIGNMENT_BE094_LIVE_QA.json) and [Checkpoint 362](build-engine/CHECKPOINT_362.md).

# Checkpoint 361 — BE-047 current-source schedule-baseline acceptance (2026-10-30)

- Disposable current-source clone: focused native project, milestone and schedule-baseline lifecycle/security tests **3/3 passed**.
- Authenticated live React → BFF → Odoo journey **1/1 passed**: PM submitted; invalid blank name returned field-level 422/no write; a distinct Owner approved; React reopened the audit/snapshot; foreign-company PM mutation and project read were denied without disclosure.
- Native regression covers self-approval denial, rejected baseline preserving official state, stale revision, immutable events/snapshot and public-user denial. Clone `be_project_plan_live_qa_98b08c2e` dropped; shared source unchanged.
- BE-047 remains PARTIAL pending DEC-17 approver policy confirmation. Counts unchanged at 30 DONE, 122 PARTIAL, 2 MISSING, 10 BLOCKED / 164. See [Checkpoint 361](build-engine/CHECKPOINT_361.md) and [QA evidence](build-engine/PROJECT_PLAN_LIVE_QA.json).

# Checkpoint 360 — BE-062 supplier quotation recording DONE (2026-10-30)

- Current-source disposable Odoo clone: focused native quote persistence/security/recommendation tests **2/2 passed**.
- Authenticated live React → BFF → Odoo journey: **1/1 passed**, including invalid validity field/no partial write, quote reopen with audit/project/company, and stale retry rejection.
- Native QA also denied unauthorized and foreign-company writes and checked user-entered compliance evidence. No business purchase line was committed by the recommendation path.
- Clone and temporary services removed; shared databases unchanged. **BE-062 DONE**. Totals: 30 DONE, 122 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (18.3%). See [Checkpoint 360](build-engine/CHECKPOINT_360.md) and [live QA](build-engine/PURCHASE_QUOTE_LIVE_QA.json).

## BE-098 persistent equipment utilization snapshots (2026-10-30)

- Current-source disposable clone: native Site-role report test **1/1 passed**. Authenticated React → BFF → Odoo journey **1/1 passed**; invalid date range returned 422 without creating a report, and the saved snapshot reopened with actor/time/company and metrics.
- Arabic RTL phone display passed without horizontal overflow. Backend report history route **1/1**, React unit tests **94/94**, production build passed.
- Example 10-day report: 240 calendar hours available, 96 checked out, 144 idle, 40% utilization. Clone and temporary BFF removed; shared DB unchanged. BE-098 remains PARTIAL pending calendar/retention policy and broader role/company acceptance. See [Checkpoint BE098](build-engine/CHECKPOINT_BE098_20261030.md) and [QA evidence](build-engine/EQUIPMENT_UTILIZATION_LIVE_QA.json).

## BE-068 vendor performance reporting slice (2026-10-30)

- Current-source disposable clone native bridge tests: **2/2 passed** after upgrading the required stale schema dependencies on the clone. Clone dropped; shared DB unchanged.
- BFF route tests **5/5**, React metrics tests **4/4**, English desktop/Arabic phone preview journeys **2/2** passed.
- Authenticated current-source live clone journey passed 1/1: the buyer saw only own-company history, the pending filter returned pending rows, and a non-purchase user received 403 without data. Clone and temporary BFF/image were removed. BE-068 stays PARTIAL pending owner acceptance of calendar-day/weighting policy and broader company UAT. See [live QA](build-engine/BE068_VENDOR_PERFORMANCE_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-vendor-performance.png), [Checkpoint BE068](build-engine/CHECKPOINT_BE068_20261030.md), and [component QA](build-engine/BE068_VENDOR_PERFORMANCE_QA.json).

## BE-063 landed unit price comparison correction (2026-10-30)

- React regression coverage now distinguishes order-total winner from landed cost per unit (1 × SAR 100 vs 5 × SAR 150). Full unit suite passed **95/95**; JS/Python syntax and diff checks passed.
- The Hoot selector selected one WebSuite test but Odoo skipped it because Chrome is absent from the QA container. No Hoot assertions ran. Temporary dependencies were removed, clone dropped, and the Odoo service is healthy.
- BE-063 remains PARTIAL. See [Checkpoint BE063](build-engine/CHECKPOINT_BE063_20261030.md) and [attempt/cleanup evidence](build-engine/BE063_HOOT_QA.json).

## BE-086 additional restricted-role export verification (2026-10-30)

- On a disposable clone, a non-admin, single-company `account.group_account_user` ran all **10** React report families and downloaded **20** files (one XLSX and PDF per report).
- ZIP and PDF signatures were verified. The user had no system-admin group. No business transactions were written; the clone and temporary services were removed.
- BE-086 remains PARTIAL pending bilingual export review and accountant sign-off. See [checkpoint](build-engine/CHECKPOINT_BE086_20261030.md) and [QA JSON](build-engine/BE086_FINANCE_EXPORT_ROLE_LIVE_QA.json).

# Checkpoint 358 — BE-045 milestone acceptance (2026-10-30)

- Current-source disposable Odoo clone: native milestone lifecycle/security tests **2/2 passed**.
- Authenticated live React → BFF → Odoo browser journey: **1/1 passed**, including invalid input/no partial write, create/reopen audit, obligation/task gate, unauthorized and foreign-company denial, and Arabic phone/RTL rendering.
- React unit suite: **90/90 passed**. Python compilation and the frontend production build passed; the build includes the executive response-shape guard.
- Native readback confirmed company/project, stakeholder, responsible user, task link, creator, update actor and reopened state. Clone dropped; shared `namaa_ksa` unchanged.
- BE-045 is DONE. Totals: **29 DONE, 123 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (17.7%)**. See [Checkpoint 358](build-engine/CHECKPOINT_358.md), [QA evidence](build-engine/PROJECT_PLAN_LIVE_QA.json) and [Arabic phone screenshot](build-engine/frontend/screenshots/live-project-plan-milestones-arabic-390.png).

## Checkpoint 359 — BE-047 current-source schedule-baseline regression (2026-10-30)

- Current-source Odoo disposable clone ran project-plan, milestone and schedule-baseline lifecycle/security tests: **3/3 passed**. The baseline case covers immutable snapshots/events, independent approval, rejection preserving the active pointer, stale revision denial, self-approval denial and public-user denial.
- The same runner's authenticated live React → BFF → Odoo browser journey passed **1/1** for project planning and milestones. It did not exercise schedule-baseline create/review in the browser; the previous isolated two-role evidence is dated Checkpoint 87.
- Clone `be_project_plan_live_qa_7d2dd485` was dropped. Shared source DB unchanged. BE-047 remains PARTIAL; current live baseline role/company acceptance and DEC-17 policy confirmation remain. See [Checkpoint 359](build-engine/CHECKPOINT_359.md) and [QA evidence](build-engine/PROJECT_PLAN_LIVE_QA.json).

# Checkpoint 357 — BE-161 quality and risk alert drill-down (2026-10-30)

- Backend business suite: **223/223 passed**, including company-scoped overdue daily-safety and corrective-action aggregation. Two stale supplier-address expectations were aligned with the existing address payload contract.
- Executive dashboard Playwright journey: **1/1 passed**, including quality and corrective-action warnings and navigation to the daily-safety register tab.
- React unit suite: **90/90 passed**.
- Vite production build passed; existing warning remains for the minified JavaScript chunk exceeding 500 kB.
- No live Odoo role/company acceptance or runtime rollout was performed. BE-161 remains PARTIAL.

## Checkpoint 356 — BE-161 overdue quality-gate alert slice (2026-10-30)

# Checkpoint 355 — Mobile sales orders (2026-10-30)

- English and Arabic/RTL phone-width sales card journeys: **2/2 passed** at 390 × 844, covering visible customer/order/status/total/reference, detail open action, and no horizontal overflow.
- React unit tests: **90/90 passed**.
- Vite production build passed with the existing bundle-size advisory (>500 kB JavaScript).

## Checkpoint 354 — Executive dashboard and mobile shell (2026-10-30)

- Executive period and company-scoped warning aggregation unit checks: **2/2 passed**.
- React unit suite: **90/90 passed**.
- English/Arabic 390px mobile navigation and appearance, executive period selection and mocked authenticated-warning Playwright journeys against the production app: **4/4 passed**, including cash/delay/lost-opportunity warning display, Latin digits in Arabic, bottom navigation, RTL drawer positioning, visible appearance popover and no horizontal overflow.
- Selected supporting workspace/accounting browser checks: **9/9 passed**; the full workspace E2E file was not run to completion.
- Vite production build passed; existing warning remains for the minified JavaScript chunk exceeding 500 kB.
- No authenticated Odoo role/company live dashboard run was performed. The production build’s service worker caches the static application shell only; offline business data and writes are not supported by this increment.

## Checkpoint 353 — BE-091 project labor-cost allocation DONE (2026-10-29)

- The live HR flow linked the native analytic line to the project BOQ labor item. Three hours at configured SAR 50/hour yielded SAR 150 analytic cost and SAR 150 BOQ labour actual.
- Native role/bridge/security: **3/3**; backend timesheet tests **3 passed** with 10 validation subtests; mocked and authenticated live browser **1/1 each**.
- Invalid fields, unauthorized user and foreign-company project requests were rejected; no partial records or source DB changes.
- BE-091 meets its four supplied acceptance criteria. See [Checkpoint 353](build-engine/CHECKPOINT_353.md) and [live QA](build-engine/TIMESHEET_HR_LIVE_QA.json).

## Checkpoint 352 — BE-089 project task timesheets DONE (2026-10-29)

- Native role/bridge/security suite: **3/3 passed** on a disposable clone.
- Backend timesheet contract/API tests: **3 passed**, 218 deselected and 10 validation subtests passed.
- Mocked browser and authenticated live React→BFF→Odoo journeys: **1/1 each passed**.
- All four supplied criteria verified: authoritative HR write, field-level API error/no partial write, actor/company/project details on reopen, and denial for unprivileged/foreign-company requests.
- Odoo recalculated SAR 150 labor cost after edit. HR has own-timesheet access without approver rights; approval is BE-090. Clone and temporary BFF removed; source unchanged.
- Totals: **27 DONE, 125 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (16.5%)**.
- See [Checkpoint 352](build-engine/CHECKPOINT_352.md), [QA](build-engine/TIMESHEET_HR_LIVE_QA.json), and [live browser journey](../frontend/e2e/timesheets.live.spec.js).

## Checkpoint 350 — Quantity Surveyor BOQ capture (2026-10-29)

- Current Odoo 20 tests on a disposable clone: **3/3 passed**, covering the Quantity Surveyor role, all four cost-line types, actor/time/project/company readback, invalid-input atomicity, public-user denial and foreign-company denial. Clone dropped; source unchanged.
- Authenticated live React → BFF → Odoo journey: **1/1 passed**. The Quantity Surveyor saved, reloaded, reopened and edited the four line types. Odoo confirmed the SAR 12,100 total and actor/time; baseline confirmation returned 422 and made no change.
- React unit tests: **90/90**; mocked BOQ browser journeys: **5/5**; live authenticated journey: **1/1**; Vite production build passed with the existing bundle-size advisory.
- See [Checkpoint 350](build-engine/CHECKPOINT_350.md), [live QA](build-engine/BOQ_QUANTITY_SURVEYOR_LIVE_QA.json), and [screenshot](build-engine/frontend/screenshots/react-boq-quantity-surveyor-live-qa.png).

## Checkpoint 349 — BE-039 awarded opportunity to project (2026-10-29)

- Current Odoo 20 clone conversion/security tests: **2/2 passed**, covering idempotent project linkage, company scoping, non-won, unauthorized and foreign-company denial. Clone dropped; source unchanged.
- Existing authenticated live React→BFF→Odoo browser journey: **1/1 passed**, including linked-project audit display, retry, invalid/non-won/no-role/foreign-company checks and Arabic project navigation.
- Evidence: [Checkpoint 349](build-engine/CHECKPOINT_349.md), [current native QA](build-engine/CRM_WON_PROJECT_ACCEPTANCE_QA.json), and [live QA](build-engine/CRM_WON_PROJECT_LIVE_QA.json).

## Checkpoint 348 — BE-040/041 project plan and crew acceptance (2026-10-29)

- Current Odoo 20 clone regression: **1/1 passed** for native phase/task/dependency and crew operations, invalid-name atomicity, and project scope; clone dropped, source unchanged.
- React mocked Playwright project-plan journey: **1/1 passed**, including Arabic RTL phone rendering and assigned-crew label.
- Previous authenticated React→BFF→Odoo ordinary-PM journey: **1/1 passed**, covering create/edit/reopen, crew, invalid input, unauthorized/foreign-company denial.
- Dependency cycle and cross-project parent negative cases are covered in [Checkpoint 333](build-engine/CHECKPOINT_333.md).
- Evidence: [Checkpoint 348](build-engine/CHECKPOINT_348.md), [QA JSON](build-engine/PROJECT_PLAN_ACCEPTANCE_QA.json), and [live QA](build-engine/PROJECT_PLAN_LIVE_QA.json).

## Checkpoint 347 — BE-066 receipt into the correct project location (2026-10-29)

- Current Odoo 20 native tests on a disposable `namaa_ksa` clone: **2/2 passed**, including project-bin receipt, destination rejection without a partial transaction, project/company and validator/time readback. Clone dropped; source unchanged.
- Current React receipt Playwright suite: **3/3 passed**; backend route/field-error contract: **1/1 passed**.
- Prior authenticated React→BFF→Odoo receipt journeys: **2/2 passed** with native stock, PO received quantities, exact lot/serial, project destination, actor/time and backorders.
- Vite production build passed; existing >500 kB main chunk advisory remains.
- Evidence: [Checkpoint 347](build-engine/CHECKPOINT_347.md), [QA JSON](build-engine/RECEIPT_DESTINATION_ACCEPTANCE_QA.json), [live QA](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json).

## Checkpoint 346 — BE-069 warehouse/site-location acceptance (2026-10-29)

- Active Odoo 20 runtime, disposable clone of `namaa_ksa`: **2 native tests passed**, covering Stock Manager warehouse/site-location provisioning, invalid input atomicity, duplicate rejection, reader denial and foreign-company/project denial. Clone dropped; source unchanged.
- Current mocked React Playwright: **1/1 passed**, including the visible creator and timestamp column.
- Prior authenticated React→BFF→Odoo warehouse/site-location journey: **1/1 passed** on an isolated clone; native warehouse and project location verified. See [Checkpoint 157](build-engine/CHECKPOINT_157.md).
- Vite production build passed; existing >500 kB chunk advisory remains.
- The additional legacy-stack live recheck did not reach browser execution because its `be_tender` registry referenced missing `be_crm_lead_code`; clone dropped. Current active Odoo clone tests passed.
- Evidence: [Checkpoint 346](build-engine/CHECKPOINT_346.md), [QA summary](build-engine/SITE_LOCATION_ACCEPTANCE_QA.json), [legacy recheck](build-engine/SITE_LOCATION_WAREHOUSE_LIVE_QA.json).

## Checkpoint 345 — BE-070 purchase receipt acceptance (2026-10-29)

- Focused native Odoo 20 test on a disposable `namaa_ksa` clone: **1/1 passed**, covering receipt persistence, invalid quantity atomicity, stale-version rejection, company and validator/time fields. Clone dropped; source unchanged.
- Backend route/contract test: **1 passed**, including `detail.fields.lines` on native validation error and 403 permission mapping.
- React mocked Playwright: **3/3 passed**, including accessible line-group validation without an API request and the completed row's company/project/validator/timestamp; lot and backorder flows also pass.
- Prior authenticated isolated React→BFF→Odoo lot/serial journeys: **2/2 passed**, with native readback of the PO, project location, company, validator/time, stock, and backorders.
- Vite production build passed; existing >500 kB main bundle advisory remains. Evidence: [Checkpoint 345](build-engine/CHECKPOINT_345.md) and [QA JSON](build-engine/PURCHASE_RECEIPT_AUDIT_QA.json).

## Checkpoint 344 — BE-069 site-location audit metadata (2026-10-29)

- Focused mocked React Playwright journey: **1/1 passed**, including the combined creator/time column and visible 2026 timestamp.
- Vite production build passed; existing >500 kB main JavaScript chunk advisory remains.
- Fresh isolated live recheck was blocked during Odoo registry initialization (`be_tender` index initialization references missing `be_crm_lead_code` table); the QA clone was dropped. This is not a live application failure and no live browser acceptance was completed.
- Previous isolated Odoo bridge checks for create/invalid input/role and company scope passed 2/2; previous live evidence remains documented in [Checkpoint 157](build-engine/CHECKPOINT_157.md). BE-069 remains PARTIAL.
- Evidence: [Checkpoint 344](build-engine/CHECKPOINT_344.md), [current recheck output](build-engine/SITE_LOCATION_WAREHOUSE_LIVE_QA.json), and [React browser spec](../frontend/e2e/project-site-locations.spec.js).

## Checkpoint 343 — Saudi customer address fields (2026-10-28)

- Isolated Odoo 20 clone of `namaa_ksa`: upgraded `namaa_ai_bridge`; customer create/search and revision-checked address-update tests **2/2 passed**, zero failures/errors; clone dropped and source DB unchanged.
- Backend customer contract/API selection: **9 passed**, including address length limits and customer update revision forwarding.
- React unit suite: **90/90 passed**. Customer create/edit/archive/restore Playwright flow: **1/1 passed**, including street, city and postal-code persistence and display after changing city.
- `npm run build` passed; existing main bundle size advisory remains.
- QA evidence: [Checkpoint 343](build-engine/CHECKPOINT_343.md) and [machine-readable report](build-engine/CUSTOMER_ADDRESS_QA.json).

## Checkpoint 342 — Fractional CRM win probability (2026-10-28)

- Frontend unit suite: **90/90 passed**, including a valid 67.5% probability, rejection below 0%, and preservation of fractional probability in the CRM payload.
- Focused React Playwright preview journeys: **2/2 passed** in English desktop and Arabic phone layouts; the CRM form created and reopened a 67.5% opportunity.
- `npm run build` passed; existing main JavaScript chunk size advisory remains.
- UI accepts decimals using the browser's unrestricted numeric step; native Odoo stores probability as Float and BFF/bridge already validate 0–100.
- No Odoo runtime/database validation was performed because this change affects the React numeric step and existing bridge/payload contracts only. BE-014 remains PARTIAL.
- Evidence: [Checkpoint 342](build-engine/CHECKPOINT_342.md).

## Checkpoint 341 — Accessible React business-form validation (2026-10-28)

- Focused React Playwright suite: **8/8 passed** across CRM, Sales, Purchase and Accounting, in English desktop and Arabic phone layouts.
- Invalid fields retain localized accessible names and reference visible, non-hidden descriptions through `aria-describedby`.
- `npm run build` and local frontend Docker image build passed; Vite's existing main-chunk size advisory remains.
- Preview browser flows only; no Odoo calls or database changes.
- Evidence: [Checkpoint 341](build-engine/CHECKPOINT_341.md), [machine-readable QA](build-engine/FORM_VALIDATION_ACCESSIBILITY_QA.json), [browser tests](../frontend/e2e/business.spec.js).

## Checkpoint 340 — Arabic BOQ editor accessibility (2026-10-28)

- Isolated clone native upgrade/regression: **30 Odoo post-test cases, 0 failures/errors**.
- Authenticated PM browser journeys: **2/2 passed** — English draft edit/reopen/revision comparison; Arabic mobile RTL editor and revision comparison. Verified localized accessible names for description, type, manufacturing BoM, unit, quantity and rate controls.
- Native readback confirmed draft 12 × SAR 110 = SAR 1,320, unchanged prior baseline 10 × SAR 100 = SAR 1,000, and stale-version update rejection. Arabic flow was read-only. Clone and temporary Odoo/BFF services removed; source unchanged.
- Evidence: [Checkpoint 340](build-engine/CHECKPOINT_340.md), [live QA JSON](build-engine/BOQ_DRAFT_REVISION_LIVE_QA.json), [RTL screenshot](build-engine/frontend/screenshots/be049-live-ar-editor-rtl.png), [reproduction script](../scripts/run_boq_revision_live_qa.py).

## Checkpoint 339 — Non-admin React accounting report acceptance (2026-10-28)

- Disposable clone of `namaa_ksa` provisioned with a temporary, single-company SAR accountant (`base.group_user` + `account.group_account_user`, no system/admin role).
- Authenticated React → temporary BFF → isolated Odoo browser journey: **1/1 passed** across all ten reports. Every report returned successfully; all XLSX/PDF downloads passed ZIP/PDF signature checks.
- Browser flow was read-only. The clone, temporary Odoo/BFF containers and QA image were removed. Source `namaa_ksa` was not used for the journey.
- Evidence: [Checkpoint 339](build-engine/CHECKPOINT_339.md), [machine-readable result](build-engine/ACCOUNTING_REPORTS_ACCOUNTANT_LIVE_QA.json), [reproduction script](../scripts/run_accounting_reports_accountant_live_qa.py).

## Checkpoint 338 — Accounting aging reports and exports (2026-10-28)

- Isolated Accounting KSA native QA: **4 passed, 0 failures/errors** for partial-payment aging/as-of cutoff, payable sign/not-due bucket, KPI preservation by the JSON API, account-user access, and general internal-user denial. QA clone dropped; source `namaa_ksa` unchanged. [Native evidence](build-engine/KSA_AGING_REPORT_QA.json).
- Mocked React report journey: **1/1 passed**, covering ten report selectors, aging buckets and Arabic summary labels.
- Live React → BFF → Odoo aging journey: **1/1 passed**; both aging reports returned six buckets and rendered. [Aging evidence](build-engine/KSA_AGING_REPORT_LIVE_QA.json).
- Full live React → BFF → Odoo report/export journey: **1/1 passed** for all ten reports. Every report response was HTTP 200; XLSX and PDF downloads were checked for valid ZIP/PDF signatures. [Full report evidence](build-engine/ACCOUNTING_REPORTS_LIVE_QA.json).
- The live checks used Odoo `admin` and were read-only. The disposable clone allowed `account.group_account_user` and denied a general internal user. No non-admin QA login is configured in `namaa_ksa`; live role and broader company-boundary acceptance remain open.
- `npm run build`: passed; Vite still warns that the main JavaScript chunk exceeds 500 kB.
- The live test now waits for export controls to return to Ready before starting the next export; this removed the intermittent browser-test race.

See [Checkpoint 338](build-engine/CHECKPOINT_338.md).

## Checkpoint 337 — Indexed CRM construction-code matching (2026-10-27)

- Clean isolated Odoo install and focused mandate/code tests: **2/2 passed**; direct foreign-company code-index read was denied by the Odoo 20 company-scoped `ir.access` domain. Disposable QA database dropped.
- Live React → BFF → Odoo workflow: **1/1 passed**; React-created code values were persisted and indexed, correct leads matched, and wrong-code/disallowed-source candidates were excluded. Temporary QA services/database removed.
- Upgrade/backfill QA on a clone of `namaa_ksa`: **passed** from `be_tender` .4 to .6; an existing CRM lead's two JSON code values were backfilled to normalized projection rows. Clone dropped.
- Local demo rollout after validated mode-0600 backup: `be_tender` .6 and `namaa_ai_bridge` .42 installed; Odoo, React and BFF health checks passed. No shared business rows changed. Backup: `/tmp/namaa_ksa_before_crm_code_index_rollout_20261027.dump`.
- Evidence: [Checkpoint 337](build-engine/CHECKPOINT_337.md), [native QA](build-engine/CRM_SCOUTING_NATIVE_QA.json), [live QA](build-engine/CRM_SCOUTING_LIVE_QA.json), and [upgrade QA](build-engine/CRM_CODE_INDEX_UPGRADE_QA.json).

## Checkpoint 336 — CRM construction trade/category facts (2026-10-27)

- Clean isolated Odoo database: **2 selected native tests passed, 0 failures/errors** for company mandate matching and CRM fact create/read/update/validation. The database was dropped; source/shared databases were unchanged.
- Authenticated live React → temporary BFF → disposable Odoo journey: **1/1 passed**. React-created CRM codes persisted exactly, the matching record appeared in scouting, and wrong-trade/category/source records were excluded. Disposable services/database were removed; source database unchanged. See [live QA evidence](build-engine/CRM_SCOUTING_LIVE_QA.json).
- Backend business API suite: **221 passed, 319 subtests passed**.
- React unit suite: **90/90 passed**.
- Bilingual React editor browser verification: **English desktop 1/1; Arabic phone 1/1**, including create, reopen and edit.
- Vite production build passed with the existing >500 kB bundle advisory. Python compilation and `git diff --check` passed.
- Upgrade QA on a restored disposable clone: both module upgrades succeeded and the focused native suite passed **2/2**. The clone was dropped.
- Local rollout: verified mode-0600 `namaa_ksa` backup, upgraded `be_tender` to .4 and `namaa_ai_bridge` to .41, rebuilt React/BFF images and restarted the services. Authenticated CRM read returned both new fields; browser opened the editor without creating business data.
- CRM editor visual refinement: focused browser suite **8/8**, React units **90/90**, production build passed. [Live screenshot](build-engine/frontend/screenshots/crm-construction-code-editor-live.png).
- Evidence: [Checkpoint 336](build-engine/CHECKPOINT_336.md), [native QA JSON](build-engine/CRM_SCOUTING_NATIVE_QA.json), and [live QA JSON](build-engine/CRM_SCOUTING_LIVE_QA.json).

## Checkpoint 331 — Live Project Manager BOQ revision workflow (2026-10-27)

- Isolated clone Odoo suite: **30 post-test cases, 0 failures, 0 errors** across `be_boq` and selected named BOQ bridge tests.
- Authenticated live React → temporary BFF → Odoo Project Manager journey: **1/1 passed**. Updated a draft from 10 × SAR 100 to 12 × SAR 110, reopened it, compared it with the earlier same-project baseline, and verified after reload.
- Native readback: current BOQ **SAR 1,320**, version 7; prior closed baseline remains **SAR 1,000** with original quantity/rate. Stale-version retry was rejected without a write.
- QA clone restored from a verified 0600 archive, then dropped. Temporary BFF/Odoo worker removed. Shared `namaa_ksa` unchanged. BE-049 remains **PARTIAL** pending independent reviewer/cross-company, Arabic/accessibility and full A1–A4 acceptance. See [Checkpoint 331](build-engine/CHECKPOINT_331.md) and [live QA evidence](build-engine/BOQ_DRAFT_REVISION_LIVE_QA.json).

## Checkpoint 330 — Versioned BOQ draft editing and revision comparison (2026-10-27)

- Focused React BOQ Playwright suite: **6/6 passed**. The draft-edit + approved-revision journey edits version 4, verifies the version 5 total, and renders changed quantity/rate against the earlier same-project baseline.
- Disposable `namaa_ksa` clone: Odoo post-test result **30 cases, 0 failures, 0 errors** across the `be_boq` suite and selected bridge cases for draft edit/version/baseline, revision comparison immutability and project/UOM access boundaries.
- Clone dropped; shared `namaa_ksa` was not changed. The browser journey mocks the BFF/Odoo boundary, so authenticated live Project Manager/Owner acceptance remains open. BE-049 remains **PARTIAL**. See [Checkpoint 330](build-engine/CHECKPOINT_330.md) and [machine-readable QA](build-engine/BOQ_DRAFT_REVISION_QA.json).

## Checkpoint 329 — Equipment and Accounting KSA asset linking (2026-10-27)
- Disposable clone of `namaa_ksa` restored from a mode-0600 custom-format backup. `be_equipment_accounting` installed and `namaa_ai_bridge` upgraded to .40 in the clone for QA. After tests, a separate verified 0600 backup was made and `be_equipment_accounting` installed in the local demo; `namaa_ai_bridge` remains .39.
- Odoo `be_equipment_accounting` post-install suite: **9 cases, 0 failures, 0 errors**. Covers same-company open-asset registration link, unique-link constraint, role denial, direct-write/create denial and existing retirement controls.
- Backend focused equipment contract/API tests: **5 passed, 11 subtests passed**. React units: **89/89**. Focused Equipment register/checkout/return Playwright journey: **1/1**. Vite production build passed; existing >500 kB JavaScript chunk advisory remains.
- Authenticated React → BFF → Odoo admin smoke passed; the equipment form shows the selector. Odoo currently returns zero eligible active-company assets; no business record was created. Non-admin accounting-role and multi-company acceptance remain open. QA details: [Checkpoint 329](build-engine/CHECKPOINT_329.md), [machine-readable evidence](build-engine/EQUIPMENT_ASSET_LINK_QA.json).

## Checkpoint 328 — Reusable BOQ spreadsheet mappings (2026-10-27)

- Isolated Odoo mapping-template access and company-scope test: **1 passed** on disposable `be_qa_boq_mapping_20261027`, upgraded to `namaa_ai_bridge` .39. The shared `namaa_ksa` database was not changed.
- Backend business suite: **220 passed, 314 subtests passed**.
- React unit suite: **89/89 passed**; focused BOQ mapping save/apply/revalidate/import Playwright: **1/1 passed**; Vite production build passed.
- Python `compileall` and scoped `git diff --check` passed. Vite reports the existing 1.33 MB minified JS bundle advisory.
- After isolated QA, local `namaa_ksa` was upgraded .38→.39 after a verified 0600 archive backup. Authenticated React→BFF→Odoo list/readback passed; one English demo mapping was seeded and read back; no BOQ business record was created.
- See [Checkpoint 328](build-engine/CHECKPOINT_328.md) and [machine-readable QA](build-engine/BOQ_MAPPING_TEMPLATES_QA.json).

## Checkpoint 327 — Auditable BOQ spreadsheet imports (2026-10-27)

- Isolated clean-database Odoo retry/provenance/security test: **1 passed**. Verified persisted metadata, identical retry, rejection of changed import source, mapping validation and immutable provenance. Disposable DB dropped.
- Backend business API + BOQ import suites: **224 passed, 314 subtests passed**. React BOQ spreadsheet-import Playwright journey: **1 passed**, including gateway retry and persisted audit display after reopening. Backend/React production images built; React bundle size advisory remains.
- Local Namaa schema upgraded after a verified 0600 archive backup; `be_boq` .6 and `namaa_ai_bridge` .37 confirmed. Authenticated, read-only React → BFF → Odoo BOQ/options smoke passed; no shared business rows created. See [Checkpoint 327](build-engine/CHECKPOINT_327.md) and [QA](build-engine/BOQ_IMPORT_HISTORY_QA.json).

## Checkpoint 326 — Arabic BOQ spreadsheet import (2026-10-27)

- BE-050 parser tests: **5 passed**. Combined backend business API and BOQ import tests: **224 passed, 314 subtests passed**. `git diff --check` passed.
- Arabic headings receive mapping suggestions; Arabic-Indic/Persian digits and Arabic grouping/decimal separators parse; Arabic item types map to native types; mapping one column to multiple fields is rejected.
- This was a parser-only change; no Odoo schema, runtime or business data changed. Native Odoo/live import journey was not rerun. BE-050 remains PARTIAL. See [Checkpoint 326](build-engine/CHECKPOINT_326.md) and [QA](build-engine/BOQ_IMPORT_ARABIC_QA.json).

## Checkpoint 325 — React scouting-agent Q&A (2026-10-27)

- Backend scouting AI/chat tests: **6 passed**. Business API suite: **219 passed**, including CSRF, request/history validation and scoped snapshot delegation.
- React scouting Playwright journey: **1/1 passed**. Native Odoo test on a disposable clone: **1/1 passed**, verifying current finding visibility, stale finding suppression, inaccessible candidate and role denial.
- Live isolated React → BFF → Odoo → Qwen 3.8 27B → Odoo journey: **1/1 passed across two turns**. The follow-up included the preceding Q&A as bounded context; each turn cited the current CRM source and returned `read_only: true`, `saved: false`. Existing finding review and audit were also verified. Clone and temporary services removed; source `namaa_ksa` unchanged.
- Python compilation and `git diff --check` passed. BE-027 remains PARTIAL because transcript storage, broader role/company acceptance, Arabic model-quality and full A1–A4 acceptance remain. See [Checkpoint 325](build-engine/CHECKPOINT_325.md) and [machine-readable QA](build-engine/CRM_SCOUTING_AI_LIVE_QA.json).

## Checkpoint 324 — Build Engine employee own-timesheet access (2026-10-27)

- Isolated `be_project` role mapping test: **1/1 passed**; BE User, Project Manager, Site and Owner imply native own-timesheet entry, while no Build Engine role implies Timesheets Approver. Clone dropped.
- Live React → BFF → Odoo journey as a general BE User: **1/1 passed**. Created and corrected a task entry; native readback confirmed signed-in employee/company/project/task, 3 hours, idempotency metadata, and recalculated SAR 150 labor cost. Disposable database dropped.
- Applied the verified group mapping to local `namaa_ksa`; SQL confirmed `be_base.group_be_user` implies `hr_timesheet.group_hr_timesheet_user`. Odoo restarted; React, progress and Odoo endpoints returned HTTP 200.
- BE-089 remains PARTIAL: timesheet review/approval, broader role/company acceptance and full story acceptance remain open. See [Checkpoint 324](build-engine/CHECKPOINT_324.md), [role QA](build-engine/TIMESHEET_ROLE_QA.json) and [live QA](build-engine/TIMESHEET_LIVE_QA.json).

## Checkpoint 323 — Supplier qualification visibility (2026-10-27)

- Isolated Odoo supplier suite: **6/6 passed**, including current/pending/expired qualification counts and the no-read-access boundary. Disposable clone dropped; shared `namaa_ksa` unchanged.
- Focused supplier React browser journey: **1/1 passed**. Full React unit suite: **89/89 passed**. Vite production build passed; existing large JS bundle advisory remains.
- The isolated QA runner now updates already installed `be_supplier` and `namaa_ai_bridge` modules before selecting the post-install test class; previous runs that only initialized an already installed module selected zero tests and were not accepted as evidence.
- BE-059 remains PARTIAL: qualification evidence requirements, approval matrix/selection policy and full story acceptance remain open. See [Checkpoint 323](build-engine/CHECKPOINT_323.md) and [native QA](build-engine/SUPPLIER_QUALIFICATION_NATIVE_QA.json).

## Checkpoint 322 — Company CRM trade and tender criteria (2026-10-27)

- Clean-install Odoo mandate test: **1/1 passed**, including persistence/reopen, company isolation, source allowlist and rejection of duplicate, empty, oversized and non-printable codes. Clone dropped; source unchanged.
- Isolated live Owner React → BFF → Odoo workflow: **1/1 passed**. Native readback verified trade codes `HVAC`, `civil`, category `BUILDING/FITOUT`, company, actor and timestamp.
- Isolated live React → BFF → Qwen 3.8 27B → Odoo → independent human review workflow: **1/1 passed**. Pending cited assessment, uncertainty, separate decision and audit were verified; all temporary resources removed and `namaa_ksa` unchanged.
- Backend focused tests: **6 passed**. React **89/89**, mocked CRM scouting browser **1/1**, production build passed. Vite continues to warn that the minified JS bundle is over 500 KB.
- BE-003 remains PARTIAL: CRM leads do not yet carry trade/category match fields; external official tender catalog/feed and full story acceptance remain open. See [Checkpoint 322](build-engine/CHECKPOINT_322.md) and [QA reports](build-engine/CRM_SCOUTING_NATIVE_QA.json).

## Checkpoint 321 — React internal-transfer payment visibility (2026-10-27)

- Isolated native Odoo payment-register suite: **8/8 passed**, including paired-leg metadata/search and the native one-leg reversal denial. Disposable clone `be_payment_register_qa_9fb075f1` was dropped; source `namaa_ksa` was not modified.
- React payment-register Playwright journey: **1/1 passed**; verified transfer label, counterpart details, paired-reference search, and absence of a one-leg reversal action. React unit suite: **89/89 passed**.
- Vite production build passed. The bundle-size warning remains: JavaScript output is approximately 1.33 MB minified.
- Two-leg reversal remains unimplemented pending DEC-27. Full AR/AP lifecycle and accountant UAT remain open. See [Checkpoint 321](build-engine/CHECKPOINT_321.md) and [native QA report](build-engine/ACCOUNTING_PAYMENTS_REGISTER_QA.json).

## Checkpoint 320 — CRM mandate allowlist and AI review acceptance (2026-10-27)

- Clean-install native Odoo mandate/source/company test: **1/1 passed**. It verifies allowed-source persistence and query filtering, AI snapshot scope, invalid input preservation, forged tenant field denial, unauthorized reader denial, and foreign-company lead exclusion.
- Isolated live Owner workflow: **1/1 passed** through React → BFF → Odoo; the allowed source selection survived refresh and company, saved actor/time and filtered candidates were visible.
- Isolated live AI/review workflow: **1/1 passed** through React → BFF → Qwen 3.8 27B → Odoo. It saved the allowlist, excluded a same-company lead from another source, generated a pending cited draft with uncertainty, then persisted a distinct human decision. Odoo readback verified mandate source, lead source, excluded candidate, reviewer and audit event. Clone and temporary services removed; source DB unchanged.
- Focused backend tests: **2 passed, 10 subtests passed**, including field-level validation and forged `company_id` rejection before Odoo RPC. React **89/89**, mocked browser **1/1**, production build passed.
- The local demo stack was updated with the additive `be_ai` 20.0.1.0.6 source relation and matching BFF/React. Read-only live candidate smoke returned 14 source options; shared business records were not written. Backup: `/tmp/namaa_ksa_before_scouting_source_allowlist_20261027.dump`.
- BE-019 is now DONE. Totals: **19 DONE, 132 PARTIAL, 3 MISSING, 10 BLOCKED / 164**. See [Checkpoint 320](build-engine/CHECKPOINT_320.md) and [QA evidence](build-engine/CRM_SCOUTING_AI_LIVE_QA.json).

## Checkpoint 319 — CRM scouting source allowlist (2026-10-27)

- Clean-install native Odoo scouting QA: **1 passed**; allowed source candidates were returned, excluded-source candidates filtered, source choices persisted, unknown/duplicate IDs rejected, and a CRM reader denied.
- Isolated live React → BFF → Odoo Owner journey: **1 passed**, including visible company name and saved actor/time, source selection, and candidate filtering. Disposable DB and temporary services removed; source databases unchanged.
- Focused backend contract/route tests: **2 passed, 10 subtests passed**. React units **89/89**, focused mocked scouting browser **1/1**, Vite production build passed.
- Local demo rollout followed QA: `be_ai` 20.0.1.0.6 installed, React/BFF rebuilt, and live read-only candidate smoke returned 14 CRM source options. A pre-upgrade DB dump is at `/tmp/namaa_ksa_before_scouting_source_allowlist_20261027.dump`; no shared business records were changed. BE-019 remains PARTIAL. See [Checkpoint 319](build-engine/CHECKPOINT_319.md), [native evidence](build-engine/CRM_SCOUTING_NATIVE_QA.json), [live evidence](build-engine/CRM_SCOUTING_LIVE_QA.json), and [screenshot](build-engine/frontend/screenshots/crm-scouting-live.png).

## Checkpoint 318 — React bank-match review and payment reversal

- Native Odoo payment suite: **7/7** on a disposable clone, including authorized statement-match metadata and reversal refusal before unmatching.
- React unit suite: **89/89**; focused mocked payment-to-reconciliation browser journey: **1/1**; isolated live payment workflow browser journeys: **2/2**.
- Live React → BFF → Odoo readback confirmed exact statement-line navigation, native undo, payment reversal, zero remaining statement matches, posted reversal and reopened invoice residual of **SAR 75**.
- Production build passed with the existing large-chunk advisory. Disposable clone and temporary BFF removed; shared `namaa_ksa` business records unchanged. See [Checkpoint 318](build-engine/CHECKPOINT_318.md) and [isolated QA JSON](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json).

## Previous — Checkpoint 317 — filtered payment CSV export

- CSV helper tests: **4 passed** for authenticated multi-page fetch behavior, formula neutralization, quoting and the 5,000-row cap/lookahead.
- React unit suite: **89/89**; React payment browser suite: **5/5** (page navigation, CSV download with all 51 rows, search reset, English/Arabic preview, and preview export hidden).
- Native Odoo payment suite: **6/6**; isolated authenticated React→BFF→Odoo workflow: **1/1**, including CSV readback with the receipt, grouped payment, linked invoices and reversal reason (3 payment rows).
- Production build passed (large-chunk advisory remains). Clone and temporary BFF removed; shared business records unchanged. See [Checkpoint 317](build-engine/CHECKPOINT_317.md) and [isolated QA JSON](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json).

## Previous — Checkpoint 316 — paginated React payment register

- Native Odoo payment tests: **6/6**, including company scope, read permissions and stable non-overlapping offset pages on a disposable clone.
- Focused backend payment-register route test: **1 passed**; search, state, limit and offset are forwarded, with bounds checked.
- React units **85/85**; payment browser suite **5/5**, including mocked authenticated paging across 51 rows, Next/Previous, filter reset, and Arabic/English preview regressions.
- Production Vite build passed (large-chunk advisory remains). Isolated React→BFF→Odoo payment lifecycle suite passed **1/1** for partial receipt, exact grouped allocation, draft cancellation and posted reversal.
- No live `namaa_ksa` business records were changed. BE-160 remains PARTIAL; payment export and broader accountant acceptance remain open. See [Checkpoint 316](build-engine/CHECKPOINT_316.md).

## Previous — Checkpoint 315 — posted payment reversal

- Native Odoo payment suite: **6 tests, 0 failures/errors** on a disposable clone.
- Backend reversal contract, route and reversed-state filter: **3 passed**, with **5 validation subcases**.
- React units: **85/85**. Payment preview browser suite: **4/4**. Production Vite build passed (large-chunk advisory remains).
- Authenticated live React→BFF→Odoo journey: **1/1 passed**. A posted SAR 200 receipt was reversed through Odoo's native wizard; native readback confirmed the posted reversal and open invoice balances SAR 300/SAR 150. Exact allocation and draft cancellation were rechecked.
- Reversal replay, conflicting retry, required reason, company-role denial, and bank-statement/internal-transfer boundaries are covered. Clone and temporary BFF removed; `namaa_ksa` unchanged. See [Checkpoint 315](build-engine/CHECKPOINT_315.md) and [QA JSON](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json).

## Checkpoint 314 — exact grouped payment allocation

- Native Odoo `payment_register` suite: **5 tests, 0 failures/errors** on a disposable `namaa_ksa` clone.
- Backend allocation contract and route: **2 passed**, including **10 validation subcases**.
- React units: **85/85**. Payment preview browser suite: **4/4**. Vite production build passed (existing large-chunk advisory only).
- Authenticated React→BFF→Odoo live browser journey: **1/1 passed**. A SAR 450 payment was split as SAR 200 and SAR 250, leaving SAR 100 and SAR 150 open on the two invoices. Partial receipt and draft cancellation readbacks also passed.
- QA clone and temporary BFF removed; source `namaa_ksa` unchanged. Evidence: [Checkpoint 314](build-engine/CHECKPOINT_314.md) and [QA JSON](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json).

## Checkpoint 313 — React draft payment cancellation (2026-10-27)

- Added a current-company, native-permission guarded Odoo action that cancels only draft payments with no posted journal entry. Repeat cancellation is safe; posted/reconciled payments require native reversal. React exposes the bilingual action for live draft rows only; preview has no write path.
- Isolated native payment tests **4/4 passed**. Targeted backend payment tests **5 passed**. Authenticated React→BFF→Odoo browser journey **1/1 passed**, covering partial receipt, grouped multi-invoice allocation and draft cancellation. Odoo confirmed final draft state `canceled`; balances for the payment journeys matched expected readback.
- The disposable database clone and temporary BFF were removed; source `namaa_ksa` was not modified. Python compilation, browser-test syntax, and `git diff --check` passed. React unit suite 85/85 and production build passed; the existing large-chunk advisory remains.
- Fixed existing payment payload validation so impossible calendar dates are rejected at the contract boundary.
- Evidence: [Checkpoint 313](build-engine/CHECKPOINT_313.md), [isolated QA JSON](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json), [native tests](../addons/namaa_ai_bridge/tests/test_accounting_payments.py), [live browser test](../frontend/e2e/accounting-document-payment.live.spec.js), [screenshot](build-engine/frontend/screenshots/live-accounting-payment-draft-canceled.png). BE-160 remains PARTIAL; story totals are 18 DONE, 133 PARTIAL, 3 MISSING, 10 BLOCKED.

- Focused native Odoo payment-register suite: **3 tests, 0 failures/errors** on a disposable clone. Verified one native grouped payment against two open invoices, linked invoice records, residuals, idempotent replay, over-allocation and invalid currency precision rejection, and bounded open-document listing.
- Authenticated live React → BFF → Odoo browser journey: **1 passed** on a separate disposable clone. One SAR 450 payment was applied across two invoices; the returned native document balances total SAR 250. Screenshot: [live allocation](build-engine/frontend/screenshots/live-accounting-payment-allocation.png).
- Targeted BFF contract/route tests: **4/4**; React units **85/85**; payment preview browser suite **3/3**; Vite production build passed.
- QA clone and temporary BFF removed; no source records changed. After runtime rebuild/restart, a read-only local admin smoke at `localhost:3200` verified sign-in, the live Allocation tab and HTTP 200 from the native open-document endpoint (0 eligible records); public ngrok `/demo.html` served Checkpoint 312. BE-160 remains PARTIAL because pooled allocations follow Odoo’s native order; exact per-invoice splits, reversal, full AR/AP lifecycle and accountant UAT remain open.
- Evidence: [Checkpoint 312](build-engine/CHECKPOINT_312.md), [isolated QA](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json), [native tests](../addons/namaa_ai_bridge/tests/test_accounting_payments.py), [BFF tests](../backend/tests/test_business.py), [live browser test](../frontend/e2e/accounting-document-payment.live.spec.js).

## Checkpoint 311 — React accounting payments register (2026-10-27)

- Isolated Odoo 20 native QA: **2 tests, 0 failures/errors** on a disposable clone. Verified current-company search/status listing, linked source invoice, payment journal/amount/direction, actor/time, invalid input rejection, reader denial and exclusion of another company's payment.
- Authenticated live React → BFF → Odoo: **1 journey passed** on a separate disposable clone. A finance user recorded a SAR 200 partial receipt against a SAR 500 invoice, then searched and reopened the saved payment with its linked invoice and accountant name. Native readback confirmed SAR 300 residual and the stored idempotency key.
- Backend business suite: **213 passed** (292 subtests); React units **85/85**; English desktop and Arabic mobile preview journeys **2/2**; Vite production build passed with the existing chunk-size advisory; Python compilation and `git diff --check` passed.
- Both QA clones and the temporary BFF were removed; shared `namaa_ksa` was unchanged. BE-160 remains PARTIAL; reversals, multi-document allocation, full AR/AP lifecycle, broader role/currency coverage and accountant UAT remain open.
- Evidence: [native QA](build-engine/ACCOUNTING_PAYMENTS_REGISTER_QA.json), [live QA](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json), [Checkpoint 311](build-engine/CHECKPOINT_311.md), [React browser flow](../frontend/e2e/accounting-document-payment.live.spec.js).

## Checkpoint 310 — company onboarding and sample construction project (2026-10-27)

- Isolated Odoo QA: **4 tests, 0 failures/errors** on disposable clone `be_onboarding_qa_60ee6511`; checklist/company persistence, actor/time audit, invalid input/no partial write, stale revision rejection, Owner-only and foreign-company denial, linked sample project/tasks, idempotency and unchanged accounting move count passed. Clone dropped and source `namaa_ksa` unchanged.
- Backend business suite: **212 passed** (292 subtests), including field-level note validation before Odoo is called, all onboarding bridge routes and same-origin write boundary.
- React unit suite: **85/85 passed**; bilingual responsive onboarding preview browser journey **1/1 passed**; production build passed with existing large-chunk advisory.
- Python compilation and `git diff --check` passed. Shared runtime rollout was not performed; `be_onboarding` is not installed in `namaa_ksa`.
- Evidence: [Checkpoint 310](build-engine/CHECKPOINT_310.md), [isolated QA JSON](build-engine/ONBOARDING_QA.json), [Odoo tests](../odoo/addons/be/be_onboarding/tests/test_be_onboarding.py), and [React browser flow](../frontend/e2e/onboarding.spec.js).

## Checkpoint 309 — scheduled in-app role digests (2026-10-27)

- Isolated Odoo 20 QA: **2 tests, 0 failures/errors** on disposable clone `be_notifications_qa_2ad47468`; Owner matrix/audit/stale-revision, Project Manager restrictions, daily/weekly schedule, idempotent generation, personal read-state and company/user scope passed. The clone and QA-only OCA `report_xlsx` copy were removed; shared `namaa_ksa` was unchanged.
- Backend business suite: **211 passed** (286 subtests); includes strict full-matrix contract and authenticated route/mutation-boundary checks.
- React unit suite: **85/85 passed**; notification Playwright flow **1/1 passed**; production build passed with existing large-chunk advisory.
- Python compilation and `git diff --check` passed. Live shared runtime rollout was not performed; `be_dashboard` is not installed and runtime addons omit `report_xlsx`.
- Evidence: [Checkpoint 309](build-engine/CHECKPOINT_309.md), [isolated QA JSON](build-engine/NOTIFICATIONS_QA.json), [Odoo bridge tests](../addons/namaa_ai_bridge/tests/test_notifications.py), [React browser test](../frontend/e2e/notifications.spec.js).

## Previous — Checkpoint 308 — React role notifications (2026-10-27)

Checkpoint 308 verified the first React notification center and role preference matrix. Scheduled generation and read tracking are covered by Checkpoint 309 above.

## Checkpoint 307 — React site attendance and HR review (2026-10-27)

- Isolated Odoo 20 attendance model/bridge QA: **4 tests, 0 failures/errors** on disposable clone `be_site_attendance_qa_0bf9e533`; clone dropped and source `namaa_ksa` unchanged.
- Backend business suite: **209/209 passed**; focused attendance contract/route suite **3/3 passed**.
- React unit suite: **85/85 passed**; focused Site/HR attendance browser journeys **2/2 passed**; Vite production build passed with the existing large-chunk advisory.
- Python compilation, Docker Compose configuration and `git diff --check` passed.
- Scope: source/isolated QA only. The `be_site` module and attendance capability were not installed/enabled in shared `namaa_ksa`. Official HR attendance/payroll reconciliation and live Odoo role/company acceptance remain open.
- Evidence: [Checkpoint 307](build-engine/CHECKPOINT_307.md), [isolated QA JSON](build-engine/SITE_ATTENDANCE_QA.json), [native tests](../odoo/addons/be/be_site/tests/test_be_site.py), [bridge tests](../addons/namaa_ai_bridge/tests/test_site_attendance.py), [React browser tests](../frontend/e2e/site-attendance.spec.js).

## Checkpoint 306 — Permission-filtered project-document search pagination (2026-10-27)

- Isolated Odoo 20 DMS QA: **5 tests, 0 failures/errors; 4 passed and 1 conditional skip** on disposable clone `be_project_docs_87ecc0e4`. Verified extracted-text matches across pages, filename search, page metadata, invalid offset/limit rejection, and existing project/DMS boundaries. Clone dropped; shared `namaa_ksa` unchanged.
- Backend suite: **206/206 passed**; React document browser Playwright: **2/2 passed**; React unit suite: **85/85 passed**; production build passed with the existing chunk-size advisory.
- Python compilation, `docker compose config --quiet` and `git diff --check` passed.
- Evidence: [Checkpoint 306](build-engine/CHECKPOINT_306.md), [isolated QA JSON](build-engine/PROJECT_DOCUMENTS_DMS_QA.json), [native tests](../odoo/addons/be/be_project_documents/tests/test_project_document.py), [React browser tests](../frontend/e2e/project-documents.spec.js).

## Checkpoint 305 — Background project-document indexing and content search (2026-10-27)

- Isolated Odoo 20 DMS QA: **5 tests, 0 failures/errors; 4 passed and 1 conditional skip** on disposable clone `be_project_docs_29ed4a0a`. Coverage includes bounded TXT/Office extraction, malformed Office package rejection, current-revision-only background indexing, content search, folder setup, immutable revisions and access boundaries. Clone dropped; shared `namaa_ksa` unchanged.
- React project-document Playwright suite: **2/2 passed**.
- Backend suite: **206/206 passed**; React unit suite: **85/85 passed**; Vite production build passed (existing chunk-size advisory).
- Evidence: [Checkpoint 305](build-engine/CHECKPOINT_305.md), [isolated QA JSON](build-engine/PROJECT_DOCUMENTS_DMS_QA.json), [native tests](../odoo/addons/be/be_project_documents/tests/test_project_document.py), [React browser tests](../frontend/e2e/project-documents.spec.js).

## Checkpoint 304 — Project document folder setup and reader/upload boundary (2026-10-27)

- Odoo 20 QA on disposable clone `be_project_docs_22ded2de`: **3 passed, 1 skipped**. The skip checks behavior when optional DMS is absent, while this suite installs DMS. Passing cases cover folder setup repeatability, company-scoped root and six standard folders, PM/Owner provisioning, reader access without upload capability, reader setup/upload denial, immutable revisions/idempotency/stale checks, DMS group and cross-project boundaries. The clone was dropped; source `namaa_ksa` unchanged.
- React project-document Playwright suite: **2/2 passed**, including mocked setup → folder navigation → upload → revision → history and folder browse/download.
- Backend suite: **206/206 passed**; React unit suite: **85/85 passed**; production build passed.
- Python compilation, `docker compose config --quiet` and `git diff --check` passed before the final QA runner report-label change. No shared runtime/schema change.
- Evidence: [Checkpoint 304](build-engine/CHECKPOINT_304.md), [isolated QA JSON](build-engine/PROJECT_DOCUMENTS_DMS_QA.json), [native tests](../odoo/addons/be/be_project_documents/tests/test_project_document.py), [React browser tests](../frontend/e2e/project-documents.spec.js).

## Checkpoint 303 — React project document upload and immutable revisions (2026-10-27)

- Odoo 20 QA on disposable clone `be_project_docs_59bf3ab7`: **2 passed, 1 skipped**. It verified upload, revision 2, byte/checksum persistence, uploader, idempotent retry, immutable content/deletion, stale revision denial, current-only listing, readable history, denied upload outside the DMS create group and cross-project history denial. The skipped browser test requires OCA DMS to be absent; DMS is installed in this suite. Clone dropped; source `namaa_ksa` unchanged.
- React project-document Playwright suite: **2/2 passed**, covering folder navigation/download and mocked first upload, revision upload and history display.
- Backend unit suite: **205/205 passed**; React unit suite: **85/85 passed**; Vite production build passed.
- Python compilation, `docker compose config --quiet` and `git diff --check` passed before the final Playwright-only test addition. Shared Odoo/React services were not deployed/restarted; OCA DMS and `be_project_documents` remain absent from shared `namaa_ksa`.
- Evidence: [Checkpoint 303](build-engine/CHECKPOINT_303.md), [isolated QA JSON](build-engine/PROJECT_DOCUMENTS_DMS_QA.json), [Odoo regression](../odoo/addons/be/be_project_documents/tests/test_project_document.py), [React browser regression](../frontend/e2e/project-documents.spec.js).

## Checkpoint 302 — React project documents through OCA DMS (2026-10-27)

- Native Odoo DMS bridge tests: **2 passed, 0 failures/errors** on disposable clone `be_project_docs_d1200670`; clone dropped and `namaa_ksa` unchanged. It verified project-linked folder navigation, file bytes, project/folder mismatch denial and explicit DMS-group read denial. The full OCA DMS suite is separately recorded as **77/77** in Checkpoint 301; it was not rerun here.
- React mocked Playwright project-document navigation/download: **1 passed**.
- Backend suite: **204 passed**; React unit suite: **85 passed**; Vite production build passed.
- Python compilation, `docker compose config --quiet`, and `git diff --check` passed.
- Shared runtime deployment was not performed. OCA DMS is not installed in shared `namaa_ksa`; the Odoo process was not restarted to load the new addon path.

## Checkpoint 298 — BE-155 risk owner assignment (2026-10-27)

- Backend strict request contract and authenticated BFF route tests: **2 passed**; React project-report browser suite: **3 passed**; Python compilation and diff whitespace check passed.
- Native Odoo project report bridge suite: **7 passed, 0 failures, 0 errors** on disposable clone be_project_report_live_2d5322c4.
- Live React → BFF → Odoo/Qwen project report browser journeys: **2 passed**. The Owner reviewed the risk draft and assigned its schedule finding to the PM; native ORM readback verified one project-linked mail activity and one risk_owner_notified audit event with matching report, project/company, actor, recipient, category, rationale and source ID.
- The risk report and closeout lessons remained review artifacts. Project write_date remained unchanged. The clone, temporary Odoo server, BFF container and QA image were removed; the source database was unchanged.
- BE-155 remains PARTIAL pending broader ordinary-user/company matrices, Arabic evaluation, explicit field-level BFF error mapping and complete A1–A4. Evidence: [Checkpoint 298](build-engine/CHECKPOINT_298.md), [live QA JSON](build-engine/PROJECT_REPORTS_LIVE_QA.json), [assignment screenshot](build-engine/frontend/screenshots/live-project-risk-owner-assigned.png).

## Checkpoint 297 — BE-157 closeout lessons (2026-10-27)

- Backend closeout-lessons generator tests: **3 passed**. React unit suite: **85 passed**; focused project-report browser suite: **2 passed**. Vite production build passed.
- Native Odoo source/revision/role/persistence suite: **6 passed** on a disposable clone. Live authenticated React → BFF → Qwen 3.8 27B → Odoo PM/Owner journeys: **2 passed** (BE-151 risk and BE-157 lessons).
- Odoo readback confirmed separate PM author and Owner reviewer, exact closeout/task/RFI source IDs, approved review state and unchanged project write date. Clone and temporary BFF/Odoo processes removed; shared `namaa_ksa` unchanged.
- BE-157 remains PARTIAL for broader production role/company acceptance, live Arabic evaluation and complete A1–A4. See [Checkpoint 297](build-engine/CHECKPOINT_297.md), [live QA](build-engine/PROJECT_REPORTS_LIVE_QA.json), and screenshots [draft](build-engine/frontend/screenshots/live-project-lessons-draft.png) / [reviewed](build-engine/frontend/screenshots/live-project-lessons-reviewed.png).

## Checkpoint 295 — BE-037 live AI-prioritized daily follow-up (2026-10-27)

- Backend generator/BFF boundary tests: **6 passed**; React unit suite: **85 passed**; focused productivity browser suite: **19 passed**; isolated Odoo native source/citation/stale-data tests: **2 passed**.
- Live acceptance: **1 authenticated React → BFF → Qwen 3.8 27B → Odoo browser journey passed** on a disposable clone. The Sales user generated and reopened the pending cited draft; direct Odoo ORM readback confirmed pending state, exact `mail.activity`/`crm.lead` sources, and unchanged open activity.
- Clone, temporary BFF and temporary frontend install removed; source QA DB unchanged. See [live QA JSON](build-engine/TASK_FOLLOWUP_LIVE_QA.json), [screenshot](build-engine/TASK_FOLLOWUP_LIVE_SCREENSHOT.png), and [Checkpoint 295](build-engine/CHECKPOINT_295.md).
- BE-037 remains PARTIAL pending broader role/company and full A1–A4 acceptance; story totals remain 18 DONE, 126 PARTIAL, 10 MISSING, 10 BLOCKED.

## Checkpoint 294 — BE-037 follow-up activity validation (2026-10-27)

- Backend task boundary regression: **1 passed**. Whitespace-only summary and impossible/noncanonical dates return 422 and do not call Odoo.
- React productivity unit suite: **5 passed**; focused browser suite: **17 passed** (the React workspace was unchanged in this increment; see Checkpoint 294).
- Odoo native bridge regression on a disposable current-source clone: **1 passed**, including no-partial-activity assertions for invalid summary/date. Clone dropped; source database unchanged.
- The initial native invocation was discarded because its container omitted Build Engine addon mounts and ran zero tests. The corrected invocation mounted current addon sources and executed the selected regression.
- Evidence and classification: [Checkpoint 294](build-engine/CHECKPOINT_294.md), [QA JSON](build-engine/TASK_FOLLOWUP_VALIDATION_QA.json). BE-037 is PARTIAL pending AI prioritization/recommendations and broader A1–A4.

## Checkpoint 293 — current-source charter and closeout acceptance (2026-10-27)

- Restored a temporary source snapshot of current `namaa_ksa` into the isolated construction QA Postgres instance because the older `be_qa_demo_full_20261025` baseline failed before browser QA on an unrelated orphaned product record. The stale source was not modified.
- Charter/AI journey: **7 native tests passed** and **1 authenticated React → BFF → Qwen → Odoo browser journey passed**. A PM drafted/submitted, an independent Owner approved, and the source-cited AI suggestion remained pending.
- Closeout journey: **6 native tests passed** and **1 authenticated React → BFF → Odoo browser journey passed**. The PM recorded all seven attestations; reopen confirmed the saved closure and actor.
- Both QA clones, BFFs and the temporary source copy were dropped. The original `namaa_ksa` DB was unchanged. Screenshots are in `docs/build-engine/frontend/screenshots/`.
- BE-046/048/148 remain PARTIAL: approval/evidence policy, automated finance/stock reconciliation, Arabic/role/company and A1–A4 work remain. See [Checkpoint 293](build-engine/CHECKPOINT_293.md) and [QA evidence](build-engine/PROJECT_CHARTER_LIVE_QA.json) / [closeout evidence](build-engine/PROJECT_CLOSEOUT_LIVE_QA.json).

## Checkpoint 292 — construction project schema repair (2026-10-27)

- Disposable clone upgrade moved `be_project` from 20.0.1.0.5 to 20.0.1.0.8 and created `be_project_charter`, `be_project_charter_event`, and `be_project_closeout`.
- Targeted `TestBeProjectCharter` / `TestBeProjectCloseout`: **9 passed, 0 failures, 0 errors**. The disposable clone was dropped.
- Removed root-package `tests` imports from `be_boq_mrp` and `be_equipment_accounting`. On another clone, targeted BOQ/MRP and equipment-accounting suites passed **11/11**, with no CRITICAL, ERROR or traceback logs; clone dropped. Shared Odoo restart after the fix also had no test-import errors.
- Backed up shared `namaa_ksa` to `/tmp/namaa_ksa_before_be_project_upgrade_20261027.dump` (mode 0600), applied the upgrade, and verified module version/tables by SQL. Odoo health, React home, Odoo login and BFF health returned healthy/HTTP 200.
- Authenticated read-only Odoo model calls from the live service returned the charter register and closeout state for project 1; no records were changed.
- Feature stories BE-046 and BE-048 remain PARTIAL; schema presence is not full end-user acceptance. See [Checkpoint 292](build-engine/CHECKPOINT_292.md) and [rollout evidence](build-engine/PROJECT_MODEL_SCHEMA_ROLLOUT_QA.json).

## Checkpoint 291 — BE-081 project-attributed cash flow (2026-10-27)

- Isolated Odoo `TestAccReports`: **8 passed, 0 failures, 0 errors**. Regression verifies a 50% analytic share of a SAR 100 cash move appears as SAR 50 project-attributed movement; project-filtered output omits company opening/closing cash balances.
- Isolated Accounting KSA security/report API suite: **15 passed, 0 failures/errors**, including finance-user access to project-filtered Cash Flow and rejection of analytic filters on unsupported report types.
- BFF report/PDF/XLSX boundary tests: **3 passed**. React accounting-reports Playwright: **1 passed**, including P&L and Cash Flow project-filter query. Vite production build passed.
- Authenticated finance-user React→BFF→Odoo acceptance on a fresh disposable clone: **1 passed**. The report returned the exact SAR 50 allocated project outflow, omitted company opening/closing balances, and returned valid filtered XLSX and PDF downloads. Native readback confirmed the project/company/account scope. QA clone and temporary services were removed.
- After saving a protected backup and upgrading the shared local demo runtime, the admin React smoke on `localhost:3200` passed against `namaa_ksa`: project-filtered Cash Flow returned SAR 50, omitted company balances, and downloaded valid XLSX/PDF. The only added accounting example is a labeled draft entry, not posted.
- Python compile and `git diff --check` passed. A first full-suite attempt caught a stale test account-cache fixture; after fixing the fixture, the full class passed.
- Isolated clone QA left its source unchanged. The separate shared demo `namaa_ksa` runtime was updated with a protected backup available at `/tmp/namaa_ksa_before_project_cf_deps_20261027.dump`. This is not full BE-081 acceptance: broader role/company access, Arabic/accessibility review, accountant UAT and full A1–A4 remain open. Odoo also logs existing missing-table messages for three `be.project.*` models; see [Checkpoint 291](build-engine/CHECKPOINT_291.md), [native QA JSON](build-engine/PROJECT_CASH_FLOW_QA.json), and [live QA JSON](build-engine/PROJECT_CASH_FLOW_LIVE_QA.json).

## Checkpoint 290 — BE-023 Owner lead qualification (2026-10-27)

- Isolated clone of `namaa_ksa`; targeted Owner qualification regression: **1 passed, 0 failures, 0 errors**.
- Owner persisted a reasoned `maybe` decision and reviewer/time audit. The lead stayed a lead; no AI suggestion or automatic promotion was created.
- Clone dropped; shared `namaa_ksa` unchanged. This is native Odoo evidence; a live React Owner journey was not run.
- BE-023 moves to PARTIAL because the existing React/Odoo qualification path supports manual Owner decisions, while live Owner acceptance and the BD AI source-backed suggestion flow remain open.
- See [Checkpoint 290](build-engine/CHECKPOINT_290.md) and [QA JSON](build-engine/CRM_QUALIFICATION_OWNER_QA.json).

## Checkpoint 289 — BE-132 permission-checked DMS export (2026-10-27)

- Installed OCA DMS and upgraded `namaa_ai_bridge` on a disposable clone of `namaa_ksa`; targeted native archive test passed **1/1**, zero failures/errors.
- Verified both attachment-backed and database-backed DMS file bytes/checksums, and verified the backing `ir.attachment` was not duplicated through generic project-file export. A project owner without access to the group-restricted directory was denied; the denied request created no second export.
- The exporter refuses to create an archive if the active user cannot read every active DMS file linked to the project; this prevents silently incomplete archives and DMS ACL bypass.
- The clone was dropped; shared `namaa_ksa` was not modified. OCA DMS full regression evidence separately reports **77/77** passed.
- Python compilation and `git diff --check` passed. BFF/browser journeys were not rerun. DMS remains absent from the current shared runtime addon path.
- See [Checkpoint 289](build-engine/CHECKPOINT_289.md), [archive integration QA](build-engine/DMS_ARCHIVE_EXPORT_QA.json), and [OCA DMS QA](build-engine/OCA_DMS_ACL_QA.json). BE-132 remains PARTIAL for runtime rollout, knowledge items, wider role/company acceptance and full A1–A4.

## Checkpoint 288 — OCA DMS Odoo 20 ACL and attachment path (2026-10-27)

- Focused DMS storage attachment lifecycle test passed after the DMS file create path validated directory-level create permission and elevated only Odoo's linked attachment write. Focused ACL and directory-copy tests from the preceding investigation remain passing.
- Fresh full DMS suite on an isolated clone: **2 failures, 0 errors / 77 tests**. Remaining: email-alias attachment routing and portal file download (HTTP 404 after direct file-token validation passes).
- This run used a disposable clone, then dropped it. Shared `namaa_ksa` and source QA database were unchanged; DMS remains uninstalled and BE-132 continues to exclude DMS-managed files. See [Checkpoint 288](build-engine/CHECKPOINT_288.md) and [QA report](build-engine/OCA_DMS_ACL_QA.json).

## Previous — Checkpoint 287 — OCA DMS Odoo 20 Binary read contract (2026-10-27)

The focused `FileDatabaseTestCase.test_compute_content` now checks Odoo 20’s structured Binary read value (`content`, `size`) and verifies payload/size against the raw ORM `BinaryBytes`; both DMS manager/user subtests passed. Full DMS suite on a disposable clone: **10 failures + 24 errors / 77 tests**, improved from 12 + 24 after updating the Odoo 20 byte decoding. Remaining directory ACL fixture, portal, storage, attachment, alias and move failures are unresolved. Clone dropped; shared `namaa_ksa` unchanged. See [Checkpoint 287](build-engine/CHECKPOINT_287.md) and [QA report](build-engine/OCA_DMS_ACL_QA.json).

## Checkpoint 286 — OCA DMS Binary decoding and file metadata (2026-10-27)

Fixed DMS base64 byte decoding at the Odoo Binary boundary while retaining raw Odoo `BinaryBytes`. On a disposable Odoo clone, **4/4** focused tests passed for the conversion contract, PDF extension, SVG/JPEG MIME detection and image thumbnail. Full DMS regression improved to **12 failures + 24 errors / 76 tests**, from 16 + 24 before this change; the earlier ACL fixture diagnosis remains relevant. Clone dropped; shared `namaa_ksa` unchanged; DMS remains uninstalled. See [Checkpoint 286](build-engine/CHECKPOINT_286.md) and [QA report](build-engine/OCA_DMS_ACL_QA.json).

## Checkpoint 285 — OCA DMS ACL test-harness investigation (2026-10-27)

The focused root-directory-copy failure was instrumented on a disposable clone. The Odoo `@users` decorator ran the test subcases as DMS manager/user, while the class-level record’s environment remained basic-user UID 223; the DMS access group contained UIDs 225 and 226. A controlled user-bound directory copy passed with `permission_create=True`. This explains the copy ACL cascade only. Full DMS suite remains red (**16 failures, 24 errors / 76 tests**) for other unresolved areas. Temporary instrumentation was restored, clones were dropped and shared `namaa_ksa` was unchanged. No access rules were relaxed. See [Checkpoint 285](build-engine/CHECKPOINT_285.md) and [QA report](build-engine/OCA_DMS_ACL_QA.json).

## Checkpoint 284 — BE-132 directly project-linked attachments (2026-10-27)

- Focused isolated Odoo archive/export lifecycle/security test: **1/1 passed**. It included and checksum-verified a direct project attachment; a different project’s attachment was excluded. Drawing revisions and approved/pending submittal cases remained covered.
- Authenticated live React → BFF → Odoo browser journey: **1/1 passed** on disposable clone `be132_live_58611527`. Odoo readback verified private export attachment, proposal/BOQ/drawing/approved-submittal/project-attachment bytes, manifest checksums, foreign project attachment exclusion, pending submittal exclusion, reader denial and foreign-company denial. Clone/BFF/image removed; shared `namaa_ksa` unchanged.
- BFF **2/2** and React units **85/85** carry forward from Checkpoint 281; not rerun. OCA DMS was not installed; its previously recorded ACL suite (15 failures + 24 errors / 80) remains a blocker to directory-based DMS export.
- BE-132 remains PARTIAL for OCA DMS ACL repair/integration, knowledge items, broader role/company matrix and full React-first A1–A4. See [Checkpoint 284](build-engine/CHECKPOINT_284.md) and [QA JSON](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json).

## Checkpoint 283 — BE-132 approved submittal revision files (2026-10-27)

- Focused isolated Odoo archive/export lifecycle and security test: **1/1 passed**. It included a superseded and issued drawing revision, included an approved submittal file and excluded a pending submittal file; source bytes and manifest checksums were verified.
- Authenticated live React → BFF → Odoo browser: **1/1 passed** on disposable clone `be132_live_445e97f4`. Odoo readback verified private ZIP link/checksum, proposal/BOQ/drawing/approved-submittal bytes, manifest metadata/checksums, pending-submittal exclusion, and reader/foreign-company denials. Clone/BFF/image removed; shared `namaa_ksa` unchanged.
- BFF export routes **2/2** and React unit suite **85/85** are inherited from Checkpoint 281, not rerun. Offline bilingual manual verifier passed **291/291 screenshots**, English/Arabic desktop/mobile layouts, no overflow or external requests.
- BE-132 remains PARTIAL: general project DMS files and knowledge items, broader role/company matrix, and complete React-first A1–A4 remain. See [Checkpoint 283](build-engine/CHECKPOINT_283.md) and [QA JSON](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json).

## Checkpoint 282 — BE-132 issued drawing revisions in project archive export (2026-10-27)

- Focused isolated Odoo archive/export lifecycle/security test: **1/1 passed**. It included a superseded and an issued drawing revision, checked drawing bytes and manifest SHA-256, and verified a draft drawing was excluded.
- Authenticated live React → BFF → Odoo browser journey: **1/1 passed** on disposable clone `be132_live_d44b1641`. Odoo readback confirmed private export attachment, project/company/actor/rationale/state, proposal and BOQ source checksums, issued drawing content and manifest reference/checksum. Read-only and foreign-company probes were denied.
- Disposable clone and temporary BFF/image were removed; shared `namaa_ksa` was unchanged. The offline bilingual manual verifier passed **291/291 screenshots**, with EN/AR desktop and phone layouts, no horizontal overflow and no external requests. The BE-132 BFF route tests **2/2** and React unit tests **85/85** are inherited from checkpoint 281 and were not rerun in this slice.
- BE-132 remains PARTIAL: project submittal/DMS attachments and knowledge items are not included; wider role/company matrix and React-first A1–A4 acceptance remain. See [Checkpoint 282](build-engine/CHECKPOINT_282.md) and [QA JSON](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json).

## Checkpoint 278 — BE-128 approved proposal and BOQ archive pack

- Fresh isolated all-custom-module Odoo 20 run: **382 passed, 0 failed, 0 errors** on `be_qa_20261026_233654_08d7`. After a final archive retry/locking refinement, focused `TestCrmTechnicalProposal`: **12 passed, 0 failures/errors** on the same isolated database. The flow created an independently approved proposal archive, confirmed BOQ baseline, rendered the BOQ report to a real PDF, stored both private PDFs with SHA-256 checksums, checked list/download/retry behavior, immutable audit metadata and denied an ordinary reader.
- Backend focused suite: **4 passed**, including strict rationale/ID contracts, project options/list/create calls, company-bound private PDF delivery and invalid-artifact rejection.
- React unit suite: **85/85 passed**. Project archive Playwright journey: **1/1 passed**, including selecting both approved sources, entering a rationale, creating the pack and verifying the two project-scoped PDF links. Vite production build passed; its existing bundle-size advisory remains.
- `namaa_ksa` was not changed. The 382-test all-module suite ran before the final archive-only retry/locking refinement; the affected proposal archive class was rerun successfully after that change. No other Odoo source changed between those runs.
- BE-128 stays PARTIAL: live ordinary-role React→BFF→Odoo acceptance, broader company/role boundaries, Arabic visual review and full A1–A4 remain open. See [Checkpoint 278](build-engine/CHECKPOINT_278.md) and [QA JSON](build-engine/PROJECT_PROPOSAL_BOQ_ARCHIVE_QA.json).

## Checkpoint 277 — React structured daily reports and offline queue (2026-10-27)

- Storage unit tests **3/3**; full React unit suite **85/85**; mocked offline/reconnect and structured capture browser journeys **2/2**.
- BFF daily-log nested contract/route **1/1**.
- Isolated Odoo upgrade plus focused `be_site` and `namaa_ai_bridge` suites **125 passed, 0 failed/errors**.
- Isolated authenticated Site-role React → BFF → Odoo browser **1/1**: queued structured daily report offline, synced after reconnect, reopened it from the register, confirmed manpower/delivery/delay data, replayed the exact payload to the same row, and received 422 for changed payload. Native Odoo readback confirmed one correct actor/company/project/date/text record and all child rows; QA fixtures were cleaned.
- The earlier clean custom-module suite **380/380 passed** at Checkpoint 276, before the structured daily-log models. It is not represented as the full current-source result. Shared `namaa_ksa` is unchanged; `be_site` remains uninstalled.
- Limitations: no offline app shell/auth restore, device soak, attachment/photo sync, multi-device conflict resolver or encrypted browser storage; DEC-07 remains open. BE-113/114 remain PARTIAL.
- Full details: [Checkpoint 277](build-engine/CHECKPOINT_277.md), [QA evidence](build-engine/SITE_DAILY_LOGS_OFFLINE_QA.json).

## Checkpoint 276 — React daily site reports (2026-10-27)

- Focused native Odoo run on isolated DB `be_qa_20261026_225136_e44c`: daily-report role/company/project/idempotency test **1/1 passed** using current source.
- Initial full clean custom-module run: **380 tests, 0 failures, 1 error** in `TestNamaaBridge.test_react_boq_revision_comparison_reads_immutable_same_project_snapshots`. Traced to `_namaa_boq_baseline_summary` missing `return result`; fixed it. Two correspondence test fixtures were also made timezone/private-project-safe. Bridge suite passed **118/118**; final full custom-module suite passed **380/380**, 0 failures/errors.
- BFF route contract **1/1**, mocked React browser **1/1**, live authenticated Site-role React→BFF→Odoo **1/1**, React unit **82/82**, Vite production build, Python compile and `git diff --check` passed. Native readback confirmed actor/project/company/date/text, identical retry reused the same record, changed-content retry returned 422, and QA seed cleanup was verified.
- Local React and demo page HTTP 200; new daily-log options route returned expected unauthenticated 401. Shared `namaa_ksa` was not changed; `be_site` remains uninstalled there. Live React→BFF→Odoo acceptance passed on an isolated QA database; enabling the capability in shared namaa_ksa remains open.
- Full evidence: [Checkpoint 276](build-engine/CHECKPOINT_276.md), [QA JSON](build-engine/SITE_DAILY_LOGS_QA.json), final Odoo full log at `/tmp/be_qa_full_retest.log` inside `build-engine-odoo-1`.

## Checkpoint 275 — BE-072 connected purchase-to-site material cost

- On a disposable clone of `namaa_ksa`, the QA runner installed `be_site` (uninstalled in source) and upgraded the relevant addons. Source DB and module state stayed unchanged.
- Created an approved BOQ-linked PO for 8 tracked material units at SAR 40, received all 8 into the project bin, then created and accountant-posted the matched vendor bill for SAR 320 untaxed / SAR 368 total with the project analytic distribution.
- Live React Warehouse Officer flow issued 6 units of the received lot and returned 2 to the project yard. Odoo verified 4 units remaining and 4 units / SAR 160 net BOQ material actual. The bill's SAR 320 untaxed vendor-bill analytic was separately recorded and not counted as consumed material.
- Existing serial issue/return journey also passed: two unique serials issued, one exact serial returned; net SAR 55 / one unit actual.
- Focused native Odoo tests **2/2**, live React → BFF → Odoo browser **1/1**. QA clone and temporary BFF removed; source unchanged. `be_site` remains uninstalled in shared `namaa_ksa`, so this local database still hides the material issue tab.
- BE-072 remains PARTIAL pending DEC-18 cost policy, broader roles/companies and A1–A4. See [Checkpoint 275](build-engine/CHECKPOINT_275.md), [live QA](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json) and [BOQ screenshot](build-engine/frontend/screenshots/live-site-material-serial-issue-boq-actuals.png).

## Checkpoint 274 — BE-079 receipt-controlled project material bill

- Native `namaa_ai_bridge` vendor-bill regressions passed **2/2**; authenticated live React → BFF → Odoo accountant journey passed **1/1** on an isolated clone.
- A same-company PO had 3 BOQ-linked material units at SAR 125.50; React exposed 2 invoiceable units after receiving 2, with 1 backordered. A SAR 999 UI price was ignored; Odoo persisted the PO price and project analytic distribution.
- Accountant-posted bill produced a SAR 251 analytic ledger entry against the linked project and BOQ line. BOQ commitment remained 3 / SAR 376.50. Material actual remained 0 until site issue, per current cost policy.
- OCR draft retry remained idempotent; mismatched retry returned 422; reader role received 403 and created no bill. Clone and temporary BFF removed; source `namaa_ksa` unchanged.
- BE-077/079 remain PARTIAL pending site-issue reconciliation, representative supplier scans, broader role/company coverage, accountant UAT and A1–A4. See [Checkpoint 274](build-engine/CHECKPOINT_274.md), [QA evidence](build-engine/VENDOR_BILL_OCR_LIVE_QA.json) and [matched bill screenshot](build-engine/frontend/screenshots/vendor-bill-po-match-live.png).

## Checkpoint 273 — BE-066 React receipt to project/site bin

- Authenticated live React → temporary clone-bound BFF → Odoo Playwright acceptance: **2 passed** (lot-tracked partial receipt to selected project bin; serial-tracked partial receipt).
- Odoo verified the lot move's selected project-linked destination, quantity **5** in the destination, PO received **5**, and backorder **2**. Serial receipt persisted **2** unique serials at one unit each; PO received **2** and backorder **1**.
- Disposable QA clone and temporary BFF/image were removed; source QA database unchanged. QA script compiled successfully.
- BE-066 stays PARTIAL pending broader warehouse route, role/company, returns/quality and supplied A1–A4 acceptance. See [Checkpoint 273](build-engine/CHECKPOINT_273.md) and [live QA JSON](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json).

## Checkpoint 272 — BE-078 live Saudi milestone billing

- Focused native `be_progress_billing` Odoo suite: **5 passed, 0 failures/errors**.
- Authenticated live React → BFF → Odoo journey: **1 passed**. A finance reader received **403**; a separate accountant created the draft from an approved SAR 200 certificate.
- Odoo postconditions verified one company/customer/source-linked `out_invoice` in draft, retry returned the same invoice, and 15% sales VAT yielded **SAR 200 untaxed + SAR 30 tax = SAR 230**.
- Disposable clone and temporary BFF/image were removed; cleanup passed and source QA DB remained unchanged. Invoice was not posted or sent to ZATCA.
- BE-078 remains PARTIAL pending retention/advance rules, wider role/company acceptance, accountant/customer UAT and complete A1–A4. See [Checkpoint 272](build-engine/CHECKPOINT_272.md), [live QA](build-engine/PROGRESS_BILLING_LIVE_QA.json) and [screenshot](build-engine/frontend/screenshots/live-progress-billing-draft.png).

## Checkpoint 267 — BE-058 React BOQ manufacturing BoM

- Fresh Odoo database installing `be_boq_mrp`: **3 tests passed, 0 failures/errors**. Matching product, mismatched product, cross-company relation and approved-baseline snapshot verified.
- Fresh Odoo database installing `namaa_ai_bridge` and dependencies: focused bridge suite **2 tests passed, 0 failures/errors**. Options, persisted result, product derivation, product mismatch and foreign-company rejection verified.
- React BOQ units **6/6**; backend contract test **1 passed** with four subtests; focused mocked Playwright BOQ journey **1/1**. Python compilation and `git diff --check` passed.
- Both disposable Odoo databases were dropped and verified; `namaa_ksa` was not changed. A cloned demo DB with an existing dangling product reference failed during registry loading before focused tests and was dropped; it is excluded from passing results.
- Live ordinary Project Manager React → BFF → Odoo journey: **1/1 passed**, including create, fresh sign-in after reload, reopen, unlink, relink and confirm. Native checks verified the confirmed BOQ line and baseline line both reference the selected BoM. See [live QA JSON](build-engine/BOQ_MRP_LIVE_QA.json), [Checkpoint 267](build-engine/CHECKPOINT_267.md), and [native/bridge QA JSON](build-engine/BE_BOQ_MRP_QA.json).
- The live runner uses an ephemeral Vite port, restarts the isolated Odoo worker after addon installation to reload its registry, and grants the QA Project Manager the required Stock/MRP read role. Disposable DB/BFF cleanup passed; source DB unchanged.

## Checkpoint 266 — BE-080 VAT-inclusive bank reconciliation

- Fresh isolated Odoo `TestReconcileEngine`: **27 passed, 0 failures, 0 errors**.
- Authenticated React → temporary BFF → Odoo browser suite: **4 passed** (cash forecast, partial invoice payment, reconciliation/undo, and reconciliation cases including VAT, overpayment, FX, split receipts, multi-invoice receipts, supplier payment and modeled short receipt).
- Native postconditions verified the synthetic SAR 115 bank debit as SAR 100 expense base + SAR 15 Saudi `15%` purchase VAT, reconciled with zero suspense.
- The source `namaa_ksa` database was cloned for QA and left unchanged. The clone and temporary BFF were removed; cleanup checks passed.
- Python compilation, JavaScript syntax and `git diff --check` passed. Screenshots: `live-bank-fee-vat-review.png` and `live-bank-fee-vat-posted.png`.
- See [Checkpoint 266](build-engine/CHECKPOINT_266.md) and [machine-readable QA](build-engine/BANK_RECONCILIATION_LIVE_QA.json).

## Previous — Checkpoint 265 — Accounting KSA bank-map support check

- Read-only Odoo shell on the current `namaa_ksa` runtime confirmed the map model and bridge method are in the active registry.
- The manager read returned one company-scoped map and one bank journal. No create/update/delete was performed.
- The earlier missing-map-model error was not reproduced; its original process/database/user are unknown. This is not a role-matrix acceptance test.
- See [Checkpoint 265](build-engine/CHECKPOINT_265.md).

## Checkpoint 264 — BE-079 React accountant bilingual OCR

- Isolated clone of `namaa_ksa`: native bridge tests **2 passed**; authenticated React accountant/reader browser journey **1 passed**.
- React upload of the bilingual Saudi scan yielded invoice reference/date, vendor identified by 15-digit VAT number, SAR 1,000 untaxed + SAR 150 VAT = SAR 1,150, and the OCR review state. Native record checks confirmed the company/accountant, one line, and draft/unposted state.
- Separate reader role received HTTP 403 from options and create routes and created no vendor bill. PO matching also passed; submitted UI price SAR 999 was ignored in favor of Odoo's approved SAR 125.50 PO price.
- Isolated database and temporary BFF were removed; `namaa_ksa` remained unchanged. Supplier-issued scans and full accountant acceptance remain open. See [Checkpoint 264](build-engine/CHECKPOINT_264.md), [React/Odoo QA](build-engine/ACCOUNTING_KSA_ARABIC_OCR_REACT_QA.json), and [underlying live run](build-engine/VENDOR_BILL_OCR_LIVE_QA.json).

## Checkpoint 263 — BE-079 bilingual Saudi vendor-bill OCR

- Added a synthetic bilingual Arabic/English invoice scan and a native Odoo regression through the real document-import path. It checks Arabic text, invoice reference/date, Saudi VAT vendor matching, SAR untaxed/tax/total values, and draft-only state.
- Fresh isolated Odoo database `be_ocr_qa_20261026`, focused `/accounting_ksa:TestBillOcr`: **18 tests, 0 failures, 0 errors**. Log: `namaa-odoo20-odoo-1:/tmp/be_ocr_arabic_qa_20261026_final.log`.
- New companies now default to `eng+ara`; existing company settings remain unchanged. Existing companies require an administrator to choose `eng+ara` to recognize Arabic scans.
- Fixture is synthetic. Real supplier-issued invoice accuracy and accountant/PO-match UAT remain open. See [Checkpoint 263](build-engine/CHECKPOINT_263.md) and [Arabic OCR QA](build-engine/ACCOUNTING_KSA_ARABIC_OCR_QA.json).

## Checkpoint 262 — BE-079 scanned vendor-bill OCR runtime

- Added a native OCR regression using the real scanned vendor-bill PDF fixture; it verifies OCR text and that the created bill remains draft.
- Fresh isolated Odoo database `be_ocr_qa_20261026`, targeted `/accounting_ksa:TestBillOcr`: **17 tests, 0 failures, 0 errors**. Log: `namaa-odoo20-odoo-1:/tmp/be_ocr_qa_20261026.log`.
- Actual local runtime check extracted 527 characters from the scanned PDF and 570 from the bill photo with `eng+ara`; installed language data reports Arabic and English, and Poppler executables are present.
- Odoo service returned HTTP 200 after rebuilding its OCR layer. The existing `namaa_ksa` database was not the QA database; no bill was posted. Arabic-text accuracy remains unverified. See [Checkpoint 262](build-engine/CHECKPOINT_262.md) and [runtime evidence](build-engine/ACCOUNTING_KSA_OCR_RUNTIME_QA.json).

## Checkpoint 261 — BE-036 React project archive follow-up

- Full `frontend/e2e/business.spec.js`: **27 passed**, including direct Project workspace navigation, accessible project selection, archive listing and project-scoped PDF link construction, plus the CRM approval/archive flow.
- React units: **80 passed**; Vite production build passed with the existing bundle-size advisory.
- This is a React-only follow-up. Odoo **373/373** and backend **238 passed, 2 skipped** remain the clean Checkpoint 260 results; this follow-up did not rerun them.
- Browser API responses are mocked. Live Odoo access and target-runtime PDF acceptance remain open. See [Checkpoint 261](build-engine/CHECKPOINT_261.md) and [BE-036 QA](build-engine/TECHNICAL_PROPOSAL_ARCHIVE_QA.json).

## Checkpoint 260 — BE-036 technical proposal archive

- Fresh clean all-module Odoo 20 run: **373 tests, 0 failures, 0 errors** on isolated database `be_qa_20261026_185819_9e25`; run log is inside `build-engine-odoo-1` at `/tmp/be_qa_20261026_185819_9e25.log`.
- Full backend suite: **238 passed, 2 skipped, 265 subtests passed**.
- React unit suite: **80 passed**; focused Playwright synthetic review → archive → link journey: **1 passed**; production build passed.
- Python compilation, QWeb XML parse and `git diff --check` passed.
- Native tests cover approval separation, stale-source refusal, invalid PDF refusal, private attachment bytes, idempotency, immutability and download serialization. Backend tests cover company mismatch, invalid PDF signatures and private no-store responses.
- Automated Odoo lifecycle data was created in disposable QA. The local demo rollout updated the addon schema only; no business records were created or edited. Browser test is mocked; target-runtime PDF visual, Arabic and live role acceptance remain open. See [Checkpoint 260](build-engine/CHECKPOINT_260.md) and [machine-readable QA](build-engine/TECHNICAL_PROPOSAL_ARCHIVE_QA.json).

## Checkpoint 252 — BE-153 variation impact suggestions

- Backend generation schema/citation tests: **4 passed**. Backend business/API suite, including two new route-boundary cases: **178 passed**.
- Native Odoo lifecycle/security tests on isolated database `be_qa_20261026_154127_22a9`: **4 passed, 0 failures/errors**. Checks covered PM save/reopen, no official variation/BOQ mutation, stale-source rejection, invalid citations, reader/other-company denial and submitted-variation rejection.
- React unit suite: **80 passed**. Contract browser journey covering generate, render, cite and advisory-only notice: **1 passed**. Vite production build passed.
- Corrected clean all-module run, including `namaa_ai_bridge`, passed **354 tests with zero failures/errors** in isolated database `be_qa_20261026_154521_105e`. The database is retained for inspection. `scripts/run_odoo_qa.py` now installs and tests the React/Odoo integration addon used by project charter and daily-safety bridge tests.
- The Playwright screenshot uses mock Odoo/model responses and is illustrative UI evidence, not live-model acceptance: [variation impact panel](build-engine/frontend/screenshots/react-variation-impact-en-1440.png).
- No live Qwen/browser/database role journey has been executed for BE-153. Full Arabic evaluation and story A1–A4 remain open.
- See [Checkpoint 252](build-engine/CHECKPOINT_252.md) and [focused native evidence](build-engine/VARIATION_IMPACT_NATIVE_QA.json).

## Checkpoint 251 — BE-152 supplier RFQ AI draft and human authorization

- Focused native Odoo lifecycle/security suite on isolated clone: **4 passed, 0 failures/errors**. Added an explicit PM capability assertion for the React action.
- Focused backend RFQ/request contract and route tests: **8 passed, 17 parameterized subtests passed**, 172 deselected.
- Authenticated React → BFF → local Qwen 3.8 27B → Odoo Playwright journey: **1 passed** using separate PM and Procurement sessions. PM generated a source-cited pending draft; Procurement reviewed with rationale and authorized exactly one linked draft PO.
- Database postconditions verified distinct author/reviewer, active company, purchase request/line, supplier, project and BOQ citations; request moved to in-progress; order stayed draft; single-order idempotency and zero supplier emails.
- The QA clone, BFF container and image were removed. Source DB remained unchanged. Odoo was restarted after installing/upgrading dependencies on the disposable clone so the live HTTP path used current model classes.
- See [Checkpoint 251](build-engine/CHECKPOINT_251.md), [native evidence](build-engine/PURCHASE_RFQ_AI_NATIVE_QA.json) and [live evidence](build-engine/PURCHASE_RFQ_AI_LIVE_QA.json).

## Checkpoint 250 — BE-154 project status/RFI report drafts

- Focused backend tests: **9 passed**, 172 deselected; 7 parameterized subtests passed.
- Isolated Odoo 20 `namaa_ai_bridge` report lifecycle/security tests: **3 passed, 0 failures/errors**.
- Live React → authenticated BFF → local Qwen 3.8 27B → Odoo two-role journey: **1 passed** on a disposable clone. PM generated an RFI report, then a separate Owner approved its review with a rationale.
- Database postconditions verified report creator/reviewer/company, exact project/RFI citations, unchanged RFI `open` state, no applied report, and no project mutation. Clone dropped and source DB unchanged.
- Ollama constrained JSON schema, strict backend validation, and production source citation checks passed in the live call. Manual model quality, Arabic evaluation, broader role/company UAT and full A1–A4 remain open.
- Evidence: [Checkpoint 250](build-engine/CHECKPOINT_250.md), [live QA JSON](build-engine/PROJECT_REPORT_LIVE_QA.json), and [screenshots](build-engine/frontend/screenshots/live-project-rfi-report-approved.png).

## Checkpoint 249 — lifecycle template live verification

- Native Odoo 20: **2 passed, 0 failures/errors** on isolated QA clone.
- Authenticated React → BFF → Odoo Playwright journey: **1 passed**.
- Postconditions verified template stage/transition graph, three approver types, immutable published v1, editable copied v2, project-type assignment and new-project inheritance.
- Clone dropped; source database unchanged.
- See [Checkpoint 249](build-engine/CHECKPOINT_249.md) and [live QA JSON](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

## Checkpoint 248 — BE-046 project charter approval

- Isolated Odoo 20 clone: **3 tests passed, 0 failures/errors**; lifecycle, required content, independent review, immutable snapshots, rejection/revision, unauthorized role and foreign company covered.
- Backend charter contract and route tests: **2 passed**; malformed payloads/project identity and missing mutation header rejected before writes.
- React mocked Playwright: **1 passed**; draft creation, submission, pending state and requester self-review denial.
- Authenticated two-role React → BFF → Odoo browser journey: **1 passed** on a disposable clone. Separate PM and Owner sessions submitted/approved; saved actors, project/company, state and event order verified. Clone and temporary services removed; source database unchanged.
- BE-046 remains PARTIAL pending DEC-25 content/approver confirmation, production role/tenant acceptance and full A1–A4. See [Checkpoint 248](build-engine/CHECKPOINT_248.md), [live QA](build-engine/PROJECT_CHARTER_LIVE_QA.json) and [traceability](REQUIREMENTS_TRACEABILITY.md).

## Checkpoint 247 — BE-048 React project closeout certification

- Isolated Odoo 20 clone: **6 tests passed, 0 failures/errors**; tested PM closeout persistence/reopen, immutability, incomplete checks, open punch blocker, unauthorized user and foreign company. Clone dropped.
- BFF contract and HTTP boundary tests: **2 passed**; strict invalid payload and missing mutation header prevented Odoo calls.
- React unit tests: **80 passed**; closeout Playwright mock journey: **1 passed**, including required checklist and saved-state reopen.
- Authenticated live React → BFF → Odoo Playwright journey: **1 passed** on a disposable clone. The saved closeout state, PM actor, company and still-active project were checked after the browser flow. Clone and temporary BFF removed; source DB unchanged.
- BE-048 remains PARTIAL: reconciliation and handover values are manager attestations; DEC-21 control/evidence policy and full A1–A4 remain open. Evidence: [Checkpoint 247](build-engine/CHECKPOINT_247.md), [native/React QA](build-engine/PROJECT_CLOSEOUT_QA.json), [live QA](build-engine/PROJECT_CLOSEOUT_LIVE_QA.json).

## Checkpoint 246 — Odoo native sidebar submenu

- Authenticated live Playwright check on `namaa_ksa`: Build Engine arrow changed `aria-expanded` false → true and showed its submenu; no browser errors.
- Odoo 20 Owl 3 compatibility fixed using `signal.Object`; module upgraded to `20.0.1.0.4`.
- Partner progress page regenerated and republished at `/demo.html`. Evidence: [Checkpoint 246](build-engine/CHECKPOINT_246.md).

## Checkpoint 236 — supplier quote compliance evidence

- Isolated current-source Odoo quote-capture test: **1 passed, 0 failures/errors**.
- Disposable clone React → BFF → Odoo supplier quote journey: **1 passed**. Database postcondition verified price, reference, dates, company/project, line compliance status/evidence/reviewer/time and draft state.
- Clone `be_supplier_quote_qa_42b72c60`, isolated Odoo process and temporary BFF were removed; cleanup postconditions passed. Shared `namaa_ksa` was not modified by this QA journey.
- React production image build passed. Existing large-chunk advisory remains.
- Evidence: [Checkpoint 236](build-engine/CHECKPOINT_236.md) and [QA JSON](build-engine/PURCHASE_QUOTE_LIVE_QA.json).

## Checkpoint 234 — React procurement recommendation review

- React unit suite: **80 passed, 0 failed**.
- Live Playwright browser smoke at `:3200`: signed into `namaa_ksa`, opened AI Workspace and rendered the empty recommendation state with no browser errors.
- Playwright `e2e/productivity.spec.js`: **17 passed, 0 failed**. This includes synthetic approve/reject flows, required rejection reason, read-only viewer controls, and existing responsive/Arabic AI and activities regression cases.
- Vite production build passed; it reports the existing large main-chunk advisory (1,094.82 kB minified).
- Isolated clone of current `namaa_ksa`: installed current-source `be_ai`; complete tagged Odoo suite: **13 tests, 0 failures, 0 errors**. Odoo ran on HTTP port 8077 so it did not contend with the demo server.
- QA clone was dropped and absence verified. After QA, `be_ai 20.0.1.0.2` was installed on local `namaa_ksa` and the React container was rebuilt. Authenticated runtime check verified `can_read=true`, `can_review=true`, and zero pending suggestions; no suggestion or purchasing record was generated.
- `git diff --check` passed for this implementation slice. See [Checkpoint 234](build-engine/CHECKPOINT_234.md).

# Build Engine test results

## Checkpoint 281 — BE-132 React project archive ZIP export

- Focused native Odoo archive/export lifecycle and security test: **1 passed, 0 failures, 0 errors** while upgrading `namaa_ai_bridge` on disposable clone `be132_live_698d6532`.
- Focused BFF export contract and route tests: **2 passed**; invalid rationale returned 422 without an Odoo write, and ZIP delivery verified company binding, content type, checksum header, `private, no-store`, and download disposition.
- React unit suite: **85 passed**. Authenticated React→BFF→Odoo browser journey: **1 passed** on the disposable clone. The PM created the archive and export, viewed the persisted history, and downloaded the ZIP; the browser verified the `PK` signature and SHA-256 response header. A reader and foreign-company project/export-history probes were denied with 403.
- Odoo readback verified the immutable export record and private linked attachment, project/company, PM actor, rationale, `exported` state, whole-ZIP checksum, both embedded PDFs against the source archive checksums, and manifest source references. The QA database, BFF and temporary image were removed; shared `namaa_ksa` was unchanged.
- Evidence: [Checkpoint 281](build-engine/CHECKPOINT_281.md), [live QA JSON](build-engine/PROJECT_ARCHIVE_EXPORT_LIVE_QA.json), [React screenshot](build-engine/frontend/screenshots/live-project-archive-export.png). BE-132 remains PARTIAL because project DMS files, drawings and knowledge content are not yet included in this ZIP; broader role/company coverage and full A1–A4 remain open.
- Portable user manual rebuild and offline browser QA: **291/291 screenshots decoded**, EN/AR at desktop 1440px and phone 390px with no horizontal overflow, BE-132 chapter and screenshot searchable, zero external requests or browser errors. See [manual QA](build-engine/frontend/MANUAL_QA.json) and [manual HTML](../frontend/public/user-manual.html).

## Checkpoint 280 — BE-045 live React project milestone and obligation acceptance

- Authenticated ordinary-Project-Manager React→BFF→Odoo journey: **1 passed** on disposable clone `be_project_plan_live_qa_665c51de`, sourced from `be_qa_20261026_233654_08d7`.
- The PM enabled project milestones, created a stakeholder handover obligation linked to a responsible person and foundation task, then reopened the project plan. Native readback verified the saved milestone, stakeholder, responsible person, task, company/project and actor links.
- The linked task was still open, so the milestone could not be marked reached. Invalid blank task input returned HTTP 422; unauthorized and foreign-company writes were denied. Existing native bridge milestone lifecycle/security regression tests remain in `addons/namaa_ai_bridge/tests/test_bridge.py`; this live run explicitly executed the related native project-plan test **1/1** during module update.
- Clone and temporary BFF/image were removed; shared `namaa_ksa` was unchanged. BE-045 remains PARTIAL pending broader role/tenant, Arabic/accessibility and full A1–A4 acceptance.
- Evidence: [Checkpoint 280](build-engine/CHECKPOINT_280.md), [live QA JSON](build-engine/PROJECT_PLAN_LIVE_QA.json), [React screenshot](build-engine/frontend/screenshots/live-project-plan-crew-dependencies.png).

## Checkpoint 279 — BE-128 live React → BFF → Odoo acceptance

- Authenticated live browser journey: **1 passed** on a disposable clone of `be_qa_20261026_233654_08d7`.
- Project Manager created a proposal/confirmed-BOQ archive pack through React. Both private PDFs returned HTTP 200, PDF content type, private no-store headers and valid PDF signatures.
- Separate read-only account and the Project Manager's foreign-company project probe both received HTTP 403. Odoo readback verified actor, company, project, proposal, baseline, rationale, private attachment ownership and SHA-256 checksums.
- Temporary database clone, BFF and image were removed; `namaa_ksa` was unchanged. Evidence: [live QA JSON](build-engine/PROJECT_PROPOSAL_BOQ_ARCHIVE_LIVE_QA.json), [checkpoint](build-engine/CHECKPOINT_279.md), [screenshot](build-engine/frontend/screenshots/live-project-proposal-boq-archive.png).
- Earlier BE-128 results remain: focused Odoo 12/12 after the final archive refinement, full isolated Odoo 382/382 before that refinement, backend 4/4, React 85/85 and build passed. BE-128 stays PARTIAL for broader role/company, Arabic visual and complete A1–A4 acceptance.

## Checkpoint 271 — BE-055/056 live contract variation lifecycle

- Focused native variation-impact lifecycle/security tests: **4 passed, 0 failures/errors**.
- Authenticated React → BFF → Qwen 3.8 27B → Odoo browser journey: **1 passed**. PM reviewed the advisory and submitted; a separately authenticated Owner approved/applied it.
- Odoo postconditions verified the pending AI advisory remained non-mutating, the approved variation kept SAR 750 amount, the BOQ quantity changed 100→110 exactly once, the Owner was the last actor, the variation baseline captured 110 and the previous snapshot retained 100.
- Disposable clone dropped and absence verified; Odoo restarted; cloned source database unchanged. See [Checkpoint 271](build-engine/CHECKPOINT_271.md) and [live QA JSON](build-engine/VARIATION_IMPACT_LIVE_QA.json).

## Checkpoint 270 — BE-054 baseline reset authorization and immutable snapshot

- Fresh isolated Odoo `be_boq` `TestBeBoq`: **24 passed, 0 failures, 0 errors**. New lifecycle test proves PM reset denial, Owner reset acceptance, draft-edit separation from the baseline snapshot and baseline-line write denial.
- Authenticated isolated React → BFF → Odoo browser journey: **1 passed**. Post-confirm BOQ edit and second-confirm attempts each returned 422; readback preserved confirmed state, original version, quantity and total. All four cost line types and the BoM baseline link were rechecked.
- Temporary database and BFF were removed; source `namaa_ksa` was unchanged. See [Checkpoint 270](build-engine/CHECKPOINT_270.md), [native QA](build-engine/BOQ_BASELINE_LOCK_NATIVE_QA.json) and [live QA](build-engine/BOQ_MRP_LIVE_QA.json).

## Checkpoint 269 — BE-053 React BOQ numeric boundaries

- BOQ unit tests: **7 passed**; includes zero-rate acceptance, exact upper-bound acceptance, and above-bound/non-finite rejection.
- Focused BOQ Playwright suite: **5 passed**. New browser case proves an over-limit quantity displays a bilingual inline field error and makes no API write. Existing BoM, create/confirm, spreadsheet-import and AI-draft journeys also passed.
- Vite production build passed. The pre-existing main-bundle size advisory remains.
- No Odoo or business-record writes were part of this frontend verification. BE-053 stays PARTIAL pending broader UOM/product, role/company, rounding and story acceptance. See [Checkpoint 269](build-engine/CHECKPOINT_269.md).

## Checkpoint 268 — BE-051 all BOQ line types in live React/Odoo flow

- React BOQ unit tests: **6/6 passed**; JavaScript syntax check and QA runner Python compilation passed.
- Authenticated disposable React → BFF → Odoo browser journey: **1/1 passed**. Created work/material/labour/equipment lines, reauthenticated and reopened, edited the manufacturing BoM relation, and confirmed the BOQ.
- Odoo postconditions verified all four types, persisted line amounts totaling SAR 12,100, actor/timestamp metadata, and matching line types plus the BoM relation on the approved baseline.
- Disposable database and temporary BFF were removed; source `namaa_ksa` was unchanged. Existing native invalid-line/UOM/foreign-project tests were not rerun in this checkpoint.
- BE-051 remains PARTIAL pending broad revision, unauthorized-role and cross-company acceptance. See [Checkpoint 268](build-engine/CHECKPOINT_268.md) and [live QA JSON](build-engine/BOQ_MRP_LIVE_QA.json).

## Checkpoint 259 — BE-035 CRM technical-proposal review

- Full isolated Odoo regression: **371 tests, 0 failures, 0 errors**. The focused technical-proposal class contains **7 passing tests** covering independent approve/reject/revise, immutable reviewer events, self-review denial, stale-source rejection, citation-restricted revision and unchanged business records.
- Backend suite: **236 passed, 2 skipped** (265 subtests). React unit suite: **80 passed**. Focused Playwright mock journeys: **2 passed** for technical-proposal draft and internal approval. Production build passed; existing large bundle advisory remains.
- Browser screenshot is synthetic. No authenticated two-user live Odoo review has been run; BE-035 remains PARTIAL. See [Checkpoint 259](build-engine/CHECKPOINT_259.md) and [QA report](build-engine/CRM_TECHNICAL_PROPOSAL_REVIEW_QA.json).

## Checkpoint 258 — BE-034 financial proposal approval PDF

- Backend PDF create/list/download boundaries: **2 passed**; verified company binding, exact PDF signature and content-type, size limit, private no-store response, and rejection of wrong-company/invalid PDF data.
- React unit tests: **80 passed**. Focused Playwright mock journey: **1 passed** for saving/reopening draft UI, creating a preview, and showing the PDF link. Vite production build passed.
- Isolated Odoo 20 native `namaa_ai_bridge` tests: **3 passed, 0 failures, 0 errors**. Covered QWeb HTML content, invalid-render no-partial-save, attachment privacy/raw bytes, idempotency, immutable preview metadata, review-state history and unauthorized reader denial.
- Real synthetic Odoo clone journey rendered a one-page A4 PDF (22,857 bytes), extracted the proposal and exact SAR 2,875 total, and verified the confirmed sale order state/total unchanged. The clone came from a database-only dump and lacked referenced filestore PDF assets, producing CSS asset 404s during rendering; inline report styling still produced the one-page artifact. Normal-database styling remains open. Shell transaction rolled back; source database unchanged.
- Full isolated Odoo regression: **367 tests, 0 failures, 0 errors**. Local rollout backup saved before upgrading `namaa_ai_bridge` to 20.0.1.0.26; React, BFF health, Odoo login and public progress page all returned HTTP 200 after rollout.
- Python compilation, XML parse and scoped `git diff --check` passed. See [Checkpoint 258](build-engine/CHECKPOINT_258.md) and [QA report](build-engine/SALES_FINANCIAL_PROPOSAL_PDF_QA.json). BE-034 remains PARTIAL pending live two-user React acceptance, broader role/project/company matrix, Arabic visual review, normal-database styling and full A1–A4.

## Checkpoint 257 — BE-032 financial proposal from confirmed Odoo pricing

- Backend generator tests: **2 passed**. BFF route tests: **3 passed** for source snapshot, draft save/list, invalid input and independent decision boundary.
- React unit suite: **80 passed**; focused React browser flow: **1 passed** using mocked Odoo/model responses. Exact displayed prices came from the synthetic confirmed-order fixture; this does not establish live-Odoo browser acceptance.
- Vite production build passed. Existing main-chunk size advisory remains.
- Isolated Odoo 20 `namaa_ai_bridge` tests: **2 passed, 0 failures, 0 errors** on a disposable clone. Source pricing and order state stayed unchanged; stale and invalid input were rejected; independent approve/reject decisions preserved rationale and immutable event rows; author self-review/reader access were denied.
- Disposable clone dropped and absence verified; source QA database unchanged. Python compilation and scoped `git diff --check` passed.
- Evidence: [Checkpoint 257](build-engine/CHECKPOINT_257.md) and [consolidated QA report](build-engine/SALES_FINANCIAL_PROPOSAL_QA.json). BE-032 remains PARTIAL pending live two-user integration, broader role/company/project acceptance, Arabic evaluation, business policy decision and full A1–A4.

## Checkpoint 256 — BE-031 customer-template technical proposal

- Generator/output tests: **4 passed** in the backend container; covered current-source citations, exact application-bound headings, section count, citation de-duplication and bounded local-model generation settings.
- BFF create/list route contract: **1 passed**; invalid payloads do not call Odoo.
- Native Odoo 20 bridge tests on disposable clone: **3 passed, 0 failures/errors**; persistence/reopen, source revision/template digest, citation allowlist, foreign source and non-Sales denial.
- Authenticated React → BFF → Qwen 3.8 27B → Odoo journey: **1 passed**. The Sales user saved/reopened one pending proposal; company, creator, citations and exact headings persisted. Opportunity write date, messages, activities and sale-order count stayed unchanged.
- Vite production build, Python compilation and focused `git diff --check` passed. Clone dropped; source DB unchanged.
- Evidence: [Checkpoint 256](build-engine/CHECKPOINT_256.md), [native QA JSON](build-engine/CRM_TECHNICAL_PROPOSAL_NATIVE_QA.json), [live QA JSON](build-engine/CRM_TECHNICAL_PROPOSAL_LIVE_QA.json), [live React screenshot](build-engine/frontend/screenshots/live-crm-technical-proposal.png).
- BE-031 remains PARTIAL; pasted text is supported, but file/PDF extraction, Arabic evaluation, wider role/company coverage and full A1–A4 are open.

## Checkpoint 245 — BE-059 supplier qualification lifecycle

- Isolated current-source Odoo module install and native acceptance tests: **5 passed, 0 failures/errors**. Coverage includes required scope, company assignment, submitter audit, independent reviewer, rationale, immutable decision history, unauthorized-role read/create/review, and foreign-company visibility.
- Isolated authenticated React → BFF → Odoo requester/manager journey: **1 passed**. Requester created/submitted; a separate manager approved; persisted company, supplier, actors, state and created/submitted/approved events were checked.
- Browser checked the English flow and Arabic approved state. See [submitted](build-engine/frontend/screenshots/supplier-qualification-submitted-live.png), [approved English](build-engine/frontend/screenshots/supplier-qualification-approved-live.png), and [approved Arabic](build-engine/frontend/screenshots/supplier-qualification-approved-live-ar.png).
- Disposable clone, agent database, Odoo, BFF, proxy and temporary image were removed. Source `namaa_ksa` was unchanged.
- Evidence: [native QA JSON](build-engine/SUPPLIER_QUALIFICATION_NATIVE_QA.json), [live QA JSON](build-engine/SUPPLIER_QUALIFICATION_LIVE_QA.json), and [Checkpoint 245](build-engine/CHECKPOINT_245.md). BE-059 remains PARTIAL; internal qualification review is not legal/regulatory certification.

## Checkpoint 243 — BE-021 CRM scouting filters

- Isolated native Odoo persistence, filter and company-boundary test: **1 passed**; clone dropped and source DB unchanged.
- Authenticated disposable-clone React → BFF → Odoo browser journey: **1 passed**. Odoo postconditions confirmed company, mandate, actor/time and matching-lead scope; clone and temporary services were removed, source DB unchanged.
- BFF request-contract and route tests: **2 passed**; invalid value range reports `max_project_value` and is rejected before Odoo mutation.
- React unit tests: **80 passed**; production build passed with the existing chunk-size advisory.
- See [Checkpoint 243](build-engine/CHECKPOINT_243.md), [native QA evidence](build-engine/CRM_SCOUTING_NATIVE_QA.json), [live QA evidence](build-engine/CRM_SCOUTING_LIVE_QA.json), and [screenshot](build-engine/frontend/screenshots/crm-scouting-live.png).

## Checkpoint 242 — post-rotation recovery verification

- Odoo admin authentication to `namaa_ksa`: **passed** after local PostgreSQL credential rotation and Odoo recreation.
- Authenticated React read routes: **6/6 HTTP 200**; database and application data remained intact.
- See [Checkpoint 242](build-engine/CHECKPOINT_242.md).

## Checkpoint 241 — React/Odoo support-route compatibility

- Focused daily-safety/API regression: **1 passed**, including compatibility URL `/api/daily-safety/options`.
- Authenticated read-only `namaa_ksa` smoke after rebuilding the backend: **6/6 HTTP 200** for customer, purchase receipt, current and legacy daily-safety options, bank maps and purchase-request options.
- Live Odoo registry includes the named bridge methods and `account.statement.import.map`. Access denials remain role-gated; smoke was run as admin and does not verify the affected user's role.
- See [Checkpoint 241](build-engine/CHECKPOINT_241.md).

## Checkpoint 240 — BE-149 scheduler suggestion slice

- Isolated Odoo bridge test: **1 passed, 0 failures/errors**; disposable clone removed and absence verified.
- Isolated native Odoo and authenticated live React → BFF → Odoo/model tests: **1 passed each** on disposable clones; both cleaned up, with source database unchanged. Native coverage includes cross-tenant denial and no sensitive disclosure.
- Backend scheduler unit tests: **5 passed**. Project schedule API boundary test: **1 passed**.
- Real configured Qwen 3.8 27B synthetic inference: **passed**, with task coverage, prerequisite order and output metadata validated.
- React unit tests: **80 passed**; focused Project Plan Playwright preview: **1 passed**; production build passed (large main-chunk advisory remains).
- Full backend suite: **175 passed, 2 skipped, 2 failed** in existing unrelated site-material issue and supplier-quote assertions. See [Checkpoint 240](build-engine/CHECKPOINT_240.md) and [live QA evidence](build-engine/SCHEDULE_SUGGESTION_LIVE_QA.json).

## Checkpoint 239 — supplier credit and debit notes through React

- Focused native Odoo bridge regression on a disposable clone: **1 passed, 0 failures/errors**. It covers customer and vendor bill origins, both native note wizard variants, source links, amounts, draft-only state, SAR, and idempotent credit retry.
- Live accountant React → BFF → Odoo Playwright journey: **1 passed**. Finance user created a vendor credit note (`in_refund`) and debit note (`in_invoice`) from a posted SAR vendor bill.
- Odoo postconditions verified both notes' company, creator, source, amount, SAR currency, draft state and idempotency operation key. QA clone, isolated Odoo process, temporary BFF, browser proxy and image were removed. Source DB unchanged.
- Evidence: [QA JSON](build-engine/VENDOR_NOTES_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-accounting-vendor-notes.png), [Checkpoint239](build-engine/CHECKPOINT_239.md).
- BE-084 stays PARTIAL pending tax/retention/reconciliation policy, edge cases, broader role/company acceptance and full story criteria.

## Checkpoint 238 — live CRM promotion approvals

- Isolated native Odoo promotion regression: **1 passed, 0 failures/errors**.
- Disposable-clone React → BFF → Odoo browser journey: **1 passed** with separate Sales and Owner sessions. Sales created two qualified-lead requests; self-approval received HTTP 403; a separate Owner approved one (native lead became an opportunity) and rejected the other (lead stayed a lead).
- Postconditions verified company, request and decision audit actors/timestamps/reasons, native lead types and approval application time.
- Disposable DB, Odoo registry, temporary BFF and browser proxy were removed. No shared demo business record was written.
- Python compilation, browser-spec syntax and `git diff --check` passed. No runtime business code changed in this verification slice.
- See [Checkpoint238](build-engine/CHECKPOINT_238.md), [QA report](build-engine/CRM_PROMOTION_LIVE_QA.json), [live browser spec](../frontend/e2e/lead-promotion.live.spec.js) and [screenshot](build-engine/frontend/screenshots/live-crm-promotion-approved-rejected.png).

## Checkpoint 237 — supplier quote recommendation producer

- Isolated Odoo 20 upgrade/test on a disposable clone: **1 passed, 0 failures/errors**. Covered Procurement vs read-only capability gating, generated source serialization, reviewed/compliant quote gating, landed unit ranking over raw price, delivery tie-breaker behavior, pending idempotency, initiating actor/time and no RFQ/PO/request-line writes.
- Disposable-clone React → BFF → Odoo browser journey: **1 passed**. It recorded a supplier quote with dates and compliance evidence, generated the recommendation, displayed source quote and landed estimate, and showed human-review controls.
- React unit tests: **80 passed, 0 failed**; Vite production build and Docker frontend image build passed.
- Authenticated smoke against deployed React at `:3200`: Dashboard, CRM, Sales, Purchase, Accounting, AI Workspace and Tasks & Workflows opened successfully; all observed BFF calls returned 200, no browser errors or business mutations. Direct authenticated Odoo RPC verified suggestion capability and list methods after the module upgrade.
- Database postconditions verified quote/request company, project and state; source quote reviewer/timestamps; suggestion source/reviewer/timestamp; no request purchase lines and no alternative PO.
- Isolated DB, Odoo process, temporary BFF and browser proxy were removed. No shared business rows were created by QA.
- `py_compile`, `git diff --check`, React production build and Docker frontend image build passed. Existing large JS chunk advisory remains.
- Post-QA local demo deployment upgraded `be_ai` to `20.0.1.0.3` and `namaa_ai_bridge` to `20.0.1.0.15`; Odoo restarted, frontend container rebuilt. React and Odoo login returned HTTP 200; authenticated Odoo RPC reported `can_read`, `can_review` and `can_generate` for the demo admin.
- Evidence: [Checkpoint237](build-engine/CHECKPOINT_237.md), [QA report](build-engine/PURCHASE_QUOTE_LIVE_QA.json), [quote capture screenshot](build-engine/frontend/screenshots/live-supplier-quote.png) and [recommendation screenshot](build-engine/frontend/screenshots/live-procurement-quote-recommendation.png).

## Checkpoint 233 — gated procurement quote suggestion

- Full platform suite: **73 passed, 3 skipped**; skips require optional knowledge-PostgreSQL integration fixtures.
- Disposable Odoo clone of `be_accounting_qa_20261024`: installed `be_ai` from current source and ran the tagged suite: **11 post-tests, 0 failures, 0 errors**. Tests cover advisory-only approval, no RFQ/PO side effect, approved-request and currency validation, source RFQ line identity and PM denial.
- Disposable clone `be_ai_proc_suggest_qa_20261026_a1` was force-dropped after test shutdown; database absence was verified. The source QA template and shared `namaa_ksa` were not modified.
- `git diff --check` passed. Evidence: [Checkpoint 233](build-engine/CHECKPOINT_233.md).

## Checkpoint 232 — scheduler evaluation baseline

- Scheduler, existing Phase 5 evaluation and QS gated-suggestion suites: **13 passed, 0 failures**.
- Scheduler synthetic dataset: **10/10 accuracy (1.00)** against the provisional 0.90 threshold.
- Verified completed-task and on-time-predecessor behavior and rejected invalid risk windows, dates and task states.
- Full platform suite: **68 passed, 3 skipped**. Skips require optional knowledge-PostgreSQL integration fixtures not configured here. Two environmental test assumptions were corrected (optional database skip handling and explicit Odoo URL for JSON-2 mocks).
- No model call, Odoo integration, business write or live database change was made. Results are synthetic and provisional. See [Checkpoint 232](build-engine/CHECKPOINT_232.md).

## Checkpoint 228 — BE-079 vendor bill OCR accountant acceptance

- Focused native Accounting KSA bridge test: **1 passed, 0 failures/errors**, now using `account.group_account_user` rather than administrator for creation and verifying reader denial.
- Live React → BFF → Odoo accountant journey: **1/1 passed**; normal internal reader options/create: **403/403**, with zero bills created by the reader.
- Draft persisted in the active company with accountant as creator, source attachment, four invoice lines, OCR review state and no posting. Idempotent retry returned the same bill; altered content returned 422.
- Disposable QA database and temporary BFF removed; shared `namaa_ksa` unchanged. Offline manual verifier passed **251/251** screenshots, responsive checks and no-external-request checks. Evidence: [QA JSON](build-engine/VENDOR_BILL_OCR_LIVE_QA.json), [Checkpoint 228](build-engine/CHECKPOINT_228.md), [screenshot](build-engine/frontend/screenshots/vendor-bill-accountant-live.png).

## Checkpoint 227 — BE-109/110 RFI create, response and deadline

- Native `be_correspondence` suite: **29 passed, 0 failures/errors**. Added boundary assertions for due-today, past-due open, answered, closed and cancelled statuses.
- Isolated React → BFF → Odoo browser journeys: **2/2 passed**. Live missing-subject RFI create returned field-level 422 and created no row; Site/PM/respondent lifecycle and stale/unauthorized updates were verified.
- Odoo postconditions verified deadline, current company/project, responder, answer/close actors and synchronized response activity. Clone and temporary services were removed. Evidence: [RFI QA](build-engine/RFI_LIVE_QA.json).

## Checkpoint 226 — BE-115 consolidated correspondence log

- Native Odoo `be_correspondence` suite: **29 passed, 0 failures/errors** on disposable clone.
- Live React → BFF → Odoo journeys: **2/2 passed**. Site submittal create/submit, PM approval and mixed RFI/submittal log/CSV verified.
- Invalid required input returned field-level 422 without a write; no-role reader received 403 with no record disclosure. Native postconditions checked project/company, actors, times, attachment revision and decision history.
- QA clone and temporary services removed; shared `namaa_ksa` unchanged. Evidence: [RFI_LIVE_QA.json](build-engine/RFI_LIVE_QA.json), [Checkpoint 226](build-engine/CHECKPOINT_226.md).

## Checkpoint 225 — BE-080 overpayment write-off

- Focused Odoo `TestReconcileEngine`: **27 post-install tests, 0 failures, 0 errors**; confirmed the overpayment case executed.
- Isolated React → BFF → Odoo browser suite: **4/4 passed**, including cash forecast, partial invoice payment, reconcile/undo and exact/split/multi-invoice/FX/short-receipt/overpayment flows.
- Overpayment postcondition: SAR 1,200 statement against SAR 1,000 invoice; invoice paid, statement reconciled, selected account `500100` credited SAR 200, suspense residual zero.
- QA clone, temporary BFF and agent database removed; no QA databases remain. Offline user manual: **249/249** screenshots decoded; bilingual desktop/mobile layouts, screenshot search/lightbox and no-external-request checks passed.
- Fixed the runner to upgrade installed `accounting_ksa` for Odoo 20 post-install discovery and reject zero executed tests. The earlier zero-test result is not counted as a pass. See [Checkpoint 225](build-engine/CHECKPOINT_225.md) and [live QA](build-engine/BANK_RECONCILIATION_LIVE_QA.json).


## Checkpoint 224 — live support smoke

- Authenticated, read-only HTTP checks through React `:3200`: bank import maps **200**, daily safety current route **200**, customers **200**, BFF liveness **200**.
- Confirmed obsolete `/api/daily-safety/options` returns **404**; React uses `/api/quality-gates/daily/options`.
- Admin-only check. Did not verify the affected user's groups/company/database; no database mutations or ACL changes.

## Checkpoint 223 — maintenance actual cost from stock issue/return

- Current-source React → BFF → Odoo Playwright passed **1/1** on a disposable clone.
- Two focused native Odoo tests passed: stock issue/return valuation and maintenance work-order/cost-ledger mutability boundaries.
- Lot-tracked issue: six units / SAR 240 were linked to an open corrective work order and confirmed BOQ line; returning two units created a -SAR 80 repair correction and reversed the project analytic cost. Net repair actual cost was **SAR 160**.
- Serial-tracked issue: two issued serial identities were preserved; returning one returned that same serial. Net BOQ actuals, audit actor/time and company/project scope were checked.
- React reopened the maintenance cost ledger and displayed both source-linked entries and the SAR 160 total. Closed work orders and cross-project work-order IDs were rejected; retry did not duplicate costs.
- The temporary BFF and disposable QA database were removed; source QA and `namaa_ksa` remained unchanged. Evidence: [QA JSON](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-site-material-maintenance-costs.png), [Checkpoint 223](build-engine/CHECKPOINT_223.md).
- Offline user manual verification passed: **247/247** screenshots decoded, Arabic/English desktop/phone layouts had no horizontal overflow, search/filter/lightbox/Escape passed, and no external requests were made. The vendor-bill and stock issue/return maintenance screenshots are labeled isolated Odoo QA.
- React unit suite passed **80/80**; Vite production build passed with the existing large-chunk advisory.

## Live React/Odoo support smoke — Checkpoint 222

- Through `http://localhost:3200`, signed in to `namaa_ksa` as `admin` and checked `GET /api/capabilities`, `/api/customers?limit=1`, `/api/purchase-receipts?limit=1`, `/api/bank-statements/maps` and `/api/quality-gates/daily/options`: **5/5 HTTP 200**.
- A fresh Odoo registry inspection confirmed the Accounting KSA bank-map model and the bank-map, customer-list and daily-safety bridge methods exist. The admin is a BE Owner, and the daily-safety options returned an available project and published template.
- Read-only verification; no business data or access groups changed. The two reported generic 404s remain unverified because their request URLs were not supplied.
- Evidence: [Checkpoint 222](build-engine/CHECKPOINT_222.md).

## Checkpoint 221 — BE-097 posted vendor bill allocation to maintenance costs

- Current-source disposable clone native `be_equipment` suite: **26 passed, 0 failures/errors**.
- Live React → BFF → Odoo PM journey: linked 3 of 5 units from a posted same-project expense bill line to the maintenance ledger. Odoo and the reopened React view showed SAR 300 allocated and 2 units remaining; a different-project line was unavailable and direct linking was denied. The bill stayed posted and no journal move was duplicated.
- Native regression also verifies split allocations totaling the bill quantity, over-allocation rejection without a write, and denial without account move line read access.
- Backend business suite: **160 passed**; React units **80 passed**; maintenance Playwright **1 passed**; production build passed with the existing large-chunk advisory.
- Isolated QA clone, temporary Odoo/BFF/image/volume were removed. The source DB and shared `namaa_ksa` were unchanged. Evidence: [QA JSON](build-engine/MAINTENANCE_PLAN_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/be097-vendor-bill-cost-link-221.png), [Checkpoint 221](build-engine/CHECKPOINT_221.md).

## Checkpoint 220 — BE-099 Accounting KSA retirement approval

- Current-source native equipment/accounting integration suite on disposable clone: **8 passed, 0 failures/errors**.
- Live React → BFF → Odoo journey used separate Procurement requester and Finance approver accounts. It verified self-approval denial, foreign-company no-disclosure, Finance read-only equipment access, absent custody/utilization actions, and successful native disposal.
- Odoo postcondition: request `RET/2026/00005` approved; journal move `MISC/2026/10/0003` posted; fixed asset closed; equipment archived; requester, approver and timestamps persisted.
- Focused React retirement Playwright: **1 passed**; React unit tests: **80 passed**; production build passed with the existing large-chunk advisory. Offline manual: **245/245** screenshots decoded; English/Arabic 1440px and 390px overflow, search/filter/enlarge/Escape, no external requests and both new isolated-QA captions passed.
- The clone, temporary services and image were removed; the source QA database and `namaa_ksa` were unchanged. Evidence: [QA JSON](build-engine/EQUIPMENT_RETIREMENT_LIVE_QA.json), [Checkpoint 220](build-engine/CHECKPOINT_220.md).

## Checkpoint 219 — corrective maintenance audit and costs

- Disposable clone of `be_accounting_qa_20261024`: native `be_equipment` suite **25 passed, 0 failures/errors**.
- Current-source React → BFF → Odoo PM flow created a company/project-linked corrective work order, recorded a SAR 125.75 repair-cost line, completed it and reopened it in React. Persisted Odoo postcondition verified creator/updater, timestamps, equipment, company, project, final state and cost line.
- Invalid duration returned **422** without a write; foreign-company equipment returned **403** without disclosure; a maintenance reader without the required role returned **403**. Live browser journey **1/1 passed**; focused mocked React journey **1/1 passed**.
- Vite production build passed with the existing chunk-size advisory. Manual rebuilt and verified **243/243** screenshots, bilingual desktop/phone layouts and offline behavior.
- Disposable clone, temporary Odoo/BFF/image and data volume removed; source QA and `namaa_ksa` unchanged. Evidence: [live QA JSON](build-engine/MAINTENANCE_PLAN_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/be096-preventive-plan-218.png), [Checkpoint 219](build-engine/CHECKPOINT_219.md).

## Checkpoint 218 — BE-096 preventive maintenance DONE

- Disposable clone of `be_accounting_qa_20261024`: tagged `be_equipment` native suite **25 passed, 0 failures/errors**.
- Current-source React → BFF → temporary Odoo runtime journey with a Build Engine PM: created and generated a plan, verified company/project/audit facts, reopened the plan in React, recorded cost, archived/restored it, and completed the adjacent corrective-work smoke. Missing required kind returned **422** with field detail and no record; foreign-company equipment returned **403** with no plan/disclosure; maintenance reader received **403**.
- Native Odoo postcondition confirmed an active preventive plan, linked company/project, PM creator/updater and timestamps, and a generated preventive request. React Playwright **1/1 passed**; focused backend validation **1/1 passed**; React unit tests **80/80 passed**; Vite production build passed with the existing large-chunk advisory.
- Disposable clone, temporary BFF, temporary Odoo container, data volume and image removed; source QA DB and live `namaa_ksa` unchanged. Evidence: [live QA JSON](build-engine/MAINTENANCE_PLAN_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/be096-preventive-plan-218.png), [Checkpoint 218](build-engine/CHECKPOINT_218.md).

## Checkpoint 217 — BE-095 equipment checkout and return

- Disposable clone of `namaa_ksa`: installed `be_equipment` and required OCA maintenance modules; **25 native module tests passed, 0 failures/errors**.
- Actual React→BFF→Odoo Site-user journey checked out equipment to a company project, reopened it, returned it and reopened it again. Final Odoo state is `in_yard`; the immutable ledger contains exactly two movements by the Site user with timestamps and project/company relations.
- Missing project returned **422** with no ledger entry. Cross-company project returned **403** with no ledger entry. A user without an equipment role received **403** for list and mutation.
- Disposable QA DB and temporary BFF were dropped. Source DB was unchanged during QA.
- The Namaa runtime then passed the same 25 native tests on a separate disposable clone after resolving the OCA maintenance addon path. A protected backup was taken before the live install: `/tmp/namaa_ksa_pre_equipment_install_20261026.dump` (10,495,408 bytes; mode 600; archive listing verified).
- Installed `be_equipment` with its OCA maintenance dependencies in live demo DB `namaa_ksa`, restarted Odoo, and confirmed `/api/capabilities`, `/api/equipment`, and `/api/equipment/options` return HTTP 200 through React. Read-only live browser smoke displayed the Equipment register and three demo assets with no page errors.
- Demo assets created through the authenticated React API: excavator (checked out to `Internal`), mobile crane (in yard), and concrete mixer (in yard). These are labeled Build Engine Demo and are ordinary removable demo records.

## Checkpoint 216 — Workspace access-error triage

- Focused native Odoo test on a disposable clone passed: `test_react_material_request_uses_native_request_and_approval_roles` (1/1). The requester had a Build Engine Project Manager role and no OCA Purchase Request group; the clone was dropped.
- Upgraded Namaa `namaa_ai_bridge` to `20.0.1.0.10` after taking `/tmp/namaa_ksa_pre_be_purchase_access_20261026.dump` (10,493,329 bytes; mode 600; archive listing verified).
- Post-upgrade authenticated calls through React `:3200`: `/api/bank-statements/maps` 200 (1 map), `/api/quality-gates/daily/options` 200 (1 project), `/api/purchase-requests/options` 200, `/api/customers` 200 (9 rows), `/api/purchase-receipts` 200 (31 rows).
- Generic 404 was not reproduced. Daily-safety role denial remains expected without Site/PM/Owner; bank-map management requires Accounting Manager.

## Latest implementation and live deployment — BE-119 (Checkpoint 215)

- `namaa_ksa` clone: native Odoo bridge test **1/1 passed**; current-source React BFF journey **passed** contract creation, creation of one evidence-gap snapshot and retrieval of its immutable history. QA clone and temporary BFF were removed; shared DB was not used for test writes.
- Backend suite: **159 passed, 224 subtests passed**. React unit suite: **80/80 passed**. Contract React Playwright: **1/1 passed**. Live browser smoke on `http://localhost:3200/` opened demo contract `CTR/00001`, displayed the persisted review and reported no page errors. The detail modal measured 780 px at desktop width, with the review heading/description laid out correctly.
- Manual rebuilt and verified: **240/240** offline screenshots, English/Arabic desktop and phone layouts, no external requests or horizontal overflow. Live screenshot: [contract review](build-engine/frontend/screenshots/react-be119-contract-review-demo.png).
- Authenticated post-deploy React API smoke: customers, purchase receipts, bank maps, daily safety options, contract options, contract list and clause-review history **7/7 returned HTTP 200** for `admin`.
- Shared modules upgraded: `be_contract 20.0.1.0.1`, `namaa_ai_bridge 20.0.1.0.9`. React image: `build-engine-react:be119-contract-review-215c`; BFF image: `build-engine:namaa-backend-be119-20261026`. Prior containers are stopped and retained for rollback. Protected database backup: `/tmp/namaa_ksa_be119_preupgrade_20261026.dump` (10,471,996 bytes; custom archive listing verified).
- The deployed test contract is `CTR/00001`; it is demo data, not a legal assessment. BE-119 remains PARTIAL pending approved legal criteria and the wider story acceptance scope.
- Evidence: [Checkpoint 215](build-engine/CHECKPOINT_215.md), [isolated integration QA](build-engine/CONTRACT_CLAUSE_REVIEW_LIVE_QA.json), and [traceability](REQUIREMENTS_TRACEABILITY.md).

## Latest implementation QA — BE-119 immutable clause evidence review (Checkpoint 214)

- Fresh disposable Odoo database install and focused native test: **1/1 passed**. Verified immutable snapshots, refreshed evidence across repeated reviews, reviewer/company/project stamps, stable Arabic checklist key and legacy clause alias, and denial to a reader without the contract role. The disposable database was dropped; shared databases were not modified.
- React unit tests: **80/80 passed**; contract review Playwright: **1/1 passed**; backend suite: **159 passed**; Vite production build passed (existing bundle-size advisory remains). Bilingual offline manual verification passed with 239/239 embedded screenshots.
- Live support checks: Odoo bank-map RPC returned successfully (1 map, 1 journal); admin daily-safety options returned successfully (1 project, 1 template). Public API probes for customer, purchase receipt, daily-safety options, bank maps and contract options returned 401 before authentication, confirming these routes exist. The exact URL for the reported generic 404 was not provided and could not be reproduced.
- Evidence: [Checkpoint 214](build-engine/CHECKPOINT_214.md) and [native QA JSON](build-engine/CONTRACT_CLAUSE_REVIEW_LIVE_QA.json).

## Latest implementation QA — BE-134 visual lifecycle graph (Checkpoint 211)

- Focused React lifecycle editor Playwright: **1/1 passed**. A stage pair selected through accessible graph buttons produced the expected directed link in the Odoo save payload, then publish/versioning continued to work.
- Isolated Odoo module tests: **2/2 passed**. Isolated live React → temporary BFF → cloned Odoo journey: **1/1 passed**. Native postconditions verified 3 stages, 3 transitions including the visually created Initiation → Technical review edge, role/group/user approvals, company/creator, published v1, editable copied v2, and project-type inheritance. QA database and BFF were removed.
- React tests: **80/80 passed**; Vite production build and `git diff --check` passed. Existing bundle-size advisory remains. Deployed `build-engine-react:workflow-visual-211`; authenticated `namaa_ksa` browser smoke confirmed the graph editor rendered without business writes. Previous React container remains stopped for rollback. Evidence: [Checkpoint 211](build-engine/CHECKPOINT_211.md) and [workflow QA JSON](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json).

## Latest support smoke — Checkpoint 210

- Authenticated, read-only status checks through `http://localhost:3200`: customers, purchase receipts, bank import maps, daily-safety options, purchase-request options and purchase requests **6/6 HTTP 200**. The missing Odoo method/model errors did not reproduce. No business writes were made.
- The reported generic 404 did not reproduce on these routes. Role-denial messages remain expected when the signed-in Odoo user lacks the relevant role or company access. See [Checkpoint 210](build-engine/CHECKPOINT_210.md).

## Latest — BE-062 supplier quote capture (Checkpoint 209)

- Isolated Odoo clone native acceptance: **1/1 passed**. Reference, received/valid-through dates, all RFQ line prices, quote actor/time, project/company, retry replay, stale/invalid/incomplete no-write, no-role and cross-company cases were checked.
- Isolated live React → temporary BFF → Odoo: **1/1 Playwright passed**. The saved quotation and recording actor appeared when the RFQ was reopened. Native postconditions verified the saved price, draft state and actor/time. Clone, registry and temporary BFF were removed.
- React unit suite: **80/80 passed**. Backend business suite: **157 passed, 220 subtests passed**. Python compilation, Vite production build and `git diff --check` passed (existing Vite chunk-size advisory remains).
- Upgraded shared Odoo modules to `namaa_ksa_purchase` 20.0.1.0.1 and `namaa_ai_bridge` 20.0.1.0.8 after saving the protected pre-upgrade dump. Deployed React/BFF `supplier-quote-209`; prior containers remain for rollback. Post-deploy authenticated routes and purchase quote detail returned HTTP 200 with no failed requests.
- Evidence: [Checkpoint 209](build-engine/CHECKPOINT_209.md), [QA JSON](build-engine/PURCHASE_QUOTE_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-supplier-quote.png).

## Latest runtime triage — Checkpoint 208

- Authenticated explicitly to `namaa_ksa` as `admin`: bank maps, purchase-request options/list and daily-safety options **4/4 HTTP 200**. React Purchase → Material requests, Accounting → CSV / Excel maps and Quality & Safety screens produced no failed HTTP responses, page errors or alerts.
- Added a demo CSV import map and assigned it to the `Bank` journal; the profile is visible in React. No statement was imported.
- The reported 403s remain role/company dependent. Existing Site/PM/Owner and purchase-request role checks were not changed. The generic 404 was not reproduced; no exact URL was provided.
- Evidence: [Checkpoint 208](build-engine/CHECKPOINT_208.md).

## BE-061 alternative supplier RFQs (Checkpoint 207)

- Disposable Odoo clone: **1/1 native test passed** after explicitly upgrading Odoo's `purchase_alternative` module and its `be_boq` consumer. The test covers selected supplier eligibility, separate native draft RFQs, copied lines/quantities, same-group membership, idempotent replay, no-role denial and foreign-company denial.
- Live React → BFF → Odoo Playwright journey: **1/1 passed**. A procurement reviewer opened the RFQ, selected two vendors, created the drafts and reopened the group. Native postconditions confirmed exactly two supplier alternatives, both draft, company-scoped, actor-stamped and quantity-correct.
- QA database, isolated Odoo registry and temporary BFF were removed. Shared `namaa_ksa` was not modified. Evidence: [Checkpoint 207](build-engine/CHECKPOINT_207.md) and [machine-readable QA](build-engine/PURCHASE_ALTERNATIVES_LIVE_QA.json).

## Latest support fix — purchase-request authorization (Checkpoint 206)

- Isolated live React → BFF → Odoo purchase fulfillment: **3/3 journeys passed**. A requester submitted a BOQ-linked request; a procurement reviewer approved it, created an RFQ, and recorded a partial receipt; a foreign company could not list or forge access to it. The clone and temporary BFF were removed.
- Material-request browser suite: **2/2 passed**, including a denied approval that retains the 403 after refreshing and displays role/company guidance. React unit tests: **80/80 passed**; Vite build passed (existing large-chunk advisory).
- Deployed React `purchase-role-guidance-206`; root, BFF health and Odoo login smoke checks returned HTTP 200. Prior container retained for rollback. No Odoo roles or ACLs changed.
- Evidence: [Checkpoint 206](build-engine/CHECKPOINT_206.md), [live purchase QA](build-engine/MATERIAL_REQUEST_FULFILLMENT_LIVE_QA.json).

## Latest — BE-106 daily safety checklist (Checkpoint 205)

- Disposable-clone native Odoo regression: **1/1 passed**. Live React → BFF → Odoo browser journey: **1/1 passed**. Site-role create, real PNG evidence upload, sign, reauthentication/reopen, invalid-date 422, 12 parallel same-date retries returning one ID, reader denial and foreign-company denial all passed. Native DB inspection confirmed one record per date, the actor/time/company/project/signature and one stored attachment. The clone, temporary registry and BFF were cleaned up.
- Full backend suite: **153/153 passed**; React suite: **80/80 passed**; quality-gate browser suite: **8/8 passed**; Vite production build, Python compilation and `git diff --check` passed. The Vite build reports its existing advisory about a JavaScript chunk over 500 kB.
- Deployed BFF and React `daily-safety-205` at `http://localhost:3200/`; root, BFF health and Odoo login smoke checks returned HTTP 200. Prior containers remain available for rollback. Shared `namaa_ksa` was not modified.
- Evidence: [Checkpoint 205](build-engine/CHECKPOINT_205.md), [isolated live QA JSON](build-engine/DAILY_SAFETY_LIVE_QA.json).

## Latest — Daily safety role guidance (Checkpoint 204)

- Authenticated `admin` read-only React → BFF → Odoo daily-safety options: **HTTP 200**, one project and one published template. Odoo shell confirms the account has Build Engine Owner and Odoo System memberships; no business data was printed or changed.
- Added bilingual UI guidance for users who receive the role-gated 403. Full quality-gate Playwright suite: **8/8 passed**, including the English/Arabic permission explanation. Updated the shared test sign-in helper to mock the direct Odoo session RPC consistently. React unit tests: **80/80 passed**; Vite build passed (existing >500 kB advisory).
- Deployed `build-engine-react:safety-role-help-204`; React root, BFF liveness and Odoo login returned HTTP 200. Prior container retained for rollback. No roles, ACLs or safety data changed. BE-106 stays PARTIAL for ordinary-role live workflow and the remaining criteria. See [Checkpoint 204](build-engine/CHECKPOINT_204.md).

## Latest — BE-017 won opportunity to project DONE (Checkpoint 203)

- Isolated disposable-clone native Odoo tests: **2 passed, 0 failed/errors**. The React → temporary BFF → isolated current-source Odoo registry Playwright journey: **1 passed**. It verified persisted company/project linkage and creator, reopened company/creator/timestamp, Arabic project action, Projects navigation, safe retry, invalid/un-won 422 and CRM-only/foreign-company 403 without disclosure.
- Disposable database dropped; temporary BFF removed; isolated Odoo HTTP registry stopped. Shared `namaa_ksa` received no business writes.
- React unit suite **80/80 passed**; Vite production build passed (existing >500 kB advisory). Python compilation, Playwright syntax and `git diff --check` passed. Deployed React root, BFF liveness and Odoo login returned HTTP 200.
- Evidence: [Checkpoint 203](build-engine/CHECKPOINT_203.md), [live QA JSON](build-engine/CRM_WON_PROJECT_LIVE_QA.json), [English project-linked screenshot](build-engine/frontend/screenshots/live-crm-project-linked.png).

## Initial pass — CRM won opportunity to project (Checkpoint 202; superseded by Checkpoint 203)

- Isolated disposable-clone native Odoo acceptance: **2 passed, 0 failed/errors**. Live React → temporary BFF → Odoo Playwright: **1 passed** for won-opportunity conversion, reopen/link, Projects navigation, idempotent retry, invalid/un-won 422 and CRM-only/foreign-company 403 without disclosure. Clone and temporary BFF were removed.
- React unit tests: **80/80 passed**. Vite production build passed (existing >500 kB advisory). Python compilation, Playwright syntax and `git diff --check` passed. Deployed React root, BFF liveness and Odoo login each returned HTTP 200.
- The live journey did not verify project company/creator/time in the reopened detail. BE-017 therefore stays PARTIAL pending A3 audit-context visibility through the intended runtime registry and ordinary intended-role acceptance. See [Checkpoint 202](build-engine/CHECKPOINT_202.md) and [evidence](build-engine/CRM_WON_PROJECT_LIVE_QA.json).

## Latest runtime smoke — Checkpoint 201

- React container rebuilt with the Namaa-specific proxy and deployed as `build-engine-react:proxy-namaa-bff-201`.
- React root, BFF liveness, Namaa Odoo login: **HTTP 200**. Unauthenticated customer API: **HTTP 401**, confirming the route is present and session-protected.
- Authenticated read-only React → BFF → Odoo calls: bank import maps, daily safety options, customer list and purchase receipts: **HTTP 200**.
- Registry inspection confirmed `account.statement.import.map` and the bridge methods are loaded. The active company has zero bank maps configured. Safety access still requires the Site, Project Manager or Owner Odoo group.
- Previous React container retained stopped for rollback. No business rows, ACLs or Odoo roles were changed.

## Latest — BE-012 lead qualification DONE (Checkpoint 199)

- Native Odoo qualification regression: **1 passed, 0 failures/errors** on a disposable QA clone. Live React → BFF → Odoo Playwright: **1 passed** across Sales, CRM reader and foreign-company Sales roles. Persisted decision/reason/reviewer/time/company/project were reopened; invalid and stale inputs returned 422; unauthorized mutations returned 403 without disclosure. Clone and BFF were removed.
- Supporting suites: React **80/80**, backend **165/165**, mocked qualification Playwright **1/1**, Vite production build passed (existing large-chunk advisory remains). Python compilation and `git diff --check` passed.
- The BE-012 live journey used image `build-engine-react:be012-company-project-context-198` and source-served Vite against an isolated database clone; the latest standalone runtime image is documented in Checkpoint 201. BE-012 is DONE against the supplied criteria; broader evaluated BD suggestions remain a separate product gap. See [Checkpoint199](build-engine/CHECKPOINT_199.md) and [live evidence](build-engine/CRM_QUALIFICATION_LIVE_QA.json).

## Checkpoint 197 — BE-010 CRM lead classification

- On a disposable clone, a Sales-role React → BFF → Odoo journey created an unmatched Government lead, edited its classification to Private, reopened it and verified persisted state, company, creator/updater and timestamps. Native postcondition: `crm.lead`, no linked customer, `private`, Sales actor.
- Field-level invalid sector input returned 422 before RPC. A non-CRM user could not classify. A foreign-company Sales user could not discover, read or update the lead; responses disclosed no lead name and the record stayed unchanged.
- Native Odoo: **3 passed, 0 failures/errors**. Backend business suite: **153 passed**. React unit suite: **80/80 passed**. Live Playwright: **1/1 passed**. Vite production build passed; existing >500 kB chunk-size advisory remains.
- Fixed `EditPayload.partner_id` being required for every document update. CRM leads can now remain customer-free while being classified; native validation continues to guard opportunities and other documents. BFF process was restarted to load this contract change. Disposable clone and BFF removed; no shared business records changed.
- BE-010 is DONE. See [Checkpoint197](build-engine/CHECKPOINT_197.md) and [live evidence](build-engine/CRM_MANUAL_LEAD_LIVE_QA.json).

## Checkpoint 194 — BE-060 material request linked to BOQ

- Disposable-clone live QA: **3 journey phases passed** through React → BFF → Odoo: requester draft/submit and separate reviewer approve/RFQ; foreign tenant request/BOQ isolation and forged cross-company denial; Odoo PO confirmation/partial receipt and React reopen with requested 8 / ordered 8 / received 3 / outstanding 5.
- Native postconditions verified same-company confirmed BOQ linkage, project analytic distribution, OCA request/RFQ, PO, completed receipt and quantities. Reopened React rows exposed responsible requester, company, project, and created/updated timestamps. Missing required date returned a field-level 422 before any Odoo RPC; native role tests deny BOQ-linked create/write without a Build Engine project role.
- Isolated native Odoo `TestNamaaBridge.test_react_material_request_uses_native_request_and_approval_roles`: **1 passed, 0 failures/errors** after upgrading `be_boq`, `be_project` and `namaa_ai_bridge` on a disposable clone; clone dropped. Focused backend validation/delegation test: **1 passed**. React unit suite: **79/79 passed**. Production Vite/Docker image builds passed (existing >500 kB bundle advisory).
- Deployed `build-engine-react:be060-material-requests-194` to `:3200`, retaining rollback container. Authenticated purchase-request, bank-map and daily-safety proxy smoke checks returned HTTP 200. The bank-map registry is present; the demo has no saved map yet.
- Disposable clone and temporary backend were removed. Source QA and shared demo business data were not changed by the live acceptance run. Evidence: [structured QA](build-engine/MATERIAL_REQUEST_FULFILLMENT_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-material-request-fulfillment.png), [Checkpoint194](build-engine/CHECKPOINT_194.md). BE-060 is DONE; adjacent stories remain independently classified.

## Checkpoint 191 — Direct CRM lead entry and Namaa module recovery

- React unit tests: **79/79 passed**. Focused Playwright for the customer-free direct lead path and existing CRM opportunity flow: **2/2 passed**. Vite production build passed; the existing >500 kB chunk advisory remains.
- Isolated disposable clone of `namaa_ksa`: installed `accounting_ksa`, `be_progress_billing`, and `be_correspondence`, refreshed `namaa_ai_bridge`, and ran the bank-map lifecycle, progress-billing create/list, and RFI versioned update tests: **4/4 passed**. Both clone databases were removed.
- Backed up shared `namaa_ksa`, then installed the three modules with demo data disabled. Authenticated calls through the live React proxy returned HTTP 200 for bank maps, bank reconciliation transactions, progress certificates, and RFIs. Purchase-request and daily-safety routes return 403 for the tested user because the Odoo business-role groups are not assigned; no ACL or role check was weakened.
- React image `build-engine-react:crm-direct-lead-191` is deployed at `:3200`; HTTP smoke passed for React, Odoo login, BFF health/OpenAPI and manual. Previous React container is retained as `build-engine-react-demo-3200-rollback-crm-191`.
- Backups: `/tmp/namaa_ksa_before_accounting_ksa_install_20261026.dump` and `/tmp/namaa_ksa_before_correspondence_progress_20261026.dump`. No demo/business records were added by this increment.


## Checkpoint 190 — Riyadh-local financial report date defaults

- React unit suite: **79/79**, including dates immediately before and after the Riyadh UTC midnight boundary.
- Focused React Playwright `e2e/accounting-reports.spec.js`: **1 passed**. With the browser fixed to `2026-10-25 21:00 UTC`, the default “To” date is `2026-10-26`; the “From” date is `2026-01-01`. The test exercises all ten report types and verifies the as-of versus period filter behavior.
- Vite production build passed; existing >500 kB bundle advisory remains. No Odoo module, calculation or financial record changed. Earlier isolated native report engine and PDF/XLSX evidence remains in [Checkpoint105](build-engine/CHECKPOINT_105.md).
- Docker image `build-engine-react:be081-riyadh-report-date-190` passed a `:3220` preview and is now deployed at `:3200`. Root, BFF health/OpenAPI, Odoo login, manual and deployed bundle checks passed; the previous container is retained stopped for rollback. No Odoo database was changed.

## Checkpoint 189 — Resource conflict detail access

- `npx playwright test --config playwright.config.js e2e/project-plan.spec.js --workers=1`: **1 passed**, including expanded crew/equipment details and the saved React QA screenshot.
- React unit suite: **78/78**. Vite build passed; the existing >500 kB bundle warning remains.
- Rebuilt `frontend/public/user-manual.html`; offline verifier passed **233/233** screenshot decodes, Arabic/English desktop/phone layout, zero external requests and gallery controls.
- Docker image `build-engine-react:be043-expandable-conflicts-189` passed a `:3218` preview smoke, then replaced the local React UI at `:3200`. `/`, BFF health/OpenAPI, Odoo login page, manual and built JS labels returned expected content/HTTP 200. Previous `:3200` container is retained stopped for rollback. No Odoo module or business data changed.
- Existing native Odoo conflict detection regression covers cross-project overlap and closed-task filtering; no Odoo/backend code changed in this increment. Full BE-043 acceptance remains open for role/company privacy and the business decision on blocking/reserving resources.

## Checkpoint 188 — Live React RFI workflow acceptance

- Disposable clone of `namaa_ksa`: installed `be_correspondence`; focused native RFI manager regression **1 passed, 0 failures/errors**.
- Full live Playwright React → BFF → Odoo role journey: **1 passed**. Site author created/submitted, Owner/PM reassigned respondent and deadline, assigned Site respondent answered, Owner/PM closed. Stale update returned **422**, Site-role update returned **403**. Native postconditions verified project/company, final assignee/deadline, answer/closure actors and response-activity lifecycle. Evidence: [RFI_LIVE_QA.json](build-engine/RFI_LIVE_QA.json).
- Fixed test Odoo `db_maxconn=4` exhaustion after React concurrently loaded workspace APIs; QA now uses 64 connections. Fixed answered-RFI detail crash by parsing Odoo datetime values safely.
- React unit suite: **78/78**. Vite production build passed (existing large-bundle advisory remains). Rebuilt the bilingual offline manual; `node scripts/verify_manual.mjs` passed **232/232** screenshot decodes, Arabic/English desktop/phone overflow, no external requests and gallery controls.
- Disposable database, QA containers and volume were removed; shared `namaa_ksa` and business records were not modified. `be_correspondence` remains uninstalled in the shared database, so BE-109/110 remain PARTIAL pending broader project/company/portal, repeat-assignment and late-response checks and reviewed rollout.

## Checkpoint 187 — Versioned RFI assignment/deadline update

- On a disposable clone restored from `namaa_ksa`, installed `be_correspondence` and ran `TestRfi.test_manager_workspace_update_is_role_checked_versioned_and_syncs_activity`: **1 passed, 0 failures/errors**. Clone was dropped; shared database unchanged.
- Backend business suite: **151 passed, 206 subtests passed**, including same-origin enforcement, strict payload validation, `be_version` forwarding and native error mapping.
- React unit suite: **78 passed**. `npx playwright test e2e/rfi.spec.js`: **4 passed**, including manager reassignment/deadline edit and refreshed detail display.
- Vite production build passed; the pre-existing bundle-size advisory remains. No live deployment or shared-demo business writes were made.
- Rebuilt `frontend/public/user-manual.html`; offline QA passed **231/231 screenshots**, bilingual desktop/phone layouts, no external requests and gallery controls.

## Checkpoint 186 — Punch evidence and closeout guard

- Isolated clone `be_be108_qa_20261026`: `be_quality_gate` + `be_project` **33 post-tests, 0 failures, 0 errors**. Evidence validation/list/read, portal denial, unresolved-item archive denial and archive after independent closeout passed.
- Backend business suite: **150 passed**; React unit suite: **78 passed**; focused `e2e/punch-list.spec.js`: **1 passed**, including mock evidence upload/link and the existing lifecycle. Python compilation and Vite build passed.
- The production image `build-engine-react:be108-punch-evidence-186b-manual` built and passed a port-3214 preview for the Odoo login proxy, BFF OpenAPI evidence endpoints, evidence UI bundle and updated manual.
- Before live rollout, `namaa_ksa` was backed up to `/tmp/namaa_ksa_before_be108_evidence_20261026.dump` inside `namaa-odoo20-db-1`, mode `0600`, 9,835,443 bytes, `pg_restore -l` valid. Upgraded module versions: `be_quality_gate` **20.0.1.0.4**, `be_project` **20.0.1.0.5**.
- React `:3200` now serves the new image with rollback container `build-engine-react-demo-3200-rollback-be108-186b` retained stopped; the previous 185 image is separately retained as `...rollback-be108-186a`. Authenticated read-only smoke verified login, capabilities, dashboard, agents, tasks, CRM, sales, purchase and accounting. No shared-demo punch record or evidence was created.
- Offline manual passed **230/230** embedded screenshot decodes, English/Arabic desktop/phone overflow and no external requests.
- BE-108 remains PARTIAL: ordinary-role live acceptance, wider tenant checks, DEC-21 closeout semantics and full A1–A4 remain.

## Checkpoint 185 — Quality and safety escalation

- Isolated clone `be_be107_qa_20261026`, restored from `namaa_ksa`: full `be_quality_gate` suite **21 post-tests, 0 failures, 0 errors** (23 total quality tests). Added checks for safety-incident and overdue daily-checklist escalation, recipient role and cross-company denial, immutable history, and Odoo activity assignment. Clone and dump were dropped after QA.
- Backend business suite: **149 passed**, including strict escalation payload, same-origin mutation, route delegation and source/company filtering. React unit suite: **78 passed**, including escalation eligibility/date boundaries. Focused Playwright journeys: **2 passed**, for safety incident and overdue daily safety escalation. Python compilation, Vite production build and Docker image build passed; the existing >500 kB bundle advisory remains.
- `namaa_ksa` backup: `/tmp/namaa_ksa_before_be107_escalation_20261026.dump` inside `namaa-odoo20-db-1`, mode `0600`, 9,821,758 bytes; archive validated. After isolated QA, `be_quality_gate` upgraded to **20.0.1.0.2** and the escalation table was verified.
- React `:3200` serves `build-engine-react:be107-escalations-185a`; the prior container remains as `build-engine-react-demo-3200-rollback-be107`. BFF OpenAPI includes escalation list/options/create routes. Authenticated live read-only customer, purchase-receipt and escalation-history calls returned HTTP 200. No escalation was created in the shared demo.
- Offline bilingual HTML manual [user-manual.html](../frontend/public/user-manual.html) now documents the escalation flow and the connected database. Verification decoded **229/229** screenshots and passed English/Arabic desktop/phone overflow checks without external requests.
- Business limitation: Owner/Project Manager routing and immediate activity notification are provisional. Response windows, severity tiers, automatic escalation and full ordinary-role live acceptance remain open under DEC-20.

## Checkpoint 184 — React project punch list

- Odoo clone `be_punch_qa_20261025`: `be_quality_gate` **19 post-tests, 0 failures, 0 errors**. Covered assignment → start → corrective work → independent verification → closeout, blocked self-verification, post-close immutability/deletion and private-project record-rule behavior. The clone and its dump were dropped after tests.
- Backend business suite: **147 passed**, including punch-list contract and BFF route-boundary tests. React unit suite: **75 passed**. Focused `e2e/punch-list.spec.js`: **1 passed**, exercising create, assign, start, resolve, verify and close.
- Vite and Docker production builds passed with the existing large-chunk advisory. Python compilation passed.
- Authenticated, read-only live smoke through React → BFF → Odoo: punch-list options **200** (one project), list **200** (zero items), customer list **200** (two rows). No punch item was created in the shared database.
- Offline manual verifier passed **228/228 screenshots**, English/Arabic desktop/phone layouts, zero external requests and no horizontal overflow.
- `namaa_ksa` `be_quality_gate` upgraded to 20.0.1.0.1 after a protected backup. React `:3200` serves the new build and manual.

## Checkpoint 183 — AI BOQ provenance persistence

- Backend AI tests: **10 passed**; BOQ API boundary/signature test: **1 passed** in a disposable test container with the test-only `respx` dependency.
- React unit suite: **75/75 passed**; focused BOQ Playwright: **3/3 passed**, including save payload and reopened provenance display; Vite production build passed with the existing chunk-size advisory.
- Rebuilt the offline bilingual user manual with **227 screenshots**, including the saved/reopened AI provenance screen. Manual verification passed **227/227** decodes, Arabic/English desktop and phone layouts, no external requests, no horizontal overflow, and gallery search/enlargement checks.
- Isolated Odoo `be_boq,namaa_ai_bridge` update and provenance regression passed on disposable database `be_boq_ai_provenance_20261025`; verified persistent hashes/model/pages, reopened list response, invalid metadata rejection without extra BOQ rows, no source attachment, and immutable provenance. A broad `/be_boq,/namaa_ai_bridge` run then passed **102 tests, 0 failures, 0 errors** on fresh disposable clone `be_boq_ai_suite_20261025`. Both clones were dropped and verified absent.
- Backed up `namaa_ksa` to protected local file `/tmp/namaa_ksa_before_be150_provenance_20261025.dump` (9,801,047 bytes), then upgraded `be_boq` to 20.0.1.0.5 and `namaa_ai_bridge` to 20.0.1.0.7. PostgreSQL confirms the five BOQ provenance columns exist.
- Deployed React image `build-engine-react:be150-boq-provenance-183b-manual` at `http://localhost:3200`, including the refreshed HTML manual; previous containers retained as `build-engine-react-demo-3200-rollback-manual-183` and `build-engine-react-demo-3200-rollback-boq-provenance-182`. Restarted BFF to load the signed-provenance validation. Authenticated customer and BOQ options/list APIs returned HTTP 200; forged source metadata returned 422. Current admin has no BOQ-create permission and no live BOQ was written.

## Checkpoint 182 — React login database default

- Production image built and deployed with `namaa_ksa` as the login default; previous container retained for rollback.
- Authenticated `namaa_customer_list` RPC through React proxy returned 2 rows; authenticated BFF `/api/customers?limit=2` returned HTTP 200 with 2 rows.
- Confirmed the selected default database exists in the Namaa PostgreSQL stack. No Odoo records or schema were modified.

## Checkpoint 181 — React database route and BOQ actual cost

- React tests: **75/75 passed**; production Vite build passed with the existing large-chunk advisory.
- Odoo `/be_boq,/namaa_ai_bridge`: **101 tests, 0 failures, 0 errors** on disposable clone `be_boq_cost_fix_20261025`, dropped afterward.
- Authenticated React `:3200` verification against `namaa_ksa`: direct customer/receipt list RPCs and BFF customer, receipt, portfolio and project-option routes returned HTTP 200.
- Namaa Odoo restarted to load current mounted bridge source; no database upgrade or mutation performed. Previous React/BFF containers retained for rollback.

## Checkpoint 176 — Portfolio critical-path highlighting

- React unit suite: **73 passed**. Focused project-plan Playwright: **1 passed**, verifying each project's critical bars and filtering. Production Vite build passed with the existing large-chunk advisory.
- Authenticated production browser smoke at :3200 returned 200 for customer and receipt lists (5 rows each) and portfolio (16 projects / 109 tasks / 8 scheduled); four per-project critical tasks were highlighted. Home Construction filter returned its 13 project tasks including four synthetic demo rows. Screenshot and QA: [timeline](build-engine/frontend/screenshots/project-portfolio-timeline-176.png), [JSON evidence](build-engine/PORTFOLIO_CRITICAL_PATH_LIVE_QA.json). Deployed image `build-engine-react:be042-portfolio-critical-176a`; previous image retained for rollback. See [Checkpoint176](build-engine/CHECKPOINT_176.md).
- Rebuilt [the offline bilingual user manual](../frontend/public/user-manual.html); verifier passed **226/226** embedded screenshots, AR/EN desktop and phone layouts, zero external requests, and no horizontal overflow.

## Checkpoint 175 — Cross-project portfolio timeline

- Native Odoo `test_react_project_portfolio_schedule_respects_project_and_company_rules`: **1 passed** on a disposable clone; private/follower-only and foreign-company projects/tasks were omitted for the ordinary project manager. Clone dropped. BFF portfolio route-forwarding test: **1 passed**.
- React unit tests: **73 passed**. Focused `project-plan.spec.js` Playwright: **1 passed**, including portfolio filter behavior and date-axis endpoint labels. Production Vite build passed; the existing >500 kB chunk advisory remains. Python compilation and scoped `git diff --check` passed.
- Authenticated production browser smoke at :3200: `/api/project-plans/portfolio` HTTP 200, 16 projects and 109 tasks; customer and purchase receipt list APIs HTTP 200 in separate authenticated calls against the supported demo database. Screenshot and structured evidence: [timeline](build-engine/frontend/screenshots/project-portfolio-timeline-175.png), [QA JSON](build-engine/PORTFOLIO_SCHEDULE_LIVE_QA.json). Deployed image `build-engine-react:be042-portfolio-175a`; prior container retained for rollback. See [Checkpoint175](build-engine/CHECKPOINT_175.md).

## Checkpoint 174 — Company calendar and live React schedule

- Odoo `TestNamaaBridge.test_project_plan_uses_company_work_calendar_and_global_leave`: **1 passed, 0 failures/errors** on disposable clone `be_calendar_schedule_demo_qa_20261025`. Sunday–Thursday calendar plus a full-day global holiday produced four working dates across 25–29 October. Clone dropped; database count 0. See [native QA](build-engine/PROJECT_CALENDAR_NATIVE_QA.json).
- React `node --test tests/*.test.js`: **73 passed**. Focused project-plan Playwright: **1 passed**, including calendar-based path display. Python compilation and scoped `git diff --check` passed.
- `build-engine-react:be042-company-calendar-174` built and deployed at `http://localhost:3200`. Odoo demo restarted to load current mounted bridge code; live React admin login and project-plan navigation passed. React created one synthetic phase and three dependent tasks in demo DB `be_qa_demo_full_20261025`; authenticated Odoo read verified 3, 4 and 2 working dates and both dependency links. React displayed a 9-working-day path. Screenshot: [project-plan-work-calendar-174.png](build-engine/frontend/screenshots/project-plan-work-calendar-174.png); details: [Checkpoint174](build-engine/CHECKPOINT_174.md).
- Current demo calendar reports `40 hours/week`, `Europe/Brussels`. No Saudi timezone/week pattern was assumed; DEC-19 tracks tenant calendar configuration. BE-042 remains PARTIAL for project-specific/crew calendars, portfolio scheduling, manual gaps and broader acceptance. Existing Vite large-bundle warning remains.

## Checkpoint 173 — Interactive Gantt scheduling

- Focused Odoo bridge test **1/1 passed** during disposable-clone module upgrade.
- Live ordinary-PM React → BFF → Odoo Playwright **1/1 passed**: create hierarchy, assign crew/dependency, edit, drag the task bar one day, resize its deadline by edge drag and keyboard, sign out/reopen. Native postconditions confirmed 2026-12-02 start / 2026-12-11 deadline and actor/company. The run also asserted HTTP 422 field-level rejection with no partial record, and denied unauthorized/foreign-company writes. Clone `be_project_plan_live_qa_9de38533` dropped. See [QA JSON](build-engine/PROJECT_PLAN_LIVE_QA.json) and [screenshot](build-engine/frontend/screenshots/live-project-plan-crew-dependencies.png).
- React unit suite **72/72 passed**, including move/resize date validation and exact Gantt endpoint ticks; focused mocked project-plan Playwright **1/1 passed**.
- PostgreSQL `max_connections` for the local Build Engine stack is now **200** to accommodate the pooled connections from retained QA databases and isolated upgrade workers. Data volume preserved during restart.

## Checkpoint 172 — Live React project plan

- Focused native Odoo project-plan test **1/1 passed** during disposable-clone module upgrade. It now rejects blank task names and verifies no partial task row was created.
- Live ordinary-PM React → BFF → Odoo Playwright **1/1 passed** on `be_project_plan_live_qa_c2ec523c`: phase/hierarchy, dependency, crew, edit/reopen, field-level 422/no partial create, and unauthorized/foreign-company denial. Native postconditions verified actor/time/project/company. Clone dropped; source database unchanged. See [QA JSON](build-engine/PROJECT_PLAN_LIVE_QA.json) and [screenshot](build-engine/frontend/screenshots/live-project-plan-crew-dependencies.png).
- Focused mocked React Playwright **1/1**, React unit suite **70/70**, backend project-task contract **1/1**. The live runner flushes the Odoo pool immediately before browser activity and cleanup to avoid PostgreSQL connection exhaustion from the multi-database QA service.

## Checkpoint 171 — React bridge-method login guard

- React unit suite **70/70 passed**; production Docker/Vite build passed.
- Authenticated calls through React `:3200` confirmed both list RPCs on `be_qa_demo_full_20261025`. Safe invalid-filter probes on the older demo returned validation errors and no rows.
- New image `build-engine-react:be-login-method-guard` is live on `:3200`; previous container retained for rollback. No Odoo database changed. See [Checkpoint171](build-engine/CHECKPOINT_171.md).

## Checkpoint 170 — React equipment utilization

- Focused native Site-role Odoo bridge test **1/1 passed** on a disposable clone; native totals and row values were verified, then the clone was dropped.
- Live React → BFF → Odoo Playwright journey **1/1 passed** as a Site user. The utilization request returned HTTP 200 and native verification matched 240 available / 96 used / 144 idle hours and 40% utilization; clone dropped. See [native evidence](build-engine/EQUIPMENT_UTILIZATION_NATIVE_QA.json) and [live evidence](build-engine/EQUIPMENT_UTILIZATION_LIVE_QA.json).
- React `:3200` serves the feature and [live screenshot](build-engine/frontend/screenshots/live-equipment-utilization.png). BE-098 remains PARTIAL; see [Checkpoint170](build-engine/CHECKPOINT_170.md).

## Checkpoint 169 — Editable React project timesheets

- Focused native Odoo bridge test **1 passed** on a disposable clone: own-entry edit, labor-cost/BOQ actual recomputation, stale revision rejection and other-user denial. Clone dropped.
- Isolated live React → authenticated BFF → Odoo Playwright **1/1 passed**. Native verification confirmed 3 hours, −SAR 150 analytic cost, creator/updater identities and project/task/company links; clone dropped and source unchanged. See [live evidence](build-engine/TIMESHEET_LIVE_QA.json) and [native evidence](build-engine/TIMESHEET_NATIVE_QA.json).
- Backend suite **156 passed**; React unit suite **70 passed**; focused mocked timesheet Playwright **1 passed**; Vite production build passed with the existing bundle-size advisory.
- React `:3200` smoke passed; current bundle, default demo DB, BFF PUT route and Odoo revision token verified. BE-089/091 remain PARTIAL. See [Checkpoint169](build-engine/CHECKPOINT_169.md).

## Checkpoint 168 — Stable bank reconciliation proposal updates

- Native Odoo `TestReconcileEngine`: **27 passed, 0 failed, 0 errors**.
- Isolated React → BFF → Odoo accounting journeys: **4/4 passed**; modeled short receipt posted SAR 10 expense and settled the invoice. Disposable clone `be_bank_rec_live_qa_f988682d` was dropped.
- Focused React Playwright **2/2**, React unit tests **70/70**, and Vite build passed. Deployed React image `build-engine-react:be080-reconcile-state-fix` to `:3200`, retaining the prior container for rollback.
- BE-080 remains PARTIAL; see [Checkpoint168](build-engine/CHECKPOINT_168.md) and [QA evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json).

## Checkpoint 167 — React demo database default

- Built and served React image `build-engine-react:be072-demo-db-fix` on `:3200`; production build passed.
- Verified the served login bundle defaults to `be_qa_demo_full_20261025`. Authenticated proxy calls to `namaa_customer_list` and `namaa_purchase_receipt_list` returned rows.
- Confirmed the legacy `build_engine` database lacks the bridge; no Odoo database was modified. Previous React container retained for rollback. See [Checkpoint167](build-engine/CHECKPOINT_167.md).

## Checkpoint 166 — Bank reconciliation audit trail

- Native Odoo `TestReconcileEngine`: **27 passed, 0 failed, 0 errors**. Verified actor/company/project snapshot on reconcile, persistent undo history, immutable events, and foreign-company read denial.
- Live React → BFF → Odoo: **4/4** journeys passed for forecast, partial document payment, exact/split/multi-invoice and FX receipts, modeled short receipt, supplier payment, and undo. Native post-check verified saved audit rows and project context after reopening.
- React unit suite **70/70**, focused model-flow Playwright **1/1**, and production Vite build passed. QA clone `be_bank_rec_live_qa_2b122591` was dropped.
- Fixed the proposal state race uncovered by short-receipt browser acceptance. BE-080 remains PARTIAL for broader banking-role UAT, edge-case coverage and full A1–A4 acceptance. See [Checkpoint166](build-engine/CHECKPOINT_166.md) and [QA evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json).

## Checkpoint 165 — Namaa customer and receipt bridge methods

- Reproduced missing method errors on Namaa Odoo `:8070`, database `namaa_ksa`. Registry logs showed the installed bridge was skipped because its construction dependencies were not installed; OCA `purchase_request` was absent from the addon path.
- Rehearsed the bridge update on disposable clone `be_namaa_bridge_qa_20261025`. It installed the declared construction dependencies and loaded both methods. The clone was dropped after verification.
- Added OCA 20 `purchase-workflow` to the Namaa Compose addon path, backed up `namaa_ksa` to `/tmp/namaa_ksa_before_bridge_install_20261025.dump`, updated `namaa_ai_bridge`, and recreated the Odoo service. Authenticated RPC calls to `namaa_customer_list` and `namaa_purchase_receipt_list` both succeeded (5 rows returned from each capped query). Compose config and diff checks passed.
- This is admin RPC verification, not ordinary-role React acceptance. React `:3200` remains routed to Build Engine Odoo `:8069` and a separate database set; see [Checkpoint165](build-engine/CHECKPOINT_165.md). No story classification changed.

## Checkpoint 164 — Serial-tracked project material issue and return

- Live React → BFF → Odoo Warehouse Officer journey passed **1/1** on disposable clone `be_issue_live_qa_d5b67777`. It performed a 6-unit lot issue/2-unit return and a 2-unit serial issue/one-serial return.
- Native Odoo verification confirmed distinct serial identities at one unit each; project/company/BOQ links; actor and done timestamps; serial issue analytic `−SAR 110`; serial return analytic `+SAR 55`; net serial BOQ actual `SAR 55 / 1 unit`. Lot issue/return actuals remained `SAR 160 / 4 units`; site stock ended at 11. Clone was confirmed dropped (zero remaining databases).
- Fixed serial issue and return browser inputs: serial quantities now have minimum 1 with step 1. React unit suite: **70/70 passed**. Vite production image `build-engine-react:be072-serial-return` is active on :3200; the prior image is retained for rollback.
- Bilingual offline manual rebuilt and verified **220/220** screenshots decoded; Arabic/English desktop and 390px phone layouts passed. [Checkpoint164](build-engine/CHECKPOINT_164.md), [QA JSON](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json), [serial issue screenshot](build-engine/frontend/screenshots/live-site-material-serial-issue-validated.png), and [serial return screenshot](build-engine/frontend/screenshots/live-site-material-serial-return-validated.png).

## Checkpoint 163 — Construction receipt destination control

- Isolated Odoo `TestNamaaBridge.test_react_purchase_receipt_can_target_a_company_warehouse_bin`: **1 passed, 0 failures, 0 errors**. Verified a same-company one-step bin receipt, rejection without mutation for an invalid destination, and preserved multi-step staging.
- Backend business suite: **145 passed**, including optional destination forwarding and invalid location ID validation.
- Mocked React receipt E2E: **3/3 passed**, including project-bin selection and request payload. React unit suite: **70/70 passed**. Vite production build passed with the existing large-chunk advisory. Offline bilingual manual: **215/215** embedded screenshots decoded; English/Arabic desktop and 390px phone layouts passed with no external requests. Python compilation and `git diff --check` passed.
- Live read-only React → BFF → Odoo browser check on :3200 passed **1/1**: four destination options appeared, a non-default bin was selected, all observed API GETs returned 200, and no business mutation was submitted. BE-066 and BE-070 stay PARTIAL for broader company/project role coverage and full A1–A4 acceptance. [QA evidence](build-engine/PURCHASE_RECEIPT_DESTINATION_QA.json), [live browser result](build-engine/PURCHASE_RECEIPT_DESTINATION_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/purchase-receipt-destination-live.png), [Checkpoint163](build-engine/CHECKPOINT_163.md).


## Checkpoint 162 — Explicit no-backorder receipt completion

- Targeted Odoo `TestNamaaBridge.test_react_purchase_receipt_can_cancel_remainder_without_native_backorder`: **1 passed, 0 failures, 0 errors**. Native Odoo completed a 3-of-4 receipt, retained PO received quantity 3, and created no backorder.
- React mocked receipt E2E suite: **3/3 passed**. The no-backorder case unchecked the default checkbox and verified `create_backorder=false` was submitted.
- No product source code changed in this test-focused slice; BE-070 stays PARTIAL for broader company/site and complete acceptance.
- Evidence: [QA JSON](build-engine/PURCHASE_RECEIPT_NO_BACKORDER_QA.json) and [Checkpoint162](build-engine/CHECKPOINT_162.md).


## Checkpoint 161 — Receipt role boundary

- Targeted Odoo `TestNamaaBridge.test_react_purchase_receipt_role_matrix_respects_native_stock_acl`: **1 passed, 0 failures, 0 errors**. Stock-only user received 3/4 and Odoo created a one-unit backorder; Purchase-only user retained read access, saw no receive permission, and direct validation was denied before completion.
- Backend `test_purchase_receipt_routes_require_mutation_and_dispatch_native_company_methods`: **1 passed**; native `AccessError` validation response is HTTP 403.
- Mocked React purchase receipt Playwright: **2 passed**, including the Purchase-only “Stock role required” guidance and hidden action.
- Vite production build passed with the existing large-chunk advisory. Python/JS syntax and diff checks passed.
- Full BE-070 remains PARTIAL. Details: [Checkpoint161](build-engine/CHECKPOINT_161.md).
- Structured evidence: [receipt role QA JSON](build-engine/PURCHASE_RECEIPT_ROLE_QA.json).


## Checkpoint 160 — Native purchase receipt acceptance

- Isolated Odoo 20 transaction test `TestNamaaBridge.test_react_purchase_receipt_accepts_native_lot_and_serial_details`: **1 selected test passed, 0 failures, 0 errors** on `be_qa_receipts_track_codex1`, after upgrading its bridge dependencies. This verifies native lot/serial details, received PO quantities, backorders, existing-lot behavior and duplicate serial rejection.
- Combined with Checkpoint159 live React tests: lot/serial receipt browser journeys **2/2**; Sales customer lifecycle **1/1**; authenticated customer and receipt list APIs HTTP **200** each.
- The live receipt browser clone's separate native shell post-check remains unverified because PostgreSQL had exhausted client slots; both clones were manually confirmed dropped after restarting only the isolated QA Odoo service. See [receipt evidence](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json) and [Checkpoint160](build-engine/CHECKPOINT_160.md).
- Backend business suite not run: `httpx` is absent on host Python and `pytest` is absent in the backend container.


## Checkpoint 159 — Customer and receipt live regressions

- Ordinary Sales customer lifecycle through React, BFF and Odoo on an isolated clone: **1/1 Playwright passed** for create, edit, archive, restore and refreshed listing; clone dropped. See [customer evidence](build-engine/CUSTOMER_LIVE_QA.json).
- Ordinary Stock/Purchase receipt journeys through React, BFF and Odoo: **2/2 Playwright passed** for lot- and serial-tracked partial receipts; React refreshed both as received. Supplemental native shell post-check was blocked by PostgreSQL client exhaustion; the QA Odoo service was restarted and the two temporary clones were confirmed dropped. See [receipt evidence](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json).
- Authenticated read-only customer and receipt list API requests through `:3200`: HTTP **200** each on `be_qa_demo_full_20261025`. `namaa_ai_bridge` was upgraded on isolated `be_accounting_qa_20261024` and `be_qa_demo_full_20261025`; `namaa_ksa` was not changed.
- Python runner syntax and `git diff --check` passed. Full Python backend tests were not available in this environment (`httpx` absent on host; `pytest` absent in backend container).
- Details: [Checkpoint159](build-engine/CHECKPOINT_159.md).


## Checkpoint 158 — Refresh customer and receipt bridge methods in QA

- Upgraded `namaa_ai_bridge` on isolated databases `be_accounting_qa_20261024` and the active demo `be_qa_demo_full_20261025`; Odoo registry inspection confirmed `namaa_customer_list` and `namaa_purchase_receipt_list` exist.
- Read-only Odoo shell calls on the demo DB returned one customer and one receipt. Authenticated React nginx → Odoo login → BFF → Odoo requests returned **HTTP 200** for `/api/customers?limit=1` and `/api/purchase-receipts?limit=1`.
- Live React purchase receipt Playwright: **2/2 passed** for lot-tracked and serial-tracked partial receipts with backorders; React refreshed and showed both as received. The runner's supplemental native shell check hit PostgreSQL's client limit. The isolated Odoo QA service was restarted and both temporary clones were then confirmed dropped; native post-check remains unverified. See [receipt run evidence](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json) and screenshots in `build-engine/frontend/screenshots/`.
- The demo DB was backed up to `/tmp/be_qa_demo_full_20261025-before-namaa-bridge-refresh.dump`. `namaa_ksa` on the separate `:8070` Odoo stack was untouched. Python backend tests were unavailable in the host environment (`httpx` missing) and backend image (`pytest` missing).
- Follow-up: verify both screens in browser as ordinary Sales and Stock/Purchase users; `:8069` QA and `:8070` Namaa remain separate stacks.
- Detailed environment note: [Checkpoint 158](build-engine/CHECKPOINT_158.md).


## Checkpoint 156 — React transition approver choices

- Odoo bridge acceptance on a disposable clone: **1/1 passed** for role/group/named-user template persistence, same-company eligible users/groups, rejection of foreign-company approvers, and denial of options to project managers.
- Native `be_workflow` group-approval acceptance: **1/1 passed**; group member approved a pending transition, and an empty configured group failed closed without advancing the workflow.
- Live React Playwright: **1/1 passed**. Created three-stage workflow with role, group and named-user approvals, published v1, made v2, assigned v1 to a company project type and read persisted relationships back through the API.
- Native postconditions confirmed project inheritance. Disposable database `be_workflow_template_qa_9185e861` was dropped; the source demo and `namaa_ksa` were not modified.
- Backend business suite: **143 passed**. React unit tests: **69 passed**. Vite production build passed with the existing large-chunk advisory. Python compilation, Playwright spec syntax and `git diff --check` passed.
- Detailed result and screenshots: [isolated QA JSON](build-engine/WORKFLOW_TEMPLATE_LIVE_QA.json), [draft](build-engine/frontend/screenshots/live-workflow-template-draft.png), [published](build-engine/frontend/screenshots/live-workflow-template-published.png), [project type](build-engine/frontend/screenshots/live-project-type-assignment.png).


## Checkpoint 155 — React project type lifecycle assignment

- Backend business suite: **142 passed**. Project type assignment contract and route focus: **2 passed**.
- React unit tests: **69 passed**. Production build passed with the existing bundle-size advisory.
- Odoo bridge test on disposable clone: **1 passed, 0 failures/errors**. Project manager assignment, update, current-company options and site-role denial passed. An admin-created native project inherited the assigned lifecycle. QA clone dropped.
- Live React Playwright journey: **1 passed** on a disposable clone. React created and published lifecycle v1, created a draft v2, created a project type, and assigned v1. Native database verification confirmed the company type, assignment, and inheritance by a new project. Clone dropped.
- React `:3200` image rebuilt and root returned HTTP 200; database remains the isolated `be_qa_demo_full_20261025`. The production `namaa_ksa` database was not changed.
- Offline bilingual manual: **213/213 screenshots decoded**; English/Arabic desktop and 390px phone layout passed without overflow. Project-type assignment screenshot search passed; no external requests.

## Checkpoint 154 — React project lifecycle templates

- Native Odoo `namaa_ai_bridge` acceptance on a disposable clone: **1 test passed, 0 failures/errors**. Covers owner-only template create/list/edit, strict condition validation, stale revision rejection, publish immutability, PM role approval and copy-on-write version 2; PM template configuration was denied.
- Backend contract/BFF tests: **2 passed**. Invalid graph payloads are rejected before an Odoo call; create/update/publish/version routes enforce same-origin writes and forward typed contracts.
- Mocked React Playwright `e2e/workflow-templates.spec.js`: **1 passed**.
- Live React Playwright `e2e/workflow-templates.live.spec.js`: **1 passed** against a disposable clone. Native postconditions confirmed company and actor, published version 1, draft version 2, separate copied stage/transition records and PM approver role. The clone was dropped.
- React unit tests: **69 passed**. Production build passed with the existing >500 kB chunk advisory.
- Current `http://localhost:3200/` demo database `be_qa_demo_full_20261025`: read-only admin smoke confirmed customer list, purchase receipts and lifecycle templates return HTTP 200; the lifecycle page displayed the seeded six-stage Saudi delivery template. `namaa_ksa` was not modified.
- Arabic lifecycle view at 390px had no horizontal overflow. Offline manual verifier passed **211/211** embedded images, EN/AR desktop/mobile layout, and no external requests.


## Checkpoint 153 — AI-assisted BOQ proposal

- `backend`: `../.venv/bin/python -m pytest -q tests/test_boq_ai.py` — **9 passed, 3 subtests passed**. Covers safe input/PDF rendering, strict UOM and zero-rate output, local model request/error, BFF same-origin and project/company/occupied-project gates.
- Local model smoke: direct call to `generate_boq_draft` using Ollama `qwen3-vl:30b` and a generated synthetic 10 m × 5 m slab plan plus 150 mm scope — returned a 7.5 m³ slab proposal, 50 m² formwork proposal, and an unknown/null reinforcement quantity; rates were normalized to zero. This does not verify model accuracy on a real project drawing.
- React `npm test` — **69 passed**.
- React `npx playwright test e2e/boq.spec.js --workers=1` — **3 passed**; the AI browser flow uses a mocked BFF response and proves no write occurs before estimator save.
- Runtime demo at `http://localhost:3200/`: read-only admin sign-in against isolated `be_qa_demo_full_20261025` passed; all **15 top-level React sections** opened with no 4xx/5xx API responses. Projects → BOQ → AI dialog opened. A synthetic drawing was uploaded through the live React → authenticated BFF → Odoo route; local `qwen3-vl:30b` returned a 7.5 m³ concrete line at zero rate. No BOQ was saved. This is a technical demo check, not scoped-role or QS accuracy acceptance.
- React `npm run build` — passed; existing ~962 kB JS bundle advisory remains.
- Offline manual: regenerated with **208 screenshots**. `node scripts/verify_manual.mjs` — **208/208 images decoded**, EN/AR desktop and 390px viewport checks passed, current isolated-demo screenshot labels and mocked AI screenshot labels checked, no external requests.
- The Build Engine demo database is an isolated copy; the Namaa `namaa_ksa` source database was not modified.


## React-only workflow handoffs — Checkpoint 152

- React unit suite: **69 passed**. Focused Playwright suites: **42 passed** across CRM, Sales, Purchase, Accounting, customer/supplier directories, productivity/AI, task navigation, contracts and tenders. Mocked business-document browser journeys verified draft create/edit/delete; customer/supplier create and role-aware supplier actions also passed. The new AI-created-record path opens the React Sales workspace and asserts that no `/odoo` link is rendered.
- Vite production build passed; the existing large-bundle advisory remains. `git diff --check` passed.
- The React app is available at local ports 5178/5179. Port 5173 is a separate D2V application.
- See [Checkpoint152](build-engine/CHECKPOINT_152.md). No user-story status changed.

## React quote anomaly review — Checkpoint 151

- Backend BFF/contract focus: **2 tests passed, 17 subchecks passed**. React mocked Purchase → Quote review journey: **1 passed**. Vite production build passed with the existing large-bundle advisory.
- Focused Odoo QA on a disposable clone: **2 tests passed, 0 failures/errors**. Covers immutable quote audit, company/project scope, peer median and landed costs, invalid reason, no-Purchase-role denial and direct write/delete denial.
- Live React → authenticated BFF → Odoo browser journey: **1 passed** as a Purchase buyer. The user flagged a quote, signed out, signed back in, and reopened history in React. Native Odoo verified one persisted review with the exact buyer, company, project, quote line, 100 company-currency landed unit price, 210 peer median and submitted reason. The isolated fixture company used USD. The disposable clone was dropped.
- Screenshots: [quote comparison](build-engine/frontend/screenshots/live-quote-anomaly-review.png) and [saved flag](build-engine/frontend/screenshots/live-quote-anomaly-flagged.png). Structured evidence: [QUOTE_ANOMALY_LIVE_QA.json](build-engine/QUOTE_ANOMALY_LIVE_QA.json); runner: [run_quote_anomaly_live_qa.py](../scripts/run_quote_anomaly_live_qa.py).
- The offline bilingual manual now embeds **203 screenshots**. Manual verification passed: **203/203 decoded**, Arabic/English desktop and phone widths without horizontal overflow, new quote screenshots searchable, no external requests or script errors.
- The quote feature is a verified React workflow slice; BE-064 remains **PARTIAL** because field-level invalid-input feedback and full project/tenant privacy acceptance across roles remain open. Source database was not modified.

## Schedule-linked material availability review — Checkpoint 150

- Isolated Odoo clone: BE-067 snapshot showed task allocation **10**, location/date forecast **5**, shortage **5**. Reopened through the project schedule with actor, company and timestamp. Verified BOQ allocation overrun is rejected, user without Stock/Procurement role is denied, and cross-company review is denied. Temporary clone dropped; source unchanged. See [QA JSON](build-engine/SCHEDULE_SHORTAGE_LIVE_QA.json).
- Live React → authenticated BFF → Odoo journey: **1 passed** with a Stock/Procurement user. The browser saved a second snapshot; Odoo verified the correct review actor, project/company, 10 required, 5 forecast and 5 shortage.
- Backend focused route/contract test: **1 passed**. React unit suite: **69 passed**. Focused mocked React schedule journey: **1 passed**; isolated live schedule journey: **1 passed**.
- Vite production build and Python compilation passed; `git diff --check` passed. Existing bundle-size advisory remains. Disposable QA clone dropped; source database unchanged.
- Updated the bilingual offline manual with the allocation/review steps; verifier passed **199/199** embedded screenshots, EN/AR desktop/phone layouts, gallery actions and no external requests.
- BE-067 remains PARTIAL; full A1–A4, wider role/company/project acceptance, field-level errors and review refresh/rescheduling policy remain.

See [Checkpoint150](build-engine/CHECKPOINT_150.md).

## Material request fulfillment visibility — Checkpoint 149

- Odoo `TestNamaaBridge.test_react_material_request_uses_native_request_and_approval_roles`: **1 passed, 0 failures/errors** on a disposable clone. Native flow created a 12-unit material request, obtained a separate approval, generated and confirmed its RFQ/PO, then received 5; OCA recomputed 12 ordered / 5 received / 7 pending.
- Backend suite: **139 passed**. React unit suite: **69 passed**. Focused mocked material-request Playwright: **1 passed**, verifying refresh updates fulfillment values.
- Live isolated React → authenticated BFF → Odoo Playwright: **1 passed**. Requester submitted an 8-unit request, a separate reviewer approved and created the RFQ, the native PO was confirmed, Stock received 3, and React reopened the request to show 8 ordered / 3 received / 5 outstanding. Native verification confirmed company and `in_progress` state. Temporary clone dropped; source unchanged.
- Vite build passed with the existing chunk-size advisory; Python compilation and `git diff --check` passed. The bilingual offline guide embeds **199 screenshots** and passed its image, EN/AR desktop/phone layout, gallery and offline checks.
- Evidence: [Checkpoint149](build-engine/CHECKPOINT_149.md), [live QA JSON](build-engine/MATERIAL_REQUEST_FULFILLMENT_LIVE_QA.json), [live screenshot](build-engine/frontend/screenshots/live-material-request-fulfillment.png).

## Immutable quality-gate sign-off — Checkpoint 148

- Isolated Odoo clone `be_qg_signoff_qa_5330a61f`: focused `TestNamaaBridge.test_react_quality_gate_review_signoff_and_company_scoped_evidence` **1 passed, 0 failures/errors**. Covers unauthorized role, required failure reason, repeated-signature rejection with unchanged signer/time/result, direct signed-note edit rejection, post-sign evidence rejection and failure payload audit details. Clone dropped.
- Backend suite: **139 passed**. React unit suite: **69 passed**. Focused mocked quality-gate Playwright: **6/6 passed**, including required failure-reason UI and rendering the saved explanation.
- Live isolated React → authenticated BFF → Odoo Playwright: **2/2 passed**. Site role recorded a failure without pass evidence, provided the mandatory reason, and reopened the gate to confirm its result, reason and signer. Native postcondition confirmed company, project, actor and timestamp. Template owner flow also passed. The live runner clone `be_qg_template_live_qa_006d12b6` was dropped after restarting Odoo freed PostgreSQL connections.
- Vite build passed with the existing chunk-size advisory. Python compilation and `git diff --check` passed. The offline bilingual manual rebuilt with **198 embedded screenshots**; its verifier decoded all 198, checked English/Arabic desktop and phone widths, search/viewer interactions and absence of external requests.
- Evidence: [Checkpoint148](build-engine/CHECKPOINT_148.md), [live QA JSON](build-engine/QUALITY_TEMPLATES_LIVE_QA.json), [live sign-off screenshot](build-engine/frontend/screenshots/live-quality-gate-failure-signoff.png).

## React quality-gate template configuration — Checkpoint 147

- Isolated Odoo clone `be_qa_qg_templates_20261025`: focused template configuration test **1 passed, 0 failures, 0 errors**. The test covers invalid-input atomicity, owner role, company scope, publication, published-template immutability, and exact text in a new draft version.
- Backend unittest suite: **139 passed**. React unit suite: **69 passed**. Focused Playwright: **5 mocked journeys passed** (including create/edit/publish/version and field-level errors) and **1 live React → authenticated BFF → Odoo journey passed**. The live journey verified actor/time/company after reopen and Site-role UI denial.
- Vite build passed with the existing bundle-size advisory; Python compilation and `git diff --check` passed. The bilingual offline manual verifier passed **197/197 screenshots**, Arabic/English desktop/mobile layout checks and no external requests. See [Checkpoint147](build-engine/CHECKPOINT_147.md).

## Equipment retirement and Accounting KSA disposal — Checkpoint 146

- Odoo 20 isolated QA database `be_qa_retirement_20261025`: **30 post-tests, 0 failures, 0 errors**. The run covered current equipment behavior and the new optional equipment/accounting integration. Native success verified a posted disposal move, asset closure, reviewer identity and equipment archive; negative tests cover self-approval, missing rejection reason, immutable submitted details, archive-before-disposal and movement-after-retirement denial.
- Backend business/API suite: **136 passed, 153 subtests passed**. React unit suite: **69 passed**. Focused Playwright: **2 passed**, both using mocked APIs; this is not live role acceptance.
- Vite build passed with the existing bundle-size advisory. Python compilation and `git diff --check` passed. Bilingual offline manual: **194/194 screenshots decoded**, English/Arabic desktop and mobile overflow checks passed, no external requests.
- A broad all-addon fresh-install attempt stopped before tests on existing malformed translation metadata in `be_vendor_performance/i18n/ar.po`. Focused QA installed only the needed dependencies and passed. The optional accounting integration remains uninstalled in shared customer databases. See [Checkpoint146](build-engine/CHECKPOINT_146.md).


## Bank reconciliation undo authorization — Checkpoint 145

- Odoo `TestReconcileEngine`: **26 tests, 0 failures, 0 errors**. New coverage denies undo to billing-only and foreign-company accountants, verifies the paid invoice and reconciled statement are unchanged after each denial, and confirms an authorized accountant can undo.
- Live React → authenticated BFF → Odoo: **4 Playwright journeys passed** (cash forecast, partial invoice payment, bank reconciliation, bank reconciliation undo); native postconditions verified exact/split/multi-invoice receipts, SAR 10 modeled write-off, supplier payment, EUR-to-SAR realized FX, SAR 200 partial invoice payment, and restored SAR 225 open invoice / suspense state after undo.
- React: **69 unit tests passed**; full `workspace.spec.js`: **18 passed**, including the delayed candidate-load/edit race. Vite build passed with the existing large-bundle advisory. The subsequent live short-receipt journey passed with a SAR 400 match and SAR 10 write-off against the SAR 390 bank line.
- The Namaa source was cloned read-only. Accounting KSA and synthetic transactions were limited to the disposable clone, which was dropped. See [Checkpoint145](build-engine/CHECKPOINT_145.md), [structured result](build-engine/BANK_RECONCILIATION_LIVE_QA.json), and [runner](../scripts/run_bank_reconciliation_live_qa.py).
- Bilingual offline manual regenerated with **192 embedded screenshots**; its verifier passed both languages at 1440px and 390px, all image decoding, search/filter/enlarge/Escape and no-external-request checks.
- BE-080 remains **PARTIAL**; wider A1–A4, accounting policy coverage and complete role/company acceptance remain open. The live authorized React undo journey is verified.

## Project minimum-stock rules and reorder alerts — Checkpoint 144

- Backend business/API suite: **134 passed, 148 subtests passed**. Includes strict threshold/revision contracts, same-origin mutation guards, list filters, restore/archive routes and Odoo method dispatch.
- React suite: **69 passed**. Vite production build passed; existing JavaScript bundle-size advisory remains.
- Focused Odoo `TestNamaaBridge.test_react_project_reorder_rules_use_native_orderpoints_and_enforce_roles`: **1 passed, 0 failures/errors** on a disposable clone. Verified native orderpoint creation/update, project/location/product/company values, below-minimum forecast and suggestion, duplicate and invalid-threshold rejection, Stock User read / write denial, no-role denial, archive/restore and cross-company non-disclosure.
- Live React → authenticated BFF → Odoo journey: **1 passed**. Manager created the native rule; invalid target below minimum showed inline field error without submitting; Warehouse Officer reopened the forecast alert without rule controls. Native Odoo verified on-hand 3, forecast 3, minimum 5, target 12, suggestion 9 and creator/time.
- Clone dropped; source QA/demo databases unchanged. Screenshots and structured evidence: [REORDER_RULES_LIVE_QA.json](build-engine/REORDER_RULES_LIVE_QA.json), [editor](build-engine/frontend/screenshots/live-reorder-rule-editor.png), [alert](build-engine/frontend/screenshots/live-reorder-rule-alert.png), [officer view](build-engine/frontend/screenshots/live-reorder-rule-officer.png). Python compilation and `git diff --check` passed.
- All four supplied BE-075 acceptance criteria are verified; story status: **DONE**. Reorder suggestions remain advisory and use the purchase-request approval path.

## Stock count and variance approval — Checkpoint 143

- Backend business/API suite: **132 passed, 143 subtests passed**. Includes strict count payload contracts, same-origin mutation boundary and Odoo bridge dispatch.
- React unit suite: **69 passed**. Mocked Playwright stock count submit → manager approve/apply: **1 passed**.
- Focused Odoo 20 `TestNamaaBridge.test_react_stock_count_requires_independent_manager_and_applies_native_inventory_adjustment`: **1 passed, 0 failures/errors** on a clone of `be_site_materials_qa_20261025`. Verified native stock change 10→8, an independent approving identity, repeated/self approval denial, direct model create/write/delete denial, invalid multi-line no-partial persistence, stale snapshot rejection without stock mutation, no-Stock-role denial and foreign-company non-disclosure. Clone dropped.
- Mocked browser journey verifies a negative quantity renders beside the quantity field and does not call the create route; then valid count and reviewer approval pass: **1 passed**.
- Live React → authenticated BFF → Odoo role-separated journey: **1 passed**. Warehouse Officer submitted a −3 variance against 30; Stock Manager approved; native Odoo reopened the applied count, verified actors/timestamps/company and on-hand 27. Disposable clone dropped. Structured evidence and screenshots: [STOCK_COUNT_LIVE_QA.json](build-engine/STOCK_COUNT_LIVE_QA.json), [review](build-engine/frontend/screenshots/live-stock-count-review.png), [pending](build-engine/frontend/screenshots/live-stock-count-pending.png), [applied](build-engine/frontend/screenshots/live-stock-count-applied.png).
- Vite production build, Python compilation and `git diff --check`: **passed**. Existing large JavaScript bundle advisory remains.
- All four supplied BE-074 acceptance criteria have evidence; story status is DONE. The workspace currently counts balances already represented as Odoo quants; newly discovered products or missing lot/serial balances are future scope.

## Project material return — Checkpoint 142

- Native Odoo return flow: **2 focused transaction tests passed, 0 failures/errors** on a disposable clone. Verified partial untracked return, lot and serial return, exact return to the original project location, Odoo's native `return_id` / `origin_returned_move_id` linkage, BOQ move-line and analytic links, quantity/cost reversal, retry idempotency, over-return rejection without stock change and no-stock-role denial.
- Backend: **130 tests passed**, including strict return payload and authenticated same-origin route behavior.
- React: **69 unit tests passed**; mocked browser issue→lot return journey **1 passed**; Vite production build passed with the existing large-bundle advisory.
- `.venv` Python compilation and `git diff --check` passed. Disposable QA clone was dropped; source QA and live/demo databases were not modified.
- Live React → authenticated BFF → Odoo Warehouse Officer journey: **1 passed**. Native Odoo verified issue 6 / return 2, same lot/site/project/company, acting user/time, yard 15→9→11, incoming analytic +SAR 80 and BOQ actuals SAR 160 / 4 units. Evidence: [SITE_MATERIAL_ISSUE_LIVE_QA.json](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json); screenshots: [return review](build-engine/frontend/screenshots/live-site-material-return-review.png), [validated return](build-engine/frontend/screenshots/live-site-material-return-validated.png), [BOQ actuals](build-engine/frontend/screenshots/live-site-material-return-boq-actuals.png). Disposable clone dropped; no source/live/demo DB changed.
- BE-073 acceptance verified: authenticated Warehouse Officer flow, invalid-input/over-return handling, reopened audit/project/company state, no-Stock-role denial and foreign-company denial. Story status: **DONE**.


## Bank reconciliation preview ordering — Checkpoint 141

- Fixed stale preview responses overwriting newer results after a transaction edit or selection.
- Targeted React Playwright regression delays the initial SAR 390 receipt preview until after the edited SAR 400 match returns. SAR 10 remains visible; a SAR 10 model write-off clears it. **1 passed**.
- Full React `workspace.spec.js`: **17 passed**. Vite production build: **passed**, with the existing large-bundle advisory.
- An intermediate retry used the less-loaded Odoo 20 stack while Build Engine PostgreSQL was near capacity; its Odoo add-on path lacked OCA `purchase_request`, so the upgrade stopped before browser tests and the clone was dropped. The subsequent Checkpoint141 run used the full Build Engine add-on path and passed the live accounting journeys.

## Bank reconciliation live follow-up — Checkpoint 141

- React stale-preview protection: targeted delayed-response Playwright regression **1 passed**; full workspace suite **17 passed**.
- Native Accounting KSA `TestReconcileEngine`: **0 failed, 0 errors across 25 tests; 1 conditional skip**.
- Live React → authenticated BFF → Odoo: **3 Playwright journeys passed** (cash forecast, invoice payment and full reconciliation journey). Short receipt: SAR 390 bank line against SAR 400 invoice; Odoo model posted SAR 10 expense, paid the invoice, reconciled the statement line and left zero suspense. Split, multi-invoice, supplier and EUR/SAR cases passed in the same run.
- Native verification confirmed all tested document/payment postconditions. The clone `be_bank_rec_live_qa_95b3d187` was dropped; source `namaa_ksa` was unchanged. Screenshot: [short receipt model review](build-engine/frontend/screenshots/live-short-receipt-model-review.png). Full evidence: [BANK_RECONCILIATION_LIVE_QA.json](build-engine/BANK_RECONCILIATION_LIVE_QA.json).
- Vite build and QA runner Python compilation passed; the build retains its existing bundle-size advisory.

## React document payment — Checkpoint 140

- Native `TestNamaaBridge.test_react_document_payment_uses_native_wizard_partial_balance_and_idempotency`: **1 passed, 0 failures/errors**.
- Focused backend payment contract and same-origin route tests: **2 passed**.
- React business workspace Playwright suite: **22 passed** including partial payment review and request payload checks.
- Live React → authenticated BFF → native Odoo: **1 passed** on a disposable `namaa_ksa` clone. A SAR 200 customer receipt against SAR 500 left SAR 300 open; Odoo verified payment, Bank journal, company and persisted operation key. Clone dropped; source DB unchanged.
- Screenshot: [live document payment](build-engine/frontend/screenshots/live-accounting-document-payment.png). Full evidence: [ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json](build-engine/ACCOUNTING_DOCUMENT_PAYMENT_LIVE_QA.json).
- The earlier combined QA attempt failed at the short-receipt preview. Checkpoint141 added latest-preview response ordering and reran the combined live journey successfully; see the follow-up section below and the structured QA result.

## React cash forecast — Checkpoint 139

- Native Odoo `TestCashForecast`: **7 tests, 0 failures, 0 errors**; one optional recurring-payments test skipped because `om_recurring_payments` is absent.
- Focused FastAPI route validation/company-scope test: **1 passed**.
- Mocked React Playwright tests: **2 passed** (live-data rendering contract and non-financial preview behavior).
- Live React → BFF → Odoo forecast: **1 passed** on a disposable clone of `namaa_ksa`; SAR 600 expected receipt and partner detail rendered for `Namaa Saudi Arabia`.
- Existing live bank reconciliation journey in the same run: **1 passed**. The disposable clone was dropped; the source database was not modified.
- Vite production build: **passed**, with the existing large-bundle advisory. Screenshot: [live cash forecast](build-engine/frontend/screenshots/live-cash-forecast.png). Structured result: [CASH_FORECAST_LIVE_QA.json](build-engine/CASH_FORECAST_LIVE_QA.json).

## Duplicate bank reconciliation proposal guard — checkpoint138

- Backend API contract/route test: **1 passed**. A proposal with a repeated journal-item ID returns HTTP 422, and the BFF does not call Odoo.
- Odoo `TestReconcileEngine` passed on a disposable SAR-configured `namaa_ksa` clone, including native duplicate-ID preview and apply rejection. The invoice residual and bank statement state remained unchanged.
- Live React → authenticated BFF → Odoo journey: **1 passed** for exact, supplier, split, modeled short, multi-invoice and EUR-to-SAR receipts. Native postconditions passed and the clone was dropped.
- See [checkpoint138](build-engine/CHECKPOINT_138.md), [contract](../backend/app/contracts.py), [native validation/test](../addons/accounting_ksa/features/reconciliation/tests/test_reconcile_engine.py), and [structured evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json).

## Reconciliation role/company denial — checkpoint137

- Odoo `TestReconcileEngine` passed on a disposable clone of the SAR-configured `namaa_ksa` database, including the new regression. Billing-only access was denied for detail, candidates, preview and apply. An accountant whose only allowed company differed from the statement company was denied detail, preview and apply. The invoice residual and unreconciled statement were unchanged after the denials.
- The live React → authenticated BFF → Odoo journey passed on the same disposable QA clone, including the EUR-to-SAR realized exchange case and all existing receipt/payment scenarios. Native ledger postconditions passed and the clone was dropped.
- See [checkpoint137](build-engine/CHECKPOINT_137.md), [native test](../addons/accounting_ksa/features/reconciliation/tests/test_reconcile_engine.py), and [structured live QA evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json).

## Foreign-currency bank reconciliation — checkpoint136

- Live React → authenticated BFF → Odoo Playwright journey: **1 passed**, including EUR transaction display, EUR preview, apply, and reopening the reconciled ledger entry.
- Native verification on a disposable clone of `namaa_ksa`: the SAR-configured company paid the EUR 200 invoice with zero residual; the statement recorded EUR 200 and SAR 790, reconciled with zero residual; suspense was clear; and Odoo posted a realized SAR 10 exchange difference at the controlled QA rate.
- The same live journey passed exact customer receipt, supplier payment, two-part receipt, configured-model short receipt, and one receipt matched to two invoices. The disposable clone was dropped.
- Accounting KSA was installed only in the clone; source `namaa_ksa` was not modified. The clone was dropped after verification. See [checkpoint136](build-engine/CHECKPOINT_136.md), [structured evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json), [EUR review screenshot](build-engine/frontend/screenshots/live-eur-receipt-review.png) and [reconciled screenshot](build-engine/frontend/screenshots/live-eur-receipt-reconciled.png).

## Live multi-invoice bank receipt — checkpoint135

- Live React → authenticated BFF → Odoo Playwright: **1 passed**; one SAR 1,200 bank receipt was matched to two posted same-customer invoices of SAR 500 and SAR 700. React displayed both matches and their separate amounts, applied the balanced proposal, and reopened the reconciled line with both source invoice references.
- Native Odoo verified both invoices are paid with zero residual, both receivable counterparts reconcile against the bank statement move, the SAR 1,200 statement line is reconciled, and suspense is clear. The disposable clone was dropped.
- The same browser run passed exact receipt, two-part receipt, configured SAR 10 short-receipt write-off and supplier-payment scenarios. See [checkpoint135](build-engine/CHECKPOINT_135.md), [structured evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json), and the two multi-invoice screenshots linked there.
- BE-080 remains PARTIAL for FX, other overpayment/tax policies, duplicate/invalid and denial cases, wider role/company acceptance and complete A1–A4.

## Live configured short-receipt reconciliation — checkpoint134

- Live React → authenticated BFF → Odoo Playwright: **1 passed** across exact customer receipt, split receipt, configured-model short receipt and supplier payment scenarios.
- Fixed suggestion ranking so an explicit invoice reference outranks an unrelated same-customer invoice with an exact amount match. Native `TestReconcileEngine`: **23 post-tests, 0 failures/errors, 1 conditional skip**, including `test_reference_beats_unrelated_exact_amount_candidate`.
- The accountant reconciled a SAR 390 receipt against a SAR 400 referenced invoice using the configured Odoo fee model. Native verification confirmed paid state, zero invoice/statement residuals, a SAR 10 expense debit and cleared suspense. Browser and native-test disposable clones were dropped.
- See [checkpoint134](build-engine/CHECKPOINT_134.md), [structured live evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json), [model review screenshot](build-engine/frontend/screenshots/live-short-receipt-model-review.png), and [native regression](../addons/accounting_ksa/features/reconciliation/tests/test_reconcile_engine.py).
- BE-080 remains PARTIAL for other write-off/tax policies, overpayment handling, FX, multi-document statements, duplicate/invalid and denial cases, wider role/company acceptance and complete A1–A4.

## Live React split-receipt reconciliation — checkpoint133

- Live React → authenticated BFF → Odoo Playwright: **1 passed**. One ordinary accountant reconciled a SAR 1,100 customer invoice from SAR 400 and SAR 700 incoming statement lines, alongside the existing exact customer receipt and supplier payment scenarios.
- React reviewed the first partial match with a SAR 400 counterline; then applied the SAR 700 remainder to the reduced invoice balance. Native Odoo confirmed both statement lines reconciled, the invoice is paid, invoice and statement residuals are zero, correct receivable links exist and suspense is clear.
- The disposable clone was dropped. See [checkpoint133](build-engine/CHECKPOINT_133.md), [structured evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json), [partial review screenshot](build-engine/frontend/screenshots/live-split-receipt-first-review.png) and [settled screenshot](build-engine/frontend/screenshots/live-split-receipt-settled.png).
- BE-080 remains PARTIAL for overpayment/write-off, FX, multiple-source-item matching, duplicate/invalid and denial/company-isolation cases, broader roles and complete story acceptance.

## Live React supplier payment reconciliation — checkpoint132

- Live React → authenticated BFF → Odoo Playwright: **1 passed**, covering a SAR 1,250 customer receipt and a SAR 875 outgoing supplier payment on one disposable clone. The accountant reviewed the proposed open item and balanced preview, applied reconciliation, then reopened each statement line.
- Native Odoo checks: **passed** for paid customer invoice and vendor bill, zero document/statement residuals, statement receivable/payable counterparts reconciled to the correct source documents, correct company/partner identity and no suspense residual.
- The clone of `be_accounting_qa_20261024` was dropped. Four React screenshots and structured evidence are linked from [checkpoint132](build-engine/CHECKPOINT_132.md) and [QA JSON](build-engine/BANK_RECONCILIATION_LIVE_QA.json).
- BE-080 remains PARTIAL: partial/multiple/foreign-currency cases, duplicate/invalid and denial coverage, wider role/company acceptance, and complete story A1–A4 remain.

## Live React bank reconciliation — checkpoint131

- Live React → authenticated BFF → Odoo Playwright journey: **1 passed**. An ordinary accountant selected a posted customer invoice, confirmed Odoo's zero-balance preview, applied the match, and reopened the reconciled statement line.
- Native Odoo postcondition verification: **passed**. Invoice `INV/2026/00001` is posted and paid with zero residual; its SAR 1,250 statement line is reconciled, the statement receivable counterpart is linked to the invoice receivable, and no suspense residual remains.
- Test ran in a disposable clone of `be_accounting_qa_20261024`, which was dropped after verification. See [structured evidence](build-engine/BANK_RECONCILIATION_LIVE_QA.json), [review screenshot](build-engine/frontend/screenshots/live-bank-reconciliation-review.png), [reconciled screenshot](build-engine/frontend/screenshots/live-bank-reconciliation-posted.png), and [checkpoint131](build-engine/CHECKPOINT_131.md).
- BE-080 remains PARTIAL: this verifies one full incoming customer receipt. Complete payment/receipt variants, duplicate/invalid/role-denial coverage, wider role/company UAT and full story A1–A4 remain open.

## Interactive React project Gantt — checkpoint130

- `npx playwright test e2e/project-plan.spec.js --workers=1`: **1 passed**. The journey opens the Foundation excavation task editor directly from its Gantt bar, changes planned start through the existing optimistic-revision update payload, and verifies the saved schedule and other project planning flows.
- `npm run build`: **passed**; the existing JavaScript chunk-size advisory remains.
- Gantt editing uses existing Odoo task permissions and revision validation; this is a mocked-BFF React journey, not live ordinary-role acceptance. BE-042 remains PARTIAL. See [checkpoint130](build-engine/CHECKPOINT_130.md).

## CRM won opportunity to delivery project — checkpoint129

- Live React → BFF → Odoo Playwright: **1 passed** using an isolated clone of `be_qa_demo_full_20261024` and a Sales + Project Manager user. The user confirmed project creation from an unlinked won opportunity; a retried BFF request returned the same project (`created: false`).
- Native verification confirmed one active project, exact CRM opportunity and company linkage, expected name, and authenticated creator. The disposable database was dropped.
- Review and linked-project screenshots: `build-engine/frontend/screenshots/live-crm-project-review.png` and `live-crm-project-linked.png`. Full record: [structured QA evidence](build-engine/CRM_WON_PROJECT_LIVE_QA.json).
- BE-017/039 remain PARTIAL for full tender-award workflow acceptance and the policy decision for Sales users without native Project Manager project-create access.

## React project timesheets — checkpoint128

- Backend `python -m unittest tests.test_business -q`: **124 passed**. New coverage validates bounded strict hours/project/task inputs, same-origin mutation protection and native bridge forwarding.
- Isolated Odoo 20 clone `be_timesheet_react_qa_20261025`: targeted `TestNamaaBridge.test_react_timesheet_entry_uses_native_costing_and_is_retry_safe` **1 passed, 0 failures, 0 errors**. Verified current employee, analytic project/task, 3.5 hours, native analytic expense −SAR 175, linked BOQ labor actual +SAR 175, idempotent retry, conflicting payload rejection and cross-project task rejection.
- Live React → BFF → Odoo Playwright `frontend/e2e/timesheets.live.spec.js`: **1 passed**. A limited timesheet user authenticated to the disposable clone, selected the seeded project/task and recorded 2.5 hours; native verification found the expected employee, company, task, date, creator, operation metadata and SAR 125 labor cost. Review and saved-state screenshots are in `build-engine/frontend/screenshots/live-timesheet-{review,recorded}.png`.
- Mocked React Playwright `frontend/e2e/timesheets.spec.js`: **1 passed**, including the submitted operation UUID, custom same-origin header and register update.
- Vite production build: **passed** with the existing bundle-size advisory. QA database and cloned filestore were removed; no demo/customer database changed.
- Portable bilingual user manual rebuilt with the timesheet screenshot and verified **164/164** embedded screenshots offline, including desktop/mobile English/Arabic and gallery/viewer interactions.
- Disposable DB cleanup passed; no source demo/customer database was modified. Broader approver/manager, multiple-company and finance cost-policy acceptance remains open. See [checkpoint128](build-engine/CHECKPOINT_128.md), [live evidence](build-engine/TIMESHEET_LIVE_QA.json) and [structured feature evidence](build-engine/TIMESHEET_REACT_QA.json).

## BE-072 project material issue actual-cost reconciliation — checkpoint125

- Isolated Odoo transaction test `TestNamaaBridge.test_react_project_material_issue_consumes_site_stock_and_links_confirmed_boq`: **1 passed, 0 failures, 0 errors** on a fresh clone; `be_boq`, `be_project`, `be_site` and `namaa_ai_bridge` were upgraded, and cleanup verified zero remaining clone databases. It verifies a confirmed BOQ issue, dedicated analytic-cost operation (default Delivery unchanged), project analytic plan, native signed analytic amount −200, linked BOQ actual +200, quantity 4, site stock reduction, retry safety, over-issue rollback and permission boundaries.
- Live React → authenticated BFF → Odoo Stock Manager Playwright: **1 passed**. Fresh isolated lot-tracked fixture issued 6 units at SAR 40; native Odoo verification found analytic amount −SAR 240 and BOQ actual +SAR 240, exact BOQ/project/company, lot identity, actor/timestamp, site balance 15→9, and unchanged standard Delivery configuration. QA clone cleanup verified zero remaining databases. Evidence: [live QA](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json), [issue screenshot](build-engine/frontend/screenshots/live-site-material-issue-validated.png) and [BOQ actuals screenshot](build-engine/frontend/screenshots/live-site-material-issue-boq-actuals.png).
- Python compilation, Playwright JavaScript syntax, screenshot-manifest JSON, and `git diff --check` passed. The offline bilingual user manual rebuilt and verified **159/159 screenshots**, English/Arabic desktop and phone layouts, and search/filter/viewer interactions. BE-072 remains PARTIAL for broader role/company acceptance and finance confirmation of valuation methods and recognition timing. See [checkpoint125](build-engine/CHECKPOINT_125.md) and [ADR0015](adr/0015-project-material-actual-costs.md).

## BE-072 tracked project material issue — checkpoint124

- Isolated native Odoo transaction test `TestNamaaBridge.test_react_project_material_issue_preserves_lot_and_serial_traceability`: **1 passed, 0 failures/errors**. It issues multi-lot and serialized stock from an exact project location, checks lot/serial identifiers and confirmed BOQ line persistence, and rejects fractional serial quantity. The QA source was cloned, `be_project`, `be_site`, and `namaa_ai_bridge` upgraded on the clone, and cleanup confirmed zero remaining clone databases.
- Mocked React stock issue Playwright: **1 passed**, including the rendered lot identity. `git diff --check` passed for touched source files. Live React → BFF → Odoo Stock Manager lot-tracked issue passed and verified the exact native lot and BOQ line; site balance 15→9 and disposable clone cleanup count 0. Live serial role acceptance and BOQ/project actual-cost reconciliation remain open.

## BE-072 React project material issue — checkpoint123

- Odoo targeted `TestNamaaBridge.test_react_project_material_issue_consumes_site_stock_and_links_confirmed_boq`: **1 passed, 0 failures, 0 errors**. Assertions cover exact site stock reduction, outgoing native picking, project and confirmed BOQ move-line linkage, operation retry, over-issue rejection without a committed picking/stock change, missing Stock role denial and foreign-project denial.
- Backend business suite: **122 passed, 118 subtests passed**. The tests cover the strict issue contract, same-origin mutation guard and authenticated native route delegation.
- Mocked React stock issue Playwright: **1 passed**. Live React → BFF → Odoo Stock Manager Playwright: **1 passed**. Disposable QA evidence confirms `WH/OUT/00075` Done, 6 issued, on-hand 15→9, project/BOQ/company and actor/timestamp; clone cleanup count **0**.
- Vite production build passed (existing chunk size advisory). User manual rebuilt and checked **158/158 screenshots**, English/Arabic desktop and phone overflow, and guide filtering/viewer/empty-state interactions. `py_compile` and `git diff --check` passed.
- BE-072 remains PARTIAL for BRD 8.1 BOQ/project actual cost reconciliation and broader tracked-product/role/company acceptance. See [checkpoint123](build-engine/CHECKPOINT_123.md) and [live evidence](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json).

## BE-071 site transfer — complete React validation — checkpoint122

- Full isolated Odoo `namaa_ai_bridge:TestNamaaBridge` suite: **58 post-tests, 0 failures, 0 errors**. Includes lot-preserving partial movement/backorder, serial one-unit enforcement and serial remainder backorder, invalid/over-reservation rejection without partial movement, denial for a user without Stock access, and denial for a Stock Manager from another company.
- Backend business suite: **120 passed, 114 subtests passed**. React unit suite: **69 passed**. Focused site transfer Playwright: **2 mocked tests passed**. Vite production build passed with its existing large-chunk advisory.
- Live React → authenticated BFF → Odoo Stock Manager Playwright: **1 passed** on a disposable cloned isolated QA database. The user selected lot stock, created/reserved 6, submitted actual 4, chose a backorder, and refreshed the Done transfer in React. Odoo shell verified a Done picking, same project/company, create and validate actors, `date_done`, exact lot, 4 units at destination, and a native backorder of 2. The disposable database was dropped; cleanup count was zero. Evidence: [QA JSON](build-engine/SITE_TRANSFER_LIVE_VALIDATION_QA.json), [review screenshot](build-engine/frontend/screenshots/live-site-transfer-lot-validation-review.png), [validated/reopened screenshot](build-engine/frontend/screenshots/live-site-transfer-lot-validated.png).
- Manual rebuilt and verified: **155 screenshots** decoded; bilingual desktop/mobile overflow and interaction checks passed. Python compilation and `git diff --check` passed. BE-071 meets all four supplied generic criteria and is DONE; other inventory stories and module parity remain incomplete. See [checkpoint122](build-engine/CHECKPOINT_122.md).

## React lot/serial project site transfers — checkpoint121

- Isolated Odoo `namaa_ai_bridge:TestNamaaBridge`: **58 post-tests, 0 failures, 0 errors**. New coverage verifies lot reservation, exact lot persistence, partial quantity movement/backorder, serial reservation, at-most-one serial quantity, and a native one-of-two serial transfer/backorder.
- Backend `test_business.py`: **120 passed, 114 subtests passed**. React unit tests: **69 passed**. Site transfer mocked Playwright: **2 passed**, including exact lot move-line payload and quantity review. Vite build passed with the existing large-chunk advisory.
- Live isolated Stock Manager React → BFF → Odoo: **1 passed** for lot-tracked transfer creation, reservation, exact lot-detail display and canceling the review dialog. The dedicated QA runner removed and verified the transfer, project location, lot, product and user. Live validation was not exercised. Evidence: [QA JSON](build-engine/SITE_TRANSFER_TRACKED_LIVE_QA.json) and [screenshot](build-engine/frontend/screenshots/live-site-transfer-lot-detail.png).
- The user manual now documents lot/serial transfer quantities in React and still directs lot-tracked purchase receipts to native Odoo detailed operations. Manual rebuild/verification passed with 153 screenshots decoded offline and English/Arabic desktop/mobile overflow checks. `py_compile` and `git diff --check` passed. See [checkpoint121](build-engine/CHECKPOINT_121.md).

## React project site stock transfers — checkpoint120

- Isolated Odoo `namaa_ai_bridge:TestNamaaBridge`: **57 post-tests, 0 failures, 0 errors**. Includes native site transfer authorization, project/company/location validation, retry fingerprint, stock reservation, stale revision and partial-validation/backorder behavior.
- Live isolated React → authenticated BFF → Odoo Stock Manager flow passed create, reserve and list refresh; the screenshot records Ready to transfer. Temporary picking, location, QA product and QA user were removed and cleanup counts verified as zero. Evidence: [SITE_TRANSFER_LIVE_QA.json](build-engine/SITE_TRANSFER_LIVE_QA.json), [screenshot](build-engine/frontend/screenshots/live-site-transfer-reserved.png). Live validation was not exercised.
- Backend business suite: **120 passed, 111 subtests passed**. React unit suite: **69 passed**. Focused mocked Playwright journey: **1 passed**. Vite production build passed with the existing large-chunk advisory. The user manual rebuilt with 152 embedded screenshots; offline verification passed screenshot decoding, bilingual desktop/mobile overflow checks and interaction checks. `py_compile` and `git diff --check` passed. Tracked products require detailed operations in native Odoo and remain a React gap. See [checkpoint120](build-engine/CHECKPOINT_120.md).

## React project site locations — checkpoint119

- Isolated Odoo `be_project,namaa_ai_bridge,be_boq`: **56 post-tests, 0 failures, 0 errors**. New test covers Stock Manager creation, project/company/parent links, listing, invalid input, unauthorized role and foreign-company project denial.
- Backend business suite: **118 passed**. React unit suite: **69 passed**. Mocked React Playwright: **1 passed**. Live isolated React → BFF → Odoo Stock Manager create/refresh/reopen: **1 passed**; temporary QA records were removed and verified. Screenshot: [live-site-locations.png](build-engine/frontend/screenshots/live-site-locations.png); evidence: [SITE_LOCATION_LIVE_QA.json](build-engine/SITE_LOCATION_LIVE_QA.json).
- Vite production build passed with the existing large-chunk advisory; Python compilation and `git diff --check` passed. Browser QA included both mocked API coverage and live isolated Stock Manager acceptance; broader multi-company/project privacy remains open. See [checkpoint119](build-engine/CHECKPOINT_119.md).

## React purchase receipts — checkpoint118

- Isolated Odoo `namaa_ai_bridge,be_boq`: **55 post-tests, 0 failures, 0 errors**. Native test covers receipt actual quantities, purchase received quantity, native partial backorder, stale-write and over-receipt rejection, unauthorized-role denial and foreign-company denial.
- Backend business suite: **116 passed**. React unit suite: **69 passed**. Mocked receipt Playwright: **1 passed**.
- Vite production build passed with the existing large-chunk advisory. Live role-based receipt browser acceptance was not run; lot/serial receipt entry remains a known limitation. See [checkpoint118](build-engine/CHECKPOINT_118.md).

Latest execution: 2026-10-25, preserved `master@5b3f3f7` baseline plus uncommitted incremental implementation. Checkpoint117 adds React approved-material-request-to-native-draft-RFQ handoff and live isolated approval/sourcing acceptance; checkpoint116 added React material-request drafts and native submit/approval controls over OCA Purchase Requests with BOQ/analytic links; checkpoint115 adds React Accounting KSA bank maps and seven-format browser coverage; checkpoint114 adds native Odoo-backed React bank import with live accountant QIF acceptance; checkpoint113 verifies live manual CRM lead creation/reopen in USD and fixes the CRM-only currency guard; checkpoint112 verifies dashboard analytics in SAR. Checkpoint110 adds live React CRM pipeline stage/probability editing and fixes stale-write response mapping; checkpoint109 adds the React CRM promotion request, independent Owner decision and audit-history workflow; checkpoint108 adds audited React lead qualification; checkpoint107 adds React site-material usage; checkpoint105 exposes all ten native accounting report types through React; checkpoint104 adds the React corrective maintenance request workflow; checkpoint103 adds immutable React maintenance repair-cost capture and signed corrections; checkpoint102 adds React preventive maintenance planning and native request generation; checkpoint101 adds the combined React RFI/submittal project log; checkpoint100 adds live drawing-linked submittal review and fixes parent-scoped JSON-2 attachment download; checkpoint99 adds React drawing task links; checkpoint98 adds the React project drawing register and file-backed revisions; checkpoint97 adds React nonconformance corrective-action lifecycle controls; checkpoint96 adds React daily safety checklists; checkpoint95 adds React quality-gate inspection/evidence workflows; checkpoint94 adds React safety incident/near-miss reports; checkpoint93 makes BOQ imports retry-safe; checkpoint92 adds React BOQ revision comparison; checkpoint91 adds React BOQ spreadsheet import. Older audit/QA runs are retained as historical evidence with their original limitations.

## React material-request to RFQ handoff — checkpoint117

- Isolated Odoo `namaa_ai_bridge,be_boq`: **54 post-tests, 0 failures, 0 errors**. Native bridge test covers reviewer Purchase ACL, company supplier selection, native OCA wizard RFQ creation, request in-progress transition, BOQ line retention, analytic distribution and stale-write denial.
- Backend business suite: **115 passed, 102 subtests passed**; strict RFQ payload and same-origin BFF dispatch covered. React unit suite: **69 passed**; mocked material-request create/submit/approve/RFQ Playwright: **1 passed**.
- Live isolated React → BFF → Odoo procurement-role create/submit/approve/RFQ Playwright: **1 passed**. Screenshot: [live RFQ handoff](build-engine/frontend/screenshots/live-material-request-rfq.png). Temporary request, draft RFQ, supplier, product and test user were removed through Odoo ORM and verified absent.
- Vite production build passed with the existing large-chunk advisory; Python compilation and `git diff --check` passed. BE-060 remains PARTIAL; requester/reviewer role separation, receipts/actual reconciliation and complete A1–A4/company-boundary acceptance remain open. See [checkpoint117](build-engine/CHECKPOINT_117.md).

## React material request — checkpoint116

- Isolated Odoo `namaa_ai_bridge,be_boq`: **54 post-tests, 0 failures, 0 errors** (one optional uninstalled-module skip). New test covers procurement-role BOQ options/link, analytic distribution, draft creation, requester submission, authorized reviewer approval, stale write rejection and unauthorized role denial.
- Backend business suite: **115 passed, 100 subtests passed**. React unit suite: **69 passed**. Focused mocked create→submit→approve React Playwright: **1 passed**. Live isolated procurement-role React → BFF → Odoo draft create/read Playwright: **1 passed**.
- Vite production build passed with the existing large-chunk advisory. Python compilation and `git diff --check` passed. The live draft, QA user and fixture product were removed through Odoo ORM.
- BE-060 remains PARTIAL pending live requester/reviewer transitions, React approved-request RFQ handoff, receipts/actual reconciliation and full A1–A4/company-boundary acceptance. See [checkpoint116](build-engine/CHECKPOINT_116.md) and [live draft screenshot](build-engine/frontend/screenshots/live-material-request-draft.png).

## React bank import formats and CSV/Excel maps — checkpoint115

- Odoo `namaa_ai_bridge`: 53 post-tests, 0 failures, 0 errors; one optional module-dependent test skipped.
- Backend business tests: 113 passed; React unit tests: 69 passed; React workspace Playwright: 16 passed, including mocked map configuration/assignment.
- React production build passed; Vite reports the existing large-main-chunk advisory.
- Isolated live QA: accounting manager created, assigned, unassigned and deleted an Odoo-native CSV map through React; mapped CSV/XLSX and native QIF/OFX/QFX/MT940/CAMT.053 imports each returned one transaction and appeared in React Bank reconciliation (format-matrix Playwright: 1 passed). QA records were cleaned.
- Odoo native `TestStatementImport`: 8 post-tests, 0 failures, 0 errors, including OFX without optional `LEDGERBAL`.
- BE-080 remains PARTIAL pending duplicate/invalid/role-denial cases, banking-role edge cases and remaining payment/receipt requirements. See [checkpoint115](build-engine/CHECKPOINT_115.md).

## React bank statement import — checkpoint114

- Isolated `be_accounting_qa_20261024` Odoo bridge suite: **52 post-tests, 0 failures, 0 errors**, including native QIF import, source attachment, summary and non-accountant denial.
- Backend business suite: **111 passed**; React unit suite: **69 passed**; mocked statement import Playwright: **1 passed**; live ordinary-accountant React → BFF → Odoo QIF import and reconciliation visibility: **1 passed**; Python compilation and Vite production build passed.
- Full workspace browser suite: **15 passed**, including 1440/768/390px English/Arabic responsive journeys, accounting preview, mocked statement import and existing reconciliation flows. Two legacy fixture assumptions (fixed five-row counts and fixed language startup) were updated to match the 29-row preview and either stored locale.
- SQL verification after ORM cleanup: zero imported `React live statement import QA` rows and zero `react-live-statement.qif` statements. The isolated QA accountant login remains available; its password is stored only in ignored `.env` as `BE_ACCOUNTING_QA_PASSWORD`.
- CSV/Excel imports still require a preconfigured Odoo journal file map. React map configuration and broad format/accountant acceptance are open; BE-080 remains PARTIAL.

## Live React manual CRM lead in USD — checkpoint113

- Isolated Sales-role browser journey through React `:3211` → Build Engine QA BFF `:18081` → Odoo `:8069`: **1 passed**. The user created and reopened a customer-free government lead, and verified company, USD currency and persisted Sales actor. Screenshot: [live-crm-manual-lead.png](build-engine/frontend/screenshots/live-crm-manual-lead.png).
- Isolated Odoo `be_accounting_qa_20261024`, upgrade `be_project,namaa_ai_bridge`, tagged bridge suite: **51 post-tests, 0 failures, 0 errors**. Includes CRM draft creation in an USD company; log: `build-engine-odoo-1:/tmp/be009_usd_crm_full_suite.log`. Targeted run also passed 1/1 on the walkthrough DB. The first full-tag attempt on that DB hit two unrelated BOQ baseline fixture/access failures; the complete rerun on the accounting QA DB passed.
- Backend business suite: **109 passed**; React unit suite: **69 passed**; CRM/Sales/Purchase/Accounting preview browser suite: **21 passed**; Vite production build and Python compilation passed. Cleanup removed the synthetic test lead via Odoo ORM; SQL verification returned zero matches. No production or `namaa_ksa` data changed.

## React lead qualification — checkpoint108

- Isolated Odoo bridge test: **1 post-test, 0 failures, 0 errors**; verifies current-company scope, Sales qualification, actor/time audit, CRM-reader denial and stale revision rejection.
- Backend business tests: **106 passed**; React unit tests: **69 passed**; mocked Playwright: **1 passed**; live Sales-role Playwright: **1 passed**.
- Live acceptance against React `:3211` → Build Engine QA BFF `:18081` → Odoo `:8069` saved and read back an audited “yes” qualification. An outdated SHA-256 revision was rejected with HTTP 422. See [checkpoint108](build-engine/CHECKPOINT_108.md) and [screenshot](build-engine/frontend/screenshots/live-crm-lead-qualification.png).
- Vite build passed with the existing large-bundle advisory. No production DB was changed.

## React site material usage — checkpoint107

- Isolated Odoo bridge test: **1 post-test, 0 failures, 0 errors**.
- Backend business tests: **104 passed**; React unit tests: **69 passed**; mocked Playwright journey: **1 passed**; Vite production build passed.
- Live Site-role Playwright against React `:3211` → Build Engine QA BFF `:18081` → Odoo `:8069`: **1 passed**. The test recorded 3.5 units against the confirmed Concrete supply package BOQ line and read it back from Odoo. Screenshot: [live-site-material-usage.png](build-engine/frontend/screenshots/live-site-material-usage.png).
- BE-072 remains PARTIAL: no warehouse inventory deduction or actual-cost reconciliation is part of this slice. See [checkpoint107](build-engine/CHECKPOINT_107.md).

## Live React customer directory — checkpoint106

- Ordinary Sales-role journey through React `:3211` → BFF `:18081` → isolated Build Engine Odoo `:8069`: **1 Playwright test passed**. It created a customer, edited it, archived/restored it, and archived the final test record. All customer BFF list/create/update/status calls returned HTTP 200.
- A Project Manager without partner create access was separately denied by native Odoo; no ACL changes were made.
- Screenshot review exposed clipped table actions; bounded table columns now keep both edit and archive actions visible. See [checkpoint106](build-engine/CHECKPOINT_106.md) and [QA screenshot](build-engine/frontend/screenshots/live-react-customer-register.png).
- React unit suite: **69 passed**; Vite production build passed with the existing chunk-size advisory; `git diff --check` passed. This is cross-cutting capability evidence, not a completion claim for CRM stories.

## All native accounting reports in React — checkpoint105

- Odoo Accounting KSA report tests on isolated `be_accounting_qa_20261024`: **30 post-tests, 0 failures, 0 errors**, including the loop that renders every report-engine key, balanced trial balance and PDF/XLSX checks.
- Backend business suite: **102 passed, 75 subtests passed**. React unit suite: **69 passed**.
- Mocked React browser journey: **1 passed**, covering all ten report choices, as-of/date-range behavior and report-specific analytic filtering.
- Live Saudi finance-role React → BFF → Odoo browser journey on `be_accounting_budget_qa_20261024`: **1 passed**; all ten reports returned company-scoped SAR data and all twenty report-specific PDF/XLSX downloads passed signature checks.
- Production Vite build passed with the existing >500 kB JavaScript chunk advisory. No production database changed. Details and screenshot: [checkpoint105](build-engine/CHECKPOINT_105.md), [live report screen](build-engine/frontend/screenshots/live-accounting-reports.png).

## React corrective maintenance work orders — checkpoint104

- Isolated Odoo `be_equipment` suite: **23 post-tests, 0 failures, 0 errors** on both `be_maintenance_cost_qa_20261025` and `be_accounting_qa_20261024`.
- Backend business suite: **101 passed, 75 subtests passed**. React unit suite: **69 passed**.
- Mocked React maintenance Playwright: **1 passed**, covering preventive plan generation, cost capture, corrective breakdown reporting and completion.
- Live PM React → BFF → Odoo Playwright: **1 passed** on isolated `be_accounting_qa_20261024`, verifying corrective request creation, completion and persisted `done` state on re-read.
- Vite production build passed with the existing >500 kB JavaScript chunk advisory. No production database changed. Details: [checkpoint104](build-engine/CHECKPOINT_104.md).

## React repair-cost ledger — checkpoint103

- Isolated Odoo `be_equipment` tagged suite on `be_maintenance_cost_qa_20261025`: **22 post-tests, 0 failures, 0 errors**, including audit/rounding, finance read-only, site denial, foreign-company denial and signed correction coverage.
- Backend business suite: **100 passed, 75 subtests passed**. React unit suite: **69 passed**. Mocked React maintenance/cost journey: **1 passed**. Vite production build passed with the existing >500 kB advisory.
- Live PM-role React → BFF → Odoo maintenance-cost persistence journey: **1 passed after final schema/field-group upgrade** on isolated `be_accounting_qa_20261024`, with the cost total and audit row reopened from Odoo after save.
- No production database changed. See [checkpoint103](build-engine/CHECKPOINT_103.md).

## React preventive maintenance planning — checkpoint102

- Isolated Build Engine equipment suite: **21 tests, 0 failures, 0 errors**; OCA maintenance plan/project suites: **22 tests, 0 failures, 0 errors**.
- Backend business suite: **99 passed**; React unit suite: **69 passed**.
- Mocked maintenance browser journey: **1 passed**. Live PM-role React → BFF → Odoo journey: **1 passed**, verifying plan creation, native request generation, persistence and archive/restore.
- Rerun on 2026-10-25: backend **99 passed, 75 subtests passed**; React **69 passed**; mocked maintenance Playwright **1 passed**; live maintenance Playwright **1 passed**. The first live rerun found all existing equipment/kind pairs occupied; a QA-only maintenance kind was committed through Odoo ORM in the isolated QA DB, after which the live journey passed.
- Vite production build passed with the existing large-chunk advisory. Screenshot: [live maintenance planning](build-engine/frontend/screenshots/live-maintenance-plan.png).
- QA used isolated database `be_accounting_qa_20261024`; no production database was changed. BE-096 remains PARTIAL; alerts, request execution/closure, corrective costs and broader role acceptance remain.

## Project correspondence log — checkpoint101

- Isolated Odoo 20 `be_correspondence` upgrade/tagged suite: **28 tests, 0 failures, 0 errors**, including combined accessible RFI/submittal history and cross-project denial.
- Backend business boundary suite: **98 passed**.
- React unit suite: **69 passed**.
- Focused mocked Playwright journey: **1 passed**, covering mixed record rendering, revision history, type filtering, CSV contents and download filename.
- Vite production build passed; existing large-bundle advisory remains.
- Backend tests ran in `be-react-qa-backend` because host Python lacks `httpx`. Odoo test database was isolated `be_accounting_qa_20261024`; no production DB changed.

## Live drawing-linked submittal revision cycle — checkpoint100

- Isolated Odoo `be_correspondence` upgrade/tagged suite: **27 tests, 0 failures, 0 errors**, including native file download bytes and unrelated-parent denial.
- Backend boundary suite: **97 passed**; React unit suite: **69 passed**.
- Live PM → Owner React/BFF/Odoo Playwright: **1 passed**, covering draft creation with drawing 74 and PDF, submission, Owner revision request, PM resubmission, separate Owner approval, persisted drawing link/audit actors and latest file download. See [live submittal record](build-engine/frontend/LIVE_SUBMITTALS_QA.json) and [screenshot](build-engine/frontend/screenshots/live-drawing-linked-submittal.png).
- Vite production build passed with the existing >500 kB advisory. User manual offline verification: **128/128 embedded screenshots decoded**, English/Arabic at 1440px and 390px without horizontal overflow, no external requests.
- Only isolated `be_accounting_qa_20261024` changed; no production DB changed.

## React drawing-to-task link — checkpoint99

- On isolated `be_accounting_qa_20261024`, upgraded `be_drawing`; native module suite **8 passed, 0 failures/errors**, including task/project/company validation and revision link preservation.
- Backend boundary suite: **97 passed**. React unit suite: **69 passed**. Mocked drawing Playwright: **2 passed**, including task selection and BFF payload.
- Live PM-role React → BFF → Odoo Playwright: **1 passed**. PM read the allowed project task, linked it to drawing revision 0, created revision 1, and downloaded the PDF; Odoo records 73/74 both reference task 1794. Task creation itself remains correctly denied to this PM role. See [live QA evidence](build-engine/frontend/LIVE_DRAWINGS_QA.json) and [screenshot](build-engine/frontend/screenshots/live-drawings-revisions.png).
- Vite production build passed with the existing >500 kB advisory. No production DB changed.

## React project drawing register — checkpoint98

- Isolated Odoo `be_drawing` upgrade/tagged suite on `be_accounting_qa_20261024`: **7 tests, 0 failures, 0 errors**, including atomic revision/file creation, malformed base64 rollback and native parent/project/company-checked file read. The database is isolated QA and was the only Odoo database changed for this slice.
- Backend business suite: **97 tests passed** in `be-react-qa-backend`, whose `/app` is a read-only mount of the current backend source during the test. New checks cover strict drawing payload/file type/filename validation, current-company project validation, upload, revision delegation, same-origin mutation enforcement, native ACL mapping and parent-scoped download.
- React unit tests: **69 passed**. Mocked drawing Playwright: **2 passed**. Live PM-role Playwright: **1 passed**, verifying capability-based navigation, file upload, revision 0→1, persisted creator ID 856 and PDF byte signature after download. See [live QA evidence](build-engine/frontend/LIVE_DRAWINGS_QA.json) and [screenshot](build-engine/frontend/screenshots/live-drawings-revisions.png). Vite production build passed with the existing >500 kB chunk advisory; Python compilation and `git diff --check` passed.
- Not covered: additional-company privacy tests, task-link editing, issue/obsolete transition policy or CAD/PDF preview. BE-125/127 remain PARTIAL; DEC-08 remains BLOCKED. No production database changed.

## React nonconformance corrective-action lifecycle — checkpoint97

- Native Odoo full custom-module suite on isolated DB `be_qa_20261025_005354_3832`: **204 tests, 0 failures, 0 errors**, including atomic workflow rollback. Latest `be_quality_gate` upgrade suite on `be_accounting_qa_20261024`: **17 tests, 0 failures, 0 errors**, covering role/company/project-scoped assignee options, evidence validation/parent access and atomic workflow rollback. Odoo logs expected constraint/access errors from tests that explicitly assert rejected operations; these do not count as test failures.
- Backend boundary suite: **94 passed, 0 failures** in disposable image `be-ncr-qa:current`. Covers strict workflow and evidence payload validation, project-bound native assignee options, same-origin mutation requirements, native access checks and evidence download handling.
- React unit suite: **69 passed, 0 failed**.
- Mocked nonconformance Playwright: **3 passed**, covering bilingual preview, validated safety report and assignment through the BFF boundary.
- Live ordinary-role React → BFF → Odoo Playwright: **1 passed** on isolated `be_accounting_qa_20261024`. PM created NCR 55, assigned it, started/resolved work and uploaded PNG evidence; separately authenticated Owner verified/closed and downloaded the attachment through React. Persisted audit fields identify PM 856 and Owner 857; attachment 7585 belongs to synthetic project 1260. Synthetic records remain in QA for inspection; credentials are not documented.
- Vite production build passed with the existing >500 kB chunk advisory; `git diff --check` passed. Mocked browser journeys and live role integration are tracked separately. No production DB changed.

## React daily safety checklists — checkpoint96

- Isolated Odoo `be_accounting_qa_20261024`: upgraded `namaa_ai_bridge`; bridge addon suite **47 passed, 0 failures, 0 errors**, including `TestNamaaBridge.test_daily_safety_checklist_uses_published_template_and_is_idempotent_per_project_date`. It verifies published-template options, date validation, project/company filtering, site-role authorization, idempotent open/resume for a project/template/day, creator/signer audit and completion state.
- Backend boundary suite in isolated `be-react-qa-backend:checkpoint91`, current backend mounted read-only: **91 passed**. Includes strict daily checklist IDs/date, options/create route delegation and invalid date rejection before Odoo calls.
- React unit suite: **69 passed, 0 failed**. Focused Quality & Safety Playwright: **3 passed**, including dated daily checklist create/resume and completion, quality-gate evidence/sign-off, role-denied controls and 390px responsive layout.
- Vite production build passed with the existing >500 kB chunk advisory. Python compilation and `git diff --check` passed.
- Browser journeys mock session/API data; they do not prove a live ordinary-role React→BFF→Odoo journey. BE-106 is PARTIAL, not DONE. QA mutated only `be_accounting_qa_20261024`; no production database changed. Current totals: **0 DONE, 116 PARTIAL, 38 MISSING, 10 BLOCKED**. See [checkpoint96](build-engine/CHECKPOINT_96.md).

## React quality-gate review and evidence — checkpoint95

- Isolated Odoo `be_accounting_qa_20261024`: upgraded `namaa_ai_bridge`; selected native bridge test **1 passed, 0 failures, 0 errors**. It verifies role denial, rejects invalid photo bytes, checks valid PNG attachment readback, records signer/time, and rejects another-company detail access.
- Backend boundary suite in isolated `be-react-qa-backend:checkpoint91`, current backend mounted read-only: **90 passed**.
- React unit suite: **69 passed, 0 failed**.
- Focused quality-gate Playwright: **2 passed**, covering required evidence before pass, upload, pass sign-off, mutation header, role-denied controls and responsive layout at 390px without horizontal overflow.
- Vite production build passed with the existing >500 kB chunk advisory. Python compilation and `git diff --check` passed.
- Browser tests use mocked API/session data; they do not prove a live ordinary-role React→BFF→Odoo journey. BE-100/101/102 remain PARTIAL. QA mutated only `be_accounting_qa_20261024`; no production database changed. See [checkpoint95](build-engine/CHECKPOINT_95.md).

## React safety incident and near-miss reporting — checkpoint94

- Isolated Odoo `be_accounting_qa_20261024`: upgraded `be_quality_gate`; targeted native test: **1 passed, 0 failures, 0 errors**. The module upgrade also parsed the revised native form/list views.
- Backend boundary suite: **88 passed, 0 failures** in retained `be-react-qa-backend:checkpoint91` with current backend mounted read-only. Covers conditional safety fields, rejection before Odoo write, and conversion of `+03:00` occurrence time to UTC.
- React unit suite: **69 passed, 0 failed**.
- Focused Quality & Safety Playwright suite: **2 passed**; the live-form test is mocked at the API/session boundary and covers required-field correction and near-miss submission.
- Python compilation and `git diff --check` passed. Vite production build passed with the existing >500 kB bundle advisory.
- Live ordinary-role React→BFF→Odoo acceptance remains open. BE-105 is PARTIAL. No production database changed. See [checkpoint94](build-engine/CHECKPOINT_94.md).

## Retry-safe BOQ spreadsheet import — checkpoint93

- Isolated Odoo `be_accounting_qa_20261024`: upgraded `be_boq,namaa_ai_bridge`; selected native duplicate-retry/fingerprint test: **1 passed, 0 failures, 0 errors**.
- Backend boundary suite: **88 passed, 0 failures** in retained `be-react-qa-backend:checkpoint91`, with current backend mounted read-only.
- Focused BOQ Playwright suite: **2 passed**, including simulated HTTP 502 followed by retry with the same operation UUID.
- React unit suite: **68 passed, 0 failed**. Vite build, Python compilation and `git diff --check` passed.
- Native and mocked retry tests are not a live ordinary-role BFF retry journey. BE-050/146 remain PARTIAL; company-boundary UAT, import history/reopen decision, other templates and runtime rollout remain. No production database changed. See [checkpoint93](build-engine/CHECKPOINT_93.md).

## React BOQ revision comparison — checkpoint92

- Isolated Odoo database `be_accounting_qa_20261024`: bridge upgrade and selected native test `TestNamaaBridge.test_react_boq_revision_comparison_reads_immutable_same_project_snapshots`: **1 passed, 0 failures, 0 errors**. Checks immutable baseline reads, same-project options, amount/line output and public-user, cross-company and foreign-baseline denial.
- Backend boundary suite: **88 passed, 0 failures** using the retained `be-react-qa-backend:checkpoint91` image with the current backend directory mounted read-only.
- React unit suite: **68 passed, 0 failed**, including six revision comparison tests.
- Vite production build and Python compilation passed. The build reports the existing JavaScript bundle advisory (>500 kB).
- `git diff --check` passed.
- No browser or ordinary-role live BFF journey was run for this feature. No production database was upgraded or modified. See [checkpoint92](build-engine/CHECKPOINT_92.md).

## React BOQ spreadsheet import — checkpoint91

- Workbook validation: **3 passed** in `backend/tests/test_boq_import.py`.
- Built `be-react-qa-backend:checkpoint91` from `backend/Dockerfile`; runtime smoke loaded `openpyxl 3.1.5`, `app.main`, and both import routes. Full backend business suite inside this isolated image: **89 passed**.
- React unit suite: **62 passed, 0 failed**.
- Focused BOQ Playwright journeys: **2 passed**, including mapping correction after a row validation error and creating one draft through mocked API responses.
- Live isolated-role React journey: **passed** against `be_accounting_qa_20261024` using a real workbook and the Build Engine PM group. The QA BFF invoked native Odoo creation, and React reopened the persisted draft with one line and USD 1,004 total. No BOQ endpoint errors or browser exceptions; temporary user/project/BOQ and support containers were removed. Evidence: [LIVE_BOQ_IMPORT_QA.json](build-engine/frontend/LIVE_BOQ_IMPORT_QA.json) and [screenshot](build-engine/frontend/screenshots/react-boq-import-live-qa-en-1440.png).
- Vite production build passed. It reports the existing JavaScript chunk advisory (>500 kB; current bundle 633.31 kB).
- Manual generated and verified after adding live evidence: **129/129 screenshots decoded**, English and Arabic at desktop/mobile sizes without horizontal overflow, interactions passed, and no external requests.
- `git diff --check` passed.
- The BFF sends one validated `namaa_boq_create` operation through the current user's session. Live basic-role acceptance passed; persisted import-batch history, retry/idempotency, cross-company denial and rollout to normal app services remain open. Existing services were not replaced; no production database was upgraded or modified. See [checkpoint91](build-engine/CHECKPOINT_91.md).

## React schedule critical-path estimate — checkpoint90

- Critical-path unit cases: **4 passed**, covering longest prerequisite chain and inclusive calendar-day durations, tied paths and phase rollup exclusion, unsupported/unscheduled dependencies, invalid dates and cycles.
- React unit suite: **62 passed, 0 failed**.
- Focused mocked project-plan Playwright: **1 passed**, including rendered 14-calendar-day path and critical-bar highlight.
- Vite production build passed; it reports the existing JavaScript chunk advisory (>500 kB). `git diff --check` passed.
- Refreshed screenshot and offline React manual verification: **126/126 images decoded**, EN/AR at 1440px and 390px without horizontal overflow, gallery/search/enlarge/Escape interactions passed, and no external requests.
- This slice only reads existing Odoo task prerequisite links and dates. It does not change Odoo models or databases and does not establish live-role acceptance. See [checkpoint90](build-engine/CHECKPOINT_90.md).

## Supplier directory maintenance — checkpoint89

- Isolated Odoo database `be_accounting_qa_20261024`, tagged `/namaa_ai_bridge`: **43 post-tests, 0 failures, 0 errors**. Includes update revision/duplicate checks, archive/restore, default active filtering, role/company denial, Purchase User read-only ACL and Purchase Manager maintenance ACL.
- Backend business suite: **86 passed, 59 subtests passed**.
- React suite: **58 passed**; focused supplier Playwright journeys: **2 passed**, covering manager create/edit/archive, archived list, restore, active list and read-only UI actions for a user without partner write ACL.
- Vite production build passed. Build reported the existing JavaScript chunk advisory (>500 kB).
- Bilingual offline user manual now documents supplier maintenance and embeds its screenshot; verification passed **126/126 images**, EN/AR desktop/mobile, with no external requests.
- This verification used isolated Odoo QA and mocked React APIs; there was no production/customer database mutation or live buyer browser acceptance.

## Schedule baseline comparison — checkpoint88

- Isolated Odoo database `be_accounting_qa_20261024`, upgrade `be_project,namaa_ai_bridge`, tagged `/namaa_ai_bridge`: **41 post-tests, 0 failures, 0 errors**. Baseline regression checks stable source task identity after deleting the live task and confirms the bridge still returns the deleted task snapshot.
- React unit suite: **58 passed**, including five pure baseline comparison cases.
- Focused mocked Playwright project-plan flow: **1 passed**, asserting changed start date, task addition/removal summaries and details.
- Vite production build passed. Build reported the existing large JavaScript chunk advisory (>500 kB).
- Scope is an isolated module upgrade plus mock React browser coverage; no live or customer database write was performed. Prior checkpoint87 evidence contains live role/access verification for the unchanged create/decision endpoints.

## React schedule baselines and change history — checkpoint87

- Isolated Odoo database `be_accounting_qa_20261024`: `be_project,namaa_ai_bridge` upgrade and tagged bridge suite passed **41 post-tests, 0 failures, 0 errors**. This includes snapshot creation, task change events, self-approval denial, approval pointer update, rejection preserving the current pointer, immutable snapshot/event protection, stale revision and public-user denial. Log: `/tmp/be_project_schedule_baseline_qa.log` in `build-engine-odoo-1`.
- Backend business suite: **85 passed, 59 subtests passed**. React unit suite: **53 passed**. Focused mocked project-plan Playwright: **1 passed**, including baseline submit, approval rationale, current baseline, decision actor and schedule change history. Vite production build and Python compilation passed. Offline manual: **125/125 screenshots decoded**; EN/AR at 1440/390, filtering, search, enlargement/Escape and no-external-request checks passed. `git diff --check` passed.
- Live ordinary-role React → BFF → isolated Odoo: PM submitted baseline; requester had no decision controls; owner approved with rationale; reauthentication reopened the approved snapshot/event/history. Cross-company project lookup returned **403** without its name; browser page errors: **0**. Temporary QA users were disabled and temporary Vite/BFF servers stopped; Namaa services and database were untouched. Evidence: [live QA JSON](build-engine/frontend/LIVE_SCHEDULE_BASELINE_QA.json) and [live screenshot](build-engine/frontend/screenshots/react-project-baseline-live-qa.png). BE-047 remains PARTIAL pending approver-role confirmation, baseline comparison and full acceptance. See [checkpoint87](build-engine/CHECKPOINT_87.md).

## React project milestones and stakeholder obligations — checkpoint86

- Isolated Odoo database `be_accounting_qa_20261024`, `be_project,namaa_ai_bridge` upgrade and tagged bridge suite: **40 post-tests, 0 failures, 0 errors**. Tests cover milestone enabling, stakeholder/responsible/task links, invalid and early completion, task-link preservation after rejection, reached state/date after task closure, stale revision and public-user denial. Log: `/tmp/be_project_milestones_qa_final.log` in `build-engine-odoo-1`.
- Backend business suite: **84 passed, 57 subtests passed**; React unit suite: **53 passed**; mocked project-plan Playwright: **1 passed**, including milestone creation and BFF payload; Vite production build and Python compilation passed. The bilingual offline manual passed **124/124 screenshot decoding**, EN/AR desktop/mobile overflow and gallery checks; `git diff --check` passed. Updated screenshot: [React project plan with stakeholder milestone](build-engine/frontend/screenshots/react-project-plan-en-1440.png).
- Browser APIs are mocked; this does not establish live-role browser acceptance. No production database was changed. See [checkpoint86](build-engine/CHECKPOINT_86.md).

## React project equipment scheduling — checkpoint85

- Isolated Odoo DB `be_accounting_qa_20261024`, upgrades `be_equipment,namaa_ai_bridge`, tagged combined suite: **58 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_equipment_plan_conflicts_qa_checkpoint85.log` in `build-engine-odoo-1`. Includes same-company task equipment assignment, task date/company constraints, same-company overlapping task warnings, exclusion of closed tasks and current custody warning.
- Backend business suite: **83 passed, 53 subtests passed**. React unit suite: **53 passed**. Focused mocked Playwright project-plan journey: **1 passed**, assigning an asset and checking crew/equipment warnings. Vite production build and Python compilation passed.
- Bilingual offline manual verifier: **124/124 screenshots decoded**, no external requests, EN/AR desktop/mobile overflow and gallery checks passed. Screenshot: [project plan with crew and equipment warnings](build-engine/frontend/screenshots/react-project-plan-en-1440.png). Warnings neither reserve nor block resources; APIs are mocked in the browser test and no production DB was changed. See [checkpoint85](build-engine/CHECKPOINT_85.md).

## Cross-project crew overlap warnings — checkpoint84

- Isolated Odoo DB `be_accounting_qa_20261024`, `namaa_ai_bridge` upgrade and tagged suite: **39 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_crew_conflict_qa_final.log` in `build-engine-odoo-1`. Native coverage creates overlapping tasks in two active-company projects with one assigned worker and verifies conflict details in the create result and project read.
- Backend business suite: **83 passed, 51 subtests passed**. React unit suite: **53 passed**. Focused mocked Playwright project-plan journey: **1 passed**, including the visible crew overlap warning. Vite production build and Python compilation passed.
- Bilingual offline manual regenerated and verified: **124/124 screenshots decoded**, no external requests, English/Arabic desktop and mobile overflow, image decoding and gallery interactions passed. Screenshot: [React project plan with crew overlap warning](build-engine/frontend/screenshots/react-project-plan-en-1440.png). Warnings do not reserve or block scheduling. Equipment reservations and live ordinary-role acceptance remain open; no production DB changed. See [checkpoint84](build-engine/CHECKPOINT_84.md).

## React project planning — checkpoint83

- Isolated Odoo DB `be_accounting_qa_20261024`, `namaa_ai_bridge` upgrade and tagged suite: **39 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_project_plan_qa_checkpoint83.log` in `build-engine-odoo-1`.
- Backend business suite: **83 passed, 51 subtests passed**. React unit suite: **53 passed**. Focused mocked Playwright project-plan create/edit journey: **1 passed**. Vite production build passed (existing large-chunk warning remains).
- Regenerated bilingual offline manual with chapter 18 and the synthetic project-plan screenshot; verifier passed **124/124 screenshots**, English/Arabic desktop/mobile layout, gallery behavior, image decoding and no external requests.
- The Playwright journey mocks the API. Isolated native tests exercise Odoo project, dependency, team, validation and revision behavior; live ordinary-role React → BFF → Odoo schedule acceptance remains open. No production database was modified. See [checkpoint83](build-engine/CHECKPOINT_83.md).

## Multi-line React contract variation drafts — checkpoint82

- Isolated Odoo DB `be_accounting_qa_20261024`, combined `be_variation,be_contract,namaa_ai_bridge` suite: **57 post-tests, 0 failures, 0 errors**. Covers PM multi-line create/edit, stale-version rejection, native approval, BOQ revision/baseline and cumulative variation ceiling. Log: `/tmp/be_variation_multi_edit_qa.log` in `build-engine-odoo-1`.
- Backend business suite: **81 passed, 46 subtests passed**. React unit suite: **53 passed**. Focused mocked Playwright contract/variation journey: **1 passed**, creating two lines, editing to three, displaying creator/updater metadata, then submitting and approving. Vite build and Python compilation passed.
- Variation screenshot: [multi-line variation request](build-engine/frontend/screenshots/react-contract-variation-en-1440.png). Manual verifier passed 123 screenshots plus image decoding, no external requests and English/Arabic desktop/mobile layout checks. The browser journey is mocked and does not establish live role acceptance; no production database changed.

## React contract variation orders — checkpoint81

- Isolated Odoo DB `be_accounting_qa_20261024`, combined `be_variation,be_contract,namaa_ai_bridge` suite: **57 post-tests, 0 failures, 0 errors**. Includes the base `be_variation` suite, PM variation create/submit/approve, BOQ revision/baseline creation, closed-contract history, and cumulative linked-contract ceiling enforcement. Log: `/tmp/be_variation_react_closed_qa.log` in `build-engine-odoo-1`.
- Backend business suite: **81 passed, 46 subtests passed**. React unit suite: **53 passed**. Focused Playwright contract/variation journey: **1 passed** against mocked APIs. Vite production build and Python compilation passed.
- Screenshot: [variation request with ceiling preview](build-engine/frontend/screenshots/react-contract-variation-en-1440.png). The bilingual offline manual verifier passed **123/123 screenshots** and desktop/mobile English/Arabic layout checks. The browser test is mocked and does not establish live role acceptance; no production database was changed.

## React contract draft editing — checkpoint80

- Isolated Odoo DB `be_accounting_qa_20261024`, combined `be_variation,be_contract,namaa_ai_bridge` suite: **47 post-tests, 0 failures, 0 errors**. Includes project-manager child edits, stale-version rejection and denial after activation. Log: `/tmp/be_contract_edit_qa_verified.log` in `build-engine-odoo-1`.
- Backend business suite: **79 passed, 42 subtests passed**. React unit suite: **53 passed**. Contract Playwright create/edit/activate journey: **1 passed** against mocked APIs. Vite production build and Python compilation passed.
- Existing child rows are updated by ID and reminder records remain linked; PMs cannot delete child rows, so omitted rows remain preserved. Live ordinary-role browser acceptance remains open; no customer DB was modified.

## React construction contracts — checkpoint79

- Isolated Odoo DB `be_accounting_qa_20261024`, combined `be_contract,namaa_ai_bridge` tagged suite: **47 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_contract_react_final.log` in `build-engine-odoo-1`.
- Backend business suite: **79 passed, 42 subtests passed**. React unit suite: **53 passed**. Focused contract Playwright create-draft/detail/activate flow: **1 passed** against mocked APIs. Vite production build and Python compilation passed.
- Screenshot: [contract detail synthetic example](build-engine/frontend/screenshots/react-contract-detail-en-1440.png). The bilingual offline manual includes chapter 17 Contracts; see [manual](../frontend/public/user-manual.html).
- The browser flow uses mocked APIs. Live ordinary-role React → BFF → isolated Odoo acceptance remains open; no production/customer DB was modified. BE-116/117/118 remain PARTIAL.

## React customer archive and restore — checkpoint78

- Odoo isolated DB `be_accounting_qa_20261024`, upgraded `namaa_ai_bridge` and tagged suite: **35 post-tests, 0 failures, 0 errors**. The suite includes current-company checks, public-user denial, active/archived listing, stale revision rejection, archive and restore. Log: `/tmp/namaa_customer_archive.log` in `build-engine-odoo-1`.
- Backend business suite: **77 passed, 38 subtests passed**. It covers status filtering, strict revision/boolean contract, same-origin mutation and Odoo method forwarding.
- React unit suite: **53 passed**. Customer Playwright flow: **1 passed**, exercising create/edit/archive/filter/restore against a mocked API. Vite production build passed.
- Captured the archive review dialog as a labeled synthetic screenshot and regenerated the bilingual HTML manual; offline verifier passed **121/121 images**, zero external requests, Arabic/English mobile and desktop overflow checks, and gallery filter/search/viewer checks. Screenshot: [customer archive review](build-engine/frontend/screenshots/react-customer-archive-review-en-1440.png).
- Browser acceptance used mocked HTTP and does not establish ordinary-role live acceptance. Native persistence and ACL behavior were verified in isolated Odoo tests. No production/customer DB was changed.

## React equipment register and custody — checkpoint77

- Isolated Odoo DB `be_accounting_qa_20261024`, `be_equipment` upgrade and tagged tests: **20 tests, 0 failures, 0 errors**. Log: `/tmp/be_equipment_react_boundary.log`.
- Backend tests: **75 passed, 36 subtests passed**; React unit tests: **53 passed**; Equipment Playwright lifecycle: **1 passed**; Vite production build passed.
- Live isolated React → BFF → Odoo procurement-role journey registered an asset with acquisition cost/date/reference, checked it out to a current-company project, returned it and reopened the record. Odoo returned current state `in_yard`, four immutable movement rows and actor metadata. Browser JavaScript errors: **0**. Screenshot: [equipment custody QA](build-engine/frontend/screenshots/react-equipment-custody-live-qa-en-1440.png).
- Native tests verify unassigned-role denial, invalid/atomic registration, company scoping, inaccessible-project denial, custody transitions and immutable history. Temporary QA access was disabled; no customer database was modified.

## React BOQ equipment lines — checkpoint76

- Isolated Odoo DB `be_accounting_qa_20261024`, combined `be_boq,namaa_ai_bridge` tagged suite: **58 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_qa_boq_equipment.log`.
- Backend business tests: **72 passed, 31 subtests passed**; React unit tests: **50 passed**; mocked BOQ lifecycle Playwright: **1 passed**; Vite production build passed.
- Live isolated React → BFF → Odoo PM run created an equipment line and rendered native actor/time metadata. Screenshot: [equipment-line QA](build-engine/frontend/screenshots/react-boq-equipment-live-qa-en-1440.png). Temporary QA PM user was deactivated; no customer DB was modified.
- Readiness endpoint reports optional agent model not ready; the authenticated BOQ routes used in the QA run returned successfully. This did not affect the BOQ workflow.

## React BOQ authoring and confirmation — checkpoint75

- Isolated Odoo DB: `be_accounting_qa_20261024`; combined `-u be_boq,namaa_ai_bridge --test-enable --test-tags /be_boq,/namaa_ai_bridge`: **55 post-tests, 0 failures, 0 errors**. Log: `/tmp/be_qa_boq_lifecycle.log`. This included PM baseline create/close checks and a regression ensuring a system administrator without Build Engine child-model rights is not shown create/edit/confirm actions.
- Backend business tests: **72 passed, 31 subtests passed** (`PYTHONPATH=. ../.venv/bin/pytest -q tests/test_business.py` from `backend/`). React unit tests: **49 passed**. Vite production build passed. Mocked React lifecycle Playwright: **1 passed** (create → confirm → close → next project BOQ allowed).
- Regenerated the bilingual offline user manual with the isolated live BOQ screenshot: **118/118** screenshots decoded, zero external requests, Arabic/English desktop and phone layout checks passed, and gallery filter/search/viewer checks passed. Evidence: `docs/build-engine/frontend/MANUAL_QA.json`.
- Live browser journey using a temporary Build Engine PM account in the isolated QA DB: React login, close an approved BOQ, create a next revision, and confirm it; close, create and confirm endpoints returned **200**. The temporary account was deactivated after the run. Screenshot: [boq-live-react-qa.png](build-engine/boq-live-react-qa.png); structured results: [BOQ_LIVE_REACT_QA.json](build-engine/BOQ_LIVE_REACT_QA.json).
- Currency shown in the screenshot follows the isolated QA company's USD configuration; this is not Saudi SAR acceptance. No writes were made to `namaa_ksa`.

## React customer edit — checkpoint74

- Isolated `be_accounting_qa_20261024`, upgraded `namaa_ai_bridge`: **28 post-tests, 0 failures, 0 errors** (Odoo reports 30 total including setup/tag accounting). Log: `/tmp/be_qa_customer_update.log`.
- Backend business tests: **70 passed, 28 subtests passed**.
- React unit tests: **45 passed**.
- Customer create/edit Playwright journey (mocked BFF): **1 passed**.
- Live React → BFF → Odoo QA journey against `be_accounting_qa_20261024`: customer GET, POST and PUT returned **200**; edited value appeared in the register. [Screenshot](build-engine/customer-edit-live-qa.png), [structured evidence](build-engine/QA_CHECKPOINT_74.json).
- Restored isolated QA admin password from local `.env` setting and rechecked login plus authenticated customer list: **200 / 200**; no password value was recorded.
- Vite production build, Python compilation and `git diff --check`: passed.
- Live journey used the isolated QA admin; ordinary-role UI acceptance remains open. No test wrote to `namaa_ksa`.

## React supplier directory — checkpoint73

- Added supplier list/create to React Purchase with KSA identity/contact fields. Current-user partner ACLs and company scope stay in native Odoo; legal identifier checks use transaction advisory locks. The UI distinguishes contact registration from qualification approval.
- Existing isolated QA database `be_accounting_qa_20261024`: tagged `namaa_ai_bridge` upgrade passed **27 post-tests, 0 failures, 0 errors**. Log SHA-256: `ccfe19c61676a40a85376688576486902f19f1764a44da0e74ecede1c72fafc4`. Details: [QA_CHECKPOINT_73.json](build-engine/QA_CHECKPOINT_73.json).
- Backend: **68 passed**. React unit: **45 passed**. Supplier Playwright create journey: **1 passed**, with mocked BFF. Production build and Python compilation passed. Actual-role acceptance and supplier qualification approval remain open; BE-059 stays PARTIAL.
- No production database changed. See [checkpoint73](build-engine/CHECKPOINT_73.md).

## React customer management — checkpoint72

- Added the React CRM customer register/create form and company-scoped BFF/Odoo bridge. KSA VAT and Commercial Registration formats are validated, duplicates are checked under per-company advisory locks, and current-user partner ACLs govern access. Created customers are available to current React CRM, Sales, Purchase, and Accounting partner lookups.
- Existing isolated QA DB `be_accounting_qa_20261024`: tagged `namaa_ai_bridge` upgrade passed **25 post-tests, 0 failures, 0 errors**. Log SHA-256: `bbd43d2bfdf9e072209e3c68ebb4a8ddc9ed59a355e7d5a6d36e66db1135ed3b`. Details: [QA_CHECKPOINT_72.json](build-engine/QA_CHECKPOINT_72.json).
- Backend business tests: **67 passed**. React unit tests: **45 passed**. Focused Playwright customer creation: **1 passed**, with mocked API. Vite build and Python compilation passed. Actual-role live browser acceptance remains open; customer edit/archive/merge governance remains incomplete.
- No production database changed. See [checkpoint72](build-engine/CHECKPOINT_72.md).

## React construction submittals — checkpoint71

- React submittal register, project/drawing options, draft create/edit, files, revision/event history, submit and review actions are served by the BFF over the authenticated Odoo session. Odoo 20 attachment storage/download uses `ir.attachment.raw`; optimistic edits use a server-owned version counter.
- Fresh isolated QA database `be_qa_20261024_205821_a24f`: **191 passed, 1 optional Helpdesk integration test skipped, 0 failures/errors** across custom Build Engine modules; `be_correspondence`: **26/26**. Log SHA-256: `d51da3445e022a2126a0346e51ea752fa546fd1facd4ff8d06829ec14288df10`. Details: [QA_CHECKPOINT_71.json](build-engine/QA_CHECKPOINT_71.json).
- Backend business suite: **65 passed**. React unit suite: **45 passed**. Vite production build: passed. Submittal Playwright and live role/company/project acceptance have not been run. Story statuses remain PARTIAL pending those criteria.
- No production database changed. See [checkpoint71](build-engine/CHECKPOINT_71.md).

## React project correspondence — checkpoint70

- Added the React Site Correspondence workspace for RFI search/status, company-project and internal-respondent selection, draft creation, deadline/overdue display, submit, assigned response, close and cancel. Writes use same-origin BFF routes and the authenticated Odoo user; native model ACLs enforce respondent/manager transitions.
- Fresh isolated Odoo QA database `be_qa_20261024_204536_e58a`: **188 passed, 1 optional Helpdesk integration skip, 0 failures/errors** across custom Build Engine modules; `be_correspondence` ran **27 tests**. Log hash, command and skip reason: [QA_CHECKPOINT_70.json](build-engine/QA_CHECKPOINT_70.json).
- Backend business suite: **61 passed, 2 skipped** (the two optional LangGraph approval tests are unavailable in this local environment). RFI API boundary tests cover date/ID validation, current record-rule delegation, same-origin mutations, assignee transition calls, and 403/422 mapping.
- React unit suite: **45 passed**; Vite production build passed. Focused Playwright RFI journeys: **2 passed**, covering create → submit → assigned answer. Its API is mocked, so it does not prove live database role/company isolation.
- Manual regenerated with **117 screenshots** including an explicitly synthetic React RFI view; offline verifier passed 117/117 images, zero external requests, Arabic/English desktop/phone layout checks, and search/filter/lightbox behavior.
- BE-109/110 remain PARTIAL until role-specific live React acceptance passes against isolated Odoo. Submittals and the consolidated RFI/submittal log remain open. No production customer database was changed.

## React end-user product direction — checkpoint69 (historical state)

- Decision: React is the daily user application for accounting, CRM, sales, purchase and construction; Odoo is the system of record/backend. See [ADR0014](adr/0014-react-as-end-user-application.md). Existing native Odoo screens are internal QA/admin evidence and do not complete an end-user story by themselves.
- At checkpoint69, story status was **0 DONE, 111 PARTIAL, 43 MISSING, 10 BLOCKED**. BE-109/110 had native acceptance evidence but their React journeys were missing. This was a product-scope reclassification, not a regression or code removal.
- At checkpoint69, the portable manual embedded 116 screenshots and labeled native Odoo pages as internal QA/admin material. Its verifier passed 116/116 images offline. Current checkpoint70 evidence is recorded above.

## BE-159 selectable project-budget period — checkpoint68

- Isolated Odoo database `be_accounting_budget_qa_20261024`: Accounting KSA update and full tagged suite passed **209 post-tests, 0 failures, 0 errors**. The additional API/security scenario checks quarter proration, reversed and malformed dates, finance-only access, and company isolation.
- Backend business suite: **56 passed**, with 16 additional subtest assertions passing. React unit suite: **45 passed**. Vite production build passed. Focused Playwright budget-view suite: **2 passed**; the browser test verifies selected dates are sent to the BFF and displayed from the response.
- Playwright's API is mocked; date calculations were directly tested against native Odoo. The previous real React/BFF/Odoo Saudi SAR browser evidence remains in [checkpoint66](build-engine/CHECKPOINT_66.md). No production/Namaa database was modified.
- BE-159 remains PARTIAL pending fiscal-year policy confirmation, owner visibility policy and accountant acceptance. See [checkpoint68](build-engine/CHECKPOINT_68.md).

## CRM addon compatibility and Odoo ACL mapping — checkpoint67

- CRM search reads optional Odoo fields only when `fields_get` reports them. Global native Odoo `AccessError` now maps to HTTP 403.
- Backend suite: **58 tests, 56 passed, 2 skipped** (LangGraph unavailable); new tests cover both behaviors. React suite remains **45 passed**; the frontend production Docker image built successfully.
- Rebuilt the local backend, then performed a read-only live Namaa browser capture. All four registers and the dashboard returned 200; 91 CRM opportunities were returned; zero API writes and zero posted demo moves.
- In the isolated SAR budget run, finance-only CRM/dashboard calls returned 403, as did a non-finance reader attempting the budget report. No Odoo DB or module was changed for this backend delivery. See [Checkpoint67](build-engine/CHECKPOINT_67.md).

## BE-159 Saudi live acceptance — checkpoint66

- Isolated QA fixture `be_accounting_budget_qa_20261024`, company `BE159 QA — Saudi Projects`, Saudi chart `sa`: approved project budget **SAR 125,000**, expected-to-date **SAR 101,712.33**, and **SAR 12,000** posted synthetic project cost. Repeatable fixture script: [seed_be159_sar_budget_qa.py](../scripts/seed_be159_sar_budget_qa.py); the second run preserved IDs and amounts.
- Real authenticated BFF-to-Odoo route returned **200** for the finance user and **403** for the non-finance reader. The `namaa_capabilities` handshake passed.
- Live React browser run against the same QA database rendered the SAR project budget and actuals. Required finance APIs returned 200, with 0 JavaScript errors. Screenshot: [PROJECT_BUDGET_ACTUALS_SAR_LIVE.png](build-engine/accounting-ksa/PROJECT_BUDGET_ACTUALS_SAR_LIVE.png).
- The finance-only QA user lacked Sales ACLs, so unrelated CRM and combined-dashboard calls were denied (502); this does not affect the project budget endpoints. The temporary listener and browser services were removed after QA.
- BE-159 remains PARTIAL pending period controls, owner visibility policy and accountant acceptance. No production/Namaa database was modified.

## BE-159 project budget versus actual — checkpoint65

- Fresh isolated Odoo 20 QA database `be_accounting_budget_qa_20261024` on the dependency-complete preview runtime: tagged `accounting_ksa` install/upgrade **209 post-tests, 0 failures, 0 errors** (17 addon tests). Log SHA-256 and scope: [budget QA record](build-engine/accounting-ksa/PROJECT_BUDGET_ACTUALS_QA.json).
- New native test checks approved budget values against the correct project analytic account, current-company binding, finance-only access and another-company result isolation.
- Full authenticated BFF report route with real Odoo sessions returned 200 and the seeded project's 125,000 planned value; the normal `namaa_capabilities` handshake passed, and a non-accounting internal reader was denied 403. This checkpoint's live route used the USD-configured base company; the subsequent Saudi SAR browser run is recorded above.
- Backend business suite: **56 tests, 54 passed, 2 LangGraph skips**. React unit suite: **45 passed**. Production build passed. Focused Playwright: **2 passed** (live mocked values and company context; 390px preview with financial totals withheld).
- Story BE-159 remains PARTIAL at checkpoint65; the later live SAR React/BFF/Odoo browser run and remaining requirements are recorded in checkpoint66 above. No production/Namaa database was upgraded.

## BE-104 nonconformance and corrective action — checkpoint64

- Isolated Odoo 20 upgrade and tagged `be_quality_gate` suite on `be_qa_demo_full_20261024`: **13 post-tests, 0 failures, 0 errors**. Log: `build-engine-odoo-1:/tmp/be104_nonconformance_qa5.log`.
- Covers record creation/audit, protected lifecycle transitions, company/project privacy, reporter boundary, assignment and due-date validation, linked failed gate items, critical evidence, separation of resolution/verification, and closed-record immutability.
- Python compilation and `git diff --check` passed. Odoo loaded the list/form/search/menu views successfully.
- Backend business/API suite: **55 tests, 53 passed, 2 skipped** because LangGraph is unavailable in the host environment. New tests cover current-company endpoints, same-origin creation, field validation, and native AccessError/ValidationError mapping.
- React suite: **45 unit tests passed**; production Vite build passed. Focused Playwright: **2 passed** (Arabic 390px read-only preview; English mocked-auth/API live create flow).
- Real BFF→Odoo integration passed on a separate QA Odoo process connected only to `be_qa_demo_full_20261024`: project options 200, create 200, list 200 with the new finding visible, and non-reporting internal reader create denied 403. Playwright authentication/API responses remain mocked; another-company privacy is not covered. BE-104 remains PARTIAL.

## BE-098 equipment utilization and idle-time report — checkpoint63

- Isolated Odoo 20 `be_equipment` upgrade and tagged suite on `be_qa_demo_full_20261024`: **14 post-tests, 0 failures, 0 errors**. Log: `build-engine-odoo-1:/tmp/be098_equipment_utilization_qa4.log`.
- Tests cover inclusive date clipping, checkout/return, transfer, open checkout, date bounds, role ACL denial and another-company equipment exclusion.
- Python compilation, equipment XML parsing and `git diff --check` passed.
- Browser action-manager rendering did not complete; this slice has no claimed browser acceptance. No live Namaa DB writes or financial postings.

## Expanded React demo dashboard — checkpoint62

- `cd frontend && npm run build`: passed with Vite 8.2.1. The build includes 29 preview records in each business register and the monthly activity chart.
- `git diff --check`: passed.
- Scope is synthetic React preview only; no Odoo/database fixture or financial posting was changed.

## Native CRM manual lead creation — checkpoint61

- Backend business suite: **49 passed**.
- React unit suite: **41 passed**; production build passed.
- Isolated Odoo 20 `namaa_ai_bridge` suite in `be_qa_demo_full_20261024`: **23 post-tests, 0 failures, 0 errors** (`build-engine-odoo-1:/tmp/be009_manual_lead_qa.log`).
- Python syntax and `git diff --check`: passed. No live `namaa_ksa` database writes.

## CRM won opportunity to project — checkpoint60

- On isolated QA DB `be_qa_demo_full_20261024`, upgraded `namaa_ai_bridge` and ran the complete module post-install test suite: **22 tests, 0 failures, 0 errors**. Log: `build-engine-odoo-1:/tmp/be017_crm_project_qa_final2.log`.
- Odoo tests cover creation by Sales with native Project Manager rights, idempotent retry, opportunity/project/company links, un-won and foreign-company rejection, CRM-only denial, and CRM detail capability.
- Backend business suite: **48 passed**. React Node suite: **40 passed** and Vite build passed. Python compilation and `git diff --check` passed.
- No production/demo DB was changed. BE-017/039 remain PARTIAL pending deployed browser/role acceptance and confirmation that project creation should require Project Manager ACL. See [Checkpoint60](build-engine/CHECKPOINT_60.md).

## CRM win rate and weighted pipeline — checkpoint59

- Backend business suite against current source in an isolated container: **47 passed, 0 failures**.
- React Node suite: **40 passed, 0 failures**; Vite production build passed. Python compilation and `git diff --check` passed.
- Native Odoo 20 `crm.lead.read_group` calls executed in isolated `be_qa_demo_full_20261024`: open aggregate returned `(1643800.0, 663273.5, 17)` for expected revenue, probability-weighted revenue and count; closed grouping with `active_test=False` returned `('won', 3)` and `('lost', 1)`, confirming archived lost opportunities are counted. This database was QA-only; no demo database write was performed.
- Metrics use current-company native CRM records. Win rate is won count divided by won plus lost count; zero closed outcomes display as unavailable. BE-018 remains PARTIAL pending rendered non-admin/company acceptance and clarification of the generic persistence/audit AC. See [Checkpoint59](build-engine/CHECKPOINT_59.md).

## CRM dashboard role and currency acceptance — checkpoint111

- Backend business tests: `docker exec be-react-qa-backend python -m unittest tests.test_business` — **109 passed**, including active-company currency aggregation and graceful handling of denied Purchase Order access.
- React unit tests: `npm test` — **69 passed**. `npm run build` — succeeded (Vite reports the existing large JavaScript chunk advisory).
- Live isolated QA: `AGENT_URL=http://127.0.0.1:18081 ODOO_URL=http://127.0.0.1:8069 npx playwright test e2e/crm-dashboard.live.spec.js --reporter=line` — **2 passed** as `qa_build_engine_sales` and `qa_build_engine_owner` against `be_qa_demo_full_20261024`.
- Sales-user dashboard values from Odoo: USD currency; 4 open opportunities; USD 5,482,500 weighted pipeline; no closed opportunities visible (win rate is unavailable); Purchase metric unavailable under this user's access rules; receivables USD 50,561.50. Owner dashboard: USD, 21 open opportunities, weighted pipeline USD 6,145,774, 3 won and 1 lost; React displayed 75%. No writes were made.
- Screenshots: [Sales dashboard](build-engine/frontend/screenshots/live-crm-win-rate.png), [Owner dashboard](build-engine/frontend/screenshots/live-crm-win-rate-owner.png). See [Checkpoint111](build-engine/CHECKPOINT_111.md).
- Scope note: this walkthrough database's active Odoo company is USD. The company badge and Dashboard follow Odoo's company currency; this is dynamic-currency verification, not Saudi SAR acceptance.

## CRM dashboard Saudi SAR acceptance — checkpoint112

- Live isolated QA rerun: `AGENT_URL=http://127.0.0.1:18081 ODOO_URL=http://127.0.0.1:8069 npx playwright test e2e/crm-dashboard.live.spec.js --reporter=line` — **2 passed**. Sales remained USD/company 1; Owner used the SAR company and rendered 3 won / 1 lost as 75%.
- A guarded ORM fixture created four synthetic CRM opportunities (three won and one archived lost) in isolated `be_qa_demo_full_20261024`. Cleanup was updated to include archived leads. Post-cleanup SQL confirmed `qa_build_engine_owner` company 1, allowed company `{1}`, zero fixture leads and zero company snapshot parameters.
- Screenshots: [Sales/USD](build-engine/frontend/screenshots/live-crm-win-rate.png) and [Owner/SAR](build-engine/frontend/screenshots/live-crm-win-rate-owner.png). The backend/React unit counts and build results are those of checkpoint111; this checkpoint changes only the QA fixture and live acceptance assertion. See [Checkpoint112](build-engine/CHECKPOINT_112.md).

## BE-068 supplier performance — checkpoint58

- Isolated Odoo 20 database: `be_vendorperf_qa_target_20261024`; only `be_vendor_performance` was upgraded for the final tagged run.
- Result: **8 post-install tests, 0 failures, 0 errors**. Tests cover native RFQ response dates, latest-of-multiple completed receipts, no/cancelled/pending receipt cases, protected derived metrics, non-Purchase menu/model denial, and no report read side effects.
- A read-only Odoo shell call compiled list, graph, pivot, detail and search views; it confirmed the installed module, `purchase.order` action target and Purchase User menu gate.
- Log: `/tmp/be_vendorperf_qa_acceptance.log` inside container `build-engine-odoo-1`. Full evidence and remaining acceptance: [Checkpoint58](build-engine/CHECKPOINT_58.md).

## BE-081 finance reports workspace — checkpoint55

- `backend/tests/test_business.py`: **47 passed** in a temporary Python venv. HTTP boundary checks cover invalid dates/report filters, mismatch between returned/current company, finance-gated analytic lookup, PDF/XLSX MIME/signature, and export company validation.
- Frontend Node suite: **39 passed**; `npm run build` passed. `git diff --check` and Python compilation passed.
- On isolated `be_theme_qa_20261024`, upgraded only `accounting_ksa` and ran `/accounting_ksa:TestKsaSecurity`: Odoo reported **14 post-tests, 0 failures, 0 errors**. Actual ORM calls as finance-enabled QA user returned Saudi-company id107, SAR P&L with 7 lines, cash flow with 11 lines, and 29 selectable analytic accounts for 2026. A real Odoo PDF rendered with `%PDF-1.4`; native XLSX export produced a valid ZIP/XLSX signature.
- Native security tests cover report access denial, invalid/cross-company analytic IDs, blocking analytic filters for cash flow, finance-gated analytic lookup and finance-gated PDF/XLSX generation. React report figures and exports come from Odoo; preview mode deliberately shows no fabricated totals.
- BE-081/086 remain PARTIAL. Non-admin browser walk-through, accountant review and complete story acceptance are outstanding. No production/demo database was upgraded.

## Construction QA and Namaa React demo database — checkpoint54

- A fresh isolated Odoo 20 database `be_qa_20261024_180934_3b41` ran the complete construction addon regression: **170 tests reported, 0 failures, 0 errors, 1 optional helpdesk skip**. Exact log: `build-engine-odoo-1:/tmp/be_qa_20261024_180934_3b41.log`. The run includes equipment custody (11), submittal/RFI (27), and owner dashboard (14) tests.
- The first clean run found two contract test helper calls closing a tender as the default user. The tender already correctly restricts closing to Procurement/Owner. The fixture now uses its procurement test account, and the subsequent fresh full run passed; production behavior was not loosened.
- At the user's request, `python3 scripts/seed_namaa_ksa_demo.py` seeded labeled demo records in the React-configured `namaa_ksa` database. The latest version has rerun successfully and preserves stable IDs. It adds a SAR pricelist, four products, synthetic CRM, quotation/sale, RFQ/purchase, a draft customer invoice, and a draft vendor bill natively matched to its confirmed PO line. No demo invoice was posted and no external API was called. The script removes only an earlier temporary USD demo order that it created, after checking its exact synthetic reference, partner, product codes and lack of invoices.
- Authenticated live same-origin reads as `admin` against `http://127.0.0.1:3200` returned HTTP 200 for CRM, Sales, Purchase, Accounting and Dashboard. Returned register counts were 3, 3, 2, and 2; dashboard totals were SAR 13,800 confirmed sales, SAR 585,000 pipeline, SAR 9,775 purchases, and SAR 0 receivables. Receivables remain zero because the fixture bills and invoice are drafts. Session was destroyed after verification. This verifies API data, not browser layout or non-admin acceptance.
- Record details: [`NAMAA_DEMO_RECORDS.json`](build-engine/NAMAA_DEMO_RECORDS.json); seed implementation: [`seed_namaa_ksa_demo.py`](../scripts/seed_namaa_ksa_demo.py).

## React tender workspace and demo refresh — checkpoint53

- The local Build Engine Odoo service was recreated with the Namaa addon mount. Using the real manifests on isolated `be_qa_demo_full_20261024`, combined `be_tender` and `namaa_ai_bridge` regression: **37 post-tests, 0 failures, 0 errors** (`/tmp/be015_final_combined_qa.log`); Odoo reported 19 and 22 tests respectively. This replaced the earlier temporary-manifest QA run.
- `scripts/verify_be015_bridge_rpc.py` authenticated as QA admin and QA Sales and exercised the live FastAPI list/options/detail routes against the demo DB. Sales can read tender details and safe confirmed BOQ options for readable projects; inaccessible CRM opportunities and bidder details are omitted. `scripts/seed_be015_react_demo.py` posted a synthetic tender draft through the same-origin BFF twice; both responses returned tender37 with its two checklist rows. This verified live BFF-to-Odoo access and idempotent creation. Browser-based role acceptance remains outstanding.
- The bridge suite covers company-scoped tender options/list/detail/draft creation, sales-role BOQ selection/draft creation, bid-detail hiding, idempotent retry, payload reuse rejection, and ISO deadline parsing. A first run exposed React's `datetime-local` format incompatibility and a too-specific test search; both were corrected before the passing run.
- Backend business API: **41 passed**. React Node suite: **39 passed**, including four tender payload tests. Frontend Docker production build passed (`be015-frontend-build-check`). Python compilation and `git diff --check` passed.
- The full synthetic walkthrough seed ran twice against only `be_qa_demo_full_20261024` with stable IDs. It contains 4 products, 2 confirmed sales, 2 confirmed purchase orders, 3 draft customer invoices, 3 draft vendor bills, CRM pipeline/qualification samples, and dashboard snapshot values for 13 projects (planned 12,000; analytic actual 2,500; five risk projects). Tender23 and bid15 remain a published tender and draft bid with three pending checklist responses. Zero fixture invoices/bills were posted and no external API calls were made.
- BE-015/016 remain PARTIAL because live role-based browser acceptance and approved portal integration are not verified. The React interface is implemented; lifecycle actions and evidence uploads open native Odoo.

## Tender checklists and submission evidence — checkpoint52

- Upgraded `be_tender` on the isolated `be_qa_be014_pipeline_20261024` database. Tagged Odoo 20 suite: **16 post-install tests, 0 failures, 0 errors** (`/tmp/be015_tender_checklist_final2.log`). New coverage verifies template snapshots, frozen templates after publication, mandatory-evidence validation, immutable completion/submission actor-time fields (including forged-context rejection), bid submit blocking, and sales-role access denial for bid responses.
- The construction walkthrough `be_qa_demo_full_20261024` was upgraded and `scripts/seed_be015_demo.py` ran twice with stable tender id23 and bid id15. It creates a published synthetic tender due 30 Nov 2026 and a draft vendor bid with three pending checklist records; it intentionally contains no uploaded supplier evidence and is not marked submitted.
- After upgrading only this QA DB and restarting the Build Engine Odoo QA container, authenticated read-only JSON-RPC verified tender23 and bid15, including three checklist templates and three bid checklist rows. The container health returned healthy.
- Related API/UI regressions: backend business tests **39 passed** and React business tests **9 passed**. No React tender screen was added in this increment.
- Python compilation and `git diff --check` passed. No external portal, posting, customer database, or real supplier evidence was used.
- BE-015/016 remain PARTIAL pending React tender screens, user-role browser walkthrough, and a product decision before adding any Etimad/portal connector.

## CRM pipeline stage and probability — checkpoint51

- The isolated Odoo database `be_qa_be014_pipeline_20261024` installed the bridge with its Odoo 20/OCA dependencies. Tagged `namaa_ai_bridge` suite: **19 post-install tests, 0 failures, 0 errors** (`/tmp/be014_namaa_bridge_suite_final.log`). Coverage includes stage visibility by team/company, invalid and out-of-range values, atomic rejection, write actor/timestamp and create/update behavior. Test fixtures use a dedicated SAR company with the Saudi chart so the KSA bridge preconditions and native journals are represented.
- Backend `test_business.py`: **39 passed**. React `business.test.js`: **9 passed**. The frontend production Docker build completed successfully (`be014-frontend-build-check`).
- `scripts/seed_be014_demo.py` was run twice against only `be_qa_demo_full_20261024`; stable IDs 51, 58 and 59 cover Qualified/62%, Proposition/48% and New/25%, respectively. All three records are synthetic and company-scoped; no posting or external call occurred. IDs and values are recorded in `build-engine/QA_DEMO_RECORDS.json`.
- BE-014 remains PARTIAL: no role-based browser walkthrough has been performed, and win-rate analytics remain BE-018 work.

## Native CRM lead promotion approval — checkpoint50

- `be_tender` upgraded on isolated `be_qa_be012_qualification_20261024`; tagged post-install suite: **14 tests, 0 failures, 0 errors** (`/tmp/be013_crm_promotion.log`). Added tests cover unapproved native conversion/direct type-write blocking, separate owner approval, requester self-approval denial, reason validation, rejection preserving lead state, immutable decisions, invalid request/access cases and cross-company visibility.
- Odoo 20 uses domain-scoped `ir.access` records; the review model grants sales users only their own company-scoped requests, owners company-scoped review access, and owner read-only visibility of company leads. Approved conversion runs through native `convert_opportunity` after approval, under a narrowly scoped server elevation; all ordinary direct conversion paths remain guarded.
- CRM native convert button is hidden for leads. The replacement request action, approval queue, reviewer form and lead audit list load successfully during module upgrade. Browser role walkthrough remains unverified.
- Dedicated construction walkthrough `be_qa_demo_full_20261024` was upgraded and `scripts/seed_be013_demo.py` ran twice with stable IDs: sales requester82, owner approver83, qualified lead55, pending review1. The lead remains a lead; no conversion or posting was performed. Role passwords remain in ignored `.env` only.
- BE-013 stays PARTIAL pending browser walkthrough and confirmation of the provisional owner approver policy (DEC-12). No production/customer database was changed.

## Native CRM lead qualification — checkpoint49

- `be_tender` was installed/upgraded and its tagged suite run on fresh isolated DB `be_qa_be012_qualification_20261024`. Final run: **11 post-tests, 0 failures, 0 errors** (`/tmp/be012_qualification_arabic_final.log`). Coverage includes yes/maybe/no decisions with required reason, reviewer/time attribution, ordinary CRM-user denial, malformed decision/reason rejection, opportunity exclusion and forged audit-value denial. Arabic `ar_001` was activated; Odoo loaded the module PO and the qualification field labels resolve to Arabic in `ir_model_fields`.
- The actual Odoo 20 browser form rendered the full-width **Lead Qualification** tab without client errors. It displayed the saved yes decision, synthetic reason and system-managed Mitchell Admin / timestamp. Screenshot: `docs/build-engine/crm/screenshots/be012-lead-qualification.png`.
- The guarded seed `scripts/seed_partner_demo_qa.py` ran twice successfully with stable qualification lead IDs 55/56/57; values are yes/maybe/no. The seed performs no posting or external calls.
- A first test command targeted a retained database that lacked the `be_tender` dependency graph; it discovered zero tests and is not counted. The fresh database run above is the valid evidence.
- BE-012 remains PARTIAL pending BD agent integration, explicit human promotion approval and complete A1–A4.

## Native RFQ comparison browser smoke — checkpoint48

- Authenticated to the isolated `be_qa_demo_full_20261024` Odoo instance and opened RFQ P00018 through the native purchase form. The estimated freight, other-fee and landed-total fields rendered without client errors.
- Opened **Alternatives → Compare Product Lines**. The table rendered all three synthetic draft RFQs and the **Estimated Landed Total** column. The $95/unit / $0-freight quote ranked at $11,400; the $90/unit quote with $1,500 estimated freight ranked at $12,300. The $11,400 landed price rendered green as the native comparison winner.
- Browser screenshot: `docs/build-engine/procurement/screenshots/be063-landed-cost-comparison.png` (portable public copy under `frontend/public/docs/`). The first browser pass exposed a stale long-running Odoo Python registry; restarting only the isolated `build-engine-odoo-1` container loaded the current installed module code. Recheck succeeded with zero Odoo client errors. No data was confirmed or posted.
- This is runtime UI evidence for the existing BE-063 partial slice, not a new story acceptance or a replacement for the 63 isolated model tests recorded below.

## Estimated landed-price comparison — checkpoint47

- Extended native Odoo alternative RFQs with editable estimated freight and other-fee values while a quote is open. Values must be nonnegative and become immutable after order commitment. An untaxed landed total is shown on the quote; fees are allocated to product lines by pretax company-currency value, falling back to quantity when all line values are zero.
- Native comparison now ranks the lowest estimated landed line/normalized unit price while retaining Odoo's earliest expected delivery ranking. A new highlighted comparison column displays the estimated landed price. Estimated quote fees are not posted accounting costs or a substitute for Odoo's native stock landed-cost valuation after receipt.
- Clean isolated DB `be_qa_be060_clean_20261024`: tagged `be_boq,purchase_request,purchase_alternative` run completed **63 post-tests, 0 failures, 0 errors**, with one optional test skipped because `purchase_requisition` is absent. Log: `build-engine-odoo-1:/tmp/be063_landed_cost.log`. Regression covers fee allocation, lower total price despite a higher base unit price, delivery-date ranking, negative fee rejection and post-commit immutability.
- The full construction walkthrough DB was upgraded in isolation and its seed run twice; IDs remained stable. It now includes three draft alternative RFQs with different fee/delivery profiles. No customer database, invoice posting or external API call was involved.
- BE-063 remains PARTIAL pending actual receipt/invoice landed-cost reconciliation, delivery performance history, role acceptance and full A1–A4.

## BOQ-linked material request to RFQ — checkpoint46

- Extended the reviewed OCA `purchase_request` workflow from `be_boq` without editing vendor source. Material request lines may link to an accessible confirmed BOQ cost code for the same product/company; the default analytic allocation is applied. The link becomes immutable once the request leaves draft.
- The native OCA RFQ wizard copies the BOQ line into the generated PO line. Its line-reuse search now includes the BOQ line, so two requests for the same product but different cost codes cannot be silently combined. The existing PO-line model revalidates the cost code, and the OCA wizard continues its native allocation/state/chatter path.
- Original workflow suite ran on isolated DB `be_qa_be063_20261024`. After adding a caller-context authorization check for BOQ-link create/write, the combined tagged suite ran on clean isolated DB `be_qa_be060_clean_20261024`: **62 post-tests, 0 failures, 0 errors**; one native alternative test skipped because optional `purchase_requisition` is absent. Module stats: be_boq25, purchase_request36, purchase_alternative15. The new role test verifies both unauthorized create and update denial for an ordinary purchase requester. Log: `build-engine-odoo-1:/tmp/be060_role_final.log`; run used `--http-port=0` to avoid the live lab port.
- Re-ran the QA seed three times after adding one draft BOQ-linked request. IDs stayed stable (`PR00083`, line109, BOQ line35). No customer DB was upgraded and no posted entries or external calls were created.
- BE-060 remains PARTIAL pending approver-role, project/company ACL acceptance and complete story criteria; status totals do not change.

## BOQ-linked procurement and native RFQ alternatives — checkpoint45

- Purchase quote/order lines in `be_boq` now link only to confirmed BOQ product lines for the same company. The relationship is available on native RFQs/POs, remains attached after commitment, and applies the BOQ project analytic account when the user has not supplied an explicit analytic distribution. A confirmed PO updates the linked BOQ line's actual quantity and cost.
- `be_boq` now depends on Odoo20's native `purchase_alternative` app for persisted alternative RFQ groups and product-line comparison by company-currency subtotal and expected date. It does not yet calculate freight/fees as landed cost; BE-063 remains PARTIAL.
- Clean isolated Odoo20 DB: `be_qa_be063_20261024`. Tagged rerun of `be_boq,purchase_alternative`: **31 post-tests, 0 failures, 0 errors**. Module stats report be_boq20 and purchase_alternative15; one native test was skipped because optional `purchase_requisition` is not installed. The first attempt exposed a fixture violation of the one-open-BOQ-per-project rule; the test setup was corrected and the same suite rerun successfully. Log: `build-engine-odoo-1:/tmp/be063_tests_rerun.log`.
- Read-only registry check confirms both modules installed, the PO BOQ field exists and the purchase form extension is active. A pre-existing computed-field `store` consistency warning for `be.boq` remains; it did not fail installation or tests.
- The isolated comparison fixture was seeded twice using `scripts/seed_be063_qa.py`; both runs returned the same record IDs and passed assertions that the lower-priced RFQ ranks best on price, the earlier delivery ranks best on date, and both records remain drafts. See `docs/build-engine/QA_BE063_RECORDS.json`.
- BE-060/063/077 remain PARTIAL: material-request linkage, explicit landed-cost policy, role/UAT and full A1–A4 remain open. No customer/live database was upgraded.

## BE-079 native supplier-reference duplicate guard — checkpoint43

- Moved the exact supplier reference check from the React bridge into `namaa_ksa_account`, making it an Odoo `account.move` constraint for ORM-created/updated vendor bills. It protects the same-company/same-supplier commercial entity, checks draft and posted bills, and serializes concurrent checks with an advisory transaction lock. It returns only a generic error and does not expose another bill's details.
- Native probable-duplicate detection for ambiguous same-date/same-amount records remains a review signal. The hard rule covers exact normalized references; OCR/import integrations using Odoo ORM receive the constraint, while direct SQL writes are outside this Odoo model guarantee.
- Isolated Odoo20 update on `be_crm011_20261024` upgraded `namaa_ksa_account,namaa_ai_bridge` and ran both tagged suites: **19 tests, 0 failures, 0 errors**. Native model tests cover duplicate create/edit rejection and another vendor's numbering; a bridge test confirms a user without accounting create access cannot create a bill. Log: `namaa-odoo20-odoo-1:/tmp/be079_accounting_invariant.log`.
- Backend **35 passed**; React **34 unit tests passed**; full Playwright **48 passed**, plus one focused Accounting edit regression after the final fixture update; Vite build passed (39 modules). No live Namaa database was upgraded.
- BE-079 remains PARTIAL pending broader finance-role permissions, Saudi accountant acceptance and complete A1–A4.

## BE-079 supplier invoice reference and duplicate guard — checkpoint42

Checkpoint42 first implemented the duplicate lookup inside `namaa_ai_bridge`; checkpoint43 supersedes that location with the accounting-model constraint so native Odoo and other ORM entry points use the same rule.

- React vendor-bill draft creation now carries an optional supplier invoice reference through the strict backend contract to the native Odoo `account.move.ref`. The reference is visible in the accounting register and bill details. Customer invoice payloads cannot use the vendor-only field.
- Odoo normalizes case and repeated whitespace, locks concurrent submissions for the same company/vendor/reference, and rejects an existing draft or posted vendor bill with the same reference. Another vendor can use the same supplier numbering. Odoo's native broader probable-duplicate detection remains a human review signal to avoid blocking legitimate same-date/same-amount invoices.
- Isolated Odoo20 `namaa_ai_bridge` update and tagged suite on `be_crm011_20261024`: **16 tests, 0 failures, 0 errors**, including exact normalized duplicate rejection, another-vendor acceptance, bill reference readback, and native PO bill matching. Log: `namaa-odoo20-odoo-1:/tmp/be079_duplicate_bill.log`. No customer/live Namaa database was upgraded.
- Backend business API tests: **35 passed**. React unit tests: **34 passed**. Full Playwright suite: **48 passed**, including vendor-reference field/payload and retry behavior. Vite production build passed (39 modules); after the final customer-invoice edit regression fixture update, that targeted browser case also passed. Python compilation and `git diff --check` passed.
- BE-079 remains PARTIAL: finance-role permission matrix, wider finance edge cases, accountant UAT, and full story acceptance are outstanding. Test database/Odoo code and browser request fixtures do not establish production runtime rollout.

## BE-011 explicit CRM merges — checkpoint41

- Updated the isolated Odoo 20 database `be_crm011_20261024`; the `namaa_ai_bridge` tagged suite reports **15 tests, 0 failures, 0 errors**. Tests perform transaction-scoped native opportunity and contact merges; verify merge chatter/note, stale revision and unmatched-candidate rejection, and deny organization merges to a CRM-only user lacking the partner-manager role. The merge tests roll back with the Odoo test transactions. Log: `namaa-odoo20-odoo-1:/tmp/be_crm011_20261024.log`. No office/customer database was upgraded.
- Backend suite against the current mounted worktree app: **36 passed**, including same-origin, request shape, identity and revision forwarding for both merge routes.
- React: **34 unit tests passed**, **48 Playwright cases passed**, including separate review confirmation, no write before confirmation, selected IDs/revisions in the request, and explicit organization destination. Production build passed (39 modules).
- Odoo enforces per-record write/unlink ACLs and the native merge wizard's group ACL. Selected rows are locked and their `write_date` is rechecked before merge. CRM chooses the surviving opportunity through native confidence ranking; organization merge keeps the opportunity-linked company record and appends a chatter note.
- Full story remains PARTIAL: false-positive and master-record policy and complete live role/company acceptance are still open.

## BE-011 CRM duplicate review — checkpoint40

- Fresh isolated Odoo 20 database `be_crm011_20261024`; `namaa_ai_bridge` install/update and tagged bridge suite: **11 tests, 0 failures, 0 errors**. Includes native matching, safe response fields, invalid record rejection and company isolation. The first fixture run exposed a company consistency violation when associating a foreign-company opportunity with a current-company partner; the fixture was corrected and the suite rerun successfully. Odoo log: `namaa-odoo20-odoo-1:/tmp/be_crm011_20261024.log`. No office or customer database was upgraded.
- Backend container tests against the current mounted `backend/app` and tests: **33 passed**. The first run used a stale baked app and could not import the current test contracts; rerunning with the worktree app mounted passed all cases.
- React: **34 unit tests passed**, **46 Playwright cases passed**, including live-shaped CRM duplicate review showing opportunity/organization candidates at desktop and 390px phone width, confirming no page overflow and no mutation request. Vite production build passed (39 modules).
- Candidate review is advisory: lead matches use Odoo's native CRM duplicate method; organization matching normalizes VAT/email for comparison. Results are limited to readable current/shared-company records and omit contact email, phone and VAT values. The React UI links out to native Odoo; no automated merge is implemented or tested.

## BE-010 government/private CRM classification —2026-10-24

- Added `be_tender_kind` end to end: strict backend request contracts, same-company CRM search fields, native Odoo create/read/update validation, and bilingual React opportunity editor, list and detail displays. Demo records cover government and private sectors.
- React: **34 unit tests passed**, production build passed, full Playwright suite **45 passed**. CRM E2E covers both Arabic phone and English desktop create/edit paths and confirms sample actions remain local.
- Backend business API suite: **32 passed** in the backend container.
- Fresh isolated Odoo 20 database `be_crm_010_20261024_165002`, installed with `--without-demo=True`: `namaa_ai_bridge` **11 tests, 0 failures, 0 errors**. It verifies native CRM create/read/update and invalid-sector rejection alongside existing bridge tests. No office/customer database was upgraded.
- A first fresh database with Odoo demo accounting rows could not complete bridge `setUpClass`, because that test setup attempts to change the company currency after journal items exist. The no-demo isolated run passed; this identifies a future test-fixture improvement, not a sector implementation failure.

BE-010 remains PARTIAL: reporting and complete authorized sales-role/company/project acceptance remain open.

## Coherent React preview demo records —2026-10-24

- Replaced unrelated placeholder rows with one shared synthetic Saudi construction dataset for CRM, sales, purchase, product catalogue, customer invoices/vendor bills and the dashboard. Five records per register link to named partners, order/site references and real product-line details. Preview dashboard totals derive from the same records; the bank reconciliation preview references the invoice examples. Corrected partner links and the SO0042 line total so the sample commercial records agree.
- Product records, line items, and totals remain client-side preview fixtures. No Odoo demo records were seeded and preview create/edit/delete remains local.
- React unit tests: **34 passed**; backend business API suite: **26 passed** (the two LangGraph-dependent tests skip when LangGraph is not installed in the test environment); Playwright: **44 passed**, including linked invoice/bill and bank reconciliation model/manual counterpart checks; Vite production build passed.
- Isolated Odoo 20 `namaa_ai_bridge` regression on `be_accounting_qa_20261024`: **8 tests, 0 failures/errors**, including PO-matched bill, credit note, CRM edit and task cases. Log: `/tmp/be_bank_rec_bridge_qa_20261024.log` in `be-theme-preview-odoo-1`. The host reported its optional HTTP port was already occupied; the named Odoo bridge tests still completed successfully.
- The portable guide was recaptured with the new populated preview screens and rebuilt, including a bank reconciliation preview capture in EN/AR. `node scripts/verify_manual.mjs`: **111/111 embedded screenshots decoded**, no external requests, no horizontal overflow at EN/AR desktop and phone widths. These browser checks use synthetic preview or watermarked tutorial records, not live data acceptance.

## BE-080 React reconciliation model flow —2026-10-24

- Fixed the reconciliation detail grid placement. The detail panel had overlapped the transaction list, which blocked clicks on configured model actions at desktop width.
- React loads configured Odoo reconciliation model writeoffs and supports manual counterpart entry from a company-scoped account search. Both paths use the same Odoo preview/validate engine. Native validation checks account, partner and tax access/company boundaries.
- Full Playwright suite: **44 passed**; backend business API suite: **26 passed**; React unit suite: **34 passed** and production build passed. The isolated Accounting KSA suite passed **204 tests, 0 failures/errors**, including manual account lookup, permissions, manual-writeoff preview/validation and rejection of an invalid account.
- BE-080 remains PARTIAL pending banking-role UAT, end-to-end accountant acceptance, complete receipt/payment coverage and remaining story criteria.

## BE-078 Progress certificate to invoice —2026-10-24

- Added the Milestone billing tab to React Accounting with active-company certificate listing, search/state filters and draft invoice status. Approved certificates without an invoice can request Odoo to create or return the linked draft; approval, configured sales taxes and accounting ACLs stay in Odoo. The action does not post or send invoices.
- Native Odoo coverage verifies unapproved certificates are rejected, configured account sales tax is carried into the draft, retry returns the same invoice, and list filters return only the matching certificate state. The BFF test covers same-origin mutation and the named bridge endpoints; Playwright covers certificate → draft invoice flow.
- Clean isolated Build Engine QA database `be_qa_20261024_152012_a3f6`: **154 native tests, 0 failures/errors**. React unit tests: **34 passed**; backend business API tests: **27 passed**; Playwright: **45 passed**; production build passed.
- BE-078 remains PARTIAL pending retention/advance policy, finance-role and customer acceptance, and full story A1–A4.

## Vendor bill to purchase order matching —2026-10-24

- Added a company/vendor-scoped lookup for approved purchase orders with quantities still available to invoice. React can select a PO and preload its available product lines; the Odoo bridge verifies vendor/company/state/line membership and cumulative available quantity.
- Bill line price, unit and taxes are taken from the Odoo purchase line. Created invoice lines retain `purchase_line_id`; React directs matched bills to native Odoo for edits so the three-way match link is preserved.
- Isolated Odoo 20 `namaa_ai_bridge` run on `be_accounting_qa_20261024`: **7 tests, 0 failures, 0 errors** (log `/tmp/be_purchase_bill_match_verified.log` in `be-theme-preview-odoo-1`). Includes PO-linked vendor bill and wrong-vendor/cumulative-excess-quantity rejection.
- Backend: **21 tests, 19 passed, 2 skipped** (host lacks LangGraph); React: **32 passed** and production build passed. The web/API suites verify payload and lookup boundaries; they do not replace accountant-role acceptance. Existing custom Odoo bridge tests were also updated to Odoo 20 activity completion semantics.
- Scope remains BE-079 PARTIAL: PO-backed bill draft matching works in QA; duplicate invoice prevention beyond Odoo's native controls, credit/debit note React flow, broader role/permission acceptance and end-to-end accountant UAT remain.

## Invoice credit/debit notes —2026-10-24

- Added React actions on posted customer invoices and vendor bills to create either credit or debit notes with a reason. The authenticated backend invokes named Odoo bridge methods only; Odoo native reversal/debit-note wizards create the linked draft and do not post it. Operation UUIDs make retries safe, and the note can only be posted through the existing review/confirmation flow.
- Isolated Odoo 20 `namaa_ai_bridge` update on `be_accounting_qa_20261024`: **8 tests, 0 failures, 0 errors** (log `/tmp/be_accounting_notes_qa_final.log` in `be-theme-preview-odoo-1`). The added case verifies native source linkage, draft state, amount, credit idempotency and debit origin.
- Backend: **23 tests, 21 passed, 2 LangGraph-dependent skips**. React: **33 unit tests passed**, production build passed, and the full **41-test Playwright suite passed**, including credit/debit note source confirmation and request payloads. This is bounded QA, not accountant acceptance or Saudi regulatory certification.
- BE-084 remains PARTIAL: native customer/vendor credit and debit draft creation is wired; finance-role permission/UAT, posting and reconciliation outcomes, taxes/retention treatment, and multi-currency/edge-case acceptance remain open.

## Accounting KSA fresh install and upgrade —2026-10-24

- Created isolated database `be_accounting_qa_20261024` on the Build Engine QA PostgreSQL instance. Fresh install of `accounting_ksa` completed; the module state is `installed`.
- Same isolated database upgraded with `-u accounting_ksa`. Both installation and upgrade executions ran the module's **204 tests: 0 failures, 0 errors**. Logs are in `be-theme-preview-odoo-1:/tmp/be_accounting_qa_20261024.log` and `/tmp/be_accounting_upgrade_20261024.log`.
- No office/customer database was changed. The Odoo 20 downloaded suites were not separately installed because OCR, bank import/reconciliation, budgets, assets and reporting already exist in the consolidated `accounting_ksa`; adding a second competing accounting stack would duplicate models and workflows. This QA database was created through the Odoo CLI and is retained for engineering verification; the current demo site's database filter does not expose this new database in its browser UI.
- Downloaded Odoo 17 job-costing package review: 249 files, proprietary Odoo Apps license, no automated tests found, and a dependency on `material_purchase_requisitions`. This remains an Odoo 20 port candidate, not installed code; perform the vendor-license/distribution check and migration before adding it.

## Latest checkpoint35 QA —2026-10-24

- Combined native construction + Accounting KSA update/test run on isolated `be_theme_qa_20261024`: **339 reported,336passed,3skipped,0failures/errors**. Exact log captured as `/tmp/be-combined-final.log`; full case catalog [QA_CASES.json](build-engine/QA_CASES.json). Accounting204cases:202passed,2conditional skips; construction135cases:134passed,1skip. Do not add earlier overlapping native runs to this total.
- Conditional skips: forecast integration with uninstalled `om_recurring_payments`; upstream administrator-without-accounting-features scenario inapplicable on this version; optional `helpdesk_mgmt_project` absent. Upstream reconciliation HttpCase tour is excluded from collection and not counted as passed.
- Fresh React **32unit+39browser** passed and production build passed; officebackend **19passed**; platform **65passed** in disposable PostgreSQL. Exact combined catalog **494reported:491passed,3skipped**. Browser tests include preview/mocked contracts, not universal live UAT.
- [RFI HTTP acceptance](build-engine/native-theme/RFI_API_QA.json): input validation/batch rollback, real roles, company/private-project/database/unauthenticated denials, state/audit/deadline persistence. [Native browser evidence](build-engine/native-theme/SCREENSHOT_MANIFEST.json): EN/AR at1440/768/390px; responsive keyboard navigation, real PM/respondent workflow and translated audit.
- [Saudi report QA](build-engine/accounting-ksa/REPORT_QA.json):12structured report APIs and12QWeb renders, independently seeded13,000SAR net profit, authenticated PDF/XLSX signatures, four real native financial views without page errors. Browser first exposed invalid static asset locations; corrected to native `/static/src/...` and passed. QA report URL corrected for internal PDF rendering. PDF signature does not replace accountant/layout review.
- [Native JSON-2 HTTP QA](build-engine/accounting-ksa/JSON2_QA.json): actual per-user temporary RPC keys verify manager/finance readiness/P&L, unauthenticated/invoicing denial, forbidden company, malformed options, private method and alternate database denial. No tokens are included in evidence.
- [Actual local-model QA](build-engine/accounting-ksa/LOCAL_AI_QA.json):all six specialist profiles completed against `qwen3.8:27b`, with company scoped accessible sources; business move count5before/after. This verifies actual connection/read-only smoke, not model accuracy or autonomous write capabilities. Unit tests cover opt-in, role/ownership, revoked financial context, protected audit fields and failed calls.
- Original office native theme read-only check passed: forest palette/search and no browser error; original office database was not upgraded with Accounting KSA. No live EDI/Fatoora or bank/government calls.

## Historical checkpoint34 QA (2026-10-23)

- `npm --prefix frontend test`: **32 passed**.
- `npm --prefix frontend run test:e2e`: **39 passed**; existing mock/preview scope retained.
- `npm --prefix frontend run build`: passed (36 modules).
- Existing backend container unittest discovery with tests mounted read-only: **19 passed**, no skips.
- `python3 docs/audit/run_platform_tests.py`: **1 +64 =65 passed**, no skips. Uses only a disposable PostgreSQL16 container, removed afterward.16 new adversarial cases cover all five tenant-selector endpoints and separate authenticated knowledge scopes. Deprecation/resource warnings remain.
- All 16 installable construction modules initialized on new `be_qa_20261023`; clean selected-module upgrade/test run: **119 tests reported, zero failures, zero errors, one optional helpdesk test skipped**. Log `build-engine-odoo-1:/tmp/be_qa_20261023-clean.log`; machine summary [ODOO_QA_RESULTS.json](audit/ODOO_QA_RESULTS.json). Fresh reproduction via `python3 scripts/run_odoo_qa.py` also passed 119 reported tests, zero failures/errors and one optional skip on second new `be_qa_20261023_200936_e00f`. No live tenant upgrades, Alembic or Fatoora calls.
- `node scripts/capture_odoo_screens.mjs`: **17 actual native Odoo views** render from authenticated QA; assertions include AI toolbar open/close, content visibility and no visible server error dialog/page exception. This caught and verified the Owl3 blank-screen fix. These are navigation checks as admin, not full user-role acceptance.
- `python3 scripts/build_frontend_manual.py` and `node scripts/verify_manual.mjs`: **84/84 embedded images decode offline**, zero external requests, no horizontal overflow in Arabic/English at1440px/390px; provenance filter/search/lightbox/Escape/empty-state checks pass. Evidence [MANUAL_QA.json](build-engine/frontend/MANUAL_QA.json).

Initial native runs are retained as failed diagnostics: one date-dependent Gantt fixture; later an old `set_param` test call plus serialization conflict from concurrent QA navigation. Fixed fixture/API and sequential native retest passed. Python passes alone missed the native Owl runtime failure; real browser capture exposed it. No full story is marked DONE by these bounded results.

Authenticated deployed React rehearsal also passed: all seven office screens rendered as admin, every observed API response was200, no business mutation or AI request was allowed, no record contents/screenshots were exported, and logout completed. Evidence [LIVE_WORKSPACE_QA.json](build-engine/frontend/LIVE_WORKSPACE_QA.json). The deployed manual and launcher returnHTTP200. Demo launcher phone layout, live readiness button and JavaScript checks passed; office readiness reports ready. These checks are navigation/connectivity rather than full role or transaction acceptance.

## Latest frontend Phase 3 and demo/manual verification (2026-10-23)

```text
npm --prefix frontend test                 → 32 passed, 0 failed
npm --prefix frontend run build            → passed (36 modules)
npm --prefix frontend run test:e2e         → 39 passed, 0 failed (no retries)
backend image unittest discovery           → 19 passed, 0 skipped
frontend-only Compose build/recreate        → passed
```

Backend command: `docker compose --env-file .env -f compose.yaml run --rm --no-deps -T -v "$PWD/backend/tests:/app/tests:ro" backend python -m unittest discover -s tests -v`. Includes the existing real LangGraph runtime approval/rejection tests with deterministic model/fake Odoo responses.

Five new unit tests cover review eligibility, authoritative run identity/status, native-only output links, valid activity dates/fields and activity filtering. Thirteen browser cases cover Arabic/English AI and task preview at 1440/768/390px without API calls or invented completion; live-shaped synthetic proposal approve/reject, context lock/continuation, missing-proposal reload, error feedback/history reopen; task validation/schedule, explicit completion/feedback and denied completion. The initial task validation-label selector issue was fixed with stable names/descriptions; final 39-case suite passed without retries.

Read-only live checks: BFF readiness returned ready for agent DB/Odoo/model availability. A direct local-model synthetic no-tools prompt returned READY, zero tool calls. A separate authenticated dashboard-agent API smoke with synthetic input returned completed/READY, zero business documents and no approval; session destroyed afterward. [LIVE_AI_SMOKE.json](build-engine/frontend/LIVE_AI_SMOKE.json) records the bounded result. No real financial/tool-based answer or AI draft acceptance is claimed.

The [single HTML guide](../frontend/public/user-manual.html) embeds 67 app screenshots and fonts (about 9.3 MiB). Offline Chromium verification: all 67 images decoded; synthetic filter 8 results; approval search 2 results; image viewer opened/closed; language toggle and restored gallery 67; phone page width 390=viewport 390; zero script errors and external requests. Eight approval/result/task tutorial images are watermarked synthetic fixtures. Source/provenance in [SCREENSHOT_MANIFEST.json](build-engine/frontend/SCREENSHOT_MANIFEST.json); screenshots are preview/synthetic only.

Rebuild: `npm --prefix frontend run build`, then `docker compose --env-file .env -f compose.yaml up -d --no-deps --build frontend`. App/guide return HTTP200. No backend/Odoo/database recreation, schema mutation, business document write or Fatoora call. One labelled synthetic AI request is stored in the actual local run history.

## Latest frontend design Phase 2 (2026-10-23)

Final commands against the current frontend:

```text
npm --prefix frontend test          → 27 passed, 0 failed
npm --prefix frontend run build     → passed (35 modules)
npm --prefix frontend run test:e2e  → 26 passed, 0 failed, no retries
```

The eight added unit checks cover invalid inputs, payload preservation, payment/type/stage filtering, subtotal behavior, field-error mapping and unchanged same-origin BFF requests with error metadata. The 16 added browser cases cover all four department flows in English desktop/Arabic phone, validation and local preview create/edit/delete without API calls; mocked update revision/line IDs/deletion list, explicit confirm/post/delete request boundaries, denied controls, stale-update feedback, sent-quotation confirmation, configured/zero prices, retry operation IDs and tablet dialog keyboard behavior. The original 10 shell checks also pass.

Initial runs found unstable field accessible names after validation, a reverse-Tab boundary and invoice test selectors that omitted the visible subtitle. Stable field names/description references, explicit modal wrapping and corrected selectors resolved them; the final entire suite passed. No suppressed or skipped failures.

`docker compose --env-file .env -f compose.yaml up -d --no-deps --build frontend` succeeded. Served http://127.0.0.1:3200 checks in fresh browser contexts covered all four registers at 1440×1000 English and 390×844 Arabic: five sample rows per screen, zero page errors, no page-level horizontal overflow. Three editor screenshots also had no internal horizontal overflow. See [phase report/screenshots](build-engine/FRONTEND_PHASES.md).

These are bounded frontend/sample/mocked-contract checks, not live Odoo ACL, tenant, accounting or compliance certification. No customer writes, model calls, database migrations or Fatoora calls were performed. Backend/Odoo/database services were not rebuilt.

## Subsequent frontend design Phase 1 (2026-10-23)

After the audit, the user authorized a phased React redesign and selected light/emerald/gold. Final commands:

```text
npm --prefix frontend test          → 19 passed, 0 failed
npm --prefix frontend run build     → passed (33 modules)
npm --prefix frontend run test:e2e  → 10 passed, 0 failed
```

The 10 browser tests cover 1440×1000, 768×1024 and 390×844 in English and Arabic, no page-level horizontal overflow,44px Appearance trigger and visible panel bounds, drawer inert/focus trap/Escape return, search shortcut/record opening, dismissible notices, persisted theme/menu preferences, CRM sample create/edit without API writes and mocked existing session login/logout. A React duplicate-key warning exposed repeated partner options in preview; deduplication fixed it and the CRM test now asserts no console errors.

Only `frontend` was rebuilt with `docker compose --env-file .env -f compose.yaml up -d --no-deps --build frontend`. Fresh browser contexts against the served http://127.0.0.1:3200 app verified Arabic and English at 1440px and 390px: light canvas, four cards, zero page errors and no horizontal page overflow. [Saved screenshots](build-engine/FRONTEND_PHASES.md) use sample data only.

Tooling: pinned Playwright dev dependency/lockfile; tracked absolute dependency symlink removed without modifying its external target. Initial npm 10 peer-resolution failed; clean local installation with legacy peer resolution succeeded, also verified by the Docker build using `npm ci --legacy-peer-deps`. No application dependency version change. These checks are frontend-scoped and do not satisfy full real-user ERP story acceptance. Business forms/AI/tasks translation and comprehensive accessibility remain open.

## Audit successful checks

| Suite / command from repository root unless stated | Actual result | What it verifies |
|---|---|---|
| `cd frontend && npm test` | 16 passed, 0 failed | Session API helpers, error handling, appearance persistence/validation, theme helpers; no rendered business E2E |
| `cd frontend && npm run build` | Exit0, Vite8.2.1, 28 modules | Office production bundle compiles |
| `docker compose --env-file .env -f compose.yaml run --rm --no-deps -T -v "$PWD/backend/tests:/app/tests:ro" backend python -m unittest discover -s tests -v` | 19 passed, 0 skipped | Existing fake-Odoo/ASGI business boundaries plus real LangGraph approval/rejection runtime with deterministic model responses; no live business writes |
| Isolated platform endpoint invocation, below | 1 passed | Agent run endpoint with disposable PostgreSQL tables |
| Isolated platform remaining suite, below | 48 passed, 1 deselected | All other current platform tests including SQL persistence; mocks/provisional evals are not real tenant acceptance |
| `/home/aymen/.nvm/versions/node/v22.23.2/bin/node --experimental-strip-types --test pwa/src/flows/materialUsage.test.ts pwa/src/sync/serverFields.test.ts` | 8 passed | Local material validation and server-field patches |
| `cd pwa && npm run build` | Exit0; TypeScript and Vite pass; service worker generated | PWA compilation/precaching |
| `cd pwa && npm run test:e2e:offline` | 2 passed | Arabic/RTL shell and offline quality-form local save; does not reconnect/apply to Odoo |
| `node --test workflow/auth.test.cjs` | 1 passed | Node-RED allowlisted internal Odoo login boundary |
| `python3 scripts/security/audit_be_ir_access.py` | `OK: 49 be_* models have ir.access coverage.` | Static row presence only, not effective authorization |
| Read-only installed-module SQL in product DB containers | Queries succeeded | Eight Namaa addons on `namaa_ksa`; six be addons on `build_engine`; full snapshots in inventory |
| Source JSON vs extracted DOCX/PDF IDs | 164 IDs in each; no IDs missing | Backlog identity coverage, not verbatim approval/content equality |

## Platform isolation and reproducibility

The successful platform runs used a new `postgres:16-alpine` container named `be-audit-pg-<random>`, no existing volume, a random loopback host port and a generated temporary password that was not printed. `KNOWLEDGE_DATABASE_URL` pointed exclusively there, `ODOO_URL=http://localhost:8069` matched importer mocks, and `KNOWLEDGE_TEST_DATABASE_URL` was unset. SQLAlchemy `Base.metadata.create_all` initialized only that disposable DB; no Alembic or live product schema operation ran. The container was removed in `finally`.

Commands inside `services/platform` with that isolated environment:

```sh
.venv/bin/python -m pytest -q --tb=short tests/test_agents.py::test_create_agent_run_endpoint
# 1 passed
.venv/bin/python -m pytest -q --tb=short tests -k 'not test_create_agent_run_endpoint'
# 48 passed, 1 deselected
```

These are **two invocations covering 49 distinct tests**, not one green full-suite invocation. The SQL fixture in `tests/conftest.py` creates and drops shared metadata per fixture. The standalone endpoint test does not initialize its own schema; running it after fixture teardown can fail. That lifecycle/order dependency should be fixed in a scoped test-infrastructure task. Tests using `knowledge_session` must never be pointed at an existing database: teardown drops metadata tables.

The audit runner is retained at [audit/run_platform_tests.py](audit/run_platform_tests.py). Run `python3 docs/audit/run_platform_tests.py` from the repository root. It needs the existing platform virtualenv, Docker and the local `postgres:16-alpine` image. It does not start the platform Compose service or its migration entrypoint.

## Initial failures and environment corrections

1. Initial command:

   ```sh
   env -u KNOWLEDGE_DATABASE_URL -u KNOWLEDGE_TEST_DATABASE_URL \
     services/platform/.venv/bin/pytest -q services/platform/tests -k 'not sql'
   ```

   Result: **2 failed, 45 passed, 1 skipped, 1 deselected**. `test_create_agent_run_endpoint` attempted the default local knowledge database and failed authentication. `test_commit_boq_json2_stub` mocked localhost while the repository-root `.env` resolved Odoo to `http://odoo:8069`, so RESPX rejected an unmocked request. No successful live import was performed.

2. Same command with `ODOO_URL=http://localhost:8069`: **1 failed, 46 passed, 1 skipped, 1 deselected**. Importer mock mismatch resolved; agent DB dependency remained. Isolated PostgreSQL resolved that dependency without changing application code.

3. `PYTHONPATH=backend .venv/bin/python -m unittest discover -s backend/tests -v`: **19 run, 17 passed, 2 skipped**, because host virtualenv lacks LangGraph. The container rerun above passed all 19. An initial `docker exec` discovery attempt also failed because tests are not shipped under `/app/tests`; the read-only bind mount supplied them to the successful one-off test container.

4. Default Node20 cannot execute `.ts` tests directly (`ERR_UNKNOWN_FILE_EXTENSION`, two file-loader failures). Node 22 with experimental type stripping passed all 8; no runtime source change was made.

5. Disposable DB harness setup initially dereferenced the virtualenv Python symlink and then saw temporary PostgreSQL initialization readiness. The retained runner uses the virtualenv path directly and TCP readiness for the final server. Both failed temporary containers were removed; they did not run the suite or touch an existing DB.

Deprecation warnings remain for FastAPI `on_event`, Starlette TestClient/httpx compatibility and some async resource cleanup. These are not silently treated as feature acceptance.

## Negative security observation

An in-process FastAPI `TestClient`, memory knowledge dependency and synthetic document were used; no network tenant data or persistent records were involved. The authenticated development principal belongs to `dev`.

| Request | Result |
|---|---|
| Ingest synthetic marker with `X-Tenant-Id: audit-tenant-b` | HTTP202 |
| Search same marker with that tenant-B header and same principal | HTTP200, 1 hit |
| Search same marker without header and same principal | HTTP200, 0 hits |

Historical audit observation, repaired by checkpoint34 in knowledge/agent endpoints: caller tenant selection overrode principal tenant. Service-layer filtering unit tests can pass while API authorization is unsafe. No passing story or tenant-isolation claim is based on those tests.

## Not verified during the initial audit (later bounded evidence above)

- Full OCA suite, DMS security and HOOT tests. Checkpoint34 separately verifies native custom construction tests and actual browser rendering; it does not retest all OCA ports. Historical counts remain historical in the migration backlog/checkpoints; DMS last reported15 failed +24 errors of80.
- Actual user-role/project/company isolation against live Odoo, production JWT/JWKS/MFA and per-user JSON-2 key binding.
- Real offline pull/push/conflict/delete/idempotency against Odoo, photos/MinIO/ClamAV, 48h/72h wall-clock soak or throttled3G target.
- ZATCA Simulation onboarding, real clearance/reporting, Saudi payroll/compliance validation or current regulatory references.
- Live AI model/agent runs, licensed external adapters, production citations/eval datasets/token budgets.
- 390×844/768×1024 office responsive acceptance and 44px controls; current PWA smoke uses desktop browser context.
- Full lint/security scans, production CI execution, tenant upgrade rehearsal, restored application/filestore backup, archive isolation under load and SLO/UAT sign-off.

No story is DONE based solely on these bounded checks. See [traceability](REQUIREMENTS_TRACEABILITY.md).

### Short-receipt reconciliation follow-up — 2026-10-25

- Added a React browser regression covering a SAR 390 bank receipt against a SAR 400 invoice: the Odoo preview must show SAR 10 remaining, a configured SAR 10 fee model must clear it, and the applied request must contain both source lines. Targeted Playwright result: **1 passed** (`frontend/e2e/workspace.spec.js`, short-receipt case).
- Added redacted Playwright stdout/stderr to the disposable live QA evidence and failure detail so subsequent live runs retain the failing assertion and browser diagnostics.
- The prior disposable live QA result still records a failure in the combined journey and the clone cleanup passed. A fresh live reproduction was not run in this follow-up because the local PostgreSQL service was at 99/100 connections. The native reconciliation unit test already covers the same SAR 390/SAR 400/SAR 10 calculation and passed in the recorded QA run; that does not replace the outstanding React → BFF → Odoo live verification.

## Checkpoint35 user delivery artifacts

- [Portable manual](../frontend/public/user-manual.html): **109 genuine captured/labelled screenshots** embedded; all109 decode offline, no external requests, EN/AR at1440/390px, Odoo filter42images, search/enlargement/Escape/empty-state passed. Native screenshot manifests distinguish synthetic QA from preview images. [Manual QA](build-engine/frontend/MANUAL_QA.json).
- [Saudi bilingual browser manifest](build-engine/accounting-ksa/SCREENSHOT_MANIFEST.json):9financial/advice screenshots including actual local Qwen advice in English/Arabic and390pxArabic; no page errors/outer horizontal overflow. Repeated native theme/RFI browser checks after accounting installation also passed (16captures).
- [QA test desk](../frontend/public/qa-checklist.html) embeds494automated case rows and26manual NOT RUN scenarios. Manual states/notes save in browser; export generates a26case JSON report. These user cases are not silently marked accepted by automated runs. [Desk interaction QA](build-engine/QA_DESK_QA.json).
- [Installable single-addon archive](../frontend/public/downloads/accounting_ksa-20.0.1.0.0.zip) contains only `accounting_ksa`, retaining tests, LGPL source and provenance. Excludes Python caches. System/Python/native Odoo dependencies still required; no live install authorized/performed by downloading it.

Final served-artifact check: demo/manual/checklist/caseJSON/addon ZIP allHTTP200 and byte-for-byte SHA256 match their source artifacts; office readiness HTTP200. Authenticated read-only navigation through all seven deployed React screens passed again, zero business mutations/page errors; logout passed. [Delivery evidence](build-engine/DELIVERY_QA.json). Bank and open-item reconciliation client actions also rendered as the finance user; bounded search check passed, not a completed matching/posting tour: [reconciliation UI evidence](build-engine/accounting-ksa/RECONCILIATION_UI_QA.json).

Additional export review: XLSX cell/shared-string contents independently confirm company and13,000SAR profit. The rendered PDF visually shows the correct company,2026period,SAR and13,000profit ([render](build-engine/accounting-ksa/QA_Profit_and_Loss_preview.png)). The current wkhtmltopdf runtime renders Latin text/numbers as outlines: pypdf/Poppler extract Arabic labels but not Latin figures. Searchable/accessible PDF and accountant print acceptance remain open; file signature/visual correctness do not imply complete PDF accessibility.

## Product-scope communication

[Standalone capability comparison](build-engine/BUILD_ENGINE_CAPABILITY_COMPARISON.html) maps feature presence against the live164-story matrix and official Odoo/SAP/Procore/DGA/Etimad/Balady source documentation. Build Engine evidence uses the isolated Odoo synthetic QA database and previously recorded regression results; vendor descriptions use their official published product documentation and are not a hands-on benchmark. No further software tests were run for this documentation-only artifact.

## Partner-meeting native feature run — 2026-10-24

The first run used `python3 scripts/run_odoo_qa.py`, created isolated database `be_qa_20261024_123150_1300`, installed Odoo 20 core + all custom `be_*` modules, and found a sales view XPath mismatch before tests. A corrected script run created `be_qa_20261024_123505_2161` and installed all modules successfully.

- The first post-install suite on that database ran151 tests and found one dashboard assertion and five submittal attachment access errors. The BOQ quote-line test and all equipment tests passed.
- Fixes: the dashboard fixture now invalidates non-stored BOQ actuals before snapshot creation; submittal attachment fixtures create files as the authorized uploading user. No attachment ACL bypass was introduced.
- After the owner decision-note policy change, the Odoo module set was upgraded and the complete suite rerun against the same isolated database: **152 tests, 0 failures, 0 errors**. It includes BE-BOQ sales quote→confirmed BOQ analytic linkage, equipment custody, submittal lifecycle, dashboard aggregation/security and existing construction modules. Odoo logged two database constraint errors inside tests that explicitly assert rejected writes; the test summary is0 failures/0 errors.
- The successful database was then seeded with synthetic partner demo records via Odoo ORM. Authenticated admin login and `/odoo` workspace returnedHTTP200. No live office/customer database was upgraded. No Fatoora calls were made.
- This is module regression evidence, not full story acceptance, accountant sign-off, production UAT or a migration/restore/security gate. No story status is promoted solely from this suite.
# Checkpoint 56 — live demo dashboard read-only smoke (2026-10-24)

- Database: `namaa_ksa`; authenticated React browser session.
- `/api/records/crm`, `/api/records/sales`, `/api/records/purchase`, `/api/records/accounting` and `/api/dashboard`: **HTTP 200**.
- Loaded counts: CRM 19, Sales 15, Purchase 12, Accounting 14.
- Browser capture blocked non-GET API requests; **0 business mutations**, **0 posted demo moves**.
- Screenshot: [Namaa live demo dashboard](build-engine/frontend/screenshots/namaa-ksa-live-demo-dashboard.png). Full response summary: [NAMAA_DASHBOARD_LIVE_QA.json](build-engine/NAMAA_DASHBOARD_LIVE_QA.json).
- Dashboard current-company SAR totals: confirmed sales 567,315.13; pipeline 19,440,000; confirmed purchases 1,748,598; receivables 0. Receivables are zero because sample invoices remain drafts.
- This is a live data/browser smoke check, not a regression suite or story acceptance.

# Checkpoint 58 — BE-068 supplier performance

- Isolated Odoo 20 QA DB `be_vendorperf_qa_target_20261024`.
- Tagged addon run: `-u be_vendor_performance --test-enable --test-tags /be_vendor_performance --stop-after-init`.
- Result: **6 post-install tests, 0 failures, 0 errors**. Covers response interval, latest date across multiple completed receipts, pending receipt handling, protected derived fields and Purchase group/menu access.
- The database is isolated from Namaa and the partner demo. An initial unfiltered dependency test attempt surfaced unrelated core `bus` tests requiring a selected database in their HTTP setup; it was stopped and rerun with module-scoped test tags.
- Full result and acceptance boundary: [Checkpoint58](build-engine/CHECKPOINT_58.md).

## React CRM lead promotion approvals — Checkpoint 109

- Isolated Odoo `namaa_ai_bridge` BE-013 transaction test: **1 targeted test passed**; verified Sales request, requester self-approval denial, Owner approval/native lead conversion, Owner rejection/lead retention and decision audit.
- Backend full suite: **110 passed, 2 skipped**. Contract checks cover positive strict lead IDs, required request/decision reasons, allowed decisions and SHA-256 revisions; route checks cover authenticated calls, mutation protection, validation and access error mapping.
- React unit suite: **69 passed**. Mocked React request → queue → approval and Owner rejection/history journeys: **2 passed**.
- Live Sales and separate Owner React → BFF → Odoo journey: **1 passed**. A fresh all-requests read verified approved state, converted opportunity type, decision reason and Owner audit identity.
- Vite production build passed. `py_compile` and `git diff --check` passed. Screenshot: [live CRM promotion](build-engine/frontend/screenshots/live-crm-promotion-approved.png).
- Isolated-only writes: synthetic promotion fixtures in `be_qa_demo_full_20261024`; bridge upgrade/test in `be_site_materials_qa_20261025`. No production/customer DB writes.

## React CRM pipeline stage and probability — Checkpoint 110

- Live isolated QA Sales-role Playwright: **1 passed**. React changed synthetic opportunity 295 from New/25% to Qualified/67%; a fresh BFF/Odoo read verified the updated stage, probability and Sales writer. Reusing the initial revision returned HTTP 422 and preserved the updated values.
- The live test exposed `crm_record_type` being included in a strict CRM update payload. React now drops that create-only field on updates; the unit suite includes a regression check.
- Odoo update `AccessError` maps to HTTP 403 and `UserError`/`ValidationError` to HTTP 422. The backend route test verifies stale-edit and permission mappings.
- Backend full suite: **110 passed, 2 skipped**. React unit suite: **69 passed**. Vite production build passed with the existing large-bundle advisory. Python compilation and `git diff --check` passed.
- Screenshot: [live CRM pipeline edit](build-engine/frontend/screenshots/live-crm-pipeline-edit.png). Only the synthetic `be_qa_demo_full_20261024` QA database was changed.

## React tracked purchase receipts — Checkpoint 126

- Fresh isolated Odoo 20 DB `be_qa_receipts_track_codex1`: targeted lot/serial receipt test passed **1/1**. It verifies the lot and serial move-line identities, purchase received quantities, a native backorder and atomic duplicate-serial rejection.
- The broader `namaa_ai_bridge` sweep ran **61 post-tests** with **0 assertion failures and 4 errors**. The errors came from optional Build Engine contract/project applications omitted from this minimal isolated installation; both receipt tests completed without error. The broad run is therefore not reported as green.
- Backend full suite: **125 passed, 2 skipped, 121 subtests passed**. React unit tests: **69 passed**. Mocked receipt journeys: **2 passed**, covering both ordinary receipts/backorder choice and tracked lot details with the exact BFF payload. Vite production build passed with its existing bundle-size advisory.
- Evidence and limitations: [Checkpoint126](build-engine/CHECKPOINT_126.md), [receipt QA JSON](build-engine/PURCHASE_RECEIPT_TRACKED_QA.json). Broader Purchase-only and warehouse role acceptance, warehouse/site policy and broad company acceptance remain open. No production database was changed.

### Live BE-070 tracked receipt acceptance (Checkpoint 126 follow-up)

- Disposable clone of `be_accounting_qa_20261024`: **1 live React → authenticated BFF → Odoo Stock/Purchase Receiver Playwright journey passed**. The receiver validated 5 lot-tracked units against a demand of 7; native Odoo verified the exact lot, Done receipt, company, validation user/time, 5 units in destination stock, PO received quantity 5, and native backorder quantity 2.
- The disposable clone `be_receipt_live_qa_4634aac1` was dropped; remaining database count **0**. The source QA and partner/demo databases were not changed.
- Screenshots: [lot detail review](build-engine/frontend/screenshots/live-purchase-receipt-lot-review.png) and [validated receipt](build-engine/frontend/screenshots/live-purchase-receipt-lot-validated.png). Structured result: [PURCHASE_RECEIPT_TRACKED_LIVE_QA.json](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json).
- The validation required restarting the local development Odoo and QA-only BFF containers to load current mounted code. The user-facing React services then passed the updated contract. This does not certify the separate partner/demo service stack.

### Live BE-070 serial-tracked receipt acceptance

- Disposable clone of `be_accounting_qa_20261024`: **2 live React → authenticated BFF → Odoo journeys passed** as a Stock/Purchase Receiver. Lot receipt: 5/7, exact lot, 5 native stock, PO received 5, native backorder 2. Serial receipt: 2/3, two unique serial lines at quantity 1 each, one destination unit per serial, PO received 2 and native backorder 1. Both checks verified validation actor/time and company scope.
- QA clone `be_receipt_live_qa_62589a08` was dropped; remaining database count **0**. No source QA or partner/demo database was changed.
- Screenshots: [serial review](build-engine/frontend/screenshots/live-purchase-receipt-serial-review.png), [serial validated](build-engine/frontend/screenshots/live-purchase-receipt-serial-validated.png). Full evidence: [PURCHASE_RECEIPT_TRACKED_LIVE_QA.json](build-engine/PURCHASE_RECEIPT_TRACKED_LIVE_QA.json).


## React warehouse provisioning — Checkpoint 157

- Targeted `namaa_ai_bridge` Odoo transaction test: **1 passed, 0 failures/errors**. A Stock Manager provisioned a native warehouse after the test removed the standard multi-warehouse/location implied groups; native Odoo setup, routes, operation types, locations and requester audit were verified, and a non-Stock user was denied.
- Backend business suite: **145 passed**. React unit suite: **69 passed**. Mocked site-location Playwright: **1 passed**. Live React → authenticated BFF → Odoo Playwright: **1 passed** on disposable clone `be_site_warehouse_qa_09573148`; native postconditions verified warehouse configuration and site-location parent before clone cleanup.
- Vite production build passed. Offline manual verification passed **214/214** embedded screenshots, EN/AR desktop/phone layout, search and viewer interactions with zero external requests. Python/JavaScript syntax and `git diff --check` passed.
- `be_qa_demo_full_20261025` and `be_accounting_qa_20261024` were backed up to `/tmp/*-before-warehouse.dump` and `namaa_ai_bridge` was upgraded on both local synthetic QA databases. No customer database was changed.
- Deployed `build-engine-react:be069-warehouse` at `http://localhost:3200/`; app, BFF health and `/user-manual.html` returned HTTP 200. Browser preview opened Purchase → Site locations and showed New warehouse without JavaScript errors; prior containers are retained for rollback.
- Evidence: [Checkpoint157](build-engine/CHECKPOINT_157.md), [structured QA](build-engine/SITE_LOCATION_WAREHOUSE_LIVE_QA.json), [warehouse screenshot](build-engine/frontend/screenshots/live-project-warehouse.png), [site screenshot](build-engine/frontend/screenshots/live-site-locations.png).
# Checkpoint 174 — Company-calendar critical-path scheduling

- Odoo `TestNamaaBridge.test_project_plan_uses_company_work_calendar_and_global_leave`: **1 passed, 0 failures/errors** after upgrading `namaa_ai_bridge` on disposable clone `be_calendar_schedule_demo_qa_20261025`. A configured Sunday–Thursday calendar with one full-day global holiday returned four working dates for the five-date task span; calendar name and company timezone were returned. Clone was terminated and dropped (database count check 0). Evidence: [PROJECT_CALENDAR_NATIVE_QA.json](build-engine/PROJECT_CALENDAR_NATIVE_QA.json).
- React `node --test tests/*.test.js`: **73 passed**. Focused `npx playwright test e2e/project-plan.spec.js --workers=1`: **1 passed**, asserting a ten-workday critical path and visible Odoo calendar name.
- `python3 -m py_compile` and scoped `git diff --check` passed. Production React Docker image `build-engine-react:be042-company-calendar-174` built successfully. Existing large Vite bundle advisory remains (1.02 MB minified, 257 KB gzip).
- Full calendar data is obtained from the configured company resource calendar. This does not verify per-employee crew availability, project-specific calendars, or portfolio Gantt behavior; BE-042 remains PARTIAL.

# Checkpoint 177 — React missing-method recovery

- React `npm test`: **75/75 passed**, including explicit missing customer-list and purchase-receipt-list bridge errors.
- `npm run build`: passed (existing bundle size advisory). Production image deployed to `:3200`; served bundle contains recovery guidance. Scoped `git diff --check` passed.
- No Odoo DB writes. Evidence: [Checkpoint177](build-engine/CHECKPOINT_177.md).

# Checkpoint 178 — Receipt-controlled vendor bills

- Disposable-clone Odoo 20 test `TestNamaaBridge.test_vendor_bill_for_receipt_controlled_material_is_limited_to_received_quantity`: **1 passed, 0 failed, 0 errors** after upgrading `be_project,be_boq,be_site,namaa_ai_bridge` on the clone.
- Verifies zero billable quantity before receipt, two units available after a partial receipt from five, native PO-line linkage and rejection above received quantity. Clone dropped; no demo/customer DB changed.
- Startup logged a missing-table warning for optional `om.bank.reconciliation.event` in this clone; the targeted test passed. See [Checkpoint178](build-engine/CHECKPOINT_178.md).

# Checkpoint 179 — Concurrent vendor-bill quantity safety

- Odoo 20 `namaa_ai_bridge` regression on a disposable clone, with `be_project,be_boq,be_site,namaa_ai_bridge` upgraded: **75 post-tests, 0 failures, 0 errors**.
- Isolated HTTP race: two distinct bill requests simultaneously waited on the same PO-line `FOR UPDATE`; after release one succeeded and one exhausted-quantity rejection returned. Persisted linked bill quantity was 1 against PO quantity 1. Clone dropped. Evidence: [VENDOR_BILL_RACE_QA.json](build-engine/VENDOR_BILL_RACE_QA.json), [Checkpoint179](build-engine/CHECKPOINT_179.md).
- Python compilation and scoped diff check passed. No active/demo/customer database was changed.

# Checkpoint 180 — Project analytics through a matched vendor bill

- Odoo `namaa_ai_bridge` suite on a disposable clone, after upgrading `be_project,be_boq,be_site,namaa_ai_bridge`: **75 post-tests, 0 failures, 0 errors**.
- Enhanced matched-bill test creates a confirmed BOQ and analytic-linked PO, verifies native distribution inheritance on the bridge-created bill, posts the bill and confirms analytic lines point to the same project account.
- Clone dropped; no active/demo/customer database changed. Python compilation and scoped diff check passed. See [Checkpoint180](build-engine/CHECKPOINT_180.md).

# Checkpoint 195/196 — CRM manual lead and Namaa live runtime recovery (2026-10-26)

- BE-009 isolated live QA: **1 React → BFF → Odoo journey passed**. Sales-role create without a customer persisted as native `crm.lead`; blank name failed before RPC; reopen confirmed company, creator, timestamps, sector and state; unauthorized and foreign-company attempts were denied without disclosure. Temporary QA clone and BFF were removed.
- Native Odoo bridge: **2 tests passed, 0 failures/errors**. Focused backend payload boundary: **1 passed**. React unit suite: **79/79**. Vite production build passed.
- Runtime recovery: restarted Odoo after confirming `accounting_ksa`, `namaa_ai_bridge`, and their models were installed in the database while the active service registry was stale. Refreshed the BFF process and deployed the already-built React image. React root, Odoo login and BFF liveness return **200**.
- Authenticated, read-only smoke through the deployed BFF: `/api/bank-statements/maps`, `/api/quality-gates/daily/options`, `/api/purchase-requests/options`, `/api/purchase-requests?limit=1`, `/api/customers?limit=1`, and `/api/purchase-receipts?limit=1` each returned **200**. Bank-map response contains zero configured maps and one journal; daily safety options contain one project and one published template.
- No shared business records were created or changed during the runtime smoke; role ACLs were not weakened. A generic 404 was not reproducible on tested routes. Capture its exact URL if it returns.

# CRM qualification company/project context — Checkpoint 198

- Native Odoo qualification regression: **3 passed, 0 failures/errors** on a disposable QA clone; company and linked project survived list/update/readback, the Sales decision/audit persisted, stale revision was rejected and the no-CRM reader was denied. The temporary clone and BFF were removed.
- React unit suite: **80 passed**. Focused `lead-qualification.spec.js`: **1 passed**, asserting company/project context in both the register and decision dialog.
- Backend suite: **165 passed** in an ephemeral container with the test-only `respx` dependency installed for that run. Host Python lacked `httpx`, `fitz` and `respx`, so the image-based runner supplied the declared runtime dependencies without changing the host environment.
- Vite production build passed (existing large-chunk advisory remains). Python compilation passed.
- BE-012 remains PARTIAL; live qualification-specific browser acceptance and evaluated BD suggestions remain open. Details: [Checkpoint198](build-engine/CHECKPOINT_198.md).

# React API routing recovery — Checkpoint 212 (2026-10-26)

- Rebuilt the Namaa BFF from current source and corrected the React Namaa Nginx proxy. Before the correction, React `/api/*` requests went to the Build Engine QA BFF while Odoo login went to Namaa, causing route 404s and database/model mismatch messages.
- Authenticated live smoke passed for dashboard, capabilities, tasks, CRM, sales, purchase and accounting (50 records each, snapshots available). Bank statement maps and daily safety options returned 200; the response contained the installed demo map, one project and one published template.
- No business records were written. A non-eligible Odoo user still needs the Site, Project Manager or Owner role to complete safety checklists. Evidence: [Checkpoint212](build-engine/CHECKPOINT_212.md).

# React vendor bill OCR — Checkpoint 213 (2026-10-26)

- React unit suite: **80 passed**; focused vendor bill OCR Playwright: **1 passed**; backend business suite: **158 passed**. Vite production build passed with the existing large-bundle advisory.
- Focused native Odoo bridge test: **1 passed, 0 failures/errors** on a disposable clone. The authenticated BFF → Odoo journey parsed the text-layer sample, returned the same draft on an identical retry, rejected the same operation ID with changed content, and verified a native `in_invoice` with four draft product lines. The disposable clone and temporary BFF were removed; `namaa_ksa` was not changed.
- Live read-only smoke on `:3200`: `vendor_bill_ocr=true`, OCR options, bank maps and daily safety options returned HTTP 200. The API routing correction from Checkpoint 212 remains active.
- Authenticated browser smoke on the deployed React app opened Accounting → Bill capture with zero page errors; [screenshot](build-engine/frontend/screenshots/vendor-bill-ocr-live.png).
- This verifies text-layer PDF reading. Scanned files need server OCR tools and were not tested in this slice. See [Checkpoint213](build-engine/CHECKPOINT_213.md) and [isolated QA evidence](build-engine/VENDOR_BILL_OCR_LIVE_QA.json).

# Checkpoint 230 — React vendor bill to approved PO

- Isolated `namaa_ksa` clone native bridge tests: **2 passed, 0 failures/errors**. Live accountant React → BFF → Odoo browser: **1 passed**. The matched draft reopened with PO origin `P00054`, line 104, company, creator and timestamps; persisted quantity 3 and SAR 125.50 from the PO despite a SAR 999 submitted UI price.
- The reader without accounting permission received 403 on OCR options/create and created zero bills. Retry/idempotency passed. Clone and temporary BFF were removed; no business rows were written to shared `namaa_ksa`.
- Backend draft-display-name regression: **2 passed** with current-company scope; after final edits the targeted regression passed again (**1 passed**). React production build passed (existing chunk-size advisory remains).
- Demo rollout: protected DB archive `/tmp/namaa_ksa_pre_be079_po_match_20261026.dump` verified, 10,691,628 bytes, mode 0600. Upgraded `namaa_ai_bridge` `.13`, restarted Odoo, rebuilt current backend/React. Read-only admin smoke passed on routes for bank maps, daily safety, purchase requests and accounting records.
- See [Checkpoint 230](build-engine/CHECKPOINT_230.md), [QA JSON](build-engine/VENDOR_BILL_OCR_LIVE_QA.json) and [matched-bill screenshot](build-engine/frontend/screenshots/vendor-bill-po-match-live.png).

## Checkpoint 231 — Purchase receipt schema repair and demo smoke checks

- Reproduced `/api/purchase-receipts` HTTP 502 against `namaa_ksa`: the database lacked `stock_picking.maintenance_request_id`, declared by current `be_equipment` source version 20.0.1.0.2; the installed database version was 20.0.1.0.1.
- Backed up `namaa_ksa` to `/tmp/namaa_ksa_pre_receipt_schema_20261026.dump` (10,692,618 bytes, mode 0600; PostgreSQL archive listing verified).
- On a disposable clone, upgraded `be_equipment`, `be_project`, and `namaa_ai_bridge`. Focused native test `test_react_purchase_receipt_records_actuals_and_native_backorder`: passed, 0 failures, 0 errors. Clone dropped.
- Applied the same module upgrades to `namaa_ksa`, restarted Odoo, and verified the missing column and installed addon versions.
- Authenticated read-only React proxy smoke checks using the demo administrator: `/api/purchase-receipts` 200 (10 rows), `/api/bank-statements/maps` 200 (1 map, 1 journal), `/api/quality-gates/daily/options` 200 (1 project, 1 template), `/api/purchase-requests/options` 200, `/api/customers` 200 (9 rows).
- Generic Werkzeug 404 and role denials were not reproduced for the administrator. Ordinary users still require the documented Odoo roles and company access. No business records were created by the checks.
- See [Checkpoint 231](build-engine/CHECKPOINT_231.md).

# Checkpoint 229 — Refresh React demo and bridge

- React production image rebuilt successfully from the current frontend source (Vite build passed; the existing >500 kB chunk advisory remains).
- Upgraded `namaa_ai_bridge` in the configured live demo DB `namaa_ksa` from version `20.0.1.0.10` to `.12`, restarted Odoo, and replaced the stale one-off `:3200` React container with the Compose frontend/backend.
- Authenticated read smoke as admin through `:3200`: bank statement maps, daily-safety options, purchase-request options and purchase-request list each returned HTTP 200. An intentionally unknown API route returned 404 as expected.
- No business records changed. Role checks were not weakened. Generic 404 and role denial for the user's specific account/action could not be reproduced under admin; exact URL and login role are required to isolate those cases.
- See [Checkpoint 229](build-engine/CHECKPOINT_229.md).

# Checkpoint 216 — Workspace access-error triage

- Focused native Odoo test on a disposable clone passed: `test_react_material_request_uses_native_request_and_approval_roles` (1/1). The requester had a Build Engine Project Manager role and no OCA Purchase Request group; the clone was dropped.
- Upgraded Namaa `namaa_ai_bridge` to `20.0.1.0.10` after taking `/tmp/namaa_ksa_pre_be_purchase_access_20261026.dump` (10,493,329 bytes; mode 600; archive listing verified).
- Post-upgrade authenticated calls through React `:3200`: `/api/bank-statements/maps` 200 (1 map), `/api/quality-gates/daily/options` 200 (1 project), `/api/purchase-requests/options` 200, `/api/customers` 200 (9 rows), `/api/purchase-receipts` 200 (31 rows).
- Generic 404 was not reproduced. Daily-safety role denial remains expected without Site/PM/Owner; bank-map management requires Accounting Manager.

# Checkpoint 235 — Local runtime/schema repair

- React production image build passed; BFF reports healthy and React serves at `localhost:3200`.
- Upgraded `namaa_ksa_purchase` `.2` and `namaa_ai_bridge` `.14` in `namaa_ksa`; confirmed `purchase_order_line.namaa_quote_compliance_status` exists.
- Direct Odoo read checks as admin passed for customers, purchase receipts, bank import maps, daily-safety options and purchase requests.
- Unauthenticated route probes returned expected 401 (not 404) for customers, purchase receipts, daily-safety options and bank import maps.
- Role authorization was not relaxed. The user's non-admin login was not available for an authenticated browser check.



## Latest live acceptance slice — BE-153 (Checkpoint 253)

The focused Odoo lifecycle/security suite passed **4/4** in a disposable clone. Authenticated React → BFF → local Qwen 3.8 27B → Odoo browser journey passed **1/1**. Postconditions confirmed a single pending suggestion by the PM with six current source citations; variation remained draft at amount delta 750, BOQ quantity remained 100, and project/task timestamps were unchanged. The clone was dropped, Odoo restarted, and the source DB was unchanged. See [live QA report](build-engine/VARIATION_IMPACT_LIVE_QA.json), [live screenshot](build-engine/frontend/screenshots/live-variation-impact-draft.png), and [Checkpoint 253](build-engine/CHECKPOINT_253.md). Arabic, ordinary-role/company boundaries and full A1–A4 remain open; BE-153 remains PARTIAL.


## BE-148 AI project charter and baseline — Checkpoint 254

Focused backend generator/route tests passed **8/8**. Combined native Odoo charter lifecycle and AI source/security tests passed **7/7** on a disposable clone. React mock browser journey passed **1/1** and Vite production build passed. Authenticated live React → BFF → Qwen 3.8 27B → Odoo journey passed **1/1**: the PM's source-cited AI suggestion remained pending; the PM created/submitted the official charter and the separate Owner approved it. Odoo verified immutable charter events and the task/source links. The clone was dropped, Odoo restarted, and the source database was unchanged. Arabic quality, broader roles/tenant boundaries and full A1–A4 remain open. See [Checkpoint 254](build-engine/CHECKPOINT_254.md), [live evidence](build-engine/PROJECT_CHARTER_LIVE_QA.json), [native evidence](build-engine/PROJECT_CHARTER_AI_NATIVE_QA.json) and [screenshot](build-engine/frontend/screenshots/live-project-charter-ai-draft.png).
## Checkpoint 255 — BE-029 CRM account research and opening-message draft (2026-10-26)

Backend generator/API focused tests passed **4/4** using the running backend container's installed dependencies (3 model constraints and 1 route contract covering create and reopen). Native Odoo permission, stale-source, citation and pending-suggestion tests passed **3/3** on a disposable clone. React mocked Playwright flow passed **1/1**; authenticated live React → BFF → Qwen 3.8 27B → Odoo flow passed **1/1** and reopened the saved draft. Vite production build passed. Odoo postconditions verify one pending suggestion by the Sales user, exact lead/organization citations, unchanged lead write date/message/activity IDs, zero messages sent and zero activities created. Both QA clones were dropped; Odoo restarted; source `be_qa_demo_full_20261025` was unchanged. Initial QA attempts exposed a nonexistent CRM group external ID and an incorrect React test proxy target; both were corrected before the final successful native and live runs. No external research or outbound communication was attempted. See [Checkpoint 255](build-engine/CHECKPOINT_255.md), [live evidence](build-engine/CRM_ACCOUNT_RESEARCH_LIVE_QA.json), [native evidence](build-engine/CRM_ACCOUNT_RESEARCH_NATIVE_QA.json), [live screenshot](build-engine/frontend/screenshots/live-crm-account-research.png), [generator tests](../backend/tests/test_crm_account_research_ai.py), [API tests](../backend/tests/test_business.py) and [browser test](../frontend/e2e/business.spec.js). BE-029 remains PARTIAL; counts **17 DONE, 117 PARTIAL, 20 MISSING, 10 BLOCKED**.

Backend generator/API focused tests passed **4/4** using the running backend container's installed dependencies (3 output/source/validation tests and 1 authenticated mutation-route contract). Native Odoo tests passed **3/3** on a disposable clone: pending suggestion persistence and reopen list, stale source rejection, foreign citation rejection, and denial for non-Sales/Owner. React Playwright live-mock journey passed **1/1**; Vite production build passed. The first native attempt exposed a wrong CRM group external ID in the new test fixture; the fixture now uses `sales_team.group_sale_salesman`, and the final isolated run passed. QA databases were dropped; source `be_qa_demo_full_20261025` was unchanged. No external research or outbound communication was attempted. See [Checkpoint 255](build-engine/CHECKPOINT_255.md), [native evidence](build-engine/CRM_ACCOUNT_RESEARCH_NATIVE_QA.json), [generator tests](../backend/tests/test_crm_account_research_ai.py), [API tests](../backend/tests/test_business.py) and [browser test](../frontend/e2e/business.spec.js). BE-029 remains PARTIAL; counts **17 DONE, 117 PARTIAL, 20 MISSING, 10 BLOCKED**.


## Checkpoint 296 — BE-151 live Qwen project risk review (2026-10-27)

- Focused backend risk/report suite: **15 passed**. React unit suite: **85 passed**. Project report browser suite: **2 passed**.
- Isolated Odoo native report suite: **4 passed**, covering role/company access, current source snapshots, category-specific citations, stale-source rejection, pending persistence and independent review.
- Live test: **1 PM → React → BFF → Qwen 3.8 27B → Odoo → independent Owner journey passed** on a disposable clone. Odoo readback verified all three domains, citations to task/BOQ/nonconformance/RFI records, independent review and unchanged project write date.
- Clone, temporary BFF and QA Odoo process removed; source database namaa_ksa unchanged. Screenshots and machine-readable results: [draft](build-engine/frontend/screenshots/live-project-risk-draft.png), [review](build-engine/frontend/screenshots/live-project-risk-review.png), [approved review](build-engine/frontend/screenshots/live-project-risk-reviewed.png), [live QA JSON](build-engine/PROJECT_RISK_LIVE_QA.json).
- BE-151 remains PARTIAL pending full story criteria, production role/company breadth, live Arabic evaluation, mitigation tracking and complete A1–A4.


## Checkpoint 299 — BD scouting Odoo handoff guardrails

Focused native test `be_ai:TestBeAi.test_bd_scouting_finding_routes_and_prevents_duplicate_handoff` passed **1/1** against a disposable clone of current `namaa_ksa`. It verified authorized CRM-lead targeting, pending `yes`/`maybe`, stored/flagged `no`, duplicate active handoff denial, invalid classification denial and runtime-only creation. The clone was dropped and the source database was unchanged. Python compilation and `git diff --check` passed. This is not a full BD-agent acceptance run: discovery runtime, React review, source-fit evidence and multi-worker concurrency stress remain open. See [Checkpoint 299](build-engine/CHECKPOINT_299.md) and [machine-readable QA](build-engine/BD_SCOUTING_HANDOFF_QA.json).


## Checkpoint 300 — CRM scouting AI assessment and human review

- Backend focused scouting suite: **7 passed**, 199 deselected (includes 7 parametrized subtests).
- React unit suite: **85 passed**. Focused Playwright mocked React review journey: **1 passed**.
- Native Odoo: **2 passed, 0 failures/errors** on a disposable clone of `namaa_ksa`; clone dropped, source unchanged.
- Vite production build and Python compilation passed; `git diff --check` passed. Build reports a large JS chunk advisory.
- Limits: the Playwright flow mocks API responses; no full React→BFF→Odoo→Qwen journey has been accepted. The increment is not deployed to shared services. See [Checkpoint 300](build-engine/CHECKPOINT_300.md) and [QA JSON](build-engine/CRM_SCOUTING_AI_QA.json).


### Checkpoint 300 live model/browser acceptance

`python3 scripts/run_crm_scouting_ai_live_qa.py` passed. One authenticated React journey used a disposable clone of `namaa_ksa`, the temporary current-source BFF and local Qwen 3.8 27B. The generated finding was source-bound to `crm.lead:92`, remained pending, then the Owner saved a reasoned matching human decision. Odoo readback confirmed approved state, reviewer, source, decision reason and audit event. The clone, Odoo worker, temporary BFF/proxy and image were removed; the shared source database was unchanged. See [live QA JSON](build-engine/CRM_SCOUTING_AI_LIVE_QA.json) and [Checkpoint 300](build-engine/CHECKPOINT_300.md).

Native scouting review coverage now includes both outcomes: a matching human decision approves the suggestion; a conflicting decision rejects it and stores the reviewer reason and rejection audit event. The updated focused Odoo suite passed **2/2** on a disposable `namaa_ksa` clone and dropped the clone.


## Checkpoint 301 — OCA DMS on Odoo 20

The current vendored OCA `dms` addon passed the complete `/dms` suite: **77 tests, 0 failures, 0 errors** on a disposable clone of `namaa_ksa`. The addon source was temporarily copied into the running Odoo 20 container's test-only addon path. Clone, copied addon and test log were removed; source database unchanged. See [Checkpoint 301](build-engine/CHECKPOINT_301.md) and [machine QA evidence](build-engine/OCA_DMS_ODOO20_QA.json).
## Checkpoint 332 — React site material issue enabled in local demo (2026-10-27)

- Re-ran isolated purchase → project-bin receipt → bill → site issue/return on current source: **2 native Odoo cases passed**; authenticated live React → BFF → Odoo browser flow **1/1 passed**. Confirmed 8 received, 6 issued, 2 returned and 4 units / SAR 160 net BOQ actual; bill analytic SAR 320 remains separate. Disposable DB and BFF removed.
- Created and validated the shared demo backup before schema rollout: `/tmp/namaa_ksa_before_be_site_install_20261027.dump`, mode **0600**, 11,574,215 bytes.
- Installed `be_site` and upgraded its related Build Engine modules in `namaa_ksa`; focused post-install regressions **2/2 passed, 0 failures/errors**. SQL confirms the target modules are installed.
- See [Checkpoint 332](build-engine/CHECKPOINT_332.md) and [isolated live evidence](build-engine/SITE_MATERIAL_ISSUE_LIVE_QA.json). BE-072 remains **PARTIAL** pending DEC-18, wider role/company/tenant acceptance and full A1–A4.

## Checkpoint 333 — Project-plan cycle and scope guards (2026-10-27)

- Extended the native bridge test to reject a dependency cycle without persisting a partial graph update, and to reject a cross-project parent without creating a partial task.
- Isolated ordinary-PM React → BFF → Odoo project-plan acceptance: **1/1 passed**. Phase/task/dependency create-edit-reopen, Gantt interactions, milestone linkage, invalid input and unauthorized/foreign-company denial passed; native readback confirmed project/company and actor. Disposable clone dropped.
- The expanded native bridge regression ran in the clone upgrade. No shared demo schema or business rows changed. See [Checkpoint 333](build-engine/CHECKPOINT_333.md) and [live QA evidence](build-engine/PROJECT_PLAN_LIVE_QA.json).

## Checkpoint 334 — Saudi Arabic bank CSV parsing (2026-10-27)

- Accounting KSA CSV parser now normalizes Arabic/Persian digits, Arabic date values, Arabic decimal/thousands separators, bidi marks and Unicode minus signs before parsing mapped amounts/dates.
- Full native `TestCsvParser` class on a disposable clone: **10 passed, 0 failures/errors**. Clone dropped; source `namaa_ksa` unchanged.
- See [Checkpoint 334](build-engine/CHECKPOINT_334.md) and [isolated evidence](build-engine/KSA_ARABIC_BANK_CSV_QA.json). This does not claim direct bank API connectivity or bank-specific layout acceptance.

## Checkpoint 335 — Mapped CSV duplicate-import protection (2026-10-27)

- CSV/Excel rows with no bank-provided transaction ID now receive deterministic import IDs; occurrence numbering preserves truly repeated equal rows in the same file.
- Full Accounting KSA CSV parser class plus native mapped-CSV re-import test on a disposable clone: **12 passed, 0 failures/errors**. Verified first import retains repeated identical rows, same-file retry creates nothing, and an extended file imports only its new row. Clone dropped; shared `namaa_ksa` unchanged.
- See [Checkpoint 335](build-engine/CHECKPOINT_335.md) and [isolated QA evidence](build-engine/KSA_BANK_CSV_IMPORT_QA.json).

# Checkpoint 374 — BE-161 live acceptance (2026-10-30)

- Native Odoo quality test **1/1** and authenticated React→BFF→Odoo browser checks **2/2** passed on isolated current-source clone.
- Owner overdue-alert drilldown and filtered register passed. Unprivileged reader and foreign-company owner did not receive the seeded record. Native postcondition confirmed current-company ownership and overdue state.
- Clone dropped, source unchanged, Odoo healthy. Evidence: [BE161_DASHBOARD_QUALITY_LIVE_QA.json](build-engine/BE161_DASHBOARD_QUALITY_LIVE_QA.json).

# Checkpoint 380 — BE-093 equipment registration DONE (2026-10-30)

- Current-source native equipment registration tests: **27/27 passed**.
- Authenticated React→BFF→Odoo live journey: **1/1 passed**; completed receipt derivation, invalid/no-write response, record reopen/audit context, unauthorized and foreign-company denials all verified.
- Focused backend route regression passed; null optional accounting asset link is omitted, explicit asset IDs are preserved.
- Disposable QA clone and temporary services removed; source unchanged; Odoo healthy. See [Checkpoint 380](build-engine/CHECKPOINT_380.md) and [live evidence](build-engine/EQUIPMENT_RECEIPT_BE093_LIVE_QA.json).

# Checkpoint 381 — BE-049 versioned project BOQ DONE (2026-10-30)

- Focused native BOQ/bridge tests: **31/31 passed**.
- Authenticated React→BFF→Odoo browser journeys: **3/3 passed**; invalid line input/no-write, actor/time/project/company reopen, same-company non-QS and foreign-company QS denials, and the Arabic RTL editor/revision comparison passed.
- Native readback confirmed the edited draft total (12 × SAR 110 = SAR 1,320), unchanged closed baseline (10 × SAR 100 = SAR 1,000), and stale-version denial without write.
- Clone, temporary BFF/Odoo services and source backup removed; source unchanged. See [Checkpoint 381](build-engine/CHECKPOINT_381.md) and [live evidence](build-engine/BOQ_DRAFT_REVISION_LIVE_QA.json).

# Checkpoint 382 — BE-152 RFQ authorization and BE-155 risk-owner notification DONE (2026-10-31)

- BE-152 native lifecycle/security suite: **4 passed**; live PM→React→BFF→Qwen→Odoo→Procurement journey: **1 passed**. Missing supplier returned a field-level 422 without persistence. Arabic draft was visibly marked pending, retained sources and uncertainty, and required independent Procurement authorization. Fresh reviewer login reopened the saved decision; exactly one linked PO remained draft and zero emails were sent. Foreign Procurement saw no source record and could not create a draft.
- BE-155 native report suite: **7 passed**; live React journeys: **2 passed**. Invalid reason returned field-specific 422 without an activity/audit write. Reopened assignment retained actor, recipient, time, project and company. Same-company read-only and foreign-company Owner/PM options/history/create probes were denied without disclosure. Odoo readback confirmed no foreign events or activities.
- Disposable clones and temporary services were removed; source database unchanged. Current totals: **50 DONE, 102 PARTIAL, 2 MISSING, 10 BLOCKED / 164 (30.5% DONE)**. See [Checkpoint 382](build-engine/CHECKPOINT_382.md), [BE-152 evidence](build-engine/PURCHASE_RFQ_AI_LIVE_QA.json), and [BE-155 evidence](build-engine/PROJECT_REPORTS_LIVE_QA.json).

# Checkpoint 383 — Offline manual and ngrok publication (2026-10-31)

- `python3 scripts/build_frontend_manual.py` regenerated the bilingual one-file guide with all 164 current statuses and acceptance criteria; output contains **330 embedded screenshots**.
- `node scripts/verify_manual.mjs` passed: **330/330** screenshots decoded offline; Arabic/English at 1440px and 390px had no horizontal overflow; zero external requests; search/filter/viewer checks passed.
- Local `/user-manual.html` returned HTTP 200 and SHA-256 matched the generated source. The public React tunnel returned HTTP 200 for the manual and demo page; `/demo.html` showed 50/164 (30.5%) and Checkpoint 382. Public manual ETag/last-modified reflect the new static file.
- Manual: [https://namaa-react-ksa.ngrok-free.app/user-manual.html](https://namaa-react-ksa.ngrok-free.app/user-manual.html). Progress: [https://namaa-react-ksa.ngrok-free.app/demo.html](https://namaa-react-ksa.ngrok-free.app/demo.html). No business database changed.
## Supplemental React project-expense capability (2026-10-31)

- React production build: passed with optional project-expense workspace included.
- Python syntax compilation: passed for the new Odoo addon model files and BFF route/contracts.
- Focused BFF contract and route tests: **12/12 passed**, covering valid payloads, invalid amount/type/IDs/date/description/extra fields, operation UUID forwarding, list bounds and native role-denial mapping. React unit suite: **96/96 passed**. These automated checks do not constitute a full native role/company acceptance matrix.
- Limitation: feature is not marked as a completed BRS story and is not considered production-ready; full expense role/company acceptance, receipt capture and reimbursement lifecycle remain open.
- Deployment: `hr_expense` and `be_project_expense` installed in `namaa_ksa` after verifying `/home/aymen/backups/namaa_ksa_pre_project_expenses_20261031.dump` as a valid PostgreSQL custom archive. SQL confirms both modules `installed`; Odoo login and backend health endpoints returned 200.
- User-authorized demo setup: created `Demo Expense Employee (Administrator)` in Namaa Saudi Arabia and linked it to admin. Odoo now reports `project_expenses=true`; options return 2 same-company projects and 6 expense categories. No expense claim was created or submitted in this setup step.
- Live React→BFF→Odoo smoke check: created and freshly reopened one labelled **SAR 10 draft-only** expense for the demo employee and project. Native readback confirms `state=draft`, 100% project analytic distribution, and no accounting move. It was not submitted or paid.
- Updated bilingual all-feature manual: **333/333** embedded screenshots decoded offline; Arabic and English passed desktop and phone overflow checks; no external requests; screenshot search, filters and viewer checks passed. The manual includes project-expense walkthrough and a screenshot of the reopened live draft-only flow. Local `:3200/user-manual.html` and `/demo.html` returned HTTP 200.

## Checkpoint 385 — BE-114 daily site reporting DONE (2026-10-31)

- Added scoped summary totals, project/date/text filters, and filtered CSV export to React daily site reports. Spreadsheet formula-leading values are escaped in the export.
- Focused React browser suite: **2/2 passed**, covering structured reporting, crew and delay summaries, text search, CSV download and offline save/reconnect.
- Current-source isolated React → BFF → Odoo Site-role journey: **1/1 passed**; native readback verified project/company, author, all structured children and exact retry behavior. Invalid changed-content retry returned 422; disposable QA records and services were cleaned up; `namaa_ksa` remained unchanged.
- Existing current-source native bridge tests verify invalid input without partial writes, immutable same-key retry, no-project/company and unauthorized-role denial. BE-114 is now DONE; offline shell/auth restore and multi-device conflict handling remain under BE-113.
- The 164-story matrix is now **51 DONE (31.1%), 101 PARTIAL, 2 MISSING, 10 BLOCKED**. This increment adds one acceptance-verified story, not a proportional score for UI volume.
- The refreshed offline bilingual manual includes the report summary/search/export screen at desktop and phone sizes: **335/335** screenshots decode offline; EN/AR desktop and mobile overflow checks pass and there are no external requests.

## Checkpoint 386 — BE-081 project financial reports DONE (2026-10-31)

- Current-source isolated React → BFF → Odoo finance-role run: **1/1 passed**; Accounting KSA report/security suite: **15 passed, 0 failed/errors**.
- Verified SAR 50 analytic allocation from the test fixture, current company identity, filtered PDF/XLSX signatures, invalid date 422, and denial/no-disclosure for a foreign-company analytic. Disposable clone and services were removed; source database unchanged.
- BE-081 is a read-only report story; report persistence/actor-event AC is N/A. Project cash flow intentionally reports analytic-attributed movement without project-owned opening/closing bank balances. Rollout sign-off is tracked separately.
- Matrix now: **52 DONE (31.7%), 100 PARTIAL, 2 MISSING, 10 BLOCKED / 164**. See [Checkpoint 386](build-engine/CHECKPOINT_386.md) and [isolated report QA](build-engine/PROJECT_CASH_FLOW_LIVE_QA.json).
# Checkpoint 388 — BE-086 restricted accounting exports (2026-10-31)

- Current-source disposable-clone Accounting KSA native suite: **16 passed, 0 failures/errors**.
- Authenticated React → BFF → Odoo accountant journey: **1/1 passed**, all ten reports queried, 10 XLSX and 10 PDF downloads validated, selected-project export reopened from immutable company-scoped history and downloaded again, Arabic history view checked.
- Export audit includes actor/company/project, dates and checksum. Native tests cover invalid-date no-write and denied foreign-company, forged-create, update and delete attempts.
- Temporary QA services and clone were removed; source database unchanged. See [Checkpoint 388](build-engine/CHECKPOINT_388.md) and [QA artifact](build-engine/ACCOUNTING_REPORTS_ACCOUNTANT_LIVE_QA.json).

# Checkpoint 389 — BE-018 CRM win-rate dashboard (2026-10-31)

- Current-source isolated CRM Sales user journey through React → BFF → Odoo: **1/1 passed**. The view rendered active-company gross/weighted pipeline and closed-outcome win rate against Odoo data.
- Current-source CRM pipeline role/security regression in the same run: native **1/1**, browser **1/1**; Sales read/write worked only in its company, and reader/foreign-company attempts were denied without lead disclosure.
- Prior two-role dashboard QA verified USD and SAR currency rendering and the Owner's 3-won/1-archived-lost result at 75%. The earlier QA clone and this run's clone were removed; source unchanged.
- BE-018's dashboard is read-only; no write validation or change audit row is expected. See [Checkpoint 389](build-engine/CHECKPOINT_389.md) and [QA](build-engine/CRM_PIPELINE_LIVE_QA.json).

## Checkpoint 400 — BE-151 project risk acceptance (2026-11-01)

- Current-source isolated Odoo native report bridge suite: **7/7 passed**.
- Authenticated React → BFF → Qwen 3.8 27B → Odoo browser journeys: **2/2 passed** (BE-151 risk report and BE-157 lessons regression); BE-155 risk-owner follow-up passed in the combined run.
- Invalid report/rationale inputs returned field-level 422 with no partial writes. A same-company reader and foreign-company Owner/PM were denied for the target-company report list and assignment/history operations without disclosure. Foreign users' own-company report list returned 200 with rows constrained to their own project/company.
- Odoo readback verified source citations, pending then independently approved risk report, risk-owner actor/time/company/project, and the linked project activity. Lessons reopen regression also passed.
- Disposable QA clone and temporary BFF/Odoo process removed; `namaa_ksa` unchanged, source Odoo healthy, original Playwright dependency symlink restored. No deployment.
- BE-151 is DONE against supplied A1–A4. See [Checkpoint 400](build-engine/CHECKPOINT_400.md), [live evidence](build-engine/PROJECT_REPORTS_LIVE_QA.json), [native tests](../addons/namaa_ai_bridge/tests/test_project_reports.py), and [browser spec](../frontend/e2e/project-risk.live.spec.js).

