feat/workspace status and onboarding flow

[Douglasymlai]

Pull Request

Related Issue

Closes #

Description

Adds a Space status rail to the Workspace tab and a dismissible onboarding path that changes for first-time vs returning users.

New users with no sessions see Show me how to use Eigent, Connect tools, and Explore use cases. Returning users get What's new about Eigent instead of the first-time prompt. Each tile can be hidden independently; dismissed tabs persist in authStore and survive reload. The first-time tile fills the composer with a guided prompt; Connect tools opens Settings → Connectors; Explore use cases opens the public use-cases page.

Once a Space has sessions or a user-bound local folder, the rail shows:

• An activity summary (sessions, tasks, automations, Space age) with a 7/30-day sparkline
• A files section grouped by Documents / Code / Data / Media / Other, plus Open folder when a local path exists

Scratch workspaces are not treated as user-bound folders, so empty Spaces stay on the empty-state copy until real work starts. The composer hides the Single Agent label at narrow widths so it doesn’t collide with the new rail.

Also extracts SpaceSnapshotStat from Space detail, adds Tag variant="text" for unpadded legends, and localizes the new copy across all layout locales.

Testing Evidence (REQUIRED)

• I have included human-verified testing evidence in this PR.
• This PR includes frontend/UI changes, and I attached screenshot(s) or screen recording(s).
• No frontend/UI changes in this PR.

Please attach screenshots of: first-time onboarding tiles, returning-user “What’s new” tile, activity + files rail on a Space with sessions, and the empty-state rail on a new Space.

Covered in unit tests:

• Guide audience (new vs existing) and dismissed-tab sanitization
• File categorization, 7/30-day activity grouping, scratch vs bound folder
• Workspace panel render, prompt fill, dismiss persistence, and composer behavior

What is the purpose of this pull request?

• Bug fix
• New Feature
• Documentation update
• Other

Contribution Guidelines Acknowledgement

• I have read and agree to the Eigent Contribution Guideline