# Checkpoint 280 — BE-045 live project milestones and stakeholder obligations (2026-10-27)

## Verified

- An authenticated ordinary Project Manager used the React project plan against a disposable clone of `be_qa_20261026_233654_08d7` to enable milestones and create a stakeholder handover obligation linked to a project task and responsible person.
- React reopened the plan and showed the persisted milestone. Native readback verified the milestone's project/company, stakeholder, responsible user, linked task, obligation text, deadline and creating user.
- The linked task remained open, so the user could not mark its milestone reached. Invalid blank task input returned HTTP 422 without a partial task; unauthorized and foreign-company writes were denied.
- The existing native bridge project-plan test passed **1/1** during the isolated addon update; the authenticated live React browser journey passed **1/1**. The native bridge suite also contains milestone lifecycle/security regression coverage; it was not separately rerun during this checkpoint.
- Evidence: [structured live QA](PROJECT_PLAN_LIVE_QA.json) and [React screenshot](frontend/screenshots/live-project-plan-crew-dependencies.png).
- Disposable clone and temporary BFF/image were removed. Shared `namaa_ksa` was not changed.

## Status

BE-045 remains **PARTIAL**. The milestone and stakeholder obligation path is now live-accepted for an ordinary Project Manager, with task completion gating and project/company access checks. Broader roles and tenant boundaries, Arabic/accessibility acceptance and full React-first A1–A4 remain. Story classifications remain **18 DONE, 123 PARTIAL, 13 MISSING, 10 BLOCKED**; this checkpoint does not promote a story to DONE.
