powerapp-canvas-project-management

Use pac canvas download with --extract-to-directory to write the \src tree directly, or download the raw .msapp and unzip it with Expand-Archive since an .msapp is a zip. These are two alternatives, not a sequence. Only the \src folder is meant for source control.

Keep a build-history log with one row per paste crossing, maintained from user reports after each hand-off. A unit counts as authored until a human pastes it into Studio and confirms; if it is not in the log, it is not in the app.

Common causes are column arity mismatches on multi-value Person or Managed Metadata fields, internal names frozen at creation like Project_x0020_Manager, and choice value case mismatches. A Filter on an unlisted choice value silently returns nothing rather than erroring.

No, pac cannot author component custom properties and fails with PA3004. Component contracts must be typed by hand in Studio; only bodies can be pasted. Plan component work in three phases: properties, body, then formulas referencing child controls.

Ask whether Studio was refreshed, since a stale editor reports working code as broken. Then request a photo of code view when a token or number is in doubt, and compare reported values like Y coordinates against the source to detect stale copies.