codex-genesis-harness 0.1.7 → 0.1.9

package/.codex/skills/spec-impact-engine/SKILL.md

@@ -1,504 +1,81 @@
 ---
 name: spec-impact-engine
-description: Automatically detect specification changes, calculate impact severity on downstream project phases, generate migration guides, and orchestrate auto-updates to prevent downstream spec drift and cascading rework.
+description: Automatically detect specification changes, calculate impact severity on downstream phases, generate migration guidance, and prevent cascading rework.
 ---
 
-# Spec Impact Engine Skill
-
-**Purpose**: Automatically detect spec changes and calculate impact on downstream phases.
-
-**Status**: NEW - Automation layer for cascade prevention
-
-## When to Use
-
-Use this skill when:
-- ✅ A spec change happens (API, database, requirements)
-- ✅ You need to know which downstream phases are affected
-- ✅ You need automatic downstream phase updates
-- ✅ You're tracking breaking changes across phases
-- ✅ You need migration guides for dependent phases
-- ✅ You want to prevent cascading rework
-
-## Commands
-
-```bash
-# Detect impact of spec changes
-invoke spec-impact-engine
-
-# Parameters:
-- changed_files: ["path/to/changed/spec.md"]
-- impact_scope: "all" | "current_phase_only"
-- auto_update: true | false
-- notify: true | false
-```
-
----
-
-## How It Works
-
-### Phase 1: Change Detection
-
-**Detects changes in:**
-- `.planning/REQUIREMENTS.md` - Feature/requirement changes
-- `.planning/API_DOCS.md` - Endpoint signature changes
-- `.planning/ARCHITECTURE.md` - System design changes
-- `.planning/DESIGN.md` - UI/UX changes
-- `.planning/STACK.md` - Tech stack changes
-- `.planning/SPEC_CHANGELOG.md` - Explicit spec entries
-- `.planning/features/*/SPEC.md` - Feature spec changes
-- `.planning/bugs/*/PLAN.md` - Bug fix plan changes
-
-**For each change, extracts:**
-```javascript
-{
-  type: "breaking" | "feature" | "internal",
-  document: "API_DOCS.md",
-  section: "/api/users/:id",
-  oldValue: "returns { name, email, role }",
-  newValue: "returns { id, name, email, roles[] }",
-  severity: "high" | "medium" | "low",
-  affectedField: "response.roles",
-  breaking: true,
-  date: "2026-05-30",
-  reason: "Support multiple roles per user"
-}
-```
-
-### Phase 2: Dependency Analysis
-
-**Maps which phases depend on what:**
-
-```javascript
-DependencyMap = {
-  phase1: {
-    provides: ["auth_system", "user_api", "jwt_tokens"],
-    provides_to: ["phase2", "phase3", "phase4", "phase5"]
-  },
-  phase2: {
-    requires: ["user_api_from_phase1"],
-    depends_on: ["phase1"],
-    provides: ["product_catalog", "search_api"],
-    provides_to: ["phase3", "phase4"]
-  },
-  phase3: {
-    requires: ["user_api_from_phase1", "product_catalog_from_phase2"],
-    depends_on: ["phase1", "phase2"],
-    provides: ["shopping_cart", "order_api"],
-    provides_to: ["phase4", "phase5"]
-  }
-}
-```
-
-**Located in:** `.codebase/PHASE_DEPENDENCY_MAP.md` (created during `/init`)
-
-### Phase 3: Impact Calculation
-
-**For each change, identifies:**
-
-```
-Change: Phase 1 API endpoint signature changed
-  ↓
-Query: Which phases import Phase 1 API?
-  ↓
-Result: Phase 2, Phase 3, Phase 4 all depend on Phase 1 API
-  ↓
-Impact chain: 
-  - Phase 2: MEDIUM impact (must update TEST_CONTRACT.md)
-  - Phase 3: HIGH impact (must update SPEC.md + TEST_CONTRACT.md)
-  - Phase 4: MEDIUM impact (may need migration code)
-  ↓
-Recommendation: Update in order: Phase 2 → Phase 3 → Phase 4
-```
-
-### Phase 4: Auto-Update Execution
-
-**AUTO-UPDATE checklist for each affected phase:**
-
-```markdown
-## Affected Phases: Phase 2, Phase 3, Phase 4
-
-### Phase 2 (.planning/features/002-product-catalog/)
-- [ ] Update SPEC.md → Replace old API call signature
-- [ ] Update TEST_CONTRACT.md → Update test expectations
-- [ ] Update PLAN.md → Note breaking change requires update
-- [ ] Create migration note: "Phase 1 API changed, updated tests"
-- [ ] Validate: Run phase 2 tests locally
-- [ ] Status: READY FOR RESUME
-
-### Phase 3 (.planning/features/003-shopping-cart/)
-- [ ] Update SPEC.md → Replace 2 places using Phase 1 API
-- [ ] Update IMPACT.md → Document dependency on Phase 1
-- [ ] Update TEST_CONTRACT.md → 5 tests need updating
-- [ ] Update PLAN.md → New migration steps added
-- [ ] Create migration guide for Phase 3 → Phase 4
-- [ ] Validate: Run phase 3 tests locally
-- [ ] Status: READY FOR RESUME
-
-### Phase 4 (.planning/phases/04-payments/)
-- [ ] Update PLAN.md → Note Phase 1 change may affect token validation
-- [ ] Review security implications
-- [ ] Check if migration code needed
-- [ ] Status: REVIEW REQUIRED
-```
-
-### Phase 5: Verification & Notification
-
-**Automatically:**
-- ✅ Runs affected phase tests
-- ✅ Checks for broken imports
-- ✅ Validates schema compatibility
-- ✅ Generates migration guides
-- ✅ Creates notification with impact summary
-
----
-
-## Impact Report Format
-
-After detection, generates `.codebase/IMPACT_REPORT_<timestamp>.md`:
-
-```markdown
-# Spec Change Impact Report
-
-**Date**: 2026-05-30  
-**Change**: API endpoint signature updated  
-**Severity**: HIGH (breaking change)  
-**Detection**: Phase 1 API_DOCS.md changed
-
-## Summary
-
-Phase 1 endpoint `/api/users/:id` response format changed:
-- OLD: `{ name, email, role }`
-- NEW: `{ id, name, email, roles[] }`
-
-This is a **BREAKING CHANGE** affecting 3 downstream phases.
-
-## Affected Phases
-
-| Phase | Dependency | Impact | Action | Status |
-|-------|-----------|--------|--------|--------|
-| Phase 2 | Imports user_api | MEDIUM | Update 1 spec, 3 tests | ⚠️ NEEDS UPDATE |
-| Phase 3 | Imports user_api | HIGH | Update 2 specs, 5 tests | ⚠️ NEEDS UPDATE |
-| Phase 4 | Imports user_api | LOW | Review only | ⚠️ REVIEW |
-| Phase 5 | Indirect via Phase 4 | LOW | N/A | ✅ OK |
-
-## Migration Strategy
-
-**Recommended execution order:**
-
-1. ✅ Phase 1: Already updated (2026-05-30 14:00)
-2. → Phase 2: Update required (est. 30 min)
-3. → Phase 3: Update required (est. 1 hour)
-4. → Phase 4: Review required (est. 15 min)
-5. → Phase 5: No action needed
-
-**Total update time**: ~2 hours
-
-## Rollback Plan
-
-If Phase 2 update fails:
-```bash
-git checkout HEAD -- .planning/features/002-product-catalog/
-# Then revert Phase 1 change if possible
-```
-
-## Auto-Generated Updates
-
-- [ ] Phase 2 SPEC.md updated
-- [ ] Phase 2 TEST_CONTRACT.md updated
-- [ ] Phase 3 SPEC.md updated
-- [ ] Phase 3 TEST_CONTRACT.md updated
-- [ ] Phase 4 PLAN.md reviewed
-- [ ] All tests passing
-- [ ] Migration guide created
-- [ ] SPEC_CHANGELOG.md entry created
-
-## Validation
-
-All affected phase tests must pass before proceeding:
-
-```bash
-cd .planning/features/002-product-catalog && npm test
-cd .planning/features/003-shopping-cart && npm test
-# Both passing ✓
-```
-
-## Timeline Impact
-
-- Phases delayed: Phase 2 (1 hour), Phase 3 (1 hour)
-- ROADMAP.md timeline may need adjustment
-- Critical path recalculation needed
-
-## Sign-off
-
-- [ ] Developer reviews impact report
-- [ ] Auto-updates validated
-- [ ] Tests passing
-- [ ] Ready to proceed
-```
-
----
-
-## Integration with Genesis Harness
-
-### New Workflows
-
-#### `/spec-change` Command
-
-```bash
-/spec-change <changed_file>
-
-# Example:
-/spec-change .planning/API_DOCS.md
-
-# Automatically:
-1. Detect what changed
-2. Calculate impact
-3. Identify affected phases
-4. Generate impact report
-5. Offer to auto-update downstream phases
-6. Run validation tests
-```
-
-#### `/propagate-spec` Command
-
-```bash
-/propagate-spec
-
-# Automatically:
-1. Check SPEC_CHANGELOG.md for unpropagated changes
-2. Find all affected phases
-3. Update all downstream phase specs
-4. Run all affected phase tests
-5. Generate migration guides
-6. Update ROADMAP.md timelines
-```
-
-#### `/validate-specs` Command
-
-```bash
-/validate-specs
-
-# Automatically:
-1. Check all phases for spec misalignments
-2. Find phases depending on changed specs
-3. Report any spec drifts
-4. Suggest updates needed
-5. Create blockers if critical misalignment found
-```
-
-### Integration Points
-
-**On `/new-feature` completion:**
-```
-1. Implementation passes tests
-2. Docs sync (existing workflow)
-3. NEW: Run spec-impact-engine
-4. NEW: Detect downstream impact
-5. NEW: Auto-update affected phases
-6. NEW: Run validation on all phases
-7. Completion
-```
-
-**On `/api-sync` completion:**
-```
-1. API contracts updated
-2. Breaking changes identified
-3. NEW: Run spec-impact-engine
-4. NEW: Propagate to downstream phases
-5. NEW: Generate migration guides
-6. NEW: Update ROADMAP.md
-```
-
----
-
-## Files Created By Skill
-
-### Core Detection Engine
-
-**`.codex/skills/spec-impact-engine/engine.js`** (200+ lines)
-- Detects file changes
-- Compares old vs new content
-- Identifies breaking changes
-- Calculates severity
-
-**`.codex/skills/spec-impact-engine/dependency-analyzer.js`** (150+ lines)
-- Maps phase dependencies
-- Calculates impact chain
-- Identifies affected phases
-- Suggests update order
-
-**`.codex/skills/spec-impact-engine/auto-updater.js`** (180+ lines)
-- Auto-updates dependent phase specs
-- Runs validation tests
-- Generates migration guides
-- Creates notifications
-
-### Templates
-
-**`.codex/skills/spec-impact-engine/templates/impact-report.md`**
-- Impact report template
-- Affected phases table
-- Migration strategy section
-- Sign-off checklist
-
-**`.codex/skills/spec-impact-engine/templates/migration-guide.md`**
-- Before/after examples
-- Step-by-step migration
-- Rollback procedures
-- Testing checklist
-
-### Configuration
-
-**`.codebase/PHASE_DEPENDENCY_MAP.md`**
-- Created during `/init`
-- Maps which phases depend on which
-- Updated when phases change
-- Used by impact engine for calculations
-
----
-
-## Example: API Breaking Change
-
-### Scenario
-
-Phase 1 API endpoint changes:
-
-```
-Before: GET /api/users/:id
-  Response: { name, email, role }
-
-After: GET /api/users/:id
-  Response: { id, name, email, roles[] }
-```
-
-### What Happens
-
-**Step 1: Detect**
-```
-User runs: /spec-change .planning/API_DOCS.md
-Engine detects: API_DOCS.md has breaking change
-```
-
-**Step 2: Analyze**
-```
-Engine finds: Phase 2 and Phase 3 depend on /api/users/:id
-Impact: Both phases need updates
-```
-
-**Step 3: Auto-Update**
-```
-Phase 2 SPEC.md:
-  OLD: "Call /api/users/:id to get { name, email, role }"
-  NEW: "Call /api/users/:id to get { id, name, email, roles[] }"
-
-Phase 2 TEST_CONTRACT.md:
-  OLD: expect(response.role).toExist()
-  NEW: expect(response.roles).toBeArray()
-
-Phase 3 similar updates...
-```
-
-**Step 4: Validate**
-```
-Run: npm test in Phase 2
-Result: ✓ All tests passing
-Run: npm test in Phase 3
-Result: ✓ All tests passing
-```
-
-**Step 5: Report**
-```
-Create: IMPACT_REPORT_2026-05-30_14-30-00.md
-Shows: 2 phases updated, 2 hours timeline impact
-```
-
----
-
-## Configuration
-
-### `.codebase/PHASE_DEPENDENCY_MAP.md`
-
-```yaml
-phases:
-  phase_1:
-    name: "Authentication & User API"
-    provides:
-      - auth_system
-      - user_api
-      - jwt_tokens
-      - user_model
-    provides_to:
-      - phase_2
-      - phase_3
-      - phase_4
-      - phase_5
-    
-  phase_2:
-    name: "Product Catalog"
-    requires:
-      - user_api_from_phase_1
-    depends_on:
-      - phase_1
-    provides:
-      - product_catalog_api
-      - search_api
-      - product_model
-    provides_to:
-      - phase_3
-      - phase_4
-  
-  phase_3:
-    name: "Shopping Cart & Orders"
-    requires:
-      - user_api_from_phase_1
-      - product_catalog_from_phase_2
-    depends_on:
-      - phase_1
-      - phase_2
-    provides:
-      - shopping_cart_api
-      - order_api
-    provides_to:
-      - phase_4
-
-breaking_change_rules:
-  - if: "API endpoint signature changes"
-    then: "HIGH severity, affects all dependent phases"
-  
-  - if: "Database schema changes"
-    then: "MEDIUM severity, affects phases using schema"
-  
-  - if: "Authentication method changes"
-    then: "HIGH severity, affects all phases"
-```
-
----
-
-## Benefits
-
-✅ **Prevents cascading rework** - Downstream phases auto-updated  
-✅ **Catches breaking changes** - Before they break dependent phases  
-✅ **Saves time** - 30-60 min manual work → automatic  
-✅ **Improves reliability** - No more discovering issues mid-phase  
-✅ **Enables safe refactoring** - Know exactly what breaks  
-✅ **Maintains timeline** - Can recalculate impact on schedule  
-
----
-
-## Next: Implementation Artifacts
-
-This skill generates/updates:
-1. `.codebase/IMPACT_REPORT_<timestamp>.md` - Detailed impact analysis
-2. `.planning/SPEC_CHANGELOG.md` - Auto-entries for all changes
-3. `.planning/features/*/SPEC.md` - Auto-updates for dependent phases
-4. `.planning/ROADMAP.md` - Timeline recalculation if needed
-5. `.planning/STATE.md` - Updated with spec change status
-6. Migration guides for each affected phase
-7. Test updates for all dependent phases
-
----
-
-**Status**: Ready for integration  
-**Integration Point**: `/new-feature`, `/api-sync`, `/spec-change` commands  
-**Automation Level**: 90% - Detects, analyzes, and auto-updates  
-**Manual Required**: Final review and sign-off by developer
+# Spec Impact Engine
+
+## Purpose
+Classify spec changes, calculate downstream impact, and produce an actionable propagation report before dependent implementation continues.
+
+## When to use
+- A requirement, API, database, UI, auth, config, or integration spec changes.
+- A phase begins and upstream specs may have changed.
+- A breaking change needs migration planning.
+- `/spec-change`, `/propagate-spec`, or `/validate-specs` is requested.
+
+## When NOT to use
+- Pure formatting or typo changes.
+- Implementation-only changes with no public or phase contract effect.
+- Review-only tasks where no spec changed.
+
+## Inputs required
+- Changed spec files or git diff.
+- `.codebase/PHASE_DEPENDENCY_MAP.md` when present.
+- Relevant contracts, fixtures, and phase docs.
+- Current roadmap and test matrix.
+
+## Outputs required
+- Impact report with severity, affected phases, and required actions.
+- Migration guide for breaking changes.
+- Recommended verification subset.
+- Follow-up handoff notes for `genesis-spec-propagation`.
+
+## Required tests
+- Add or update expected-output fixtures when impact report shape changes.
+- Run affected contract/fixture checks.
+- Run `scripts/run-evals.sh` after changing this skill or detection script.
+
+## Required fixtures
+- Use `templates/impact-report.md` for report shape.
+- Use `templates/migration-guide.md` for breaking changes.
+- Keep example outputs in `examples/` aligned with template changes.
+
+## Required contract updates
+- Update `contracts/` if public input/output shape changes.
+- Mark breaking contract changes before implementation.
+- Keep `.codebase/API_CONTRACTS.md` synchronized.
+
+## Required codebase map updates
+- Update `.codebase/CURRENT_STATE.md` when impact analysis changes current work.
+- Update `.codebase/TEST_MATRIX.md` if required verification changes.
+- Record unresolved risks in `.codebase/RECOVERY_POINTS.md`.
+
+## Token saving rules
+- Inspect changed spec snippets first, not full phase folders.
+- Use the phase dependency map before broad searches.
+- Summarize unaffected phases instead of expanding them.
+
+## Acceptance criteria
+- Each changed spec is classified as breaking, feature, or internal.
+- All affected phases are listed with severity and action.
+- Breaking changes include migration guidance.
+- Recommended verification is explicit.
+
+## Common mistakes
+- Treating optional field additions as no-impact without checking E2E/UI.
+- Ignoring transitive downstream dependencies.
+- Producing a report without required next actions.
+- Updating downstream files directly before impact classification.
+
+## Recovery workflow
+1. Re-run detection on the smallest changed-file set.
+2. If severity is unclear, mark it medium and require manual review.
+3. Hand off affected phases to `genesis-spec-propagation`.
+4. Record unresolved uncertainty in `.codebase/RECOVERY_POINTS.md`.
+
+## Workflow references
+- `checklists/checklist.md`: required impact checklist.
+- `templates/impact-report.md`: report template.
+- `templates/migration-guide.md`: migration template.
+- `detect-spec-changes.sh`: local detection helper.

