[SaladDay]

Change

Give incoming issues a type and needs-triage, including the documentation form. Preserve Desktop and CLI intake while clarifying that the published source covers the standalone CLI. Allow policy questions without forcing a product or platform selection. Add contribution-policy guidance to the issue chooser and document manual triage for type, product and pending assessment/information.

The label scheme draws on VS Code's triage guide and Ruff's labels. Code and documentation PRs remain collaborator-only. Everyone may report issues and suggest improvements; an accepted issue does not authorize an external PR.

No product code, repository permissions, notification workflow, automatic closing, or PR eligibility controls are changed.

Validation

• PASS: git diff --check.
• PASS: pnpm test:release-tools, including the new four-form label and contribution-policy regression.
• PASS: pnpm verify, all 14 gates at 3b2253e, full profile on macOS, Node 26.7.0 and pinned pnpm 9.12.0.
• NOT RUN: Windows/Linux execution and live GitHub issue submission using the unmerged templates. No synthetic public issue was created. CI remains required before merge.

Publication and contribution checks

• Existing file licenses and attribution are preserved; no imported implementation.
• No credentials, account data, private source history, or review material added.
• No source files added or removed; no inventory regeneration needed. The regression is in the existing release-tool test gate.
• English maintainer guidance updated. README entry points and product behavior are unchanged.

Maintainer handoff

Three labels were added: cli, needs-triage and needs-info. The existing desktop label is reused. All 90 open issues in the snapshot now have labels: 74 await maintainer assessment and 3 await requested information. Existing type labels were preserved except #119, whose explicit login-failure report was corrected from question to bug. No issues were closed, assigned, or marked high priority.

Product labels are applied manually: desktop or cli (TUI, headless, ACP and source builds/tooling). Unclear reports and repository-policy questions remain without a guessed product label. There is no repository or priority-label layer. The Feishu workflow still only sends notifications. Keep good first issue and help wanted unused while external PRs are closed.

Shared-source port: not needed; public repository support configuration and maintainer guidance only.

---

^{Need help on this PR? Tag @codesmith-bot with what you need. Autofix is disabled.}