vibe-coding-master 0.4.42 → 0.5.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -4,7 +4,7 @@
4
4
  <meta charset="UTF-8" />
5
5
  <meta name="viewport" content="width=device-width, initial-scale=1.0" />
6
6
  <title>VibeCodingMaster</title>
7
- <script type="module" crossorigin src="/assets/index-BrH67ca7.js"></script>
7
+ <script type="module" crossorigin src="/assets/index-BaDS9Ohj.js"></script>
8
8
  <link rel="stylesheet" crossorigin href="/assets/index-BM6nSKae.css">
9
9
  </head>
10
10
  <body>
package/package.json CHANGED
@@ -1,12 +1,11 @@
1
1
  {
2
2
  "name": "vibe-coding-master",
3
- "version": "0.4.42",
3
+ "version": "0.5.1",
4
4
  "description": "Local GUI session cockpit for Claude Code role sessions.",
5
5
  "type": "module",
6
6
  "files": [
7
7
  "dist",
8
8
  "dist-frontend",
9
- "docs",
10
9
  "scripts",
11
10
  "README.md"
12
11
  ],
@@ -41,7 +41,6 @@ const requiredFiles = [
41
41
  const requiredFileEntries = [
42
42
  "dist",
43
43
  "dist-frontend",
44
- "docs",
45
44
  "scripts",
46
45
  "README.md"
47
46
  ];
@@ -1 +0,0 @@
1
- # Architecture
package/docs/TESTING.md DELETED
@@ -1,82 +0,0 @@
1
- # Testing
2
-
3
- Validation strategy for `vibe-coding-master` (TypeScript/Node app). Reviewer-owned.
4
-
5
- ## Validation Levels & Commands
6
-
7
- | Level | Scope | Command |
8
- | --- | --- | --- |
9
- | L0 | format / typecheck | `npm run typecheck` (`tsc -p tsconfig.json --noEmit && tsc -p tsconfig.node.json --noEmit`) |
10
- | L1/L2 | unit + module/integration tests | `npm run test` (vitest, runs `tests/unit/**` and `tests/integration/**`) |
11
- | L3 | smoke / E2E (browser) | `npm run e2e` (Playwright) |
12
- | L4 | full regression / release | `npm run prepack` (build + `verify:package`) + full `npm run test` + `npm run e2e` |
13
-
14
- Targeted run: `npx vitest run <path/to/test.ts>`.
15
-
16
- ### Test environment note
17
-
18
- `vitest.config.ts` runs in `environment: "node"` (no jsdom). Frontend tests are
19
- therefore either pure-helper tests or component tests rendered with
20
- `react-dom/server` `renderToStaticMarkup` (static HTML assertions), not DOM/event
21
- tests. Component modules that load browser globals at import time (e.g. the
22
- xterm-backed `terminal/xterm-view`) must be stubbed with `vi.mock` before the
23
- component under test is imported.
24
-
25
- ## Required prerequisite: build before full `npm run test`
26
-
27
- `tests/unit/backend/harness-templates-sync.test.ts` spawns the real harness
28
- installer (`scripts/install-vcm-harness.mjs`), which runs the compiled CLI at
29
- `dist/backend/cli/install-vcm-harness.js`, falling back to the TypeScript source
30
- only when the `tsx` binary is present. In a clean checkout with no `dist/` and no
31
- `node_modules/.bin/tsx`, the installer exits with
32
- `compiled CLI not found. Run npm run build first.` and this single test fails.
33
-
34
- **Run `npm run build` before a full `npm run test`** (or before final acceptance).
35
- All other unit tests run without a build. This is a documented prerequisite, not a
36
- product defect or known issue.
37
-
38
- ## Final-validation cleanup
39
-
40
- `npm run build` first runs `npm run clean` (`scripts/clean-build.mjs`), removing
41
- `dist/` and `dist-frontend/`. Final acceptance therefore runs from a clean state via:
42
-
43
- ```
44
- npm run build && npm run test
45
- ```
46
-
47
- Do not treat any pre-cleanup test result as final acceptance evidence.
48
-
49
- ## Harness "Fixed install" three-state UI cases
50
-
51
- Backend derivation — `tests/unit/backend/harness-service.test.ts`:
52
-
53
- | ID | Scenario | Proves |
54
- | --- | --- | --- |
55
- | B1 | fresh repo, all harness files missing | `initialized === false`, `needsApply === true` |
56
- | B2 | after `applyHarness` | `initialized === true`, `needsApply === false` |
57
- | B3 | pre-existing non-VCM `CLAUDE.md` (action `insert`) | `initialized === false` |
58
- | B4 | pre-existing `.claude/settings.json` without VCM hooks (action `update`) | `initialized === false` |
59
- | B5 | drifted managed block (version 0) | `initialized === true`, `needsApply === true` |
60
-
61
- Frontend render — `tests/unit/frontend/harness-panel.test.ts`
62
- (entry: `HarnessPanel`, rendered via `renderToStaticMarkup`, `xterm-view` mocked):
63
-
64
- | ID | State | Entry / input | Key assertions |
65
- | --- | --- | --- | --- |
66
- | F1 | A — not initialized | `initialized:false, needsApply:true` | subtitle "Not initialized"; only `Initialize` button; no Refresh/Update; no "Files to update" list |
67
- | F2 | B — has updates | `initialized:true, needsApply:true, plannedChanges:[..]` | subtitle "N pending updates"; "Files to update" list with paths; `Update` + `Refresh`; no `Initialize` |
68
- | F3 | C — up to date | `initialized:true, needsApply:false` | subtitle "Up to date"; `Refresh` only; no `Update`/`Initialize`; no list |
69
- | F4 | busy | each state with `busy:true` | every fixed-install action button rendered `disabled` |
70
-
71
- Run: `npx vitest run tests/unit/backend/harness-service.test.ts tests/unit/frontend/harness-panel.test.ts`.
72
-
73
- ## Known testing gaps
74
-
75
- - No DOM/interaction (click) tests for the frontend: the node test environment uses
76
- static-markup rendering, so button `onClick` wiring is verified by code review and
77
- by the backend status-reload behavior, not by simulated events. A jsdom +
78
- `@testing-library/react` setup would be needed for true interaction coverage and is
79
- not currently configured.
80
- - No L3 Playwright smoke was run for this task (UI conditional-rendering change with
81
- full backend + frontend unit coverage). Reserve E2E for release-level or
82
- cross-cutting flow changes.