Remove MVP-specific hard-coding

[mariajgrimaldi]

Description

Several parts of the authorization logic include hard-coded behaviors introduced for the Ulmo MVP. These assumptions limit the framework’s ability to support additional scopes and create inconsistent behavior across different areas of the ecosystem if we plan to scale.

This issue tracks:

• Identifying all places where authorization logic depends on hard-coded assumptions.
• Documenting how these assumptions block support for additional scopes.
• Implement the needed long-term changes to remove these hard-coded paths and unify behavior across scope types.