[EPIC-DOC-01]: 🏗️ Portal Workspace Setup & Nuxt Content/Studio Integration

## 🎯 Business Value Block
Establish the structural foundation for the Connect Platform Knowledge Hub within our monorepo. This track configures Nuxt Content to parse our markdown directories, connects the Nuxt Studio cloud production dashboard, enforces our Google Stitch structural design system design tokens, and hooks up the automated static asset generation routing to Firebase Hosting.

## 🔗 Traceability Mapping
* **RTM Feature Group Key:**

## 🏁 Concrete Tasks & Acceptance Criteria
- [ ] Scaffold Module: Initialize a decoupled /apps/docs workspace container utilizing Nuxt 4 and the @nuxt/content module.

- [ ] Studio Linkage: Generate and securely inject the STUDIO_TOKEN within the project environment variables; configure nuxt.config.ts to allow verified cloud visual editing permissions.

- [ ] Design Token Injection: Bind our layout definitions, primary color tokens, typography scales, and global header/footer parameters to the Nuxt theme configuration.

- [ ] Directory Setup: Establish the core routing architecture folders:

/content/index.md (Portal Hub Landing)

/content/why-connect/ (Executive / Vision)

/content/what-we-offer/ (Product / Capabilities)

/content/who-is-using-us/ (Ecosystem / Partners)

/content/get-started/ (Onboarding Paths)

- [ ] Deployment Configuration: Map the documentation build output to your global firebase.json deployment rules, ensuring feature branches trigger isolated, static preview channel URLs.

- [ ] Deployment Configuration: Docker deployment of Studio to CloudRun, as a separate editing site. Constrain access to IDir emails.

- [ ] Local Verification: Confirm that running the local monorepo command boots the docs development server seamlessly with fast hot-reloading active.

## 🏁 Definition of Done (Sprint Gates)
- [ ] All child `Feature` and `Task` tickets closed
- [ ] Requirements Traceability Spreadsheet updated with direct issue links
- [ ] End-to-end functionality verified in Staging/Preview
- [ ] Prepared for bi-weekly Tuesday Demo

Start by inspecting the monorepo and the planned /apps/docs workspace, then review nuxt.config.ts, firebase.json, and the listed /content paths. Verify how STUDIO_TOKEN and the Nuxt Studio permissions should be configured, and confirm the local development command. Done means the docs server runs with hot reload, content routes resolve, previews deploy through Firebase, and the Studio deployment and access constraints work in staging.

Written by the indexing model from the issue text.