matcher: reconstruct, then compare

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.

Recover the source structure that explains retail's bytes. AGENTS.md holds:

• the authority;
• the modelling rules;
• the project adapter, with its generic verbs: build, match, diff, disasm, xref, class, gate, rules;
• the code-rules profile: dialect, naming and layout style per module, and evidence sources.

This skill is the working loop. Use the other skills for these:

• decomp-code-rules: the rules every line you write must follow, and what counts as a match.
• wall-identifier: classify a plateau.
• helper-recovery: open-coded helpers.
• permute: only a diagnosed register/schedule residue.

The goal is source a reader can understand. Identical bytes prove that the source is faithful. A match counts only when the source also passes the [match] code rules and the reader test: