Repository navigation
Consolidate managed storage configuration, references, and migration - #50
Merged
Merged
Conversation
added 4 commits
November 9, 2026 17:47
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Closes EpistasisLab/ASAREE_Issues#50
Managed files previously used independent roots and deployment-specific paths. This change adds a shared data root with compatible directory overrides, propagates resolved configuration to workers/MCP subprocesses, and resolves stable namespace/key references in workspace state, managed knowledge commands, and Agent runtime metadata. Row snapshots now use workspace storage without depending on the dataset directory's parent.
An offline copy-first migration inventories both databases and files, verifies ready artifacts and pinned identities, migrates documented locator fields, and supports verification, interruption recovery, and rollback. Opaque row values, learned payloads, names, and arbitrary output JSON remain unchanged; explicitly unavailable historical artifacts retain their status and evidence. Sources and unknown files are retained.
Atomic publication protects dataset files, workspace generations, manifests, scripts, exports, and row snapshots. Retention protects publication/attempt references and retained workspace inputs. Knowledge unregister retains historical managed content and never deletes external files. Compose narrows new external bundle browsing; the operator guide covers configuration, migration, lifecycle, and coordinated PostgreSQL/files/Redis backup and restore. Existing input pins, workspace formats/slots, MCP scope checks, export expiry, and SQLite indexes remain supported; #69 replaces SQLite separately.
Validation:
Storage migration is an explicit offline operator action. Both databases use separate guarded transactions, so writers must remain stopped through cutover/recovery. Reclamation remains conservative and operator-directed; legacy knowledge ownership requires explicit confirmation. No production migration or deployment is part of this PR.