[WIP]docs: refresh bilingual wiki text for OpenBitFun 1.0 - #3098
Draft
uiharuayako wants to merge 1 commit into
Draft
uiharuayako wants to merge 1 commit into
uiharuayako wants to merge 1 commit into
Conversation
uiharuayako
marked this pull request as draft
September 18, 2026 04:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Refresh the bilingual OpenBitFun 1.0 GitHub Wiki text as reviewable sources in
docs/wiki/pages/. Screenshots are intentionally deferred.Type and Areas
Type: docs
Areas: user documentation / GitHub Wiki publication
Motivation / Impact
The live Wiki still describes 0.x-era branding, modes, and entrypoints. This text refresh is based on v1.0.0 source documentation and development revision f72a28e.
GitHub Wikis do not support native PRs. This PR targets the main repository for review, not the
.wiki.gitrepository. Merging does not automatically update the live Wiki. A maintainer with Wiki write access must publish the reviewedpages/*.mdseparately. The README records the upstream Wiki snapshot, requires reconciliation if it changed, and provides a non-force-push publication procedure. No synchronization workflow or credentials are added.Verification
node docs/wiki/check-links.mjsnode --check docs/wiki/check-links.mjspnpm run check:repo-hygienegit diff --cached --checkDocumentation/source-reference checks only. No application code changed; no runtime, cross-platform, remote workspace, Remote Connect, peer, or Dispatch end-to-end tests were run. Office/model/service availability is documented with prerequisites and limits.
Reviewer Notes
docs/wiki/README.mdanddocs/wiki/README.zh-CN.md..wiki.gitpublication; use the README/file browser for main-repository review.Checklist