GPT Orchestration Build

Convert findings into working software. Own the implementation result; do not merely redistribute the list or return another plan.

Establish the build contract

1. Read repository instructions and capture the branch, dirty-path ledger, relevant diffs, manifests, and available verification commands.
2. Confirm that the user authorized implementation. Treat review-only or audit-only requests as read-only.
3. Gather all supplied findings from the conversation, reports, plans, issues, test output, and working tree.
4. Normalize them into a finding ledger with:
   • stable identifier and concise outcome;
   • evidence and affected paths;
   • confidence, severity, and user impact;
   • prerequisites and conflicts;
   • owner and write scope;
   • acceptance test;
   • final disposition.
5. Preserve pre-existing user changes. Never reset, checkout, stash, or overwrite unrelated work.