Complete contributor entry points and cross-repository delivery #39

External contributors need working question and task entry points, clear PR handoffs, and a path through actual delivery. This issue tracks the GitHub collaboration setup and remaining cross-repository contribution improvements. Coordination contact: @xiaoland.

GitHub collaboration

• Enable organization Discussions with .github as the source repository.
• Publish and pin the community navigation.
• Review and merge .github#36: default issue forms, SUPPORT, contribution triage, and PR handoff. Verify inherited Bug/Task forms and native types in impl-swift and impl-ts after merging.
• Use native issue types, keep Status/Priority in the mixed issue-and-PR Project, and retain only useful discovery, automation, and historical labels. Record next actions on existing issues.
• Use Project Convert Organization Launch milestone's issues into document #12 for current collaboration and identify other boards as historical.
• Record next responders and delivery dependencies on this task's PRs.
• Qualify a small, credential-free newcomer task: docs#45, linking the website contribution guide to Q&A, Ideas, and current work.
• Resolve historical umbrellas with explicit outcomes: workflow documentation #8 completed; broad automation #9 and retired-site TLS #21 closed as not planned.

Code and documentation delivery

• Publish the original UI release tarballs and verify their final URLs anonymously.
• Preserve package.json semver in impl-ts; merge exact-version overrides and the regenerated lockfile in #171.
• Verify a fresh frozen install without npm authentication, consumer builds, and real fork CI in #171; five ordinary checks passed, both trusted previews skipped. Main delivery also passed.
• Release the corrected CLI and update the website's supported installation instructions.

The source fix in impl-py#153 is merged and main delivery passed. The CLI publication workflow skipped upload because the version was unchanged. The generated impl-py#161 now includes CLI 0.3.0 and an existing Core 0.9.0 release change; that cross-project release has not been merged as part of the CLI source-fix cleanup.

The maintainer explicitly authorized the UI backfill, merging ui#64 / .github#36, and then merging the verified consumer #171. All are merged and current impl-ts main installs the existing UI versions from verified public URLs. No organization package token is required for contribution setup.

The public original tarballs match Registry and consumer-lockfile SHA-512. UI #64 preserves the current Logo/SwiftPM release workflow and passed its full local check, GitHub checks, and merged-main release workflow. The consumer lockfile also preserves all unrelated resolutions. #171 passed a cold-cache public-URL install and the full Workspace contract plus both browser E2E lanes in real fork CI. A separate macOS empty-store/no-token install and all consumer builds also passed after extending only the local download timeout for large third-party tools.

Release reconciliation found the README Changeset in #64 was already delivered in 2.6.0. ui#73 removes it; the redundant 2.6.1 proposal ui#72 is held as draft. Merging the correction also triggers the existing workflow to mirror the original 2.6.0 tarball, which requires the additional explicit merge/publication decision documented in #73. No new npm version is needed.

A small newcomer opportunity is docs#45. docs#44 remains a broader self-hosting verification task for contributors comfortable with deployment. Historical issue conclusions remain on the original threads; age alone is not a reason to close them.

Completion requires usable question and task entry points, visible PR handoff ownership, templates active on main, and actual anonymous-consumer evidence for any installation blocker claimed as resolved. Track collaboration setup and package publication separately.