codex-genesis-harness 0.1.8 → 0.1.9

package/.codex/skills/genesis-harness/scripts/init-planning.sh

@@ -2,6 +2,7 @@
 set -euo pipefail
 
 confirmed="${PROJECT_BRIEF_CONFIRMED:-0}"
+idea="${USER_IDEA:-}"
 root="."
 script_source="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
 
@@ -16,8 +17,12 @@ while [ "$#" -gt 0 ]; do
       [ -n "$root" ] || { echo "--root requires a path" >&2; exit 2; }
       shift 2
       ;;
+    --idea)
+      idea="${2:-}"
+      shift 2
+      ;;
     --help|-h)
-      echo "Usage: $0 --confirmed [--root path]" >&2
+      echo "Usage: $0 --confirmed [--root path] [--idea \"user brief\"]" >&2
       echo "Or: PROJECT_BRIEF_CONFIRMED=1 $0 [--root path]" >&2
       exit 0
       ;;
@@ -43,11 +48,78 @@ fi
 
 cd "$root"
 
+normalize_inline() {
+  printf '%s' "$1" | tr '\n' ' ' | sed 's/[[:space:]]\+/ /g; s/^ //; s/ $//'
+}
+
+trim_to_words() {
+  local text="$1"
+  local limit="${2:-8}"
+  printf '%s\n' "$text" | awk -v limit="$limit" '{
+    out="";
+    for (i = 1; i <= NF && i <= limit; i++) {
+      out = out (i == 1 ? "" : " ") $i
+    }
+    print out
+  }'
+}
+
+normalized_idea="$(normalize_inline "$idea")"
+detected_stack="$(bash "$script_source/detect-stack.sh" "$root" 2>/dev/null || true)"
+
+if [ -n "$normalized_idea" ]; then
+  idea_summary="$normalized_idea"
+  project_title="$(trim_to_words "$normalized_idea" 8)"
+  project_users="Users described in the brief and adjacent stakeholders."
+  core_value="Turn the idea into a focused v1 outcome without losing the original brief."
+  product_scope="- [ ] Build around this brief: $normalized_idea"
+  current_milestone="Phase 1 discovery and planning bootstrap"
+  success_criteria="- [ ] The first implementation plan stays aligned with this brief: $normalized_idea"
+  functional_requirements="- [ ] Support the core flow implied by the brief: $normalized_idea"
+  user_stories="- [ ] As a target user, I want the product described in this brief: $normalized_idea"
+  acceptance_criteria="- [ ] Discovery confirms scope, QA path, and tech stack for: $normalized_idea"
+  known_unknowns="- [ ] Confirm exact product approach, feature cut, and owners for: $normalized_idea"
+  summary_focus="- [ ] Bootstrap planning from the user idea: $normalized_idea"
+  summary_recent="- [ ] Init seeded planning docs from the first user brief."
+  summary_next="- [ ] Close INIT_QA.md and turn this brief into approved scope."
+  stack_direction="Product direction clue: $(printf '%s' "$normalized_idea" | cut -c1-140)"
+else
+  idea_summary="No explicit user brief captured yet."
+  project_title="TBD"
+  project_users="TBD"
+  core_value="TBD"
+  product_scope="- [ ] TBD"
+  current_milestone="TBD"
+  success_criteria="- [ ] TBD"
+  functional_requirements="- [ ] TBD"
+  user_stories="- [ ] As a user, I want TBD so that TBD."
+  acceptance_criteria="- [ ] TBD"
+  known_unknowns="- [ ] TBD"
+  summary_focus="- [ ] Initialize harness and complete discovery / QA alignment."
+  summary_recent="- [ ] Initial planning skeleton and discovery phase created."
+  summary_next="- [ ] Answer INIT_QA.md and complete Phase 01 discovery artifacts."
+  stack_direction="Product direction clue: TBD"
+fi
+
+if printf '%s' "$normalized_idea" | grep -Eiq 'mobile|ios|android|responsive'; then
+  stack_hint="Mobile-first delivery is implied by the brief."
+else
+  stack_hint="TBD"
+fi
+
+current_iso_utc="$(date -u +"%Y-%m-%dT%H:%M:%SZ")"
+current_day_local="$(date +"%Y-%m-%d")"
+
 mkdir -p \
+  .codebase \
+  .codebase/context \
+  .codebase/failures \
+  .codebase/memories \
   .planning/diagrams \
   .planning/research \
   .planning/decisions \
   .planning/phases/00-foundation \
