Rental-operations-platform/docs/PHASE_10_HANDOFF_v1.0.md

Phase 10 Handoff to Phase 11

Handoff status

Phase 10 repository bootstrap and architecture are complete. Phase 11 may implement approved homepage components and sections only after the CI browser job passes and must not bypass the inherited release gates.

Authoritative inputs for Phase 11

Read in this order:

1. docs/architecture/ADR-0001_REPOSITORY_FOUNDATION.md
2. docs/PHASE_10_IMPLEMENTATION_REPORT_v1.0.md
3. docs/IMPLEMENTATION_ISSUE_REGISTER_v1.0.csv
4. docs/quality/VALIDATION_RESULTS_v1.0.md
5. contracts/phase9/09_DEVELOPER_HANDOFF_v1.0.md
6. contracts/phase9/DECISION_LOG_v9.0.md
7. contracts/phase9/DEFINITION_OF_DONE_v1.0.md
8. src/contracts/phase9/route-manifest.json
9. src/contracts/phase9/component-contracts.ts
10. src/content/locales/{en,fr,ar}

When runtime copies and immutable Phase 9 history differ only because of the approved project rename, use the runtime RentalDriveGo copy. For design, behavior, evidence, and release policy, the immutable Phase 9 package remains authoritative unless a later recorded decision supersedes it.

Required Phase 11 entry gates

Before merging homepage implementation:

• Run the full CI workflow on Node.js 24.17.0.
• Install official Playwright browsers and pass functional and accessibility suites.
• Generate and review the three initial visual baselines.
• Confirm no critical/high regression from the implementation issue register.
• Keep PUBLIC_RELEASE_APPROVED=false.

Implementation rules that may not be weakened

• Preserve server-rendered locale, lang, dir, theme, canonical, and hreflang behavior.
• Keep Arabic at document-level RTL and use logical CSS.
• Consume semantic tokens; do not add raw brand colors.
• Keep server components as the default and justify every client boundary.
• Do not add public claims, evidence, pricing, legal text, CRM behavior, analytics vendors, login destinations, or contact routes without resolving the corresponding issue.
• Do not import Phase 8 prototype source as production implementation.
• Do not disable validators to make a branch green. Fix the branch.

Phase 11 suggested sequence

1. Pass the scaffold in clean CI and commit reviewed visual baselines.
2. Build foundational primitives from the Phase 9 component contracts.
3. Add header/navigation behavior without inventing unresolved destinations.
4. Implement homepage sections in approved order using locale resources and semantic tokens.
5. Add section-level unit, accessibility, RTL, responsive, and visual checks as each section lands.
6. Keep unavailable evidence-driven modules suppressed behind explicit approved content gates.

Commands

corepack enable
corepack prepare pnpm@11.9.0 --activate
pnpm install --frozen-lockfile
pnpm check
SITE_ORIGIN=http://127.0.0.1:3000 PUBLIC_RELEASE_APPROVED=false pnpm build
pnpm test:e2e

pnpm check covers static quality and unit gates. Browser tests remain separate because they require installed browser binaries and a network environment not governed by an administrator-wide URL blocklist.

Exit condition for Phase 11

Phase 11 is not complete merely because sections render. It must preserve all Phase 10 gates, pass supported locale/theme/viewport scenarios, and leave every unresolved product or legal decision traceable rather than encoded as anonymous copy or dead links.