Complete contributor entry points and cross-repository delivery #39

External contributors now have working question and task entry points, clear PR handoffs, and a verified path through setup and delivery. Coordination contact: @xiaoland.

GitHub collaboration

• Enable organization Discussions with .github as the source repository and pin the community navigation.
• Merge .github#36 and verify inherited Bug/Task forms and native types in impl-swift and impl-ts.
• Use native issue types, keep Status/Priority in the mixed issue-and-PR Project, and retain useful discovery, automation, and historical labels.
• Keep Project #12 as the current collaboration board and close obsolete boards while preserving their history.
• Record next responders and delivery dependencies on this task's PRs.
• Qualify credential-free newcomer task docs#45; retain broader self-hosting verification task docs#44 for contributors comfortable with deployment.
• Close historical umbrellas with explicit outcomes: workflow documentation Development workflow #8 completed; broad automation Automate the development workflow #9 and retired-site TLS SSL certification invalid for orgs-document #21 closed as not planned.

Code and documentation delivery

• Publish the original UI tarballs and verify final URLs anonymously against their Registry and consumer-lockfile SHA-512.
• Preserve package.json semver and unrelated resolutions in impl-ts, with exact-version public overrides.
• Verify cold public-URL installs without npm authentication, all consumer builds, and genuine fork CI; five ordinary checks passed and both trusted previews skipped. Main delivery passed.
• Publish the corrected CLI and update supported website installation instructions. The public CLI 0.3.0 wheel passed SHA-256 verification, fresh installation, v2 command help, and the three existing HTTP-boundary regression tests. The updated website passed checks, preview, main deployment, and public-page verification.

The duplicate UI 2.6.1 proposal ui#72 was closed without publication; the existing original 2.6.0 package was mirrored without rebuilding or overwriting it. No organization package token is required for contribution setup.

This contribution-delivery task is complete. The subsequent demo maintenance for Core 0.9.0 also completed successfully, including a verified recovery branch, migration, restored service, production protocol checks, and stable promotion. The actual Core reports 0.9.0 and readiness at the expected database contract.