+  .planning/phases/01-discovery-and-qa \
   .planning/features \
   .planning/bugs \
   .planning/audits \
@@ -95,19 +167,19 @@ write_if_missing .planning/PROJECT.md <<'EOF'
 
 ## What This Project Is
 
-TBD
+__PROJECT_WHAT__
 
 ## Target Users
 
-TBD
+__PROJECT_USERS__
 
 ## Core Value
 
-TBD
+__PROJECT_VALUE__
 
 ## Product Scope
 
-- [ ] TBD
+__PROJECT_SCOPE__
 
 ## Out Of Scope
 
@@ -123,11 +195,11 @@ TBD
 
 ## Current Milestone
 
-TBD
+__PROJECT_MILESTONE__
 
 ## Success Criteria
 
-- [ ] TBD
+__PROJECT_SUCCESS__
 EOF
 
 write_if_missing .planning/REQUIREMENTS.md <<'EOF'
@@ -161,12 +233,13 @@ EOF
 write_if_missing .planning/ROADMAP.md <<'EOF'
 # Roadmap
 
-**Note**: Phase 0 (Foundation) is setup and documentation only. Feature phases will be added after requirements are finalized.
+**Note**: Phase 0 (Foundation) is setup and documentation only. Phase 1 captures discovery, QA alignment, and tech stack sign-off before feature phases are planned.
 
 | Phase | Type | Status | Dependencies | Acceptance Criteria |
 |---|---|---|---|---|
 | 00 Foundation | Setup | [ ] | None | Project docs completed, requirements confirmed, harness verified |
-| TBD | Feature | [ ] | 00 Foundation | To be planned after requirements finalized |
+| 01 Discovery & QA | Validation | [ ] | 00 Foundation | Product approach confirmed, QA checklist answered, tech stack signed off |
+| TBD | Feature | [ ] | 01 Discovery & QA | To be planned after requirements finalized |
 EOF
 
 write_if_missing .planning/STATE.md <<'EOF'
@@ -176,7 +249,7 @@ Current project state: [ ] Initialized planning harness pending product confirma
 Current phase: 00 Foundation (Setup phase - documentation only)
 Current feature or bug: None
 Last completed task: None
-Next task: Confirm project brief and refine planning docs.
+Next task: Run discovery Q&A to confirm product approach and tech stack.
 Blocked items: None
 Latest verification result: Not run
 EOF
@@ -409,15 +482,52 @@ write_if_missing .planning/SUMMARY.md <<'EOF'
 
 ## Current Focus
 
-- [ ] Initialize and confirm planning harness.
+- [ ] Initialize harness and complete discovery / QA alignment.
 
 ## Recent Changes
 
-- [ ] Initial planning skeleton created.
+- [ ] Initial planning skeleton and discovery phase created.
 
 ## Next Recommended Task
 
-- [ ] Confirm product brief and fill required planning docs.
+- [ ] Answer INIT_QA.md and complete Phase 01 discovery artifacts.
+EOF
+
+write_if_missing .planning/INIT_QA.md <<'EOF'
+# Init Discovery Q&A
+
+Complete this immediately after `/init`. The next agent turn should request answers or explicit assumptions for every section below.
+
+## Product Direction
+
+- [ ] What problem is this project solving?
+- [ ] Who is the primary user?
+- [ ] What is the smallest acceptable v1 outcome?
+- [ ] What approaches were considered and which one is preferred?
+
+## QA Closure
+
+- [ ] Happy path is described end-to-end.
+- [ ] Failure and edge cases are listed.
+- [ ] Out-of-scope items are explicitly captured.
+- [ ] Acceptance criteria are measurable.
+- [ ] QA sign-off owner is named.
+
+## Tech Stack Sign-Off
+
+- [ ] Backend/runtime choice confirmed.
+- [ ] Frontend/client choice confirmed.
+- [ ] Storage/database choice confirmed.
+- [ ] Test strategy confirmed.
+- [ ] Deployment target confirmed.
+- [ ] Final tech stack owner is named.
+
+## Required Output To User
+
+Ask for a concise answer that closes:
+1. product approach
+2. tech stack
+3. QA sign-off / approval owner
 EOF
 
 write_if_missing .planning/config.json <<'EOF'
@@ -666,6 +776,56 @@ Review Phase 0 documentation quality.
 - [ ] Team confirms understanding
 EOF
 
