This protected closeout note documents the presentation-layer QA pass across protected Hub surfaces. It confirms styling, logout visibility, route-link clarity, and unified CTA language without altering auth, Supabase, SQL, schema, RLS, admin APIs, Netlify Functions, sign-in routing, role-save logic, or protected business logic.
These protected pages close the donor/DFI data-room pack by defining when a submission is stable enough to circulate, what the committee pack must contain, and how purpose-bound data-room access is governed.
The v177 pass strengthens the protected review experience. It does not introduce live automation, database writes, workflow execution, policy changes, credential changes, or new API behavior.
The portal landing route, admin pages, auth files, Supabase configuration, function code, and sign-in routing are preserved as baseline assets.
| Surface family | QA focus | Closeout posture |
|---|---|---|
| Governance | Governance shell, logout CTA, donor-readiness links, resistance-routing and evidence-traceability route clarity. | Unified Protected documentation routes use consistent institutional CTA language. |
| Exports | Donor pack links, QA checklist, submission status, database readiness visibility, and deferred live-client messaging. | Unified Documentation surfaces remain available before any live registry loading. |
| Programmes | Protected programme routes remain connected through the route registry without changing programme business logic. | Referenced Registry links preserve existing programme entry points. |
| Public Projects | Project governance surfaces are linked as protected review entry points only. | Referenced No project workflow logic changed. |
| Blue Governance | Shared Blue Governance workspace and institutional reporting route remain linked for cross-module review. | Referenced Existing Blue workspace shell remains authoritative. |
| Mining | Mining environment route remains available from the protected registry for review continuity. | Referenced No mining data or logic surfaces changed. |
| Admin | Admin surfaces are hash-preserved and excluded from presentation edits. | Preserved No admin regression introduced by v177. |
Used for protected module entry points and governance surfaces.
Used for donor-submission and export-readiness surfaces.
Used for traceability and evidence-lineage surfaces.
Used for protected validation and reviewer-readiness summaries.
The v178 additions preserve the protected shell and provide final reviewer links for donor submission and committee review.
Protected surfaces inherit the same governance spine as public surfaces, while keeping live evidence, reviewer actions, personal data, programme records, and committee packs inside role-governed protected environments.
Protected Surface QA Closeout assurance: Protected surfaces inherit the same governance spine as public surfaces while keeping live evidence, reviewer posture, access, and export controls inside protected contexts.
This workspace does not replace human authority. It makes readiness, exceptions, conditions, reviewer posture, and export posture visible so authorised users can make defensible decisions.