TNQ-4 P1: Frontend shell hardcodes first-party extension IDs in ActivityStream, markdown, useProjectCounts

[rawkode]

Finding

TNQ-4 confirmed findings (multiple):

1. ActivityStream (frontend/src/components/ActivityStream.vue) hardcodes specific extension event types (dev.comtrya.issues.*, dev.comtrya.pull-request.*, dev.comtrya.epic.*, etc.) and constructs navigation hrefs like /r/{workspace}/{repo}/issues/{number} — duplicating extension-owned route contracts in the shell.

2. useProjectCounts (frontend/packages/sdk-vue/src/use-project-counts.ts) hardcodes ext_issues and ext_epics op names and specific event topics to maintain per-project count state. This is extension business logic in the generic SDK.

3. Markdown renderer (frontend/packages/sdk-vue/src/markdown.ts) hardcodes /x/issues/{workspaceId}/{N} route inside the generic shell markdown renderer, coupling a kernel-generic component to ext_issues' URL shape.

Impact

P1 — wit-contract violation. Adding a new issue-like extension requires editing the shell. Renaming ext_issues routes breaks ActivityStream and the markdown cross-reference links silently. Conflicts with the SP6 goal that extensions are the single source of truth for their own surfaces.

Fix

• Extension event manifests should declare a displayName, icon, and a routeTemplate (/r/{workspace}/{repo}/issues/{number}) so ActivityStream can drive navigation generically from the event data.
• useProjectCounts should drive counts from extension-declared WIT ops via a manifest-based subscription, not hardcoded strings.
• Markdown issue-link resolution should go through an extension-provided resolver, not a shell-embedded URL pattern.

These are design-level changes; the fix belongs in the SP6 / codegen phase. For now, file as a known architectural debt item.

Files

• frontend/src/components/ActivityStream.vue
• frontend/packages/sdk-vue/src/use-project-counts.ts
• frontend/packages/sdk-vue/src/markdown.ts

Related

• SP6: rebuild Apollo Federation v2 (v3 north star) #203 (SP6 — federated GraphQL, which resolves the extension-owned routing)
• [P2][server/maintainability] main.rs is a 10,776-line god-file mixing routing, handlers, auth, git, CUE, storage and tests #86 (god-file), [P2][frontend/wit-contract] use-project-counts hardcodes specific extensions, op names, event topics, and re-implements backend state-bucketing in the generic SDK #119 (use-project-counts)

Priority

P1 — wit-contract violation; blocks extension ecosystem expansion

[rawkode]

Status update: Still open. ActivityStream, markdown renderer, and use-project-counts all hardcode first-party extension IDs. This is architectural debt that dissolves when SP6 (federated GraphQL #203) allows extensions to declare their own event types and route templates. Until then it stays acknowledged debt rather than a blocking fix.