+write_if_missing .planning/phases/01-discovery-and-qa/PLAN.md <<'EOF'
+# 01 Discovery & QA Plan
+
+Phase 1 closes product direction before feature planning starts.
+
+- [ ] Ask discovery questions from INIT_QA.md
+- [ ] Confirm preferred product approach
+- [ ] Confirm tech stack and deployment direction
+- [ ] Record QA sign-off owner and acceptance criteria
+- [ ] Update PROJECT.md, REQUIREMENTS.md, STACK.md, ROADMAP.md
+- [ ] Mark feature planning ready
+EOF
+write_if_missing .planning/phases/01-discovery-and-qa/TASKS.md <<'EOF'
+# 01 Discovery & QA Tasks
+
+- [ ] Ask user to confirm product approach
+- [ ] Ask user to confirm target users and success criteria
+- [ ] Ask user to confirm backend, frontend, database, and deployment stack
+- [ ] Run new-feature-qa checklist against current scope
+- [ ] Run requirements-validation checklist
+- [ ] Assign QA sign-off owner
+- [ ] Update ADR-001-tech-stack.md with chosen stack
+- [ ] Update PROJECT.md and REQUIREMENTS.md with approved direction
+- [ ] Update STATE.md next task toward first feature plan
+EOF
+write_if_missing .planning/phases/01-discovery-and-qa/TESTS.md <<'EOF'
+# 01 Discovery & QA Tests
+
+- [ ] INIT_QA.md completed with no unresolved blockers
+- [ ] STACK.md has confirmed stack values or documented assumptions
+- [ ] QA owner and approval path recorded
+- [ ] ROADMAP.md ready for first feature phase creation
+EOF
+write_if_missing .planning/phases/01-discovery-and-qa/VERIFICATION.md <<'EOF'
+# 01 Discovery & QA Verification
+
+- [ ] INIT_QA.md answered
+- [ ] PROJECT.md, REQUIREMENTS.md, STACK.md updated
+- [ ] ADR-001-tech-stack.md updated
+- [ ] Next phase can be created without open product ambiguity
+EOF
+write_if_missing .planning/phases/01-discovery-and-qa/REVIEW.md <<'EOF'
+# 01 Discovery & QA Review
+
+- [ ] Product approach is explicit
+- [ ] Tech stack is explicit
+- [ ] QA sign-off path is explicit
+- [ ] No blocking TBD remains for feature planning
+EOF
+
 write_if_missing .planning/features/FEATURE_TEMPLATE.md <<'EOF'
 # Feature Template
 
@@ -695,6 +855,16 @@ write_if_missing .planning/checks/CHECKS.md <<'EOF'
 - [ ] Architecture boundaries
 - [ ] Project verification
 EOF
+
+write_if_missing .codebase/PHASE_DEPENDENCY_MAP.md <<'EOF'
+# Phase Dependency Map
+
+| Phase | Depends On | Purpose |
+|---|---|---|
+| 00 Foundation | None | Bootstrap planning harness and baseline docs |
+| 01 Discovery & QA | 00 Foundation | Close product direction, QA checklist, and tech stack sign-off |
+| Feature phases (TBD) | 01 Discovery & QA | Implementation planning begins only after discovery is closed |
+EOF
 for check in lint typecheck test build docs-sync architecture-fitness; do
   write_if_missing ".planning/checks/$check.md" <<EOF
 # $check
