Testcraft Studio frontend 08: OFFICE_SETUP.md

# Testcraft Studio - office setup

1. Extract `Testcraft_Studio_Office.zip` to a normal folder.
2. Ensure Node.js is installed.
3. Open PowerShell in that folder and run:

```powershell
node serve.cjs
```

4. Open http://127.0.0.1:5175/ and keep the terminal open.
5. Select MCM and enter the system password. Public sample values are `team-demo` for User access and `admin-demo` for Administrator access.

The prebuilt presentation requires no npm installation or internet connection. Stop it with Ctrl+C. If the port is in use, run `node serve.cjs 5176` and open http://127.0.0.1:5176/.

Start with a workspace, create its System Baseline using at least one document, and submit it for Administrator approval. Baseline document additions/removals also require approval. Then add source-linked requirements. In Workspace chat, ask document questions, request Technical / Functional / Business test cases, and use follow-up messages to refine the draft. Open supporting sources, save the draft to Test suites, or export CSV. Choose a template or upload Excel before generating to use its columns. Answering clarifications is optional.

For source development, run `npm.cmd ci`, then `npm.cmd run dev`. Rebuild with `npm.cmd run build` and check with `npm.cmd test`. Use Node.js 20.19+ in the 20.x release line or Node.js 22.12+.

To consolidate CR changes, apply the CR selection in Knowledge versions and choose **Merge CRs into baseline**. Name the new baseline and submit it. An Administrator reviews the changes in Baseline approvals and selects **Approve CR merge**. Approval creates a new version containing those changes; the previous baseline and unchanged knowledge remain available.

This is a frontend using browser-local storage and local evidence lookup. The chat interaction and structured test-case drafts are ready for review; a real LLM connection, backend authentication, document extraction, agents, and server-side approval enforcement are deferred. Uploaded documents and conversations stay in the browser where they were created and are not included in this ZIP. The included screen PDF documents the earlier walkthrough; the chat changes are available in the application.