Skip to content

Commit 9955272

Browse files
ToolboxAidToolboxAid
committed
Capture SSoT ideas and delete obsolete branch - PR_26159_047-capture-ssot-notes-delete-branch
1 parent ed28e3a commit 9955272

5 files changed

Lines changed: 299 additions & 2 deletions

File tree

‎docs_build/dev/admin-notes/PS_commands.txt‎

Lines changed: 7 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -1,4 +1,9 @@
11

2-
- Remove-Item .\directory-name -Recurse -Force
2+
- Start server:
3+
npm run dev:local-api
34

4-
- tree /f
5+
- Delete directory recursivly
6+
Remove-Item .\directory-name -Recurse -Force
7+
8+
- display directory, subdirectories and files
9+
tree /f

docs_build/dev/admin-notes/edit_input.txt renamed to docs_build/dev/admin-notes/engine/edit_input.txt

File renamed without changes.

‎docs_build/dev/admin-notes/index.txt‎

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -1,3 +1,4 @@
1+
12
[.] Start the server
23
npm run dev:local-api
34

‎docs_build/dev/reports/ssot_branch_delete_report.md‎

Lines changed: 67 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,67 @@
1+
# SSoT Branch Delete Report
2+
3+
PR: PR_26159_047-capture-ssot-notes-delete-branch
4+
Generated: 2026-06-08
5+
Runtime behavior changed: No
6+
Playwright impacted: No
7+
8+
## Branch Guard
9+
10+
| Check | Status | Evidence |
11+
| --- | --- | --- |
12+
| Read `docs_build/dev/PROJECT_INSTRUCTIONS.md` first. | PASS | Project instructions were read before deleting the branch. |
13+
| Current branch is `main`. | PASS | `git branch --show-current` returned `main`. |
14+
| Worktree was clean before execution. | PASS | `git status --short` returned no modified or untracked files before this PR's report files were created. |
15+
16+
## Branch Deleted
17+
18+
| Branch | Status | Evidence |
19+
| --- | --- | --- |
20+
| `PR_26151_004-gamefoundry-site-structure-ssot` | PASS | `git push origin --delete PR_26151_004-gamefoundry-site-structure-ssot` deleted the remote branch. |
21+
22+
## Validation Evidence
23+
24+
### Local Branch Query
25+
26+
```text
27+
git branch --list "PR_26151_004-gamefoundry-site-structure-ssot"
28+
(no output)
29+
```
30+
31+
### Remote-Tracking Branch Query
32+
33+
```text
34+
git branch -r --list "origin/PR_26151_004-gamefoundry-site-structure-ssot"
35+
(no output)
36+
```
37+
38+
### Remote Head Query
39+
40+
```text
41+
git ls-remote --heads origin PR_26151_004-gamefoundry-site-structure-ssot
42+
(no output)
43+
```
44+
45+
## Commands Run
46+
47+
```text
48+
git fetch origin
49+
git push origin --delete PR_26151_004-gamefoundry-site-structure-ssot
50+
git fetch --prune origin
51+
git branch --list "PR_26151_004-gamefoundry-site-structure-ssot"
52+
git branch -r --list "origin/PR_26151_004-gamefoundry-site-structure-ssot"
53+
git ls-remote --heads origin PR_26151_004-gamefoundry-site-structure-ssot
54+
```
55+
56+
## Validation Checklist
57+
58+
| Requirement | Status | Evidence |
59+
| --- | --- | --- |
60+
| Validate SSoT notes report exists. | PASS | `docs_build/dev/reports/ssot_ideas_captured.md` exists. |
61+
| Validate SSoT branch is deleted locally. | PASS | Local branch query returned no output. |
62+
| Validate SSoT branch is deleted remotely. | PASS | Remote-tracking and remote head queries returned no output. |
63+
| Do not merge old code. | PASS | No merge command was run. |
64+
| Do not cherry-pick old code. | PASS | No cherry-pick command was run. |
65+
| Do not copy old CSS/partials/JS. | PASS | Only concept/report files were created. |
66+
| Playwright impacted: No. | PASS | Report and branch cleanup only. |
67+
| Do not run full samples validation. | PASS | Skipped because no runtime/sample behavior changed. |

‎docs_build/dev/reports/ssot_ideas_captured.md‎

