Greptile Summary

This PR makes two documentation updates to docs/platforms/windows.md: it fixes a minor wording duplication in the Windows companion app blurb ("contributions" appeared twice), and adds a new section guiding contributors through GitHub connectivity issues on restricted networks, including how to authenticate with a personal access token when gh auth login fails.

• The companion app wording fix is clean and correct.
• The new "Git and GitHub connectivity" section has a logic gap in step 3: gh auth refresh -h github.com -s read:org works only against credentials stored via gh auth login. Since the entire purpose of the section is to work around a failed gh auth login (due to network blocks), no stored OAuth session exists for gh auth refresh to act on. On the same blocked network it would simply attempt the browser/device flow again and time out. The right fix for missing read:org in the PAT flow is to create a new token with the required scope and reassign the environment variable.

Confidence Score: 3/5

• Safe to merge after correcting the gh auth refresh step in the PAT-based auth flow
• The companion app wording fix is straightforward. The new connectivity section is helpful, but step 3 gives instructions (gh auth refresh) that won't work in the scenario the section describes — using GH_TOKEN env var precisely because stored credentials don't exist. That's a concrete, fixable accuracy issue that would mislead contributors hitting this edge case.
• docs/platforms/windows.md — specifically the step 3 gh auth refresh instruction in the new "Git and GitHub connectivity" section

This is a comment left during a code review.
Path: docs/platforms/windows.md
Line: 262-265

Comment:
**`gh auth refresh` inapplicable in the env-var PAT flow**

Step 3 instructs the user to run `gh auth refresh -h github.com -s read:org`, but `gh auth refresh` operates on credentials stored via `gh auth login` — not on the `GH_TOKEN` environment variable set in step 2. Since the whole reason for using the env-var approach is that `gh auth login` failed due to network issues, there are no stored credentials to refresh, and this command will either fail or attempt to re-initiate the browser/device flow on the same blocked network.

The correct resolution in the PAT flow is to create a new token that already includes the `read:org` scope and reassign the variable — not to call `gh auth refresh`. (`gh auth refresh` is the right command only when the user has gone through `gh auth login` and needs to add scopes to a stored OAuth session, which is exactly the path this section works around.)

How can I resolve this? If you propose a fix, please make it concise.

_{Reviews (1): Last reviewed commit: "docs(windows): clarify companion app CTA..." | Re-trigger Greptile}

This PR only changes docs/platforms/windows.md. The failing WhatsApp extension-fast tests appear unrelated to this change. If I don't have permission to re-run CI on this repo, a maintainer could re-run the failed jobs.

Addressed Greptile’s note about the PAT env-var flow: when using \GH_TOKEN, we no longer recommend \gh auth refresh. If \gh auth status\ warns about missing
ead:org, the correct fix is to mint a new token that includes that scope and reassign $env:GH_TOKEN. The doc also clarifies that \gh auth refresh\ only applies when you authenticated via \gh auth login\ and have stored credentials to refresh.

@openclaw-barnacle This PR is now MERGEABLE + CLEAN, and checks are green (or marked as skipping). Also, Greptile’s note about the PAT env-var flow has been addressed in the doc: for the \GH_TOKEN\ path we no longer recommend \gh auth refresh; if \gh auth status\ warns about missing
ead:org, the guidance is to mint a new token including that scope and reassign $env:GH_TOKEN. If you have a moment, could you please take a look and merge? Thanks!

Codex review: needs changes before merge.

Summary
The PR edits docs/platforms/windows.md to fix duplicated Windows companion-app wording and add Windows contributor guidance for GitHub connectivity and PAT-based gh authentication.

Reproducibility: not applicable. this is a docs-only PR, not a runtime bug. The high-confidence check is comparing current main with the PR head and GitHub's mergeability state.

Next step before merge
The remaining blocker is a narrow one-file branch update/conflict repair that automation can attempt; maintainer merge and docs-scope judgment remain afterward.

Security
Cleared: The diff is documentation-only and explicitly warns not to commit or paste tokens; it does not change code, CI, dependencies, or secret storage.

Review findings

• [P2] Resolve the Windows docs conflict — docs/platforms/windows.md:273

Maintainer prep done for this docs-only PR.

What changed from the stale branch:

• rebased the content onto current main
• preserved the current Windows docs structure, WSL/source-dev guidance, and Related links
• kept the companion-app wording fix and the Git/GitHub connectivity note
• kept the PAT guidance from the earlier review fix: GH_TOKEN users should mint a token with the needed scopes; gh auth refresh only applies to stored gh auth login credentials

Prepared head: bdb37d7e82f509ed31dcf3fe666d0f410ea39892

Local verification:

• git diff --check
• pnpm exec oxfmt --check --threads=1 docs/platforms/windows.md
• pnpm check:docs

CI is green after applying proof: override; this is docs-only and the docs validation above is the behavioral proof for the change.