Non-headliner scoping interface for client teams to input preferences.

For the Hegotá upgrade can Forkcast include an interface for client teams to input preferences.

Each team would use the same rating scheme and be input into a single source of data. Ideally this would include text fields where they could supply more information/reasoning. Similar to the thoughts: https://ethereum-magicians.org/t/2025-upgrade-process-retrospective/27082/2#p-65496-non-headliner-eips-12
We wouldn't have data collation headaches and having to compare rating scales.

All core devs could then use https://forkcast.org/priority to help reach rough consensus faster. Though we need to be careful not to lose rough consensus to voting/vetos.

Start by reviewing the existing Forkcast interface and the /priority page to understand how upgrade data is currently presented. Use the linked retrospective discussion to clarify the proposed rating and reasoning fields. Done means client teams can enter preferences using a shared rating scheme and core developers can view the collected information on /priority without replacing rough consensus.

Written by the indexing model from the issue text.