Lines changed: 224 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,224 @@
1+
# SSoT Ideas Captured
2+
3+
PR: PR_26159_047-capture-ssot-notes-delete-branch
4+
Generated: 2026-06-08
5+
Source branch: `origin/PR_26151_004-gamefoundry-site-structure-ssot`
6+
Source head before deletion: `0aee05215`
7+
Runtime behavior changed: No
8+
Playwright impacted: No
9+
10+
## Scope
11+
12+
This report captures useful product and IA ideas from the old SSoT branch before deletion. It intentionally does not merge, cherry-pick, or copy old implementation code.
13+
14+
Do not reuse from the old branch:
15+
16+
- `GameFoundryStudio/assets/css/*`
17+
- `GameFoundryStudio/assets/partials/*`
18+
- `GameFoundryStudio/assets/js/gamefoundry-partials.js`
19+
- old `GameFoundryStudio/` path structure as an implementation location
20+
- old `docs/dev/*` workflow artifacts
21+
22+
Future implementation should rebuild surviving ideas through current root paths, Theme V2, current header/session behavior, current toolbox registry/data contracts, and current `docs_build/dev/reports/*` workflow.
23+
24+
## Branch Context
25+
26+
- Behind main before deletion: 339
27+
- Ahead of main before deletion: 39
28+
- Unique changed files before deletion: 38
29+
- Main difference: old standalone `GameFoundryStudio/` page tree and old CSS/partial structure versus current root pages plus `assets/theme-v2`.
30+
31+
## Public Destinations
32+
33+
### Cloud
34+
35+
Useful idea to preserve:
36+
37+
- Treat Cloud as a first-class public destination for project storage, sync, version management, and release support.
38+
- Position Cloud as the bridge between local tools and connected creator workflows.
39+
- Possible future page goals:
40+
- show saved projects and assets
41+
- show sync/storage status
42+
- explain Local Mem / Local DB / future hosted storage boundaries
43+
- link to publishing readiness when deploy work begins
44+
45+
Modern rebuild note:
46+
47+
- Rebuild as a Theme V2 root page if Cloud becomes current product scope.
48+
- Do not reuse old `GameFoundryStudio/cloud/index.html` or old CSS.
49+
50+
### Publish
51+
52+
Useful idea to preserve:
53+
54+
- Treat Publish as the creator path from project to playable public page.
55+
- Preserve the product concept of release versions, previews, metadata, readiness checks, analytics, rollback safety, and Arcade handoff.
56+
- Possible future page goals:
57+
- publish candidate checklist
58+
- manifest validation gate
59+
- asset readiness gate
60+
- debug/release mode gate
61+
- public play URL readiness
62+
63+
Modern rebuild note:
64+
65+
- Rebuild only after publish/deploy data contracts are scoped.
66+
- Align with `docs_build/dev/reports/game-deploy-path-plan-report.md` rather than the old static page.
67+
68+
### Docs
69+
70+
Useful idea to preserve:
71+
72+
- Treat Docs as a public/creator-facing learning destination for manifests, tools, validation rules, publishing, and platform architecture.
73+
- Suggested content buckets:
74+
- Manifest Guide
75+
- Tool Guides
76+
- Publishing Rules
77+
- Validation Rules
78+
79+
Modern rebuild note:
80+
81+
- Rebuild as current documentation IA if product docs become in-scope.
82+
- Keep dev/admin docs under `docs_build/dev/`; keep public docs separate from internal reports.
83+
84+
## Tool Builder / Tool Creator / Tool Publisher
85+
86+
### Tool Builder
87+
88+
Useful idea to preserve:
89+
90+
- A first-class tool-planning surface for building new tools or tool layouts.
91+
- Old branch concept used left/center/right regions and accordion panels.
92+
- Possible modern interpretation:
93+
- tool template checklist
94+
- required file scaffold checklist
95+
- Theme V2 compliance checklist
96+
- toolbox registration checklist
97+
98+
Modern rebuild note:
99+
100+
- Rebuild only through current first-class tool rules and `toolbox/_tool_template-v2` patterns.
101+
- Do not copy the old one-file HTML layout.
102+
103+
### Tool Creator
104+
105+
Useful idea to preserve:
106+
107+
- A guided creator/editor surface for defining tool behavior and user-facing workflow.
108+
- Possible modern interpretation:
109+
- tool purpose
110+
- input/setup panel plan
111+
- center work-surface plan
112+
- right diagnostics/status plan
113+
- validation lane plan
114+
115+
Modern rebuild note:
116+
117+
- Rebuild as a new small PR only after the intended data source and registry contract are clear.
118+
119+
### Tool Publisher
120+
121+
Useful idea to preserve:
122+
123+
- A publishing/readiness surface for promoting a tool from concept to available Toolbox entry.
124+
- Possible modern interpretation:
125+
- readiness status
126+
- required tests
127+
- registry visibility
128+
- screenshots/docs
129+
- role/access notes
130+
131+
Modern rebuild note:
132+
133+
- Rebuild around current toolbox metadata/status model, not static old pages.
134+
135+
## Tool Group Landing Page Concepts
136+
137+
Useful group concepts to preserve as IA:
138+
139+
- Building / Creation
140+
- Technology / System
141+
- Assets / Content
142+
- Media / Community
143+
- Design / Animation
144+
- Configuration / Admin
145+
146+
Useful pattern:
147+
148+
- Each group page explains the group purpose.
149+
- Each group links to related tools and destinations.
150+
- Group pages can help users browse by workflow rather than by tool name alone.
151+
152+
Modern rebuild note:
153+
154+
- Rebuild group pages from current toolbox registry/category data.
155+
- Avoid static duplicated lists.
156+
- Do not copy old group HTML or old meaning color CSS.
157+
- Respect current Admin/My Stuff and role-aware navigation rules.
158+
159+
## Account Branding / Controls
160+
161+
### Branding
162+
163+
Useful idea to preserve:
164+
165+
- A brand reference page for colors, mascot roles, and visual identity.
166+
- Branch examples included brand color names and mascot descriptions.
167+
- Possible future use:
168+
- internal brand system page
169+
- admin-only design reference
170+
- public brand page if product marketing needs it
171+
172+
Modern rebuild note:
173+
174+
- Rebuild through Theme V2 tokens and current asset paths.
175+
- Do not copy old brand swatch CSS or old mascot page markup.
176+
177+
### Controls
178+
179+
Useful idea to preserve:
180+
181+
- A controls/reference page showing common form controls with foundry-style grouping.
182+
- Possible future use:
183+
- Theme V2 design-system reference
184+
- admin-only design QA page
185+
- reusable controls documentation
186+
187+
Modern rebuild note:
188+
189+
- Rebuild as Theme V2 design-system documentation if needed.
190+
- Do not copy old page-local control CSS.
191+
192+
## Recommended Future PR Slices
193+
194+
1. Public destination planning PR:
195+
- decide whether Cloud, Publish, and Docs are current product pages
196+
- define root paths and navigation ownership
197+
198+
2. Publish readiness PR:
199+
- connect Publish concepts to manifest, asset, debug, candidate, deploy, and public URL gates
200+
201+
3. Toolbox IA PR:
202+
- map Tool Builder / Tool Creator / Tool Publisher concepts to current toolbox registry/status data
203+
204+
4. Tool group PR:
205+
- derive group landing pages from current toolbox metadata
206+
207+
5. Theme V2 design-system docs PR:
208+
- decide whether Branding and Controls belong under Admin, Account, or public docs
209+
210+
## Final Recommendation
211+
212+
Delete the old SSoT branch after this capture report. Its useful ideas are now documented, while its implementation path is obsolete under current Theme V2, current root page organization, local API/session work, and toolbox registry direction.
213+
214+
## Validation Checklist
215+
216+
| Requirement | Status | Evidence |
217+
| --- | --- | --- |
218+
| Capture Public destinations: Cloud, Publish, Docs. | PASS | See `Public Destinations`. |
219+
| Capture Tool Builder / Tool Creator / Tool Publisher concepts. | PASS | See `Tool Builder / Tool Creator / Tool Publisher`. |
220+
| Capture tool group landing page concepts. | PASS | See `Tool Group Landing Page Concepts`. |
221+
| Capture Account Branding / Controls concepts. | PASS | See `Account Branding / Controls`. |
222+
| Do not merge old code. | PASS | No merge command was run. |
223+
| Do not cherry-pick old code. | PASS | No cherry-pick command was run. |
224+
| Do not copy old CSS/partials/JS. | PASS | Report captures concepts only and explicitly rejects old implementation paths. |

0 commit comments

Comments
 (0)