[johnnyhuy]

Part of #86
Closes #112

What changed: showcase template cards no longer dump visitors on the generic /self-service list. Each card now deep-links to its own scaffolder template page via a new templateShowcaseLink helper in showcaseConfig, using the real Template entity names from examples/templates (ai-hub-service, answer-engine-worker, mcp-server, github-blank-repo, github-pull-request-docs, docs-blank-repo for GitLab Blank Repo, docs-template-gitlab-merge-request for GitLab Merge Request Docs). The Answer Engine Worker card in the answer-engine category points at the same answer-engine-worker template. Non-template cards are unchanged. No visual or styling change.

How it was verified:

• mise run install - passed
• mise run lint - passed (packages/backend 1 file, permission module 3 files, theme 1 file, plausible 8 files, packages/app 46 files, no errors)
• mise run test - passed: 3 suites passed, 1 skipped, 22 tests passed, 1 skipped (was 21 passed). New test: deep-links every template card to its real template entity. Existing tests updated for the new link shape.
• mise run dev - frontend on localhost:3000 and backend on localhost:7007 both came up. Signed in as guest, opened /showcase, and read the live link hrefs with agent-browser snapshot -i -u. All eight template links resolved to /self-service/templates/default/ as listed above, and clicking the AI Hub Service card landed directly on the AI Hub Service scaffolder form (Create a new component, AI Hub Service heading, Step 1 form). Frontend-only slice, so mise run build (Docker image) was not run.

Proof:
Capture method: agent-browser snapshot succeeded, PNG capture was blocked. The agent-browser screenshot command hung twice and was terminated, so no PNG is attached (same block as the previous run). The live snapshot hrefs are the behaviour proof:

• AI Hub Service - http://localhost:3000/self-service/templates/default/ai-hub-service
• Answer Engine Worker - http://localhost:3000/self-service/templates/default/answer-engine-worker
• MCP Server - http://localhost:3000/self-service/templates/default/mcp-server
• GitHub Blank Repo - http://localhost:3000/self-service/templates/default/github-blank-repo
• GitHub Pull Request Docs - http://localhost:3000/self-service/templates/default/github-pull-request-docs
• GitLab Blank Repo - http://localhost:3000/self-service/templates/default/docs-blank-repo
• GitLab Merge Request Docs - http://localhost:3000/self-service/templates/default/docs-template-gitlab-merge-request
• Answer Engine Worker Template - http://localhost:3000/self-service/templates/default/answer-engine-worker

Backend catalog log during the same run confirmed all seven Template entities were processed under those exact names (template:default/ai-hub-service and the rest), so the deep links target real pages, not guessed slugs.

Known gaps and follow-ups:

• The parent epic Curate plugin showcase for templates GitHub and answer engine #86 stays open.
• Noticed while the stack was up, unrelated to this slice: the catalog reports conflicting entityRefs for group:default/readers, developers, admins and user:default/guest, because default-catalog/groups.yaml and default-catalog/users.yaml already define them and the files added for the guest demo baseline in the previous slice define them again. That wants its own small slice under Release demo-ready developer portal experience #85 to pick one source.
• Johnny: no design or taste call was made here. The Gumroad-style landing page look under Ship public showcase landing page with Gumroad-style direction #84 is still yours to direct.