docs: sync beta6 release documentation

[benym]

What

• audit 0.4.0-beta.5..master for beta6 user-visible behavior
• keep the README changes already merged by feat: add current-branch isolation mode #210 unchanged
• update the website version selector to 0.4.0-beta.6
• add the missing beta5 and beta6 Chinese and English release notes
• synchronize the website pages directly corresponding to changed Classic Skills: state management, build, hotfix, tweak, and archive
• advance the website submodule with one beta6 release commit based directly on the main repository's recorded website pointer

Skill behavior covered

• full workflow can explicitly keep working on the current branch
• hotfix and tweak require an explicit current/branch/worktree choice instead of silently defaulting
• current, branch, and worktree isolation bind bound_branch and block branch drift
• confirmed takeover uses comet state rebind
• current-isolation archive offers push-current or keep-local instead of feature-branch merge/PR actions

Scope control

The website branch contains one release-specific commit and changes only 13 files: docs.json, two changelog pages, and five directly affected documentation pages in each language. It does not include the Superpowers design/plan commits or unrelated Native documentation commits.

Verification

• all 12 changed MDX files compile successfully with @mdx-js/mdx
• docs.json parses successfully
• git diff --check passes
• both repositories contain one release-specific commit

Summary by Sourcery

Sync website documentation and release notes with 0.4.0-beta.6, including updated behavior descriptions for Classic Skills and advancing the website submodule to the new release pointer.

Documentation:

• Add and update English and Chinese release notes for 0.4.0-beta.5 and 0.4.0-beta.6.
• Refresh website documentation pages for Classic Skills state management, build, hotfix, tweak, and archive to reflect beta6 behavior.

Chores:

• Advance the website submodule to the beta6 release commit aligned with the main repository's recorded website pointer.

Summary by CodeRabbit

• Chores
  • Updated the website to the latest version, incorporating the newest available changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 3d24f80b-cd4b-4131-8a94-bd5e69455d70

📥 Commits

Reviewing files that changed from the base of the PR and between e97a0e6 and 397cfe9.

📒 Files selected for processing (1)

• website

---

📝 Walkthrough

Walkthrough

The website git submodule pointer was updated from commit 375fd7d53175872068c570a2fd4f78cb2d0a0c99 to ef2cdcf92a86c360d78e00ce15624aacae6962dd.

Changes

Website submodule update

Layer / File(s)	Summary
Update website submodule reference website	The tracked website submodule commit reference was replaced with a newer commit.

Estimated code review effort: 1 (Trivial) | ~2 minutes

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title is concise and accurately summarizes the release documentation sync for beta6.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch release-beta6

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[sourcery-ai]

Reviewer's guide (collapsed on small PRs)

Reviewer's Guide

Updates the documentation website submodule for the 0.4.0-beta.6 release, adding release notes in English and Chinese and syncing specific Classic Skills docs and the version selector with the audited beta5→beta6 behavior, via a single release-specific commit in the website repo.

File-Level Changes

Change	Details	Files
Advance the documentation website submodule to the beta6 release-specific commit aligned with the main repo’s website pointer.	Update the website submodule reference to point to the new beta6 release commit Ensure only release-related documentation changes are included, excluding unrelated design or Native docs	website
Update documentation version selector and release notes to cover 0.4.0-beta.6 (and missing beta5) in both English and Chinese.	Set the website’s documentation version selector to 0.4.0-beta.6 Add or update English release notes for beta5 and beta6 Add or update Chinese release notes for beta5 and beta6 Verify all changed MDX files compile and docs.json parses correctly	docs.json changelog page(s) (English) changelog page(s) (Chinese)
Synchronize Classic Skills documentation pages with the audited beta6 behavior for state management, build, hotfix, tweak, and archive workflows.	Update state management docs to reflect explicit branch/worktree choices and current branch workflow Update build docs to match beta6 behavior as audited from beta5..master Update hotfix and tweak docs to require explicit current/branch/worktree choice and document isolation semantics Update archive docs to describe current-isolation archive options (push-current vs keep-local) instead of feature-branch merge/PR flows Document confirmed takeover via comet state rebind and bound_branch behavior preventing branch drift	Classic Skills state-management page(s) (EN/zh) Classic Skills build page(s) (EN/zh) Classic Skills hotfix page(s) (EN/zh) Classic Skills tweak page(s) (EN/zh) Classic Skills archive page(s) (EN/zh)

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[greptile-apps]

Greptile Summary

This PR updates the website submodule for the beta6 documentation sync.

• Advances the website gitlink to a new commit.
• Keeps the main repository changes limited to the submodule pointer.

Confidence Score: 2/5

Recursive submodule checkout can fail on the updated website pointer.

• The changed gitlink records a commit that must be fetched by exact SHA.
• The configured submodule remote does not currently provide that commit by SHA.
• A normal recursive checkout can stop before any website docs build runs.

website

Important Files Changed

Filename	Overview
website	The submodule pointer was advanced to ef2cdcf92a86c360d78e00ce15624aacae6962dd, but that commit must be reachable from the configured submodule remote for recursive checkout to work.

_{Reviews (1): Last reviewed commit: "docs: sync beta6 website metadata" | Re-trigger Greptile}