Continue work on the AUTHORITATIVE LIVE Grand Project Overview application.

AUTHORITATIVE INSTALLATION:
C:\xampp\GrandProjectOverview

AUTHORITATIVE DATABASE:
C:\xampp\GrandProjectOverview\data\dashboard.db

PUBLIC URL:
https://gpo.jamie.waltons.co.nz

PROJECT:
GP-PROJ-001 — Grand Project

A Special One implementation round is authorized for the first genuine remaining Asset Registry / ServiceVault gap:
GP-ASSET-005 — Property relationships.

Use live GPO only as the authority. Verify canonical main first. Reuse the canonical Companies & Relationships model and the accepted Asset Registry company/customer ownership integration; do not create a duplicate property/location model. Inspect the canonical Asset Registry foundation evidence, the historical MINION-17 Asset Registry company/customer ownership integration, and the ServiceVault property/location bridge evidence before coding. Implement only the smallest coherent property-relationship slice that is genuinely missing, with validated property/location distinction, tenant/company protection, and focused tests. Do not broaden into GP-ASSET-006, GP-ASSET-007, or unrelated ServiceVault workflows.

Rules:
- Allocate a fresh unique CMD-* source-run ID.
- Use the permanent PowerShell Execution Standard.
- Apply the Two-Strikes Rule.
- Inspect canonical implementation before coding.
- Reuse Companies & Relationships and the accepted Asset Registry ownership integration where it already provides canonical company/customer identity and validation.
- Preserve the Asset Registry / ServiceVault authority split; do not duplicate company, property, or location master data.
- Keep MINION-10 documentation-only.
- Use Minions On Demand; do not automatically reuse MINION-17 unless the live evidence and ownership check prove it is safe.
- Preserve tenant/company isolation and cross-company protection.
- Reuse Storage/File references where relevant.
- Run focused Grand Project tests for property relationships, ownership validation, and repository/service integration.
- Run composer run ci if source changes occur.
- Run git diff --check.
- Commit the worker changes, push the worker branch, integrate the accepted work, push canonical main, and verify the remote SHA.
- Stop after the smallest coherent property-relationship slice is complete and verified.