fix(init): preserve protocol selection order from server (BLO-802)

[Copilot]

Protocol choices in substreams init displayed in random order due to Go map iteration having undefined ordering. The server sends generators sorted by weight, but this ordering was lost during client-side grouping.

Changes

cmd/substreams/init.go

• Track protocol group insertion order using a protocolOrder slice alongside the grouping map
• Iterate over the slice instead of the map when building UI options

// Before: random order due to map iteration
for _, value := range filteredProtocols {
    protocolOptions = append(protocolOptions, ...)
}

// After: preserves server order
var protocolOrder []string
for _, gen := range resp.Msg.Generators {
    if !groupExists {
        protocolOrder = append(protocolOrder, gen.Group)
        // ... 
    }
}
for _, group := range protocolOrder {
    value := filteredProtocols[group]
    protocolOptions = append(protocolOptions, ...)
}

cmd/substreams/init_test.go (new)

• Unit test verifying protocol and generator order preservation

---

💬 We'd love your input! Share your thoughts on Copilot coding agent in our 2 minute survey.

[maoueh]

@copilot The plan was to fix all choices related ordering and not just the root generator list.

Here a sub questions exhibiting the same problem:

# run 1
┃ Chosen protocol:  EVM - EVM
┃ Choose the type of project that you want to create.
┃ > evm-hello-world      - Creates a Substreams that extracts USDC log data from blocks
┃   evm-events-calls-raw - (without ABI) Get raw Ethereum events/calls and create a Substreams as source
┃   evm-events-calls     - (with ABI) Decode Ethereum events/calls using an ABI and create a Substreams as source

# run 2
┃ Chosen protocol:  EVM - EVM
┃ Choose the type of project that you want to create.
┃ > evm-hello-world      - Creates a Substreams that extracts USDC log data from blocks
┃   evm-events-calls     - (with ABI) Decode Ethereum events/calls using an ABI and create a Substreams as source
┃   evm-events-calls-raw - (without ABI) Get raw Ethereum events/calls and create a Substreams as source

You need to fix the bug globally for any other choices

[Copilot]

@copilot The plan was to fix all choices related ordering and not just the root generator list.

Here a sub questions exhibiting the same problem:
...

I see the generator ordering issue you're showing. I've reviewed the code and the generator list is built by iterating selector.Generators which is populated in order from resp.Msg.Generators (lines 251-267).

Could you clarify which specific "sub questions" or other choice presentations you're seeing ordering issues with? Are you seeing:

1. Different generator orders when selecting the same protocol between runs (as shown)?
2. Other list selections later in the conversation flow that show ordering issues?
3. Both?

This will help me identify if there's another map iteration we need to fix, or if the issue might be server-side (e.g., server sending generators in different orders).

[maoueh]

@copilot Ok the other ordering bug was on the server, let merge this one and I will spawn you to fix the sever.