> **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:** `developer.md` — the live cold-start engineering authority: architecture, boundaries, data, hazards, verification, gaps and safe continuation. > - **Its siblings:** [`changelog.md`](changelog.md) and [`plan.md`](plan.md) and [`ideas.md`](ideas.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 developer guide ## Purpose Optional third-party creator tools integrated with GMM. P-094 owns the study; the public landing is /gitcraft/. ## Architecture and authorities catalogue.json declares approved apps, release prefixes, official resources and any pinned source build. service.php owns release checks, extraction, staging, activation and managed-file records. index.php authorises installer mutations. ui.php and the workspace files provide the independent Gameznet shell. Central registry/environment/index integration is retained as a source-protected candidate; it is not installed. ## Boundaries and non-goals No runtime installs on page load. No ArtCraft services backend, copied restricted service assets, paid provider requests or role changes. SolidCraft public integration is excluded. Do not treat startup tests as full app acceptance. Do not modify Office/core release machinery in this project. ## Data flow and storage Publisher HTTPS release -> approved URL -> SHA-256 validation -> private staging -> validated ZIP paths -> managed-file manifest -> app directory activation. Previous files and updater locks live outside the web root. installed-state.json is denied publicly. WordPress media uses the signed-in user's REST nonce and normal upload permission. The connector lists only that account's media; it is not yet the private GMM library contract. ## Dependencies PHP 8+, cURL, ZipArchive, filesystem permissions and browser WebAssembly/WebGL capabilities. Heavy native paths may need additional browser capabilities; each upstream app documents its own limits. Hosted updater uses WordPress manage_options and request tokens. Local updater checks the portable platform identity and loopback context. ## Invariants and refactoring hazards Preserve unknown local/research files, source notices and modified managed files. Refuse traversal, executable ZIP content and symlinks. Keep runtime downloads out of the default platform package. Deployment must be scoped to selected suite files; never replace an existing live GMM tree with a divergent local tree. Bind browser calls to this chat's own tab and yield shared Office1 browser use to its coordinated owner. ## Current implementation 19 local apps, 18 hosted; AniCraft is a source build from a pinned upstream tag/toolchain. PhotoCraft gets a same-bytes publisher snippet-path repair. Gzip wasm derivatives decode to original bytes. The hosted workspace has an explicit account-media sidebar and export capture, not full editor command APIs. The basic PhotoCraft PNG workflow passed, including a fresh account-media reopen and exact decoded RGBA equality. Native PSD save/file-drop reopen passed for one single-layer fixture. WordPress rejects PSD account upload. Test attachments100051648/100051649 were deleted and return404; retained local evidence is in P-094. ## Verification commands Run php -l on changed PHP, node --check on browser/workspace JS, php working/GitCraft/tests/updater.php from the Federation root, and php gmm/tests/dependency-authority-test.php from the site root. Recorded local/live browser startup and text workflow receipts are in the project evidence. Browser scripts must pass an explicit bound tab and check page identity before every mutation. Installer fixture tests use only disposable working/ fixtures. ## Known gaps Per-editor editing/export/reopen, native-project media MIME handling, member-role upload policy, private-library ownership/quota, paid provider routing, MCP capabilities and ads acceptance remain open. Anonymous free editor access is available. A single successful WordPress upload proves that route only. ## Safe continuation Read P-094's current checkpoint and evidence. Obtain the coordinated browser slot, select this chat's own tab, verify the URL, continue with the next editor workflow or the native-project storage contract; the PhotoCraft fixture flow is complete and its two attachments were removed. Advance one editor workflow at a time. Preserve upstream code and document any adapter changes separately.