parent-synclisted

# parent-sync ## Mission Push approved child-project state up to a parent project. Provenance preserved. Conflicts surface at parent. Push requires explicit user approval every time. ## Pre-flight 1. Read `config/PARENT_SYNC.md`. If `enabled: false` → exit with "Parent sync not configured". 2. Validate `parent_path`: - Path exists - Contains a flat `memory/` (is a Zeref OS v4.3+ project) - Writable by current user 3. If `child_id` is null → assign one: - Default: basename of current project root - Or prompt user for custom id - Persist to `config/PARENT_SYNC.md` ## STAGE (called on /stop or /sync-parent) 1. Read `push_content:` list from `config/PARENT_SYNC.md` (default: summary, decisions, risks, open_questions) 2. For each content type: - **summary**: read `memory/index.md` + last 3 events from `memory/patterns/PATTERNS.jsonl` → compose 1-page summary - **decisions**: read recent entries (last 30 days) from `memory/DECISIONS.md` - **risks**: read open-status entries from `memory/RISKS.md` - **open_questions**: read all open from `memory/OPEN_QUESTIONS.md` 3. Pass each through `evidence-curator` FILTER_SYNC — keep only grade ≥ medium 4. Pass each through `privacy-guardian` per current privacy mode (`PRIVACY.md`) - If mode = `local-only` → REFUSE, exit with "local-only mode blocks parent sync" 5. Write staged content to `memory/sync/outbound/<iso>/`: ``` memory/sync/outbound/2026-05-30T14:23:11Z/ summary.md decisions.md