permute: search, then explain

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.

Permutation is an evidence loop that comes after reconstruction and wall classification (matcher, wall-identifier). The objective remains retail's exact structure, not the highest fuzzy spelling. Never keep generated declarations, fake locals, volatile carriers or unexplained source distortions.

Choose candidates

• Derive candidates from the build rather than a hand-kept list: complete functions below 100% whose first divergence is register/schedule.
• Exclude EH funclets and other compiler-generated code unless you are investigating them on purpose.
• Unchanged functions that dropped below a proven exact: good for replaying compiler state.
• High-scoring functions never proven exact: good for quick pattern discovery.

Run several islands and keep several distinct states