docs: add onboarding outreach and feedback templates

Author: dtsong

.github/ISSUE_TEMPLATE/config.yml

@@ -1,5 +1,8 @@
 blank_issues_enabled: true
 contact_links:
+  - name: Manual onboarding feedback form
+    url: https://github.com/dtsong/my-opencode-codex-setup/blob/main/docs/onboarding-feedback.md
+    about: Use this if a tester cannot submit a GitHub issue directly.
   - name: Discussions
     url: https://github.com/dtsong/my-opencode-codex-setup/discussions
     about: Ask open-ended questions and share ideas.

.github/ISSUE_TEMPLATE/onboarding_feedback.md

@@ -0,0 +1,47 @@
+---
+name: Onboarding feedback
+about: Share first-time setup experience for council-lite onboarding validation.
+title: "onboarding: "
+labels: ["question"]
+assignees: []
+---
+
+## Participant
+
+- Alias/name:
+- Date:
+
+## Environment
+
+- OS:
+- Shell:
+- Repo tag/commit tested:
+
+## Commands Run
+
+```text
+Paste exact commands run.
+```
+
+## Outcome
+
+- Result: success | partial | fail
+- Time-to-first-success (minutes):
+
+## Friction Points
+
+What was confusing, slow, or unclear?
+
+## Errors/Output
+
+```text
+Paste relevant logs/errors.
+```
+
+## Suggestions
+
+What would make onboarding easier for a first-time user?
+
+## Recommendation
+
+- Would you recommend this onboarding flow to a friend? yes | no | maybe

README.md

@@ -106,3 +106,5 @@ See `docs/workflows-playbook.md` for usage patterns.
 - practical usage examples in `examples/`
 - release checklist in `docs/release-checklist.md`
 - launch checklist in `docs/open-source-launch.md`
+- friend outreach message in `docs/friend-outreach-template.md`
+- onboarding feedback channels in `docs/onboarding-feedback.md`

docs/friend-outreach-template.md

@@ -0,0 +1,35 @@
+# Friend Outreach Template
+
+Use this message when inviting friends to help validate onboarding.
+
+## Copy/Paste Message
+
+Hey! I am testing onboarding for my OpenCode/Codex setup and would love your help.
+
+Goal: verify whether a new user can get from clone to a successful council-lite run quickly and clearly.
+
+If you are up for it, please run these steps:
+
+```bash
+git clone https://github.com/dtsong/my-opencode-codex-setup.git
+cd my-opencode-codex-setup
+./install.sh --conflict-policy skip --profiles core,council-lite
+./scripts/council-lite.sh run "Onboarding validation run"
+./scripts/council-lite.sh list
+./scripts/validate-council-lite.sh --latest
+./install.sh --uninstall
+```
+
+Then share feedback in one of two ways:
+
+1. Open a GitHub issue using the "Onboarding feedback" template
+2. Send me the manual feedback form in `docs/onboarding-feedback.md`
+
+What I need from you:
+- OS + shell
+- whether it succeeded (`success` | `partial` | `fail`)
+- time-to-first-success (minutes)
+- any confusion points or rough edges
+- what would make this easier for new users
+
+Thank you - this feedback directly decides when council-lite can move from beta to stable.

docs/onboarding-feedback.md

@@ -0,0 +1,59 @@
+# Onboarding Feedback Guide
+
+This guide provides two fast channels for onboarding feedback:
+
+1. GitHub issue template (preferred)
+2. Manual form (copy/paste)
+
+Related tracker issue: `#6`
+
+## Option 1: GitHub Issue Template (Preferred)
+
+Open a new issue and choose **Onboarding feedback**:
+
+- URL: `https://github.com/dtsong/my-opencode-codex-setup/issues/new/choose`
+- Template file: `.github/ISSUE_TEMPLATE/onboarding_feedback.md`
+
+Why preferred:
+- keeps feedback structured and searchable
+- makes follow-up actions easier to triage
+- links directly to onboarding validation tracking
+
+## Option 2: Manual Feedback Form
+
+Copy and fill this template if someone cannot use GitHub issues:
+
+```markdown
+## Onboarding Feedback
+
+- Participant alias:
+- Date:
+- OS:
+- Shell:
+- Repo commit/tag used:
+
+### Commands Run
+```text
+Paste exact commands run.
+```
+
+### Result
+- Outcome: success | partial | fail
+- Time-to-first-success (minutes):
+
+### Friction Points
+-
+
+### Errors/Output (if any)
+```text
+Paste relevant logs or errors.
+```
+
+### Suggested Improvements
+-
+
+### Would you recommend this onboarding flow?
+- yes | no | maybe
+```
+
+If feedback is collected manually, add it as a comment on issue `#6` so it counts toward the 3-confirmation gate.

docs/open-source-launch.md

@@ -32,9 +32,11 @@ This is separate from `docs/release-checklist.md`, which is for recurring versio
 - [ ] GitHub release drafted with highlights and known limitations
 - [ ] launch announcement copy prepared (X/LinkedIn/GitHub Discussion)
 - [ ] first 3-5 starter issues prepared for contributors
+- [ ] friend outreach template is ready (`docs/friend-outreach-template.md`)
 
 ## Post-launch Follow-up
 
 - [ ] monitor first-week issues and triage daily
 - [ ] collect onboarding friction points from early users
+- [ ] onboarding feedback issue template/manual form are active (`docs/onboarding-feedback.md`)
 - [ ] publish first-week patch release plan