fix(agent): remove alphabetical sort to preserve insertion order for primary agents

[Cretezy]

Issue for this PR

Closes #7372

Type of change

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

What does this PR do?

Removes the secondary alphabetical sort from Agent.list() so primary agents appear in insertion order (built-in first, then user-defined in config declaration order).

Previously, adding a custom "home" agent caused the TUI tab order to become "build" -> "home" -> "plan" instead of the expected "build" -> "plan" -> "home" because h < p alphabetically. Removing the [(x) => x.name, "asc"] sort criterion restores the user's intended ordering.

This PR does not add an explicit ordering field (e.g. order: number) for agents. It simply relies on declaration order in the config, which is the simpler fix and sufficient for the current use case.

How did you verify your code works?

• Inspected the source: packages/opencode/src/agent/agent.ts — list() now sorts only by default agent priority, preserving insertion order for the rest.
• Tab cycling in the TUI now follows: Build → Plan → Home.

Screenshots / recordings

N/A

Checklist

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

[github-actions]

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

Found potentially related PRs:

• feat(agent): add order field for configurable agent cycling order #19127: feat(agent): add 'order' field for configurable agent cycling order — May be related as it addresses agent ordering, though this appears to be an older approach using a configuration field rather than relying on insertion order.

• feat(agent): add order field for configurable agent cycling order #24691: feat(agent): add order field for configurable agent cycling order — Similar to feat(agent): add order field for configurable agent cycling order #19127, this proposes configurable agent cycling order, which relates to the same TUI tab ordering issue your PR fixes.

These PRs suggest there has been prior discussion about controlling agent tab order. Your PR takes a simpler approach by preserving insertion order instead of requiring explicit configuration. Verify whether these older PRs were closed/rejected in favor of the approach your PR implements.

[github-actions]

Automated PR Cleanup

Thank you for contributing to opencode.

Due to the high volume of PRs from users and AI agents, we periodically close older PRs using automated criteria so maintainers can focus review time on the most active and community-supported contributions.

This PR was closed because it matched the following cleanup criteria:

• The PR was created more than 1 month ago
• The PR had fewer than 2 positive reactions
• Positive reactions are counted as thumbs-up, heart, celebration, or rocket reactions on the PR

PRs created within the last month are not affected by this cleanup.

If you believe this PR was closed incorrectly, or if you are still actively working on it, please leave a comment explaining why it should be reopened. A maintainer can review and reopen it if appropriate.

Thanks again for taking the time to contribute.

[Cretezy]

Still a problem