Skip to content

docs: assess Persona Workspace parity and stage implementation - #2952

Draft
rmusser01 wants to merge 2 commits into
devfrom
codex/persona-workspace-parity-plan
Draft

rmusser01 wants to merge 2 commits into
devfrom
codex/persona-workspace-parity-plan

Conversation

@rmusser01

@rmusser01 rmusser01 commented Sep 13, 2026

Copy link
Copy Markdown
Owner

Workspace Assistant Defaults V1 is merged, but the server and current Chatbook dev differ in explicit opt-out, automatic provisioning, permission-profile references, and chat startup behavior. This documentation-only PR records those differences against pinned commits and provides a backend-first five-stage plan for #2950.

The plan puts resolver privacy/diagnostics and durable user choices before permission binding and provisioning, then gates Research Workspace adoption on preserving Persona identity through normal and RAG execution. It preserves the existing V1 completion boundary and keeps every implementation stage open in Backlog.

Artifacts:

  • Docs/Design/2026-09-13-persona-workspace-parity-assessment.md
  • Docs/superpowers/plans/2026-09-13-persona-workspace-parity-implementation-plan.md
  • Assessment TASK-13243; implementation TASK-13244, TASK-13245, TASK-13246, TASK-13248, TASK-13247.

Verification: referenced server paths and document links checked; Python test example parsed; staged diff whitespace checks passed. Fresh unmodified-backend baseline: 32 passed, 1 failed, 6 warnings. The existing v48 migration test rewinds a modern database into a Notes v59 registry collision; its repair is tracked in the first stage. Chatbook tests and browser UAT were not run. Bandit is not applicable to this documentation-only diff.

This draft changes no runtime behavior and does not claim parity is complete. It proposes implementation sequencing for review. The repository requires a human-written Change summary explaining the changes and rationale before merge; no such summary is represented by this agent-authored description.

Refs #2950, #1922. Does not close either implementation tracker.


Summary by cubic

Documents where the server's Persona Workspace defaults diverge from Chatbook dev and records a backend-first five-stage implementation plan for #2950. The parity assessment (TASK-13243) is complete; the five implementation stages (TASK-13244 through TASK-13248) stay open in Backlog.

Plan

  • Adds the assessment and implementation plan under Docs/Design/ and Docs/superpowers/plans/, plus five open Backlog tasks.
  • Tool-profile parity depends on a focused #1922 contract; Research Workspace adoption waits for all backend stages.
  • A pre-existing v48 migration test failure is documented and its repair is tracked in Stage 1. This PR changes no runtime behavior.

Written for commit 15c9698. Summary will update on new commits.

Review in cubic

@coderabbitai

coderabbitai Bot commented Sep 13, 2026

Copy link
Copy Markdown

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

rmusser01 added a commit that referenced this pull request Sep 13, 2026
TASK-13243 is complete with review artifacts in #2952 and linked from #2950. All five implementation tasks remain pending.
Track #2950 and TASK-13243 with pinned server/Chatbook evidence. Put resolver privacy and durable opt-out before permission binding, provisioning, and Research Workspace adoption. Plan: Docs/superpowers/plans/2026-09-13-persona-workspace-parity-implementation-plan.md.
TASK-13243 is complete with review artifacts in #2952 and linked from #2950. All five implementation tasks remain pending.
@rmusser01
rmusser01 force-pushed the codex/persona-workspace-parity-plan branch from 3e4bbf1 to 15c9698 Compare September 13, 2026 20:10
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