Merge pull request #11 from dtsong/docs/open-source-launch-day-one

docs: record launch readiness and day-one operations

Author: dtsong

.github/workflows/validate.yml

@@ -72,6 +72,8 @@ jobs:
     steps:
       - name: Checkout
         uses: actions/checkout@v4
+        with:
+          fetch-depth: 0
 
       - name: Run gitleaks
         uses: gitleaks/gitleaks-action@v2

docs/first-week-patch-plan.md

@@ -0,0 +1,38 @@
+# First-Week Patch Plan
+
+This plan defines how we handle the first week after open-source launch.
+
+## Daily Cadence (Days 1-7)
+
+1. Check new GitHub issues twice daily (morning/evening local time).
+2. Triage each issue into one of: `bug`, `docs`, `enhancement`, `question`.
+3. Add priority tags manually in issue body if needed: P0/P1/P2.
+4. Respond to onboarding feedback within 24 hours.
+5. Log recurring friction points in issue #6.
+
+## Patch Criteria
+
+Cut a first-week patch release when any of the following happen:
+- one confirmed onboarding blocker (`fail` outcome)
+- two or more users report the same setup/documentation confusion
+- any security-sensitive report needing remediation
+
+## Candidate Scope for First Patch
+
+- installer conflict messaging clarity
+- README quick-start and troubleshooting improvements
+- council-lite docs clarity and validation examples
+- minor script robustness fixes without breaking interfaces
+
+## Target Timeline
+
+- Day 1-2: collect issues and cluster by theme
+- Day 3-4: implement highest-impact fixes
+- Day 5: run full release checklist and smoke tests
+- Day 6-7: publish patch tag/release notes and close loop with reporters
+
+## Owner Checklist
+
+- keep `docs/release-checklist.md` green before tagging
+- include migration/behavior notes in release body
+- link fixes back to original issue IDs

docs/launch-announcement.md

@@ -0,0 +1,63 @@
+# Launch Announcement Copy
+
+Use these drafts for launch day. Edit version/tag and call-to-action links before posting.
+
+## GitHub Discussion / Long Form
+
+`my-opencode-codex-setup` is now open source.
+
+This repo is a practical OpenCode + Codex starter inspired by `my-claude-setup`, focused on reusable agents, structured skills, and executable workflow scripts.
+
+Highlights in `v0.2.0`:
+- profile-aware installer (`core`, `council-lite`, `council-research`)
+- council-lite session lifecycle (`run`, `list`, `resume`)
+- council-lite artifact validation and CI smoke coverage
+- launch-ready docs, templates, and policy files
+
+If you want to try it, start here:
+
+```bash
+git clone https://github.com/dtsong/my-opencode-codex-setup.git
+cd my-opencode-codex-setup
+./install.sh --profiles core,council-lite
+./scripts/council-lite.sh run "First run"
+./scripts/validate-council-lite.sh --latest
+```
+
+Contributions are welcome. Good starter issues:
+- #7
+- #8
+- #9
+- #10
+
+If onboarding feels rough anywhere, please open an issue using the onboarding feedback template.
+
+## X / Short Form
+
+I just open sourced `my-opencode-codex-setup`.
+
+Portable OpenCode + Codex starter with:
+- reusable agents + practical skills
+- profile-aware installer
+- council-lite `run/list/resume` flow
+- launch-ready OSS docs/templates
+
+Repo: https://github.com/dtsong/my-opencode-codex-setup
+Start: `./install.sh --profiles core,council-lite`
+Feedback: onboarding issue template in repo
+
+## LinkedIn / Medium Form
+
+I am open sourcing `my-opencode-codex-setup`, a portable OpenCode + Codex setup inspired by `my-claude-setup`.
+
+The goal is practical reuse: agents, skills, workflows, and profiles you can adopt quickly without rebuilding everything from scratch.
+
+What is included:
+- profile-aware installer and clean uninstall path
+- `council-lite` session scaffolding with artifact validation
+- CI smoke checks across Linux/macOS and secret scanning
+- contributor docs, templates, and launch readiness checklists
+
+Try it: https://github.com/dtsong/my-opencode-codex-setup
+
+If you test onboarding, I would especially value friction-point feedback via the repo onboarding template.

docs/open-source-launch.md

@@ -6,37 +6,42 @@ This is separate from `docs/release-checklist.md`, which is for recurring versio
 
 ## Repository Settings
 
-- [ ] repository description and topics are current
-- [ ] default branch protection is configured (required checks and no force push)
-- [ ] Discussions is enabled (if using community support flow)
-- [ ] issue labels are seeded (`bug`, `enhancement`, `docs`, `question`, `good first issue`)
+- [x] repository description and topics are current
+- [x] default branch protection is configured (required checks and no force push)
+- [x] Discussions is enabled (if using community support flow)
+- [x] issue labels are seeded (`bug`, `enhancement`, `docs`, `question`, `good first issue`)
 
 ## Community and Policy
 
-- [ ] `README.md` includes quick start and support expectations
-- [ ] `CONTRIBUTING.md` includes local validation and PR guidance
-- [ ] `CODE_OF_CONDUCT.md` and `SECURITY.md` are reviewed and current
-- [ ] issue/PR templates are reviewed for launch wording
+- [x] `README.md` includes quick start and support expectations
+- [x] `CONTRIBUTING.md` includes local validation and PR guidance
+- [x] `CODE_OF_CONDUCT.md` and `SECURITY.md` are reviewed and current
+- [x] issue/PR templates are reviewed for launch wording
 
 ## Technical Launch Readiness
 
-- [ ] CI passes on pull requests and main
-- [ ] secret scanning passes
-- [ ] installer/profile flow tested on a clean environment
-- [ ] council-lite run/list/resume/validate flow tested end-to-end
+- [x] CI passes on pull requests and main
+- [x] secret scanning passes
+- [x] installer/profile flow tested on a clean environment
+- [x] council-lite run/list/resume/validate flow tested end-to-end
 
 ## Release and Communication
 
-- [ ] `CHANGELOG.md` has release notes for launch tag
-- [ ] launch tag created (for example, `v0.2.0`)
-- [ ] 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`)
+- [x] `CHANGELOG.md` has release notes for launch tag
+- [x] launch tag created (for example, `v0.2.0`)
+- [x] GitHub release drafted with highlights and known limitations
+- [x] launch announcement copy prepared (X/LinkedIn/GitHub Discussion)
+- [x] first 3-5 starter issues prepared for contributors
+- [x] 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
+- [x] onboarding feedback issue template/manual form are active (`docs/onboarding-feedback.md`)
+- [x] publish first-week patch release plan
+
+## Notes
+
+- Launch announcement drafts: `docs/launch-announcement.md`.
+- First-week triage and patch procedure: `docs/first-week-patch-plan.md`.