{
  "prompt": "Continue work on the AUTHORITATIVE LIVE Grand Project Overview application.\n\nAUTHORITATIVE INSTALLATION:\nC:\\xampp\\GrandProjectOverview\n\nAUTHORITATIVE DATABASE:\nC:\\xampp\\GrandProjectOverview\\data\\dashboard.db\n\nPUBLIC URL:\nhttps://gpo.jamie.waltons.co.nz\n\nPROJECT:\nGP-PROJ-001 \u2014 Grand Project\n\nA Special One implementation round is authorized for the first genuine remaining Asset Registry / ServiceVault gap:\nGP-ASSET-005 \u2014 Property relationships.\n\nUse 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.\n\nRules:\n- Allocate a fresh unique CMD-* source-run ID.\n- Use the permanent PowerShell Execution Standard.\n- Apply the Two-Strikes Rule.\n- Inspect canonical implementation before coding.\n- Reuse Companies & Relationships and the accepted Asset Registry ownership integration where it already provides canonical company/customer identity and validation.\n- Preserve the Asset Registry / ServiceVault authority split; do not duplicate company, property, or location master data.\n- Keep MINION-10 documentation-only.\n- Use Minions On Demand; do not automatically reuse MINION-17 unless the live evidence and ownership check prove it is safe.\n- Preserve tenant/company isolation and cross-company protection.\n- Reuse Storage/File references where relevant.\n- Run focused Grand Project tests for property relationships, ownership validation, and repository/service integration.\n- Run composer run ci if source changes occur.\n- Run git diff --check.\n- Commit the worker changes, push the worker branch, integrate the accepted work, push canonical main, and verify the remote SHA.\n- Stop after the smallest coherent property-relationship slice is complete and verified."
}