Tracking Issue: restructure PowerContext documentation

[PsiACE]

Goal

Define a clear documentation layout and fill the current gaps.

User and developer documentation must reflect the current code and public
contracts. RFCs are frozen design records and may become outdated.

Proposed layout

The following layout is illustrative. File names and final page boundaries may
change during implementation.

docs/en/
├── index.md                         # Product landing page and main entry points
├── docs/                            # Current user-facing documentation
│   ├── index.md                     # Documentation overview and journey selection
│   ├── tutorials/                   # Guided learning journeys with working outcomes
│   │   ├── codex-quickstart.md
│   │   └── ...
│   ├── how-to/                      # Steps for completing specific tasks
│   │   ├── install-and-run.md
│   │   └── ...
│   ├── explanation/                 # Concepts, boundaries, and system behavior
│   │   ├── core-concepts.md
│   │   └── ...
│   └── reference/                   # Current interfaces, configuration, and contracts
│       ├── interfaces.md
│       └── ...
├── development/                     # Current implementation and extension guidance
│   ├── core-protocol.md
│   └── ...
├── rfcs/                            # Frozen design records
├── blog/                            # Published engineering notes
└── changelog/                       # User-visible release changes

Keep docs/zh/ structurally equivalent.

Tracking

• Confirm the layout and classify existing pages.
• Add the missing explanation pages.
• Separate Memory and Handoff terminology and workflows.
• Document current Handoff, Review, Experience, Skill, and Report behavior.
• Move procedures out of reference pages.
• Audit docs against code, OpenAPI, CLI, Client, and MCP.
• Fix RFC navigation and release information.
• Keep English and Chinese navigation synchronized.
• Ensure make docs-test passes.

Documentation quality

Keep pages short, scannable, and suitable for human readers. When a page covers
a workflow, state the steps and expected outcome clearly. If AI helps draft a
page, use the documentation-writer and humanizer skills, then have a human
verify and approve the result.

[chenncy]

Hi @PsiACE, I’d like to contribute to the documentation restructuring.

As a first small contribution, could I take one clearly scoped page (for example, the Codex quickstart or an install-and-run how-to), including the matching docs/en and docs/zh pages and navigation updates? I will base it on the current code and public interfaces, run make docs-test, and open a PR for review.

Please let me know which page or subtask would be most useful to start with.

[PsiACE]

could I take one clearly scoped page?

hi @chenncy The Codex onboarding docs would be a good start. Please consolidate the duplicated docs, verify the tool and plugin installation flow, and simplify it where possible based on your experience with other production's plugins. Keep the English and Chinese pages in sync.