You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs_build/dev/PROJECT_INSTRUCTIONS.md
+21Lines changed: 21 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -180,6 +180,27 @@ Project Workspace is the next first real Toolbox rebuild target. Its contract ow
180
180
181
181
Do not implement Project Workspace runtime behavior, persistence, database behavior, authentication, or save/load flows before the rebuild PR explicitly scopes those capabilities.
182
182
183
+
## TARGETED MSJ VALIDATION GOVERNANCE
184
+
185
+
Every tool, page, or `src/` change must declare its impacted MSJ/test lane.
186
+
187
+
Run only the affected MSJ/test lane by default.
188
+
189
+
Do not run the full suite for small scoped changes unless one of these shared surfaces changes:
190
+
- shared runtime behavior
191
+
- shared parser behavior
192
+
- shared DB behavior
193
+
- shared Theme V2 behavior
194
+
- cross-tool integration behavior
195
+
196
+
If a shared source file changes, name the affected dependent lanes and run only those targeted lanes unless the dependency impact proves broader validation is required.
No CSS, page-local CSS, inline styles, style blocks, DB, auth, cloud, persistence, or new tools were added.
39
+
40
+
## Manual Test Notes
41
+
42
+
-`?role=guest` shows the guest banner and no visible Project Data controls.
43
+
-`?role=user` shows the creator banner and no visible Project Data controls.
44
+
-`?role=admin` shows the admin banner and Project Data submenu.
45
+
- Project Data submenu contains Reset Project Data, Seed Demo Project, and Clear Test Data.
46
+
- Clicking the buttons does not mutate `localStorage` or `sessionStorage`.
47
+
- No duplicate Admin appears under Toolbox.
48
+
- No console errors were observed by the Playwright lane.
49
+
50
+
## Validation Notes
51
+
52
+
Impacted lane: `workspace-contract` through `npm run test:workspace-v2`.
53
+
54
+
Validation run:
55
+
-`npm run test:workspace-v2` passed with 4 Playwright tests.
56
+
-`git diff --check` passed.
57
+
58
+
Skipped lanes:
59
+
- runtime
60
+
- integration
61
+
- engine
62
+
- samples
63
+
- recovery/UAT
64
+
65
+
Skipped-lane rationale: this is an inert Toolbox page/header wireframe control and docs contract bundle. No shared runtime, real persistence, parser, engine, sample, or cross-tool behavior changed.
These actions are declared for upcoming Project Workspace rebuild planning only. They must not perform destructive behavior until a later implementation PR explicitly scopes the mock repository behavior.
77
+
78
+
## Implementation Guidance
79
+
80
+
Design for multi-user ownership now, but implement single-user behavior first in a later Project Workspace implementation PR.
81
+
82
+
The first implementation PR should use a mock SQL-shaped repository interface so the data shape can later map cleanly to a real SQL database.
83
+
84
+
## Validation Notes
85
+
86
+
Impacted lane: `workspace-contract` through `npm run test:workspace-v2`.
87
+
88
+
Skipped lanes:
89
+
- runtime
90
+
- integration
91
+
- engine
92
+
- samples
93
+
- recovery/UAT
94
+
95
+
Skipped-lane rationale: this bundle adds a docs contract and inert Toolbox header controls only. It does not change engine runtime, parsers, real DB behavior, samples, or cross-tool integrations.
96
+
97
+
Full suite is required when shared runtime, shared parser, shared DB, shared Theme V2, or cross-tool integration behavior changes.
The first Project Workspace implementation PR must build against the mock SQL-shaped repository contract defined in `docs_build/dev/reports/mock-db-user-project-contract.md`.
13
+
14
+
The first implementation should support single-user behavior over multi-user-ready tables:
15
+
-`users`
16
+
-`projects`
17
+
-`project_members`
18
+
19
+
The table design must preserve future multi-user ownership and membership behavior even while the first implementation behaves as a single-user Project Workspace.
20
+
21
+
## Out Of Scope For This Bundle
22
+
23
+
- No Project Workspace runtime implementation.
24
+
- No real database.
25
+
- No auth.
26
+
- No cloud sync.
27
+
- No persistence implementation.
28
+
- No save/load behavior.
29
+
- No new tools.
30
+
- No CSS changes.
31
+
32
+
## Validation Notes
33
+
34
+
Impacted lane: `workspace-contract`.
35
+
36
+
Validation run:
37
+
-`npm run test:workspace-v2` passed with 4 Playwright tests.
38
+
-`git diff --check` passed.
39
+
40
+
Skipped lanes:
41
+
- runtime
42
+
- integration
43
+
- engine
44
+
- samples
45
+
- recovery/UAT
46
+
47
+
Skipped-lane rationale: this bundle creates a contract, an inert admin-only wireframe control, governance, and tests. It does not change shared runtime, shared parser, real DB implementation, engine, samples, or cross-tool integration behavior.
Added targeted MSJ validation governance to `docs_build/dev/PROJECT_INSTRUCTIONS.md`.
6
+
7
+
Every tool, page, or `src/` change must declare its impacted MSJ/test lane.
8
+
9
+
## Rule
10
+
11
+
Run only the affected MSJ/test lane by default.
12
+
13
+
Do not run the full suite for small scoped changes unless one of these shared surfaces changes:
14
+
- shared runtime behavior
15
+
- shared parser behavior
16
+
- shared DB behavior
17
+
- shared Theme V2 behavior
18
+
- cross-tool integration behavior
19
+
20
+
If a shared source file changes, name affected dependent lanes and run only those targeted lanes unless the dependency impact proves broader validation is required.
21
+
22
+
Reports must state:
23
+
- impacted lane
24
+
- skipped lanes
25
+
- why skipped lanes were safe to skip
26
+
- when the full suite is required
27
+
28
+
## This Bundle
29
+
30
+
Impacted lane: `workspace-contract`.
31
+
32
+
Command run:
33
+
-`npm run test:workspace-v2`
34
+
35
+
Skipped lanes:
36
+
- runtime
37
+
- integration
38
+
- engine
39
+
- samples
40
+
- recovery/UAT
41
+
42
+
Skipped-lane rationale: the bundle updates Toolbox role-banner wireframe markup, its existing page script visibility wiring, governance docs, and Playwright coverage. It does not alter shared runtime, shared parser, shared DB implementation, shared Theme V2 CSS, engine behavior, samples, or cross-tool integration.
43
+
44
+
Full suite is required when shared runtime, shared parser, shared DB, shared Theme V2, or cross-tool integration behavior changes.
45
+
46
+
## Validation Notes
47
+
48
+
-`npm run test:workspace-v2` passed with 4 Playwright tests.
0 commit comments