package/.codex/skills/spec-impact-engine/checklists/checklist.md

@@ -0,0 +1,10 @@
+# Spec Impact Engine Checklist
+
+Use this checklist whenever a specification change may affect downstream phases.
+
+- [ ] Identify the changed spec files and classify each change as breaking, feature, or internal.
+- [ ] Map affected downstream phases through `.codebase/PHASE_DEPENDENCY_MAP.md` when present.
+- [ ] Update affected tests, contracts, fixtures, SDK/client expectations, and E2E scenarios.
+- [ ] Generate or update a migration guide for breaking changes.
+- [ ] Record the impact report and verification result in `.codebase/` memory.
+- [ ] Run the relevant verification subset before declaring propagation complete.

package/.codex-plugin/plugin.json

@@ -1,6 +1,6 @@
 {
   "name": "genesis-skill-set",
-  "version": "0.1.6",
+  "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,11 +27,12 @@
       "Review"
     ],
     "defaultPrompt": [
-      "Use $genesis-harness and run /genesis-init.",
-      "Use $pipeline-orchestration-skill to run the full test-first harness workflow.",
-      "Use $api-contract-skill to create endpoint contracts and tests before implementation."
+      "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."
     ],
     "brandColor": "#2563EB"
   }
 }
-

package/CHANGELOG.md

@@ -6,7 +6,31 @@ The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.1.0/),
 
 ---
 
-## [0.1.7] - 2026-06-01
+## [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
+- **4 New Genesis Skills for TDD and Workflows**: Added `genesis-executing-plans`, `genesis-test-driven-development`, `genesis-verification-before-completion`, and `genesis-using-git-worktrees` to enforce strict TDD, verification, and isolation principles.
 
 ### Changed
 - **Skill Consolidation**: Merged overlapping skills to resolve duplicated slash commands and clean up the architecture.