orchestrator: run the workers, merge the results

Project guide: the repository's AGENTS.md. If the repository has none, use AGENTS-template.md and ask the user to fill in its project adapter.

You plan lanes, launch workers, relay rulings and merge. Workers do the matching, guided by:

• AGENTS.md;
• the matcher and helper-recovery skills;
• decomp-code-rules.

Use wall-identifier when a function is stuck, when triaging plateaus, or when asked "why won't this match".

What the campaign produces is readable source. The headline number is matched under the rules: functions whose bytes match and that pass every [match] rule. Bytes-matched is the second number. Report both, every time. MATCH-PENDING functions (exact but failing a rule, usually a fakematch) are open work, not progress.