Missing version in the UI

[CameronVetter]

I just updated to the last release, I wanted to verify that my update was successful after my container restarted, but realized there is no place in the UI to see what version is running.

[emmanueldaien-cloud]

@/tmp/tmp.xx3njG6FW0

[emmanueldaien-cloud]

ClawSweeper status: review started.

I am starting a fresh review of this issue: Missing version in the UI This is item 1/1 in the current shard. Shard 0/1.

This placeholder means the worker is alive and reading the current context. I will edit this same comment with the actual review when the claws are done clicking.

Crustacean status: shell secured, claws on keyboard, evidence pebbles being sorted.

[emmanueldaien-cloud]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Summary
Current main still does not expose the running app version in the checked UI shell, and the only directly related implementation attempt was closed because it mixed this small UI request with unrelated changes and an unsafe client-side package.json import. This remains a valid narrow feature request for maintainers to land separately.

Reproducibility: not applicable. this is a feature request, and source inspection shows the current UI shell does not render the app version even though the repository metadata contains it.

Next step
A focused follow-up PR can implement the user-visible version badge without reopening the scope and security problems that caused PR #76 to be closed.

Review details

Best possible solution:

Add a small read-only version badge in the shared workspace header or another always-visible operator surface, sourcing the value from a build-time env/version constant rather than importing package.json into client code.

Do we have a high-confidence way to reproduce the issue?

Not applicable: this is a feature request, and source inspection shows the current UI shell does not render the app version even though the repository metadata contains it.

Is this the best way to solve the issue?

Yes: a small UI-only badge sourced from a build-time version constant is the narrowest maintainable solution. The prior attempt shows the maintainers do not want unrelated UI/backend changes or a client-side package.json import mixed into this fix.

Acceptance criteria:

• npm run build
• Verify the main Workspaces page shows the same version as package.json/release metadata
• Confirm no unrelated UI behavior, API routes, or task status logic changed

What I checked:

• Package version exists but is only in project metadata: package.json on current main declares version 2.5.1, so the release value exists in source but is not surfaced by itself to operators. (package.json:3, 481cf1279e63)
• Current Workspaces header has no version badge: src/components/WorkspaceDashboard.tsx renders the main Mission Control header with the Activity Dashboard and New Workspace controls, but no version string or version fetch. (src/components/WorkspaceDashboard.tsx:36, 7416cf57ed6f)
• Other visible shell surfaces also omit version output: src/app/layout.tsx only wraps the app with DemoBanner, ToastProvider, and ChatProvider, and src/app/settings/page.tsx renders settings controls without any app-version display. (src/app/layout.tsx:13, 5303d7459316)
• A prior PR already targeted this request but was rejected for scope and implementation choice: Closed PR feat(ui): show app version badge on Workspaces header #76 proposed a workspace header version badge, but maintainer review said the branch bundled unrelated UI/backend changes and explicitly asked for a narrow version-only follow-up that avoids client-side import pkg from '../../package.json'. (src/components/WorkspaceDashboard.tsx:1, 1bcf48b88380)
• Current header surface likely comes from merged PR history: Merged PR feat: dedicated Agent Activity dashboard + mobile card UX polish #48 added the current Activity Dashboard entry point and mobile polish on the workspace dashboard, which makes that file the most likely place for a future version badge. (src/components/WorkspaceDashboard.tsx:1, 46c3e6b1d1e7)

Likely related people:

• pkgaiassistant-droid: Merged PR feat: dedicated Agent Activity dashboard + mobile card UX polish #48 added the current WorkspaceDashboard header structure and adjacent UX on the same file this request would likely touch. (role: introduced the current workspace dashboard header surface; confidence: high; commits: 46c3e6b1d1e7; files: src/components/WorkspaceDashboard.tsx)
• crshdn: Cut the current v2.5.1 release commit touching version metadata and left the blocking review on PR feat(ui): show app version badge on Workspaces header #76 asking for a narrower, safer implementation of this exact UI request. (role: recent maintainer and reviewer for the exact feature area; confidence: high; commits: 14344f92975a; files: package.json, README.md)
• Charlie: Authored an earlier version-bump commit that updated package.json and README release metadata, which is adjacent to exposing the runtime version in the UI. (role: earlier release/version maintainer; confidence: medium; commits: 589cc34a69c8; files: package.json, README.md)

Remaining risk / open question:

• The issue does not specify whether the version should appear only on the Workspaces page or on additional surfaces like Settings, though either placement would likely satisfy the operator need.

Codex review notes: model gpt-5.4, reasoning medium; reviewed against 14344f92975a.