fix(repository): sort in-memory artifact and representation results to match Postgres adapter ordering

[Copilot]

The in-memory createInMemoryRelationalWorkspaceRepository returned getPersistedArtifacts and getPersistedRepresentations in arbitrary Map insertion order, while the Postgres adapter orders by artifact_id / representation_id. This inconsistency made behavior backend-dependent and tests potentially order-sensitive.

Changes

• src/subsystems/supabase/repository.ts — Added .sort() on both getPersistedArtifacts and getPersistedRepresentations returns, ordering by artifactId / representationId via localeCompare, aligning with the Postgres adapter's ORDER BY clause.

// before
return Array.from(state.artifacts.values()).filter(
  (record) => record.workspaceId === workspaceId && record.sourceId === sourceId,
);

// after
return Array.from(state.artifacts.values())
  .filter((record) => record.workspaceId === workspaceId && record.sourceId === sourceId)
  .sort((a, b) => a.artifactId.localeCompare(b.artifactId));

---

💬 Send tasks to Copilot coding agent from Slack and Teams to turn conversations into code. Copilot posts an update in your thread when it's finished.

[Copilot]

Copilot wasn't able to review any files in this pull request.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.