Skip to content

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

docs(storage): clarify legacy v1 profile fixture scopes

Steven Enamakel56ae487c8986
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 cc86938bd2..100e912339 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,17 +17,22 @@ 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 isolated desktop profile database stores owner documents in the
+ historical `local` scope; the profile directory itself supplied user
+ isolation. `security/approval` writes a pending `approvals` record there;
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/store` writes a legacy `threads_transcript_keys` record in that
+ scope; 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
+- The TinyFlows catalog writes a `flows_definitions` record in the same
+ per-profile database. 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`
+- `secrets` contains an encrypted `fixture-secret` document in the same scope
using the fixture-only master key `[0x5a; 32]`; the integration test reads it
with TinyStorage's `DocumentSecrets` API after desktop boot.
+- The generator also emits the retired workspace conversation log at
+ `legacy-workspace/memory/conversations/threads.jsonl`; the host E2E copies it
+ to the profile workspace and confirms the thread owner imports it read-only.
The host E2E test copies this database to an existing profile's
`users/u1/workspace/storage/storage.db`, boots the desktop host with layout
@@ -44,5 +49,6 @@ 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
```
-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.
+The checked-in database SHA-256 is
+`0519e2d0d32ec3690182a243f7ea1469f66c6a4c160a94718c391ca3cde701b1`.
+Regenerate and verify it with `sha256sum` when updating the fixture.
diff --git a/tests/storage_legacy_profile_boot_e2e.rs b/tests/storage_legacy_profile_boot_e2e.rs
index 06f2f75b63..ee20c15623 100644
--- a/tests/storage_legacy_profile_boot_e2e.rs
+++ b/tests/storage_legacy_profile_boot_e2e.rs
@@ -126,7 +126,6 @@ fn desktop_boot_reads_a_preserved_existing_v1_profile_database() {
);
assert!(credential.to_string().contains("u1"), "profile credential was not installed: {credential}");
let threads = rpc(&base, "openhuman.threads_list");
- let flows = rpc(&base, "openhuman.flows_list");
assert!(
threads.to_string().contains("fixture-thread"),