Skip to content

The fastest, cheapest, most efficient open-source agent harness. Run more than 500 agents on a $10 VPS.

docs(storage): document legacy v1 profile fixture coverage

Steven Enamakela534632edc1d
diff --git a/crates/openhuman-core/src/storage/import/fixtures/legacy-v1-profile/README.md b/crates/openhuman-core/src/storage/import/fixtures/legacy-v1-profile/README.md
index 638994c64b..cc86938bd2 100644
--- a/crates/openhuman-core/src/storage/import/fixtures/legacy-v1-profile/README.md
+++ b/crates/openhuman-core/src/storage/import/fixtures/legacy-v1-profile/README.md
@@ -17,15 +17,25 @@ owner models and writer transformations from `2d3e22636e^`:
- `profiles/types.rs::ProfileMeta` is written to the `cluster` scope's
`profiles` collection with `created_at` removed from the body and retained
as TSD `created_ms` metadata, matching `ProfileRegistry::body_of`.
+- `security/approval` writes a pending `approvals` record under `profile:u1`;
+ the boot owner converter must retain it as `approvals.requests`.
+- `threads/store` writes a legacy `threads_transcript_keys` record under
+ `profile:u1`; the boot owner converter must retain it as
+ `threads.transcript_keys`.
+- The TinyFlows catalog writes a `flows_definitions` record under `local`, the
+ operator catalog scope. Desktop boot must migrate it through the TinyFlows
+ catalog owner and the public `flows_list` operation must return it.
+- `secrets` contains an encrypted `fixture-secret` document under `profile:u1`
+ using the fixture-only master key `[0x5a; 32]`; the integration test reads it
+ with TinyStorage's `DocumentSecrets` API after desktop boot.
-The focused import test reads this checked-in database through the real boot
-import pipeline, then deserializes the migrated cost and artifact records into
-their owner types and reads the profile through `ProfileRegistry`. It checks
-that the source database hash is unchanged and that deleting an imported
-record survives a repeated boot import. This proves the TSD document inventory
-and owner schema conversions for these records. Secrets, module state, and
-workspace artifact files use separate production import paths and are not
-covered by `run_all` in this test.
+The host E2E test copies this database to an existing profile's
+`users/u1/workspace/storage/storage.db`, boots the desktop host with layout
+auto-migration enabled, and reads threads, approvals, secrets, and flows
+through their owner APIs. It compares the legacy database bytes before and
+after boot. The focused core import test continues to verify the owner schema
+conversions for cost, artifacts, and profile metadata, as well as
+non-resurrection after deletion.
The standalone generator is under `generator/`; it is not a workspace member
or product dependency. Regenerate a fresh database at a caller-selected path:
@@ -34,5 +44,5 @@ or product dependency. Regenerate a fresh database at a caller-selected path:
cargo run --locked --manifest-path crates/openhuman-core/src/storage/import/fixtures/legacy-v1-profile/generator/Cargo.toml -- /absolute/path/to/storage.db
```
-The checked-in database SHA-256 is
-`df0d66c4763f7ab95b71242ebcb75479caf56b863e5893dea228124952c90a40`.
+Regenerating also refreshes the checked-in database SHA-256; verify the value
+with `sha256sum` and keep it in sync with the integration test's fixture.