[johnnyhuy]

The showcase now labels built-in catalog and TechDocs search separately from the answer-engine extension template, and states the services needed for generated answers. The landing hero and its refreshed portal screenshot use the same accurate capability wording.

Part of #86
Part of #85
Closes #123

Verified after rebasing onto the Backstage 1.56.5 upgrade on main

• mise run install passed, with existing peer warnings and no lockfile changes.
• mise run lint passed across all five packages.
• mise run test -- --runInBand --verbose passed 38 tests in six suites, with one existing skipped test in one skipped suite.
• BROWSER=none mise run dev compiled successfully and served the changed showcase and landing page. Playwright clicked Guest > Enter, selected Answer Engine and captured both availability labels and the complete landing page.
• git diff --check passed.
• No backend or packaging changes. The Docker build is covered by the PR's Build workflow.

Behaviour proof from the test output

ShowcasePage
  ✓ distinguishes live keyword search from the answer-engine extension (277 ms)

Test Suites: 1 skipped, 6 passed, 6 of 7 total
Tests:       1 skipped, 38 passed, 39 total

That test verifies the availability labels, demo disclaimer, search link and worker-template destination. The landing regression checks the catalog/docs search promise.

Browser proof from this worktree

Capture method (a) succeeded. Existing servers occupied ports 3000/7007 and 3001, so gitignored local overrides used 3301/7301. Disabling automatic browser opening avoided a macOS AppleScript startup hang. The full landing capture uses a 1440 by 2160 viewport so Backstage's internal scroll container includes the footer. Screenshots are committed under .tmp/proof/; packages/app/public/portal-showcase.png is also refreshed from the running page.

Existing React/MUI deprecation warnings, the signals WebSocket 404 and unavailable TechDocs search indexes were observed during preview. This slice clarifies capability presentation; it does not implement answer generation or change indexing. The parent epics remain open.

The final-head Build workflow passed mise run install, mise run lint, mise run test and mise run build on 629ba9a. CodeQL and both Socket Security checks also passed. This supplies Docker build verification despite the unavailable local daemon.