Skip to content

Latest commit

 

History

History
23 lines (16 loc) · 2.4 KB

runtime-storage.md

File metadata and controls

23 lines (16 loc) · 2.4 KB

Local Runtime Directories

English | 简体中文

The host's .runtime/ directory is ignored by Git. It contains application data, rebuildable caches, and development diagnostics, so it must not be deleted wholesale. Distribution Java resides in vendor/java/windows-x64, and native materials also reside in the source tree. Required distribution inputs must not exist only under .runtime/.

Directory Conventions

Path Purpose and retention
app/ Application data. Preserve databases and files in projects/, packages and state in plugins/, and user settings. Do not treat all of user-data/ as disposable cache.
packaging/, plugin-sdk/ Packaging and SDK export staging. Individual task directories can be removed after the task ends and diagnostics are no longer needed; do not clear the entire tree during active tasks.
bundled-plugins/ Explicitly prepared optional plugin archives and delivery index, used for bundled installation and manual reinstallation. Default host builds do not create these materials. Run pnpm prepare:plugins only with explicit sources and all materials required by the catalog.
bundled-plugins-build/ Staging for explicit plugin preparation and prebuilt package checks. Tools remove only their own new subdirectories, without deleting active installation data.
test-results/, acceptance/, plugin-acceptance/ Reports from test and acceptance entry points. Retain history as needed.
signing/, native-signing/ Signing caches and staged materials, managed by the signing workflow.
tasks/ Temporary scripts, logs, and configuration for local diagnostics and testing, separated into purpose-specific subdirectories.
archive/ Local materials from completed tasks, retained as needed and not used as application runtime inputs.

Keep only clearly assigned subdirectories and necessary documentation at the root. Store logs, reports, and redirected command output in the appropriate subdirectory. Archived scripts may reference old interfaces or machine-specific paths; inspect them before reuse.

Before cleanup, stop applications or builds using the directory, confirm its absolute path and purpose, and remove only rebuildable caches or temporary materials no longer needed. Preserve project databases, results, plugin state, and user configuration separately. Leave active task directories in place.