Show candidate display aliases

[SoundBlaster]

Summary

• Render SpecGraph candidate display aliases in Product Workspace overview and topology.
• Link related task: Human-Friendly Candidate Aliases.

Motivation

• Operators should see readable candidate labels without losing canonical references.
• Existing artifacts without aliases must remain usable.

Goals

• Prefer display aliases in presentation while retaining canonical node ids for evidence and actions.
• Keep execution, promotion, and mutation authority unchanged.

Changes

• Project alias index, node aliases, and endpoint aliases through the Product Workspace API.
• Render aliases in Candidate Overview and topology with title-based fallback for older artifacts.

Validation

• Tests added/updated for changed behavior
• Local checks passed

Commands run:

.venv/bin/python -m pytest tests/test_idea_to_spec_workspace.py tests/test_specspace_api_v1.py -q
make test
npm test --prefix graphspace
npm run build --prefix graphspace
npm run lint:fsd --prefix graphspace
UI_PORT=5192 make ui-e2e-product-demo

Results:

• Backend suite: 970 passed.
• Frontend suite: 552 passed.
• Execution-backed Playwright product demo: 1 passed.

Risks / Notes

• Backward compatibility impact: additive optional alias fields with title/id fallback.
• Migration/config changes required: none.
• Known limitations: SpecSpace renders producer aliases and does not create or edit them.

Checklist

• PR title clearly describes the change
• Scope is focused and minimal
• Documentation updated (or N/A)
• API/artifact/UI-state changes distinguish presence from readiness/status
• Temporary or intermediate paths are scoped to the current run/task where relevant
• No secrets or sensitive data added

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 8a405fbc70

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".