[huangruiteng]

Goal And Delivered Outcome

Move Community & Contributing near the end of both READMEs so the product, capability and documentation reading path stays continuous. The section is now third from last:

Current Status → Community & Contributing → Star History → License

Previously it appeared between Capabilities and Partner Projects. This is the maintainer-requested placement amendment to merged PR #7394, targeting main.

Author Declaration

Written by: model_agent — OpenAI Codex.

Implemented against

No separate written specification; the placement request described above is the basis. Presentation guidance: docs/development/design.md at base 8cb50a2cd2f382378264545b7168f52967e2fe9e.

Criterion	Disposition	Paths / evidence
Community near the end, before the popularity and legal footer	implemented	Both READMEs end with Community, Star History and License as their final three H2 sections
Keep the strengthened content and contributor avatars	implemented	Exact source parity for the moved block, including QR codes, links, privacy disclosure and legacy anchors
Keep English and Chinese placement aligned	implemented	README.md, README.zh-CN.md; heading-order and browser checks

Scope And Continuation

Complete within this scope. Only the two root READMEs change. The section moves intact; all bytes outside the moved block are retained. No runtime, permission, workflow or dependency changes. No successor is needed for this amendment.

Validation

• Tested revision: c5b1129174cc8aa637629be42c4f473bea736436
• Run state: finished
• Input classes: public_fixture

Check kind	Result	Public-safe evidence / limitation
static	passed	Source comparison confirms identical moved blocks and identical remaining content, every explicit anchor retained, one avatar wall per language, and the final H2 order
static	passed	git diff --check origin/main HEAD
static	passed	uv run --extra test loopx --format json canary premerge --from-git-diff --git-diff-base origin/main --no-progress: four direct checks and all 13 selected checks pass, including the public-boundary check
static	failed	Standalone loopx check --scan-path README.md --scan-path README.zh-CN.md: both README boundary scans are clean; the composite command still reports two existing local Goal canonical-authority errors, unrelated to these files
manual	passed	Ego Lite browser, GitHub Markdown-rendered footer excerpts: English/Chinese desktop at 1120px and narrow at 390px; avatars and QR images load, no horizontal overflow
real_backend	not_applicable	Documentation ordering only; no application or provider behavior changed

Coverage: exact source preservation covers every retained link and disclosure without revalidating unchanged external destinations. Browser evidence below shows the footer's new reading order; the preview uses GitHub-rendered Markdown in a lightweight reading frame, not the full GitHub page chrome.

Frontend / Visual Evidence

• UI impact: changed
• Before: Current Status leads directly into Star History and License; Community is earlier in the README.
• After: Community follows Current Status and precedes Star History and License.
• Source data: public_fixture — public README text and existing public images only.
• Tested boundary: before is base 8cb50a2cd2f382378264545b7168f52967e2fe9e; after is c5b1129174cc8aa637629be42c4f473bea736436. No separately hosted preview.
• Attention review: product and technical content stays together; participation and contributor recognition close the reading path. No new panels or explanatory copy.
• Craft review: native Markdown headings and existing image treatment retained. This move adds no visual tokens or interactive states.

Desktop footer — before and after

English before	English after

Chinese before	Chinese after

Narrow footer — 390px

English after	Chinese after

Type of Change

• Documentation update

LoopX Area

• Public docs or presentation surface (README, protocols, dashboard)

Shared-authority RFC fixture impact

N/A — no control-plane, authority or RFC changes.

Boundary Checklist

• Diff, description and attachments contain only public-safe material.
• No maintainer-owned benchmark work duplicated.
• Change scoped to the requested README amendment.
• No paired RFC changed; bilingual check passes.
• Before/after visual evidence included above.
• Commit includes a DCO Signed-off-by trailer.