docs: refresh the ByteFolk homepage around released products

[PeterGuy326]

Current approved revision: R2 supersedes R1 REQ-004 / AC-004 for the homepage headers. Both headers follow the live organization avatar; avatar restoration is tracked separately in #18.

ByteFolk homepage refresh — R1

DEC-BYTEFOLK-PROFILE-001 · 2026-09-08T03:15:14.132Z · status=ready

The owner requested an update of https://github.com/bytefolk. The current profile still calls the desktop product Org Workbench and says no installer release exists, although RoleWeave v0.1.1 is public. Visitors must currently read long component descriptions before finding a usable entry point.

Scope

Refresh the public profile README with the existing approved ByteFolk symbol, clearer hierarchy, concise user-oriented copy, desktop and CLI entry points, and a compact component directory. Add a Simplified Chinese companion for the same information. This is a documentation-only homepage change, not a new product claim or brand redesign. Related branding roadmap: #25.

Requirements and acceptance

• REQ-001 / AC-001: prominent RoleWeave entry uses the canonical repository, a real public v0.1.1 release, and macOS Apple Silicon / Windows x64 downloads; the unsigned OS-signing limitation remains visible. No stale no-installer claim.
• REQ-002 / AC-002: offer the released Digital Employee CLI and a credential-free offline quickstart without claiming model quality, deployment readiness, or automatic cross-product integration.
• REQ-003 / AC-003: distinguish mem MCP binaries from source-only UI/API setup; doc and design-system remain source previews. List only verified public repositories.
• REQ-004 / AC-004: keep the approved symbol geometry unchanged; support light/dark GitHub rendering; English and Simplified Chinese links and release facts agree.
• REQ-005 / AC-005: repository governance/brand checks, link verification, and GitHub-rendered preview pass before review.

Non-goals and boundaries

No avatar replacement, repository renaming, pin reordering, organization settings, permissions, policy, CI changes, secrets, installer rebuilding, or private repository disclosure. Existing checkout changes remain untouched. Use a dedicated branch and ordinary PR. This repository's required CODEOWNER approval is not waived by an exception previously granted for RoleWeave.

Validation and rollback

Verify releases and public visibility through GitHub; run ruby scripts/validate-governance.rb and ruby scripts/validate-brand-assets.rb; inspect GitHub-rendered Markdown and all public links. Review the final diff for private data and unsupported claims. Rollback is a focused revert PR of the two profile files. No runtime or data migration.

R1 approved scope derives from the owner's request to optimize and update the organization homepage. Publication remains gated by this repository's checks and independent approval.

[PeterGuy326]

Homepage avatar correction — R2 (ready)

DEC-BYTEFOLK-PROFILE-002 · 2026-09-08 · status=ready

The owner explicitly requested that the homepage reuse the current ByteFolk organization avatar, then authorized submitting the correction and merging after the current checks and independent approval pass. PR #29 was merged while this follow-up was being prepared, so its published content is preserved and the correction will use a focused follow-up PR from main.

R2 inherits R1 REQ-001/AC-001 through REQ-003/AC-003 and REQ-005/AC-005. It supersedes only REQ-004/AC-004 for the homepage image source:

• REQ-004 / AC-004: Both profile documents use the current public avatar URL returned by GET /orgs/bytefolk, currently https://avatars.githubusercontent.com/u/309981672?v=4, with meaningful localized alt text and unchanged 72-by-72 dimensions. No alternate black/white SVG is selected by theme. Reuse the original avatar without recropping or recoloring it.
• Preserve every byte after the first closing paragraph in both documents, all product links, repository brand assets, organization settings and permissions.
• Verify the original mismatch, both corrected headers, GitHub GFM rendering, avatar availability, repository governance/brand validators, and whitespace checks. Inspect a GitHub preview before publication. A green asset validator is not evidence that external URLs or README image choices were checked.
• No avatar upload or redesign, runtime change, dependency change, protected-branch exception, force push, or unrelated copy change. Rollback is a focused revert PR of the header-only correction.

Reopening this tracking record covers the requested avatar correction only; the R1 homepage refresh remains delivered by PR #29. R2 publication remains subject to a fresh independent CODEOWNER approval.

[PeterGuy326]

Closing as completed. Re-verified against main just now rather than relying on the delivery comments:

• profile/README.md:2 — <img src="https://avatars.githubusercontent.com/u/309981672?v=4" alt="ByteFolk organization avatar" width="72" height="72">
• profile/README.zh-CN.md:2 — <img src="https://avatars.githubusercontent.com/u/309981672?v=4" alt="ByteFolk 组织头像" width="72" height="72">
• GET /orgs/bytefolk → avatar_url = https://avatars.githubusercontent.com/u/309981672?v=4

All three agree, so R2 REQ-004 / AC-004 holds: both profile documents use the current public avatar URL, alt text is localized per document, and the 72-by-72 dimensions are unchanged. No stale black/white SVG is selected by either header.

Delivery was #29 (99c967a04b) for the R1 homepage refresh plus #30 (7aa4a5b65d) for the avatar correction. Neither carried a closing keyword, which is why this stayed open. Reopen if a REQ-001/002/003/005 acceptance point is found unmet.