docs: note the interim go install path after the module rename

[steipete]

The module rename landed in #970, but go install github.com/openclaw/gogcli/cmd/gog@latest fails today: @latest still resolves v0.34.2, which declares the old module path.

Verified locally:

• @latest (new path) → module declares its path as: github.com/steipete/gogcli
• @main via the public proxy → same error from a stale cached pseudo-version
• @main with GOPROXY=direct → resolves v0.34.3-0.20260809060808-342ffd1f8be9 and runs
• go install github.com/steipete/gogcli/cmd/gog@v0.34.2 → works, reports v0.34.2

This documents the working pinned command until the first post-rename tag ships, so the README does not carry an instruction that fails. The @latest line stays as the steady-state form.

[clawsweeper]

Codex review: needs maintainer review before merge. Reviewed August 9, 2026, 2:12 AM ET / 06:12 UTC.

ClawSweeper review

What this changes

The PR adds an interim README command that installs the last pre-rename release from the former Go module path until a new-path release is tagged.

Regression provenance

Possible regression — probable (reviewed change; known regression link). No predecessor PR is attributed.

Merge readiness

✅ Ready for maintainer review

Keep open: current main changed the Go module path but still advertises a new-path @latest command before a post-rename release contains it. This focused README correction remains necessary. Likely related people: steipete (high confidence).

Priority: P3
Reviewed head: 617b3a5a6f79611b09dcc31af3dc36a8d3cd2be0

Review scores

Measure	Result	What it means
Overall readiness	🐚 platinum hermit (4/6)	A focused, source-consistent documentation patch with no correctness or security finding.
Proof confidence	🌊 off-meta tidepool	Not applicable: This collaborator-authored documentation correction includes a concrete local install result in the PR body; the external-contributor proof gate does not apply.
Patch quality	🐚 platinum hermit (4/6)	No actionable review findings were identified.

Verification

Check	Result	Evidence
Real behavior	Not applicable	Not applicable: This collaborator-authored documentation correction includes a concrete local install result in the PR body; the external-contributor proof gate does not apply.
Evidence reviewed	4 items	Current installation guidance: Current main documents the new-path @latest command, while go.mod declares the renamed module path. Rename provenance and release status: Commit 342ffd1 renamed the module on current main; no local release tag contains that commit, while the supplied context identifies v0.34.1 as the latest release. README history: The current module-rename commit and recent README standardization work are attributed to Peter Steinberger in repository history.
Findings	None	None.
Security	None	None.

How this fits together

The README is the primary installation entry point for the gog command-line client. Its Go install command is resolved through Go module version metadata and produces the executable users run locally.

flowchart LR
A[README install instructions] --> B[Go install command]
B --> C[Go module resolution]
C --> D[Module path and version]
D --> E[gog executable]

Loading

Before merge

None.

Agent review details

Security

None.

Review metrics

Metric	Value	Why it matters
Documentation scope	1 file affected; 9 lines added, 0 removed	The patch is confined to the user-facing Go installation instructions.

Technical review

Best possible solution:

Merge the temporary guidance, then remove the old-path pin after the first release containing the renamed module so the new-path @latest command is again the sole Go-install recommendation.

Do we have a high-confidence way to reproduce the issue?

No live reproduction was run because Go installation would write module caches; current source confirms the renamed module is on main, and the PR body provides a concrete reported resolution path.

Is this the best way to solve the issue?

Yes. Until a release tag carries the renamed module path, documenting the known working old-path pinned install is the narrowest way to avoid a failing README command.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 342ffd1f8be9.

Labels

Label changes:

• add P3: This is a small temporary documentation correction with no runtime change.
• add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This collaborator-authored documentation correction includes a concrete local install result in the PR body; the external-contributor proof gate does not apply.

Label justifications:

• P3: This is a small temporary documentation correction with no runtime change.
• rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🌊 off-meta tidepool and patch quality is 🐚 platinum hermit.
• status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This collaborator-authored documentation correction includes a concrete local install result in the PR body; the external-contributor proof gate does not apply.

Evidence

What I checked:

• Current installation guidance: Current main documents the new-path @latest command, while go.mod declares the renamed module path. (README.md:34, 342ffd1f8be9)
• Rename provenance and release status: Commit 342ffd1 renamed the module on current main; no local release tag contains that commit, while the supplied context identifies v0.34.1 as the latest release. (go.mod:1, 342ffd1f8be9)
• README history: The current module-rename commit and recent README standardization work are attributed to Peter Steinberger in repository history. (README.md:34, 342ffd1f8be9)
• Proposed scope: The supplied PR diff modifies only README.md, adding nine lines of interim installation guidance and no code, dependency, or workflow changes. (README.md:38, 617b3a5a6f79)

Likely related people:

• steipete: Current-main history attributes the module rename and preceding README standardization work to Peter Steinberger, who is steipete in the supplied PR context. (role: module-rename author and recent README contributor; confidence: high; commits: 342ffd1f8be9, 0a3ebe9ad788; files: go.mod, README.md)

Rating scale

Score	Internal tier	Crab rank	Meaning
6/6	S	🦀 challenger crab	Exceptional readiness
5/6	A	🦞 diamond lobster	Very strong readiness
4/6	B	🐚 platinum hermit	Good normal PR; ordinary maintainer review
3/6	C	🦐 gold shrimp	Useful, but confidence is limited
2/6	D	🦪 silver shellfish	Proof or implementation needs work
1/6	F	🧂 unranked krab	Not merge-ready
N/A	NA	🌊 off-meta tidepool	Rating does not apply

Overall follows the weaker of proof and patch quality.
Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

Workflow

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.