docs: add GITOPENCLAW-How-to-be-like-GITCLAW.md

[Copilot]

Summary

• Problem: No documentation explaining the "fork is the installation" model — how .GITOPENCLAW differs from .GITCLAW's npm dependency approach
• Why it matters: Users need to understand that forking the OpenClaw source repo IS the installation — no npm install openclaw step, always up to date via git fetch upstream
• What changed: New doc at .GITOPENCLAW/docs/GITOPENCLAW-How-to-be-like-GITCLAW.md; updated docs/README.md with link
• What did NOT change: No code, config, lifecycle scripts, or workflows modified

Change Type (select all)

• Bug fix
• Feature
• Refactor
• Docs
• Security hardening
• Chore/infra

Scope (select all touched areas)

• Gateway / orchestration
• Skills / tool execution
• Auth / tokens
• Memory / storage
• Integrations
• API / contracts
• UI / DX
• CI/CD / infra

Linked Issue/PR

User-visible / Behavior Changes

None

Security Impact (required)

• New permissions/capabilities? No
• Secrets/tokens handling changed? No
• New/changed network calls? No
• Command/tool execution surface changed? No
• Data access scope changed? No

Repro + Verification

Environment

• Docs-only change, no runtime environment needed

Steps

1. Read .GITOPENCLAW/docs/GITOPENCLAW-How-to-be-like-GITCLAW.md
2. Verify links in .GITOPENCLAW/docs/README.md

Expected

• Document renders correctly, all relative links resolve

Actual

• As expected

Evidence

• Screenshot/recording — N/A, markdown docs only

Human Verification (required)

• Verified scenarios: Document structure, internal links, consistency with existing .GITOPENCLAW and .GITCLAW docs
• Edge cases checked: Link paths verified against actual repo structure
• What you did not verify: Rendering on GitHub (will be visible once merged)

Compatibility / Migration

• Backward compatible? Yes
• Config/env changes? No
• Migration needed? No

Failure Recovery (if this breaks)

• How to disable/revert this change quickly: Revert commit — docs only
• Files/config to restore: .GITOPENCLAW/docs/README.md (one line removed)
• Known bad symptoms reviewers should watch for: Broken relative links

Risks and Mitigations

None

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.