> **This file belongs to GitCraft.** It is one of five files that document this app, > and they are a closed set — nothing here points outside it. > > - **Parent:** [`help.html`](help.html) — the GitCraft help page. Start there; it contains > this file's contents in readable form, along with everything else about GitCraft. > - **This file:** `plan.md` — the approved steps for this app, in order, tickable. Approved work only. > - **Its siblings:** [`changelog.md`](changelog.md) and [`ideas.md`](ideas.md) and [`developer.md`](developer.md), in this same folder. > > **Working rule:** preserve User Help for users; update `developer.md` in real time with coding changes. Run > `php ../.././build-help.php --app gmm/dependencies/gitcraft --apply` to update the human page. > There is no sixth documentation file. Having read these five you have read the whole of the > GitCraft documentation. # GitCraft plan - [x] Preserve and move the existing installation; reconcile the full publisher catalogue. - [x] Publish permitted browser runtimes and anonymous tool access. - [x] Add explicit optional setup and version checks through GMM Dependencies. - [ ] Complete per-editor import, meaningful edit, native project save/reopen and export acceptance. - [x] Verify PhotoCraft basic PNG account import/export/save/reopen and clean both known test attachments. - [ ] Complete remaining editor account workflows and native-project storage; WordPress PSD upload is rejected. - [ ] Integrate the private GMM library with ownership and quota checks; current connector uses WordPress media permissions. - [ ] Define editor capabilities and authenticated MCP/AI connectors. Do not expose a general shell or assume GUI automation is an editor API. - [ ] Choose the first upstream fork after workflow comparisons; record source commit, licence notices and upstream update policy. - [ ] Resolve SolidCraft interface terms before public integration. - [ ] Add advertising through the platform's existing consent and placement system after functional acceptance.