docs: update homepage RoleWeave downloads to v0.1.2

[PeterGuy326]

Tracking record

Refs #37, R1. Follow-up to #28/#29/#30: RoleWeave v0.1.2 was published on 2026-09-12, but the merged homepage still offers the v0.1.1 installers. The owner authorized this version refresh before sharing the organization page with the company group.

Summary

Both profile READMEs (English and Simplified Chinese) now point the explicit RoleWeave download buttons and release-notes link at the published v0.1.2 assets, and the installer note states v0.1.2. The signing limitation text, Qoder CLI host requirement, and every other byte of the merged homepage are unchanged. No avatar, brand asset, copy rewrite, organization settings, permissions, CI, or other file changes.

Acceptance criteria

Acceptance criterion	Status	Implementation / evidence
#37 REQ-001 / AC-001: both languages link the real public v0.1.2 assets and notes page; no v0.1.1 download reference remains	PASS	Diff replaces all six 0.1.1 occurrences per file; grep -c "0\.1\.1" returns 0 on both files at head; all three v0.1.2 URLs return HTTP 200 (checked anonymously with curl)
#37 REQ-002 / AC-002: installer note states v0.1.2 and keeps the accurate constraints	PASS	Note now reads "The current v0.1.2 installers…" / "当前 v0.1.2 安装包…"; platform scope, unsigned status, and Qoder CLI 1.1.x requirement unchanged and consistent with the v0.1.2 release notes
#37 REQ-003 / AC-003: governance, brand, and whitespace checks pass; both documents render; languages agree	PASS locally (see ledger); required remote CI must pass on the candidate head

Validation ledger

Command or check	Expected	Actual	Evidence
ruby scripts/validate-governance.rb (clean checkout of head, UTF-8 locale)	exit 0	exit 0	"Validated 5 issue forms, issue template config, 7 required files, and local Markdown links."
ruby scripts/validate-brand-assets.rb	exit 0	exit 0	"Validated 5 ByteFolk SVGs and one opaque 1024x1024 RGB avatar."
git diff --check 0aaff62…HEAD	no whitespace errors	clean	no output
git diff --stat 0aaff62…HEAD	only the two profile files	2 files, 4 insertions(+), 4 deletions(-)	profile/README.md, profile/README.zh-CN.md
Anonymous HTTP HEAD on the three v0.1.2 URLs	200 each	200 each	dmg, exe, and release tag pages
GitHub Actions Governance on the PR head	pass	pending	required remote check

Tests and coverage

• Tests added or changed: none; documentation-only change. The repository's executable checks (governance, brand, whitespace) cover it and were run locally at head.
• Coverage before / after, when measured: not applicable; no runtime code.
• Intentionally uncovered behavior and reason: none.

Change classification

• User-visible behavior
• Internal refactor or maintenance
• Documentation only
• Build, CI, dependency, or repository configuration
• Breaking change
• Security-sensitive change

Risk and rollback

• Risk level and affected components: minimal; two profile documents, four lines each.
• Compatibility, migration, privacy, performance, or operational impact: none; no runtime, data, or settings change.
• Rollback procedure: focused revert PR of the two profile files, or restore the v0.1.1 strings.

Breaking or security notes

None.

Author checklist

• A maintainer confirmed that the linked issue or tracking record was ready before implementation began, or the automation was pre-authorized under GOVERNANCE.md.
• This branch was created from an up-to-date default branch and contains no unrelated changes.
• I ran the repository's applicable tests, lint, type checks, builds, coverage, and security checks.
• I added a regression test for a bug fix, or explained why one is impractical.
• I updated relevant documentation and changelog files.
• I reviewed the diff for secrets, personal data, generated artifacts, and dependency risk.
• The PR is ready for CI and review by someone other than the sole author.
• All reported results are reproducible.

Reviewer notes

• The change is a pure version-string refresh; verify with git diff origin/main...HEAD that only the two RoleWeave sections differ.
• Independent check worth reproducing: grep -rn "0\.1\.1" profile/ returns nothing at head, and the three v0.1.2 URLs resolve anonymously.
• Required CI and a fresh CODEOWNER approval from a non-author reviewer are merge gates; squash merge after conversations are resolved.

[Bindy-lbb]

Reviewed. Diff is exactly the version-string refresh described: 4 lines changed in each of profile/README.md and profile/README.zh-CN.md, updating the three RoleWeave links (arm64 dmg, x64 exe, release notes tag) and the installer note from v0.1.1 to v0.1.2. No other content touched.

Independently verified:

• All three v0.1.2 URLs resolve with HTTP 200 (checked anonymously).
• The GitHub release v0.1.2 exists with both installer assets present (roleweave-0.1.2-arm64.dmg, roleweave-0.1.2-x64.exe).
• Governance check is green.

LGTM, approving.