GET /projects/{projectId}/branches returns branch names mismatched with @id values

The branch list endpoint returns branch objects where the name field is not correctly associated with the
@id field. Names appear to be shuffled or rotated across the returned objects, such that each branch's @id
points to a different branch's name.

Steps to reproduce:

1. Create a new project (default branch is created, e.g. UUID e5d49053, name "Initial")
2. Create a new branch named "test01" from the default branch (new branch gets UUID f05c0f4d)
3. Call GET /projects/{projectId}/branches

Expected response:
[
{ "@id": "e5d49053-...", "name": "Initial", ... },
{ "@id": "f05c0f4d-...", "name": "test01", ... }
]

Actual response:
[
{ "@id": "e5d49053-...", "name": "test01", ... },
{ "@id": "f05c0f4d-...", "name": "Initial", ... }
]

The names are swapped. Creating additional branches compounds the problem — each subsequent GET /branches
call returns names in an increasingly incorrect order.

Additional observations:

• GET /projects/{projectId}/branches/{branchId} (single branch detail) always returns the correct name for
  a given @id. The bug is isolated to the list endpoint.
• The created timestamps in the list response also appear to be swapped along with the names, suggesting
  the entire branch record (except @id) is misassociated.
• The branch creation endpoint (POST /projects/{projectId}/branches) returns the correct name in its
  response.

Workaround: Fetch each branch individually via GET /projects/{projectId}/branches/{branchId} using the @id
values from the list response, then use the name from each detail response.

Environment: https://experimental.starforge.app/ — observed consistently across multiple projects and
sessions.