Skip to content

Design: Profile Backup / Restore / Transfer UX #76

Closed
1 of 1 issue completed
Closed

Description

@DoodleBears

Remaining Profile portability scope — reconciled 2026-09-30

This issue owns identity-preserving Profile Backup, Managed Restore, Profile Transfer and Disaster Restore UX. PersonaBot public sharing/export/import lives in #17/#18 and its feature Project; it is not blocked on the full Profile backup design.

  • Export Profile to one .botharness-backup; Import Profile from one file.
  • Restore As New / Replace Existing, staging validation and explicit confirmation.
  • Readiness/rebind/activation checklist, unavailable Workspace and provider fingerprint mismatch.
  • Transferred Out and Disaster Restore behavior; Session facets omitted/unsupported and sensitive operational facets.
  • Keep a concise explanation of clone sharing versus identity-preserving Profile operations; do not duplicate Tracer: publish a Memory Git repo and import through a Bot link #17's selector/publisher UX.

Remaining deliverables

  • Minimal Profile user flow and error/confirmation matrix.
  • Backup/Restore/Transfer copy, information hierarchy and size/validation presentation.
  • DSH Settings/Plugin surface and Host RPC requirements.
  • Narrow Profile implementation slices after the design is accepted.

References: ADR-0040–0044, current living architecture. No scheduler, retention catalog or incremental backup chain.

Historical scope before 2026-09-30 reconciliation (superseded where inconsistent)

Why

#71 已确定 PersonaBot Export、单文件 Profile Backup、Managed Restore、Profile Transfer、Disaster Restore 与 dependency rebind 的业务语义,但尚未把它们整理成 Human 能理解的最小操作流程。

Scope

  • PersonaBot Export/Import(clone)与 Profile Backup/Managed Restore(保留 identity)的清晰区分。
  • 仅两个基础动作:Export Profile → 一个 .botharness-backup;Import Profile ← 一个文件。
  • Restore As New / Replace Existing、手动备份提示、staging validation、readiness/rebind/activation checklist。
  • Session facet omitted/unsupported、Unavailable Workspace、provider fingerprint mismatch、Transferred Out、Disaster Restore 的说明与恢复路径。
  • 敏感 operational facets、估算大小、结构校验失败的呈现。

Deliverables

  • 最小用户流程与错误/确认矩阵。
  • PersonaBot Export、Profile Backup、Transfer 三条路径的文案和信息层级。
  • DSH Settings/插件页 slot 与 Host RPC 需求。
  • 拆出 PersonaBot Export 与 Profile Backup/Restore 的独立实现票。

Related

Non-goals

  • 不增加 scheduler、backup catalog、retention、增量链或自动备份。

Accepted design and implementation handoff — 2026-10-05

Human accepted PR #881; verified head passed full CI and merged as 43fe4b6b3df707bdacd172180c68bfee129e3451. Implementation is coordinated in native child hub #882, with #883/#884/#885 canonical-owner slices and #886 complete-core round trip. Each runtime PR requires real DSH evidence and its own Human QA. This design issue does not claim runtime backup/restore delivery; #505 remains blocked on production portability and sharing contracts.

Activity

  1. added this to the v1.1 milestone on Sep 19, 2026
  2. added
    V1.1Milestone v1.1; mirrors the GitHub milestone
    area:ui-uxInteraction and visual experience; may accompany a code-layer area
    feature:exportExport, import, backup, and transfer
    scope:designDesign decision or UX contract
    on Sep 22, 2026
  3. changed the title [-]设计:PersonaBot Export / Profile Backup / Restore / Transfer UX[/-] [+]Design: Profile Backup / Restore / Transfer UX[/+] on Sep 30, 2026
  4. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    ContributorAuthor

    Agent work claim

    • Agent: Codex
    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • Issue scope: design-only Profile Backup / Restore / Transfer UX proposal under ADR-0040–0044: minimal flows, copy and confirmations, readiness/rebind, Settings and owning Host operation requirements; no runtime implementation or Tracer: Preserve model plans in Profile Backup only #505 completion claim.
    • Branch: codex/76-profile-portability-design
    • Started: 2026-10-05 14:20 UTC
    • State: active

    #325 / PR #879 are merged and completed. #76 has no existing claim, assignee or open PR at preflight. Implementation slices will be published only after Human accepts this design.

  5. added
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 5, 2026
  6. self-assigned this
    on Oct 5, 2026
  7. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome — paused for Human acceptance

    • Task: codex/local/01a0f25f-2150-75e3-8895-23d35394b8d8 (not a DSH Session)
    • State: paused
    • PR: docs: propose Profile backup, restore and transfer UX #881
    • Reviewed head: 3b2dd92a69df434bc94bad2a57949db807d9fa36
    • Scope: bilingual design proposal only. Minimal flows, sensitive core disclosure, size/privacy summaries, error/confirmation matrix, existing Settings seam and proposed owning Host operations, verified-transfer cancellation UX, readiness/rebind/activation, and subsequent vertical-slice order.
    • Standards: PASS, 0 findings. Spec: PASS, 0 remaining findings; initial sensitive-core and source-cancellation omissions fixed in both languages.
    • Local validation: format and bilingual Release Ledger checks passed; documentation build passed (326 pages), and relative document links resolve. No runtime UI or executable behavior changed, so no functional E2E screenshot is claimed for this proposal.
    • Remote CI: final-head lint/format/typecheck passed; test/build/docs workflow still running at handoff. This is not merge approval or an all-CI-pass claim. CodeRabbit's successful status says rate limited and is not a completed review.

    Human acceptance should confirm complete-core/private-data disclosure, identity-preserving new versus stopped-target replacement, explicit readiness/authorization repair, Transferred out and cancellation/disaster-recovery posture. No implementation tickets have been published. After design acceptance, publish narrow implementation slices and continue real DSH E2E with screenshot/recording and per-PR Human QA. #76 stays open until that handoff; #505 remains blocked on production full Backup/Restore and its other contracts. No #272 Windows acceptance or additional merge is claimed.

  8. added and removed
    agent:activeOne or more coding-agent tasks currently claim this issue; see claim comments for task IDs
    on Oct 5, 2026
  9. DoodleBears commented on Oct 5, 2026

    @DoodleBears
    ContributorAuthor

    Agent work outcome — completed design handoff

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

V1.1Milestone v1.1; mirrors the GitHub milestonearea:ui-uxInteraction and visual experience; may accompany a code-layer areafeature:exportExport, import, backup, and transferscope:designDesign decision or UX contractwayfinder:grillingWayfinder grilling ticket

Type

No type

Projects

  • Status
    Done

Relationships

None yet

Development

No branches or pull requests

Issue actions