repoburg 1.3.240 → 1.3.242

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -20,6 +20,15 @@ Repoburg consists of a few key components that work together:
20
20
  - **Frontend Application:** The web-based UI where you interact with your sessions, review AI-generated plans, and manage templates. Hosted at [app.repoburg.com](https://app.repoburg.com).
21
21
  - **Account Portal (`website2` + `account-server`):** The account authentication portal, hosted at [repoburg.com](https://repoburg.com). Handles login and the device authorization flow for the CLI/daemon.
22
22
 
23
+ ## Getting Started
24
+ ## Metadata Persistence (File-Based)
25
+
26
+ Repoburg configuration metadata lives as JSON files in `.repoburg/metadata/` — one subdirectory per artifact type, one file per record. The backend reads these files on every request, so external edits apply immediately without a restart.
27
+
28
+ Every project gets `.repoburg/metadata/README.md` — a shipped doc describing each artifact type, its purpose, and how to change the files. The backend regenerates it on every start; its source is `backend/src/metadata-store/metadata-readme.ts`. Built-in records (files with the `_meta.generated` banner) are regenerated from `backend/src/seeding/data/` on every start — user records are edited directly.
29
+
30
+ Developer CLIs (run in `backend/`): `npm run metadata:validate` validates all files (`--file <path>` for one), `npm run metadata:migrate` imports legacy SQLite rows (idempotent; `--dry-run`, `--force-merge` supported).
31
+
23
32
  ## Getting Started
24
33
 
25
34
  ### Prerequisites