Skip to content

Sync CE: personal memory wiki, Dreaming and proactive scheduling - #226

Merged
Luhaozhu merged 2 commits into
mainfrom
sync/ce-20261111-personal-memory
Nov 11, 2026
Merged

Luhaozhu merged 2 commits into
mainfrom
sync/ce-20261111-personal-memory

Conversation

@Luhaozhu

@Luhaozhu Luhaozhu commented Nov 11, 2026 •

Copy link
Copy Markdown
Contributor

Purpose and behavior

  • Before: The public main branch lacks the topic-based personal-agent memory workspace, recoverable Dreaming pipeline and proactive scheduling.
  • After: Personal agents use a topic-based memory wiki with guarded writes, change history, snapshots and a recoverable Dreaming pipeline. Proactive checks can review eligible user conversations and propose work through existing approval flows.

Change walkthrough

  • Flow: Personal-agent API and conversation entry points call personal_agent/memory/ for wiki reads/writes and Dreaming; memory version/usage models and CE migrations persist audit and lifecycle state; the frontend workspace renders pages, changes and snapshots. personal_agent/scheduling/proactive_probe.py, guards and tasks select eligible conversations and feed the existing task/approval router.
  • Decisions: This is a maintainer-requested generated CE sync from upstream, applied onto public main without importing private Git history. CE-specific fixes add an idempotent memory-table upgrade, omit enterprise-only chat-sharing fields from proactive probes, supply missing English memory translations. Public review instructions, PR template/workflow and review-check scripts are preserved. The branch includes current public main (bf846fe), including the already merged Sync CE: repair local upgrades and improve knowledge and chat flows #225 fixes. The final delta is 179 files, 15,601 additions and 1,828 deletions.

Risk and compatibility

  • Risk: high
  • Boundaries: Database upgrades, memory retention/deletion, user ownership, proactive scheduling need review. CE remains independent of enterprise models and services. Existing approval boundaries remain in the proactive path; no real external messaging or tool-write test was performed. This PR contains no deployment inventories, signing credentials or release artifacts.
  • Human review: Maintainers must assess ownership filters, memory source validation and lifecycle deletion/recovery, existing-database compatibility before merge. Human approval is pending. In particular, current bilingual Dreaming documentation says 90 days before archiving, while lifecycle code uses 60 idle days for archiving and 90 archived days for deletion; the intended policy and documentation need reconciliation before approval.

Verification

  • Evidence: Clean CE derivation passed required-runtime, forbidden-output, brand and license gates; CE import/OpenAPI/ORM checks; 59 CE release/sandbox/route regression tests; and the full CE frontend build on Node 22. The new CE migration regression verifies repeated upgrade and preservation of existing memory data, and the proactive-probe test excludes other-user, automation and channel conversations. Upstream personal-agent regression selection passed 324 tests. Both full-edition frontend builds passed. Existing-database memory/proactive migrations were exercised twice on isolated SQLite data. The preserved public PR-context suite passed all 19 tests. The main-sync merge head 1d56a47 has the identical Git tree (e7f3d75) as the previously validated sync head; resolving the model-registration conflict preserved the tested memory table imports.
  • Limits: No comprehensive live-provider, external-send, multi-worker stress or long-running retention test was performed. Native branded desktop smoke checks are separate from this public CE tree and do not establish CE package acceptance. Full-edition lint remains at its existing 245-error baseline; a clean lint result is not claimed.

Recovery

  • Steps: Disable personal-agent proactive and Dreaming execution before reverting affected application code. Preserve the database and agent workspace together before upgrade; restore matching backups if schema or memory state is incompatible. Reverting code alone cannot restore deleted wiki pages, discarded snapshots or external tool effects. Do not blindly downgrade memory migrations on real data, since their downgrade removes the added tables.

Review follow-up

  • Disposition: Initial human review is pending. Derivation failures discovered during preparation were repaired upstream (enterprise-field leakage, missing memory migration, marketplace exports and translations) and the complete CE gates were rerun successfully. The retention-policy/documentation mismatch above remains explicitly identified for review.

Community checklist

  • This is an allowed contribution or a maintainer-reviewed generated sync.
  • Public bilingual documentation is updated in both languages where applicable.
  • Links/code snippets were checked and CONTRIBUTING.md was read.

@Luhaozhu Luhaozhu changed the title Sync CE: personal memory wiki, proactive scheduling and upgrade repairs Sync CE: personal memory wiki, Dreaming and proactive scheduling Nov 11, 2026
@Luhaozhu
Luhaozhu merged commit 151e43f into main Nov 11, 2026
7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant