[turinglambdaai]

Scope correction

Racket packages are developer libraries, not desktop apps or standalone marketing products. Add a focused EN/ZH maintainer standard for package-native README, Scribble API documentation, executable snippets, RackUnit/regression tests, package metadata, dependency verification and CI. Link it from both repository READMEs; do not change customer-facing HTML.

Key rules

• First-party libraries need a tested install/require/first-use path and normative Scribble, not an independently designed jrtx.site site, app screenshot or checkout flow.
• Preserve actual package-vs-collection metadata, source/API semantics, licenses and provenance of upstream/forks.
• Prioritize real failures and runnable examples; do not add unverified catalog links or benchmark claims.
• Product and content categories keep their own appropriate standards.

Reference package-quality issue #7; existing portfolio docs issue #5 retains the actual product pages and public claims. Source baseline: 2203a927b9947d3ab6f3e9cad9f2892d4f199497. No runtime/HTML change, revert is one isolated docs commit. Validate bilingual links and existing CI before merge.