Table of Contents
Resource releases and wiki maintenance
Keep this Git checkout beside web-framework/. All new plugins/themes belong here, each in a dedicated folder with JSON metadata (id, name, description, version). Independently version changed resources, bump repository VERSION, and document behavior in CHANGELOG.md. Update docs/ function references whenever implementations change; keep README files short.
tools/build_catalog.py exports build(root): discovers every plugin/theme JSON manifest, builds a deterministic ZIP containing implementation, templates, assets and resource README at archive root, computes SHA-256, and writes schema-version-1 catalog entries. Unchanged packages retain their exact published archive bytes and checksums. It excludes tests, bytecode and cache folders; retains previous versioned archives. Run python tools/build_catalog.py from the checkout. Commit source, metadata, archives, docs, catalog and version together, then push.
Run python tools/sync_wikis.py to synchronize both repositories' detailed docs/*.md pages to their corresponding Gitea wikis. The script accepts optional repository paths. It uses GITEA_TOKEN or Git's configured stored credential, enables missing wikis, initializes Home, clones each wiki into temporary storage, copies maintained pages, commits changed content, and pushes without force. It converts local Markdown page links to wiki slugs and preserves unrelated wiki pages and cleans temporary clones. Credentials are never printed or written to Git remotes.
The framework's companion release builds and pushes a new Docker version and latest, then retains the current and five previous numeric framework image versions. Resource ZIP archives remain available for installed catalog versions. See the framework release guide for the complete release procedure.
Media-suite releases must run tests/test_media_plugins.py and tests/browser_media_check.py with external AI/Discord calls mocked. Rebuild all changed archives and verify checksums; install those archives in the new Docker image and verify provider modules load through its locked Node runtime. Keep the Kaizoku source revision, upstream copyright notices, GPL text and capability/function references updated. Do not include local node_modules in archives.