Possible Future Directions (out of Scope for This Audit)

Following the feedback_code_changes_as_ideas_for_future rule, three candidate paths, in increasing complexity:

1. Boost canonical framework root in the rewrite path. When a bare query (no --framework) matches a framework_aliases.synonyms entry, append the canonical framework slug to the query as an OR clause: nfc OR corenfc. This should pull the canonical framework root up. Small surgical change in the SmartQuery layer.

1. Per-source authority boost when the query matches a synonym. When the query matches a synonyms entry, give the matching framework a temporary RRF source-weight bonus. Larger change but follows the existing source-weight pattern.

1. Document synonym usage in the CLI help. The current cupertino search help doesn't mention that --framework arguments accept synonyms. If the synonyms are filter-only, this should be made discoverable so users know to type --framework nfc rather than expecting bare-query synonym routing.

None is proposed as immediate work. The baseline exists so that any future change to the synonyms mechanism is measured against this 18% top-1 baseline as the regression starting point.