docs: add launch checklist and council-lite quality gates

Author: dtsong

CHANGELOG.md

@@ -2,6 +2,32 @@
 
 All notable changes to this project are documented in this file.
 
+## [0.2.0] - 2026-02-11
+
+Profile platform and council-lite maturation release focused on OSS hardening.
+
+### Added
+
+- Profile management layer with registry/manifests and installer profile commands.
+- `council-lite` profile and session lifecycle workflow (`run`, `list`, `resume`).
+- Structured council-lite artifact generation under `memory/council-lite/<session-id>/`.
+- Council-lite artifact validator: `scripts/validate-council-lite.sh`.
+- CI matrix coverage on Linux and macOS.
+- Secret scanning in CI with gitleaks.
+- One-time launch checklist: `docs/open-source-launch.md`.
+- Council-lite promotion gates: `profiles/council-lite/QUALITY_GATES.md`.
+
+### Changed
+
+- Installer now supports explicit conflict handling policy (`--conflict-policy fail|skip`), with `fail` as default.
+- Profile and workflow docs updated for council-lite lifecycle and validation commands.
+- Release checklist expanded with conflict-policy and council-lite validation checks.
+
+### Notes
+
+- `council-lite` remains `beta` pending quality-gate completion.
+- `council-research` remains `experimental` and battle-testing-driven.
+
 ## [0.1.0] - 2026-02-11
 
 Initial public baseline release for `my-opencode-codex-setup`.

README.md

@@ -105,3 +105,4 @@ See `docs/workflows-playbook.md` for usage patterns.
 - `SECURITY.md` and `CODE_OF_CONDUCT.md`
 - practical usage examples in `examples/`
 - release checklist in `docs/release-checklist.md`
+- launch checklist in `docs/open-source-launch.md`

docs/open-source-launch.md

@@ -0,0 +1,40 @@
+# Open Source Launch Checklist
+
+Use this one-time checklist when preparing the first broad public launch.
+
+This is separate from `docs/release-checklist.md`, which is for recurring version releases.
+
+## 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`)
+
+## 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
+
+## 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
+
+## 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
+
+## Post-launch Follow-up
+
+- [ ] monitor first-week issues and triage daily
+- [ ] collect onboarding friction points from early users
+- [ ] publish first-week patch release plan

docs/profiles.md

@@ -52,6 +52,8 @@ This file is created or updated during install/profile changes.
 2. Enable `council-lite` when you want more orchestration.
 3. Try `council-research` only when you are comfortable with fast iteration and changing behavior.
 
+Council-lite promotion criteria are tracked in `profiles/council-lite/QUALITY_GATES.md`.
+
 After enabling `council-lite`, run:
 
 ```bash

docs/release-checklist.md

@@ -6,6 +6,7 @@ Use this checklist before tagging a release.
 
 - [ ] `README.md` reflects current scripts, skills, and agent docs
 - [ ] `docs/roadmap.md` reflects current phase status
+- [ ] `docs/open-source-launch.md` reviewed if this is a launch window
 - [ ] examples still run as documented
 - [ ] no local-only assumptions or paths leaked into docs
 

profiles/council-lite/QUALITY_GATES.md

@@ -0,0 +1,40 @@
+# Council Lite Quality Gates
+
+Use these gates to decide when `council-lite` can move from `beta` to `stable`.
+
+## Scope
+
+Applies to:
+
+- `scripts/council-lite.sh`
+- `scripts/validate-council-lite.sh`
+- related profile/install and docs behavior
+
+## Promotion Gates (Beta -> Stable)
+
+- [ ] at least 20 documented real-world council-lite runs
+- [ ] at least 95% artifact validation pass rate over the last 20 runs
+- [ ] no critical data-loss or session-index corruption issues in the last 10 runs
+- [ ] no P1/P2 installer-profile regressions in the last 2 releases
+- [ ] onboarding validated by at least 3 users from clean setup to first successful run
+
+## Operational Gates
+
+- [ ] `run`, `list`, `resume`, and validator commands pass in CI
+- [ ] installer conflict-policy behavior (`fail` and `skip`) is tested and documented
+- [ ] uninstall leaves no managed profile state behind
+- [ ] docs are synchronized (`README`, `docs/profiles.md`, workflow docs, changelog)
+
+## Evidence Requirements
+
+- [ ] run log entries with date, scenario, and outcome
+- [ ] known limitations list reviewed before each release
+- [ ] change impact noted in release notes for any behavior changes
+
+## Exit Decision
+
+Promotion requires maintainers to confirm:
+
+- [ ] all gates above met
+- [ ] no unresolved high-severity council-lite issues
+- [ ] next release notes mark `council-lite` as `stable`

profiles/council-lite/README.md

@@ -4,6 +4,8 @@ Stability: `beta`
 
 Council Lite provides a lightweight deliberation workflow on top of the core profile.
 
+Promotion criteria from `beta` to `stable` are defined in `profiles/council-lite/QUALITY_GATES.md`.
+
 ## What It Adds
 
 - `commands/council-lite.md`