feat(memory): portable project memory via .zo/ directory#44
Merged
Conversation
…repos Project state (STATE.md, DECISION_LOG, PRIORS, sessions, plans, config) now lives in the delivery repo under .zo/, making projects portable across machines via git pull. ZO public repo retains only platform-level memory. New module: project_config.py (ProjectConfig + LocalConfig models, YAML I/O, TargetConfig adapter). MemoryManager gains memory_root override. Orchestrator gains plan_path override. Scaffold creates .zo/ dirs. CLI discovery layer (_detect_delivery_repo, _load_project_context) supports both .zo/ and legacy layouts. New zo migrate command. zo continue gains --repo flag. zo status gains --repo and optional project_name. 521 tests passing, ruff clean, validate-docs 10/10. Sanitised all client references from tracked files. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Deploying zero-operators with
|
| Latest commit: |
909188e
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://1ea34ef0.zero-operators.pages.dev |
| Branch Preview URL: | https://claude-lucid-swirles.zero-operators.pages.dev |
5 tasks
SamPlvs
added a commit
that referenced
this pull request
Apr 30, 2026
feat(memory): portable project memory via .zo/ directory
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.
Summary
.zo/, making projects portable across machines viagit pullzo migratecommand copies legacy project state into.zo/directoryzo continue --reporeconnects to a project on a new machine with auto-environment detectionzo status --repoand optional project_name auto-detected from.zo/config.yamlmemory/zo-platform/)Changes
src/zo/project_config.py— ProjectConfig + LocalConfig Pydantic models, YAML I/O, TargetConfig adapterzo migrateCLI command,tests/integration/test_migrate.py(8 tests)tests/integration/test_zo_dir_layout.py(8 tests),tests/unit/test_project_config.py(14 tests)memory.py(memory_root override),orchestrator.py(plan_path override),scaffold.py(.zo/ dirs)cli.py— discovery layer, updated build/continue/status/gates/watch-training commandsTest plan
ruff check src/zo/cleanvalidate-docs.sh9 passed, 0 failedzo migrate ivl_f5 --repo ~/ivl_f5successfully migrated prod-001 statezo continue --repoon GPU server (blocked on merge)🤖 Generated with Claude Code