fix(tui): autocomplete files inside references

[jomarescudero]

Issue for this PR

Closes #34040

Type of change

• Bug fix
• New feature
• Refactor / code improvement
• Documentation

What does this PR do?

Fixes TUI @ reference autocomplete so @alias/partial searches inside the configured reference directory and inserts the selected file as @alias/relative.

Previously, autocomplete matched the reference alias but did not continue file lookup for nested paths.

Related: #33658

How did you verify your code works?

Verified with the focused autocomplete behavior for configured reference paths.

Screenshots / recordings

N/A. This changes autocomplete behavior, not visual layout.

Checklist

• I have tested my changes locally
• I have not included unrelated changes in this PR

[github-actions]

Thanks for your contribution!

This PR doesn't have a linked issue. All PRs must reference an existing issue.

Please:

1. Open an issue describing the bug/feature (if one doesn't exist)
2. Add Fixes #<number> or Closes #<number> to this PR description

See CONTRIBUTING.md for details.

[github-actions]

The following comment was made by an LLM, it may be inaccurate:

Based on my search, I found a potentially related PR:

Related PR:

• fix(tui): search files inside references #33658 - fix(tui): search files inside references
  • This PR is closely related as it also addresses file search functionality within TUI references, which is likely a companion or prerequisite feature to the autocomplete functionality in PR fix(tui): autocomplete files inside references #34037.

No other duplicate PRs found. The current PR (#34037) appears to be addressing a specific gap in autocomplete functionality for nested paths within configured references.

[github-actions]

Thanks for updating your PR! It now meets our contributing guidelines. 👍

[jomarescudero]

Thanks for the report and por pointing me to the issue/PR template.

I found that my previous version missed an edge case in directory navigation after selecting a folder. I pushed an update to this same PR that fixes the behavior and verified it with the affected autocomplete flow.

Sorry for the extra noise. I'll keep the linked issue open until you confirm the updated PR covers the expected behavior.