@@ -747,4 +917,66 @@ for script in "$script_source"/*.sh; do
   chmod +x ".planning/scripts/$(basename "$script")"
 done
 
+GH_PROJECT_WHAT="$project_title" \
+GH_PROJECT_USERS="$project_users" \
+GH_PROJECT_VALUE="$core_value" \
+GH_PROJECT_SCOPE="$product_scope" \
+GH_PROJECT_MILESTONE="$current_milestone" \
+GH_PROJECT_SUCCESS="$success_criteria" \
+perl -0pi -e 's/__PROJECT_WHAT__/$ENV{GH_PROJECT_WHAT}/g; s/__PROJECT_USERS__/$ENV{GH_PROJECT_USERS}/g; s/__PROJECT_VALUE__/$ENV{GH_PROJECT_VALUE}/g; s/__PROJECT_SCOPE__/$ENV{GH_PROJECT_SCOPE}/g; s/__PROJECT_MILESTONE__/$ENV{GH_PROJECT_MILESTONE}/g; s/__PROJECT_SUCCESS__/$ENV{GH_PROJECT_SUCCESS}/g' .planning/PROJECT.md
+
+GH_FUNCTIONAL_REQUIREMENTS="$functional_requirements" \
+GH_USER_STORIES="$user_stories" \
+GH_ACCEPTANCE_CRITERIA="$acceptance_criteria" \
+GH_KNOWN_UNKNOWNS="$known_unknowns" \
+perl -0pi -e 's/- \[ \] TBD\n\n## Non-Functional Requirements/- [ ] TBD\n\n## Seeded From User Idea\n\n$ENV{GH_FUNCTIONAL_REQUIREMENTS}\n\n## Non-Functional Requirements/s; s/- \[ \] As a user, I want TBD so that TBD\./$ENV{GH_USER_STORIES}/g; s/## Acceptance Criteria\n\n- \[ \] TBD/## Acceptance Criteria\n\n$ENV{GH_ACCEPTANCE_CRITERIA}/s; s/## Known Unknowns\n\n- \[ \] TBD/## Known Unknowns\n\n$ENV{GH_KNOWN_UNKNOWNS}/s' .planning/REQUIREMENTS.md
+
+GH_STACK_DIRECTION="$stack_direction" \
+GH_STACK_HINT="$stack_hint" \
+GH_STACK_CLUES="$detected_stack" \
+perl -0pi -e 's/Version constraints: TBD/Version constraints: TBD\n\n## Product Direction Clues\n- $ENV{GH_STACK_DIRECTION}\n- $ENV{GH_STACK_HINT}\n\n## Repository Stack Clues\n$ENV{GH_STACK_CLUES}/s' .planning/STACK.md
+
+GH_SUMMARY_FOCUS="$summary_focus" \
+GH_SUMMARY_RECENT="$summary_recent" \
+GH_SUMMARY_NEXT="$summary_next" \
+perl -0pi -e 's/- \[ \] Initialize harness and complete discovery \/ QA alignment\./$ENV{GH_SUMMARY_FOCUS}/g; s/- \[ \] Initial planning skeleton and discovery phase created\./$ENV{GH_SUMMARY_RECENT}/g; s/- \[ \] Answer INIT_QA\.md and complete Phase 01 discovery artifacts\./$ENV{GH_SUMMARY_NEXT}/g' .planning/SUMMARY.md
+
+GH_IDEA_SUMMARY="$idea_summary" \
+perl -0pi -e 's/Complete this immediately after `\/init`\./Complete this immediately after `\/init`.\n\n## Original User Brief\n\n- [ ] $ENV{GH_IDEA_SUMMARY}\n/s' .planning/INIT_QA.md
+
+write_if_missing .codebase/CURRENT_STATE.md <<EOF
+# Current System State
+
+**Time**: $current_day_local
+**Status**: \`IN_PROGRESS\`
+**Latest Session**: \`$current_day_local-auto-init-bootstrap\`
+
+## Active Bootstrap
+
+- Planning harness initialized automatically from the first user brief.
+- Current planner phase: \`REQUIREMENTS_GATHERING\`
+- User brief: $idea_summary
+- Next task: Answer \`.planning/INIT_QA.md\` and confirm product approach, QA closure, and tech stack.
+EOF
+
+write_if_missing .codebase/state.json <<EOF
+{
+  "current_state": "REQUIREMENTS_GATHERING",
+  "active_work": "Auto-init from user idea",
+  "session_id": "$current_day_local-auto-init-bootstrap",
+  "session_started_at": "$current_iso_utc",
+  "latest_recovery_point": "Auto-init bootstrap in progress",
+  "required_verification": [
+    "genesis-harness init --yes --platform codex --idea '<user brief>'",
+    "Answer .planning/INIT_QA.md",
+    "Update .planning/PROJECT.md, REQUIREMENTS.md, STACK.md"
+  ],
+  "pending_tasks": [
+    "Confirm product approach",
+    "Confirm QA sign-off owner",
+    "Confirm tech stack"
+  ]
+}
+EOF
+
 echo "Project Genesis Harness planning files initialized."

package/.codex/skills/genesis-pipeline-orchestration/SKILL.md

@@ -18,7 +18,20 @@ Do not use for small read-only questions.
 Goal, current state, module index, test matrix, contracts, fixtures, and acceptance criteria.
 
 ## Outputs required
-Phase logs, tests, fixtures, implementation, contracts, memory updates, docs updates, and change summary.
+Phase logs, a machine-readable feature queue, tests, fixtures, implementation, contracts, project verification evidence, a final handoff, memory updates, docs updates, and change summary.
+
+## Runtime lifecycle
+Use the CLI as the durable control plane:
+
+1. `genesis-harness run --idea ...` creates the first execution-ready feature.
+2. `genesis-harness add-feature ...` appends additional planned features.
+3. `genesis-harness next` resolves the single active feature.
+4. `genesis-harness complete-feature ...` verifies that feature and promotes the next queued feature.
+5. After the final feature, `genesis-harness verify-project ...` reruns every feature proof plus the project proof and creates the handoff.
+6. `genesis-harness complete-project ...` moves `RELEASE_READY` to `COMPLETED`.
+7. `genesis-harness pipeline-audit` checks queue, state, proof, handoff, and event-history consistency.
+
+Do not treat feature completion as project completion.
 
 ## Required tests
 Create failing tests in Phase 1 before implementation.
@@ -42,5 +55,4 @@ No phase is skipped and the final report includes verification evidence.
 Combining phases, implementing before fixtures, and leaving state non-resumable.
 
 ## Recovery workflow
-If interrupted, resume from the last completed phase log and rerun verification before continuing.
-
+If interrupted, resume from `.runs/<session-id>/STATE.json`, `RESUME.md`, and append-only `EVENTS.jsonl`, then rerun the relevant verification before continuing.

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-skill-set",
-  "version": "0.1.7",
+  "version": "0.1.9",
   "description": "Genesis harness skill system for Codex test-first, contract-first, memory-aware autonomous workflows.",
   "author": {
     "name": "Genesis Skill Set"
@@ -27,7 +27,9 @@
       "Review"
     ],
     "defaultPrompt": [
-      "Use $genesis-harness and run /genesis-init.",
+      "Use $genesis-harness. If the repo is blank and the user gives an idea, treat it as implicit init and bootstrap from that brief.",
+      "Use genesis-harness add-feature, next, and complete-feature to drive each queued feature through verified completion with evidence.",
+      "After all features are verified, use verify-project, complete-project, and pipeline-audit to close the project only from RELEASE_READY.",
       "Use $genesis-pipeline-orchestration to run the full test-first harness workflow.",
       "Use $genesis-api-contract to create endpoint contracts and tests before implementation."
     ],

package/CHANGELOG.md

@@ -6,6 +6,27 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ---
 
+## [0.1.9] - 2026-06-11
+
+### Added
+- **Non-interactive bootstrap CLI**: Added `genesis-harness init --platform ... --yes --idea ...` for deterministic project initialization from a blank repo or first product brief.
+- **Run pipeline**: Added `genesis-harness run --idea ... --yes` to persist discovery answers and promote the first implementation slice into `.planning/features/`.
+- **Resume artifacts**: Added `.runs/<session-id>/INPUT.md`, `DISCOVERY.json`, `STATE.json`, and `RESUME.md` so future sessions can resume from disk.
+- **Typed first-slice contracts**: The first scaffolded feature can now emit API/UI contracts and fixtures under `contracts/api`, `contracts/ui`, `fixtures/api`, and `playwright/fixtures`.
+- **Verify-gate contract tests**: Added tests for the expanded `verify-gate`, workflow contracts, state metadata, and CLI bootstrap smoke paths.
+
+### Changed
+- **Verify-gate hardening**: `genesis-harness verify-gate` now runs structural verify, eval regression, docs-gate, cold-start, package dry-run, and LeanCTX reporting.
+- **CI verification**: GitHub verification now delegates to a reusable verify workflow.
+- **npm publishing**: Publish workflow now targets GitHub release/manual events and uses npm trusted publishing with provenance instead of long-lived npm tokens or CI-mutated versions.
+- **Package contents**: `README.EN.md` and `README.VI.md` are included in the npm tarball because root `README.md` links to both language guides.
+
+### Release Notes
+- `package.json`, `package-lock.json`, `.codex-plugin/plugin.json`, `VERSION`, README labels, and this changelog are aligned on `0.1.9`.
+- `tmp_pack/package/**` remains tracked as the historical pack artifact; the accidental deletion from the release-prep commit was restored.
+
+---
+
 ## [0.1.8] - 2026-06-01
 
 ### Added

package/README.EN.md

@@ -167,6 +167,48 @@ genesis-harness prime
 
 ---
 
+## 🧭 Release v0.1.9
+
+Genesis v0.1.9 adds a deterministic bootstrap path that starts from a product idea, records discovery answers, scaffolds the first implementation-ready feature, and persists a resumable checkpoint.
+
+```bash
+genesis-harness init --platform codex --yes --idea "<brief>"
+genesis-harness run --platform codex --yes --idea "<brief>" \
+  --product-approach "<approach>" \
+  --primary-user "<user>" \
+  --v1-outcome "<smallest useful outcome>" \
+  --qa-owner "<owner>" \
+  --backend "<runtime>" \
+  --frontend "<client>" \
+  --database "<storage>" \
+  --deployment "<target>" \
+  --test-strategy "<tests>"
+genesis-harness resume
+genesis-harness add-feature --title "Notify staff" --slug "staff-notifications" --verify-cmd "npm test"
+genesis-harness next
+genesis-harness complete-feature --verify-cmd "npm test" --evidence "All feature tests passed"
+genesis-harness verify-project --verify-cmd "npm run verify" --evidence "Acceptance suite passed"
+genesis-harness complete-project --evidence "Release candidate accepted"
+genesis-harness pipeline-audit
+```
+
+Release highlights:
+
+1. Blank repos can be initialized from the first user idea.
+2. Init now creates Discovery & QA scaffolding plus `.codebase/PHASE_DEPENDENCY_MAP.md`.
+3. `run --idea` can promote discovery answers into the active first feature under `.planning/features/`.
+4. First-slice scaffolding can generate typed API/UI contracts and fixtures.
+5. `.runs/<session-id>/` stores resumable run artifacts.
+6. `verify-gate` now covers verify, evals, docs-gate, cold-start, package dry-run, and LeanCTX.
+7. `add-feature`, `next`, and `complete-feature` operate a repeatable multi-feature execution queue with persisted evidence and lead-time metrics.
+8. `verify-project` reruns every feature proof plus the project proof, creates the implementation handoff, and moves the project to `RELEASE_READY`.
+9. `complete-project` requires release or acceptance evidence, while `pipeline-audit` detects lifecycle drift.
+10. npm publishing is hardened for GitHub release/manual runs with provenance and trusted publishing.
+
+Before tagging, confirm `package.json`, `.codex-plugin/plugin.json`, `VERSION`, `CHANGELOG.md`, and README version labels all agree.
+
+---
+
 ## 🔬 Research-First Guarantee (NEW)
 
 **Every important decision is grounded in evidence. No guessing.**
@@ -776,7 +818,7 @@ npm run pack:check      # Check npm package
 - ✅ **Skills**: 25 fully implemented & verified (added 5-Phase MVP Roadmap planner, advanced self-healing and compaction engines)
 - ✅ **Test Coverage**: 80%+ required
 - ✅ **Token Savings**: 40-60%
-- ✅ **Production Ready**: Yes (v0.1.8)
+- ✅ **Production Ready**: Yes (v0.1.9)
 - ✅ **Auto-Research Enforcement**: Active
 - ✅ **Auto-Debug Verification**: Active
 - ✅ **Auto-Spec-Propagation**: Active
@@ -788,7 +830,7 @@ npm run pack:check      # Check npm package
 
 MIT License - See [LICENSE](LICENSE)
 
-**Genesis Codex Harness** - Build production software with Codex | v0.1.8 | June 2026
+**Genesis Codex Harness** - Build production software with Codex | v0.1.9 | June 2026
 
 ---
 

package/README.VI.md

@@ -167,6 +167,48 @@ genesis-harness prime
 
 ---
 
+## 🧭 Release v0.1.9
+
+Genesis v0.1.9 bổ sung luồng bootstrap deterministic: bắt đầu từ ý tưởng sản phẩm, ghi lại discovery answers, scaffold feature đầu tiên sẵn sàng implement, và lưu checkpoint để phiên sau resume từ ổ đĩa.
+
+```bash
+genesis-harness init --platform codex --yes --idea "<brief>"
+genesis-harness run --platform codex --yes --idea "<brief>" \
+  --product-approach "<approach>" \
+  --primary-user "<user>" \
+  --v1-outcome "<smallest useful outcome>" \
+  --qa-owner "<owner>" \
+  --backend "<runtime>" \
+  --frontend "<client>" \
+  --database "<storage>" \
+  --deployment "<target>" \
+  --test-strategy "<tests>"
+genesis-harness resume
+genesis-harness add-feature --title "Thông báo cho nhân viên" --slug "staff-notifications" --verify-cmd "npm test"
+genesis-harness next
+genesis-harness complete-feature --verify-cmd "npm test" --evidence "Toàn bộ test feature đã pass"
+genesis-harness verify-project --verify-cmd "npm run verify" --evidence "Acceptance suite đã pass"
+genesis-harness complete-project --evidence "Release candidate đã được chấp nhận"
+genesis-harness pipeline-audit
+```
+
+Điểm chính của release:
+
+1. Repo trống có thể init trực tiếp từ ý tưởng đầu tiên của user.
+2. Init tạo Discovery & QA scaffold cùng `.codebase/PHASE_DEPENDENCY_MAP.md`.
+3. `run --idea` có thể đưa discovery answers thành feature đầu tiên đang active trong `.planning/features/`.
+4. First-slice scaffold có thể sinh API/UI contracts và fixtures có kiểu rõ ràng.
+5. `.runs/<session-id>/` lưu artifacts để resume.
+6. `verify-gate` giờ bao phủ verify, evals, docs-gate, cold-start, package dry-run, và LeanCTX.
+7. `add-feature`, `next`, và `complete-feature` vận hành queue nhiều feature lặp lại, đồng thời lưu evidence và lead-time metrics.
+8. `verify-project` chạy lại toàn bộ feature proof cùng project proof, tạo implementation handoff, rồi chuyển dự án sang `RELEASE_READY`.
+9. `complete-project` yêu cầu release hoặc acceptance evidence; `pipeline-audit` phát hiện lifecycle drift.
+10. npm publish được harden cho GitHub release/manual runs với provenance và trusted publishing.
+
+Trước khi tag release, cần xác nhận `package.json`, `.codex-plugin/plugin.json`, `VERSION`, `CHANGELOG.md`, và nhãn version trong README đều khớp nhau.
+
+---
+
 ## 🔬 Bảo Đảm Research-First (MỚI)
 
 **Mỗi quyết định quan trọng đều dựa trên bằng chứng. Không đoán mò.**
@@ -769,7 +811,7 @@ npm run eval            # Chạy evaluation
 - ✅ **25 Skills**: Hoàn toàn kế thừa và triển khai đầy đủ (đã bổ sung lộ trình 5-Phase MVP, tự chữa lành & nén context)
 - ✅ **Test Coverage**: 80%+ required
 - ✅ **Token Savings**: 40-60%
-- ✅ **Production Ready**: Yes (v0.1.8)
+- ✅ **Production Ready**: Yes (v0.1.9)
 - ✅ **Auto-Research Enforcement**: Active
 - ✅ **Auto-Debug Verification**: Active
 - ✅ **Auto-Spec-Propagation**: Active
@@ -781,7 +823,7 @@ npm run eval            # Chạy evaluation
 
 MIT License - Xem [LICENSE](LICENSE)
 
-**Genesis Codex Harness** - Xây dựng phần mềm production với Codex | v0.1.8 | Tháng 6, 2026
+**Genesis Codex Harness** - Xây dựng phần mềm production với Codex | v0.1.9 | Tháng 6, 2026
 
 ---
 

package/README.md

@@ -129,6 +129,67 @@ genesis-harness prime
 
 ---
 
+## 🧭 Release v0.1.9
+
+Genesis v0.1.9 turns the harness from a planning scaffold into a resumable runtime bootstrap that can start from a single product idea and carry the first feature slice into implementation.
+
+### Runtime Bootstrap
+
+```bash
+# Initialize a blank repo from a user idea
+genesis-harness init --platform codex --yes --idea "Build a staff-facing request queue"
+
+# Run deterministic discovery and promote the first feature slice
+genesis-harness run \
+  --platform codex \
+  --yes \
+  --idea "Build a concierge booking assistant" \
+  --product-approach "Staff-facing tablet dashboard" \
+  --primary-user "Front-desk staff" \
+  --v1-outcome "Staff can log, prioritize, and resolve guest requests in one queue" \
+  --qa-owner "Operations lead" \
+  --backend "Node.js" \
+  --frontend "React" \
+  --database "PostgreSQL" \
+  --deployment "Fly.io" \
+  --test-strategy "Node integration tests and Playwright smoke tests"
+
+# Resume the active run from disk
+genesis-harness resume
+genesis-harness add-feature --title "Notify staff" --slug "staff-notifications" --verify-cmd "npm test"
+genesis-harness next
+genesis-harness complete-feature --verify-cmd "npm test" --evidence "All feature tests passed"
+genesis-harness verify-project --verify-cmd "npm run verify" --evidence "Acceptance suite passed"
+genesis-harness complete-project --evidence "Release candidate accepted"
+genesis-harness pipeline-audit
+```
+
+### What Changes
+
+1. **Implicit init from an idea**: Empty repos can be bootstrapped directly from the first product brief.
+2. **Discovery & QA phase**: Init now creates `.planning/INIT_QA.md`, a Discovery & QA phase, and `.codebase/PHASE_DEPENDENCY_MAP.md`.
+3. **Idea-seeded planning docs**: `PROJECT.md`, `REQUIREMENTS.md`, `STACK.md`, `SUMMARY.md`, `.codebase/CURRENT_STATE.md`, and `.codebase/state.json` are seeded from the user brief when available.
+4. **Deterministic `run --idea` pipeline**: Discovery answers can be provided in one command and promoted into an active first feature under `.planning/features/`.
+5. **Typed first-slice contracts**: The first feature scaffold can generate API/UI contracts and fixtures under `contracts/api`, `contracts/ui`, `fixtures/api`, and `playwright/fixtures`.
+6. **Resumable run artifacts**: `.runs/<session-id>/INPUT.md`, `DISCOVERY.json`, `STATE.json`, and `RESUME.md` persist the active checkpoint.
+7. **Stronger verify-gate**: `genesis-harness verify-gate` now runs structural verify, evals, docs-gate, cold-start, package dry-run, and LeanCTX reporting.
+8. **End-to-end lifecycle**: Features are queued and verified one at a time; project-wide verification creates a release-ready handoff before final completion.
+9. **Durable audit trail**: `.runs/<session-id>/EVENTS.jsonl` records lifecycle events, while `pipeline-audit` detects queue, state, proof, and handoff drift.
+10. **Release publishing hardening**: GitHub release/manual publishing now uses npm trusted publishing with provenance instead of long-lived npm tokens or CI-mutated versions.
+
+### Release Readiness Checklist
+
+```bash
+npm run verify
+npm run eval
+npm run pack:check
+node bin/genesis-harness.js verify-gate
+```
+
+Before tagging, confirm `package.json`, `.codex-plugin/plugin.json`, `VERSION`, `CHANGELOG.md`, and the README version labels all agree.
+
+---
+
 ## 📦 Quick Start & Usage
 
 ### 1. Installation
@@ -157,6 +218,23 @@ After installation, simply type standard commands in your Codex chat interface t
 
 *All commands are strictly enforced to run in a Codex-only, no-switching environment.*
 
+For non-interactive CLI bootstrap, use:
+
+```bash
+genesis-harness init --platform codex --yes --idea "<brief>"
+genesis-harness run --platform codex --yes --idea "<brief>" \
+  --product-approach "<approach>" \
+  --primary-user "<user>" \
+  --v1-outcome "<smallest useful outcome>" \
+  --qa-owner "<owner>" \
+  --backend "<runtime>" \
+  --frontend "<client>" \
+  --database "<storage>" \
+  --deployment "<target>" \
+  --test-strategy "<tests>"
+genesis-harness resume
+```
+
 ---
 
 ## 🏗️ What Gets Installed
@@ -202,7 +280,7 @@ If you prefer not to install them globally, you can configure your Agent Client
 - ✅ **Codex-Only Enforcement**: `100%`
 - ✅ **Skills Matrix**: 25 fully implemented, structured, and verified skills
 - ✅ **Token Caching Savings**: `40% to 60%` verified per enterprise project
-- ✅ **Stability & Readiness**: Production Ready (`v0.1.8` - June 2026)
+- ✅ **Stability & Readiness**: Production Ready (`v0.1.9` - June 2026)
 
 ---
 
@@ -212,5 +290,5 @@ Licensed under the [MIT License](LICENSE). Contributions, bug reports, and featu
 
 ---
 
-**Genesis Codex Harness** v0.1.8 | June 2026
+**Genesis Codex Harness** v0.1.9 | June 2026
 👉 **[Full English Guide](README.EN.md) | [Tiếng Việt Hướng Dẫn](README.VI.md)**