# Checkpoint 279 — BE-128 live React → BFF → Odoo archive acceptance (2026-10-27)

## Verified

- An authenticated Project Manager used the real React Project archive screen against a disposable clone of `be_qa_20261026_233654_08d7` to create an archive pairing an independently approved proposal with a confirmed BOQ baseline.
- Both proposal and BOQ links were fetched through the React same-origin path and returned HTTP 200, `application/pdf`, private `no-store` headers and valid `%PDF-` signatures.
- The separate read-only user was denied archive options with HTTP 403. The Project Manager also received HTTP 403 when probing a project owned by a different company.
- Native Odoo readback verified one saved pack with the expected project, company, proposal, baseline, Project Manager actor, rationale, private attachment ownership, and matching SHA-256 checksums for both PDFs. Native authorization checks denied both the read-only role and foreign-company project.
- Browser journey: **1 passed**. The generated screenshot is [live-project-proposal-boq-archive.png](frontend/screenshots/live-project-proposal-boq-archive.png); machine-readable evidence is [PROJECT_PROPOSAL_BOQ_ARCHIVE_LIVE_QA.json](PROJECT_PROPOSAL_BOQ_ARCHIVE_LIVE_QA.json).
- The isolated QA clone and temporary BFF/image were removed. The shared `namaa_ksa` database was not modified. The isolated Odoo worker was restarted to load the current mounted addon source; it returned healthy afterward.

## Status

BE-128 remains **PARTIAL**. Live PM create/download and read-only/foreign-company denials now pass. A broader role/company matrix, Arabic PDF visual review, and the remaining full React-first A1–A4 acceptance criteria remain open. Story classifications remain **18 DONE, 123 PARTIAL, 13 MISSING, 10 BLOCKED**; DONE is the acceptance-verified count, not a weighted completion estimate.
