codex-genesis-harness 0.1.6 → 0.1.7

package/scripts/run-evals.sh

@@ -10,25 +10,21 @@ skill_names=(
   genesis-upgrade-design
   genesis-architecture
   genesis-planning
-  genesis-mvp-planning
   genesis-codebase-map
   genesis-design-spec
   genesis-api-contract
-  ui-ux-test-skill
+  genesis-ui-ux-test
   genesis-harness-engineering
   genesis-ai-provider
   genesis-pipeline-orchestration
-  genesis-research
-  genesis-docs
-  genesis-release
   genesis-api-sync
   genesis-debug-guide
   genesis-docs-automation
   genesis-spec-propagation
-  genesis-release-orchestration
   genesis-performance-profiling
   genesis-observability-automation
   genesis-research-first
+  genesis-release
   spec-impact-engine
 )
 
@@ -59,25 +55,7 @@ done
 for skill_name in "${skill_names[@]}"; do
   assert_file "$skill_root/$skill_name/SKILL.md"
   assert_file "$skill_root/$skill_name/agents/openai.yaml"
-  
-  expected_name="$skill_name"
-  case "$skill_name" in
-    genesis-architecture) expected_name="architecture-skill" ;;
-    genesis-planning) expected_name="planning-skill" ;;
-    genesis-codebase-map) expected_name="codebase-map-skill" ;;
-    genesis-design-spec) expected_name="design-spec-skill" ;;
-    genesis-api-contract) expected_name="api-contract-skill" ;;
-    genesis-harness-engineering) expected_name="harness-engineering-skill" ;;
-    genesis-ai-provider) expected_name="ai-provider-skill" ;;
-    genesis-pipeline-orchestration) expected_name="pipeline-orchestration-skill" ;;
-    genesis-research) expected_name="research-skill" ;;
-    genesis-docs) expected_name="docs-skill" ;;
-    genesis-release) expected_name="release-skill" ;;
-    genesis-api-sync) expected_name="api-sync-skill" ;;
-    genesis-debug-guide) expected_name="debug-guide-skill" ;;
-  esac
-
-  assert_contains "$skill_root/$skill_name/SKILL.md" "name: $expected_name"
+  assert_contains "$skill_root/$skill_name/SKILL.md" "name: $skill_name"
 done
 
 assert_contains "$repo_root/scripts/install.sh" '--target agents|legacy|both'
@@ -116,4 +94,21 @@ for skill_name in "${skill_names[@]}" project-genesis-harness; do
   [ ! -e "$tmp/codex/skills/$skill_name" ] || fail "legacy uninstall target remains: $skill_name"
 done
 
+assert_contains "$repo_root/bin/genesis-harness.js" "genesis-harness remember"
+assert_contains "$repo_root/bin/genesis-harness.js" "genesis-harness recall"
+assert_contains "$repo_root/bin/genesis-harness.js" "genesis-harness forget"
+assert_contains "$repo_root/bin/genesis-harness.js" "genesis-harness prime"
+assert_contains "$repo_root/bin/genesis-harness.js" "genesis-harness view-mockup"
+
+# Test Beads Memory Commands
+node "$repo_root/bin/genesis-harness.js" remember evalsmoke "Verify that evals can store facts." >/dev/null
+node "$repo_root/bin/genesis-harness.js" recall evalsmoke | grep -q "Verify that evals" || fail "recall failed to find test fact"
+node "$repo_root/bin/genesis-harness.js" prime | grep -q "Verify that evals" || fail "prime failed to include test fact"
+
+# Find the ID of the stored fact to forget it
+bead_id=$(node "$repo_root/bin/genesis-harness.js" recall evalsmoke | grep -o "\[[0-9a-f]\{6\}\]" | head -n 1 | tr -d '[]')
+node "$repo_root/bin/genesis-harness.js" forget "$bead_id" >/dev/null
+node "$repo_root/bin/genesis-harness.js" recall evalsmoke | grep -q "Verify that evals" && fail "forget failed to delete test fact" || true
+
+
 echo "evals passed"

package/scripts/uninstall.sh

@@ -7,25 +7,21 @@ skill_names=(
   genesis-upgrade-design
   genesis-architecture
   genesis-planning
-  genesis-mvp-planning
   genesis-codebase-map
   genesis-design-spec
   genesis-api-contract
-  ui-ux-test-skill
+  genesis-ui-ux-test
   genesis-harness-engineering
   genesis-ai-provider
   genesis-pipeline-orchestration
-  genesis-research
-  genesis-docs
-  genesis-release
   genesis-api-sync
   genesis-debug-guide
   genesis-docs-automation
   genesis-spec-propagation
-  genesis-release-orchestration
   genesis-performance-profiling
   genesis-observability-automation
   genesis-research-first
+  genesis-release
   spec-impact-engine
   project-genesis-harness
 )

package/scripts/verify.sh

@@ -9,25 +9,21 @@ skill_names=(
   genesis-upgrade-design
   genesis-architecture
   genesis-planning
-  genesis-mvp-planning
   genesis-codebase-map
   genesis-design-spec
   genesis-api-contract
-  ui-ux-test-skill
+  genesis-ui-ux-test
   genesis-harness-engineering
   genesis-ai-provider
   genesis-pipeline-orchestration
-  genesis-research
-  genesis-docs
-  genesis-release
   genesis-api-sync
   genesis-debug-guide
   genesis-docs-automation
   genesis-spec-propagation
-  genesis-release-orchestration
   genesis-performance-profiling
   genesis-observability-automation
   genesis-research-first
+  genesis-release
   spec-impact-engine
 )
 
@@ -195,7 +191,7 @@ verify_harness_skill() {
   grep -q 'Definition Of Done' "$skill_dir/SKILL.md" || fail "missing Definition Of Done"
   grep -q 'Quality Rubric' "$skill_dir/SKILL.md" || fail "missing Quality Rubric"
 
-  for ref in workflows.md planning-schema.md research-rubric.md quality-rubric.md; do
+  for ref in workflows.md planning-schema.md research-rubric.md quality-rubric.md state-machine.md; do
     [ -f "$skill_dir/references/$ref" ] || fail "missing reference: $ref"
     grep -q "references/$ref" "$skill_dir/SKILL.md" || fail "SKILL.md does not mention reference: $ref"
   done
@@ -268,67 +264,11 @@ verify_one() {
     genesis-new-design|genesis-upgrade-design)
       verify_design_skill "$skill_dir" "$dir_name"
       ;;
-    genesis-architecture)
-      verify_skill_metadata "$skill_dir" "architecture-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-planning)
-      verify_skill_metadata "$skill_dir" "planning-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-mvp-planning)
-      verify_skill_metadata "$skill_dir" "genesis-mvp-planning"
-      verify_minimal_skill "$skill_dir"
-      ;;
-    genesis-codebase-map)
-      verify_skill_metadata "$skill_dir" "codebase-map-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-design-spec)
-      verify_skill_metadata "$skill_dir" "design-spec-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-api-contract)
-      verify_skill_metadata "$skill_dir" "api-contract-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    ui-ux-test-skill)
-      verify_skill_metadata "$skill_dir" "ui-ux-test-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-harness-engineering)
-      verify_skill_metadata "$skill_dir" "harness-engineering-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-ai-provider)
-      verify_skill_metadata "$skill_dir" "ai-provider-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-pipeline-orchestration)
-      verify_skill_metadata "$skill_dir" "pipeline-orchestration-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-research)
-      verify_skill_metadata "$skill_dir" "research-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-docs)
-      verify_skill_metadata "$skill_dir" "docs-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-release)
-      verify_skill_metadata "$skill_dir" "release-skill"
-      verify_skill_protocol "$skill_dir"
-      ;;
-    genesis-api-sync)
-      verify_skill_metadata "$skill_dir" "api-sync-skill"
+    genesis-architecture|genesis-planning|genesis-codebase-map|genesis-design-spec|genesis-api-contract|genesis-ui-ux-test|genesis-harness-engineering|genesis-ai-provider|genesis-pipeline-orchestration|genesis-api-sync)
+      verify_skill_metadata "$skill_dir" "$dir_name"
       verify_skill_protocol "$skill_dir"
       ;;
-    genesis-debug-guide)
-      verify_skill_metadata "$skill_dir" "debug-guide-skill"
-      verify_playbook_skill "$skill_dir"
-      ;;
-    genesis-docs-automation|genesis-spec-propagation|genesis-release-orchestration|genesis-performance-profiling|genesis-observability-automation)
+    genesis-debug-guide|genesis-docs-automation|genesis-spec-propagation|genesis-performance-profiling|genesis-observability-automation|genesis-release)
       verify_skill_metadata "$skill_dir" "$dir_name"
       verify_playbook_skill "$skill_dir"
       ;;

package/.codex/skills/genesis-docs/SKILL.md

@@ -1,46 +0,0 @@
----
-name: docs-skill
-description: Keep Codex harness docs synchronized with skills, contracts, tests, memory, and release behavior. Use after any workflow, public interface, install, verification, or package behavior change.
----
-
-# Docs Skill
-
-## Purpose
-Keep docs short, accurate, and linked to source-of-truth artifacts.
-
-## When to use
-Use after changing skills, CLI behavior, contracts, fixtures, tests, repository memory, or publish flow.
-
-## When NOT to use
-Do not use to duplicate full architecture manuals in `AGENTS.md`.
-
-## Inputs required
-Changed files, public behavior, verification results, and affected users.
-
-## Outputs required
-Updated README, AGENTS map, codebase memory, changelog-style summary, and changed docs list.
-
-## Required tests
-Run docs-related verification and package dry-run when docs affect packaging or install instructions.
-
-## Required fixtures
-Update templates/examples when docs describe reusable workflows.
-
-## Required contract updates
-Update contracts when docs describe new interface behavior.
-
-## Required codebase map updates
-Update `.codebase/CURRENT_STATE.md`, `MODULE_INDEX.md`, or summaries as needed.
-
-## Token saving rules
-Keep docs concise. Link to templates and contracts instead of repeating them.
-
-## Acceptance criteria
-Docs match behavior and do not duplicate large internal manuals.
-
-## Common mistakes
-Letting AGENTS.md grow too large, documenting unverified behavior, and missing install docs.
-
-## Recovery workflow
-If docs drift, add verify assertions or checklist items that catch the drift next time.
-

package/.codex/skills/genesis-docs/agents/openai.yaml

@@ -1,7 +0,0 @@
-interface:
-  display_name: "Docs Skill"
-  short_description: "Synchronize harness documentation"
-  default_prompt: "Use $docs-skill to update concise docs and repository memory after changes."
-policy:
-  allow_implicit_invocation: true
-

package/.codex/skills/genesis-mvp-planning/SKILL.md

@@ -1,114 +0,0 @@
----
-name: genesis-mvp-planning
-description: "Define, structure, and automate the creation of a standard 5-Phase MVP Roadmap right after project initialization. Guarantees a decision-complete path to production-ready launch."
----
-
-# Genesis MVP 5-Phase Planning Skill
-
-## Purpose
-
-The `genesis-mvp-planning` skill is designed to transition a newly initialized project into a structured, decision-complete **5-Phase MVP Roadmap**. Instead of leaving the repository with only a blank generic Phase 0 (Foundation) folder, this skill maps out the entire lifecycle of a production-ready Minimum Viable Product across exactly 5 logical, sequential phases.
-
----
-
-## When to use
-
-Use the `genesis-mvp-planning` skill when:
-- You have just run `/genesis-init` (or `/init`) and need to map out the implementation timeline.
-- You want to scope an application specifically to its MVP (Minimum Viable Product) boundaries.
-- You want to establish clear gates and milestones for each stage of the project lifecycle.
-
----
-
-## When NOT to use
-
-Do NOT use the `genesis-mvp-planning` skill when:
-- The project is already midway through development with a pre-existing mature roadmap.
-- The task is a minor, single-file bug fix or simple refactoring that doesn't affect the project timeline.
-- The roadmap has already been fully approved and is currently active.
-
----
-
-## Inputs required
-
-Before running this planning skill, ensure the following inputs are gathered:
-- **Project Brief / Intent**: Clear understanding of what application is being built and target users.
-- **Technology Stack**: Backend, frontend, database, auth provider, and deployment target.
-- **Core MVP Features List**: The primary business value proposition that must be delivered.
-
----
-
-## Outputs required
-
-Executing this skill creates the following structured deliverables:
-- `.planning/ROADMAP.md`: Updated roadmap with 5 distinct phases defined.
-- `.planning/phases/PHASE_1_CORE/`: Planning directory for Phase 1 (Foundation & API Core).
-- `.planning/phases/PHASE_2_AUTH/`: Planning directory for Phase 2 (Authentication & Security).
-- `.planning/phases/PHASE_3_FEATURES/`: Planning directory for Phase 3 (Core MVP Features).
-- `.planning/phases/PHASE_4_INTEGRATIONS/`: Planning directory for Phase 4 (Third-Party Integrations).
-- `.planning/phases/PHASE_5_READINESS/`: Planning directory for Phase 5 (Production Readiness & Observability).
-
----
-
-## Required tests
-
-The planning deliverables are validated using:
-- [ ] `test/planning/roadmap-structure.test.js`: Verifies `ROADMAP.md` contains all 5 phases with valid status checkboxes.
-- [ ] `test/planning/phase-completeness.test.js`: Verifies each phase directory contains standard `SPEC.md`, `PLAN.md`, and `TASKS.md`.
-
----
-
-## Required fixtures
-
-- `fixtures/planning/roadmap-expected.md`: The canonical structure of a 5-Phase MVP roadmap.
-- `fixtures/planning/phase-config-expected.json`: Complete configuration template mapping out the 5 phases.
-
----
-
-## Required contract updates
-
-Update the following files if phase boundary standards change:
-- `contracts/planning/roadmap.schema.json`: Schema validator for `ROADMAP.md` files.
-- `contracts/planning/phase.schema.json`: Schema validator for individual phase directories.
-
----
-
-## Required codebase map updates
-
-After mapping out the 5-Phase MVP:
-- **`.codebase/CURRENT_STATE.md`**: Update current phase to Phase 1, and add the full 5-phase overview.
-- **`.codebase/MODULE_INDEX.md`**: Add references to each of the 5 phase directories.
-
----
-
-## Token saving rules
-
-1. **Reuse templates**: Do not rewrite the basic structure of the phases. Use the provided phase templates in `templates/`.
-2. **Summarize context**: Do not read every detail of the repository. Use `SUMMARY.md` and module index.
-3. **Draft sequentially**: Plan one phase at a time to keep prompt sizes small.
-
----
-
-## Acceptance criteria
-
-The 5-Phase MVP roadmap is ACCEPTED when:
-- [ ] `ROADMAP.md` is updated with 5 clearly defined phases, dates, and success criteria.
-- [ ] All 5 phase planning folders (`PHASE_1_CORE` to `PHASE_5_READINESS`) are created and populated.
-- [ ] No feature code is written before the 5 phase boundaries are validated.
-
----
-
-## Common mistakes
-
-### Mistake 1: Starting Phase 3 (Core Features) before Phase 1 (API Core)
-- **Problem**: Writing UI screens without verified backend models and schemas leads to massive rework.
-- **Fix**: Complete Phase 1 and 2 to establish a solid database and API contract first.
-
----
-
-## Recovery workflow
-
-### Recovery 1: Phase drift or timeline changes
-1. Mark the affected phase as `[!] blocked` in `ROADMAP.md`.
-2. Document the change in `SPEC_CHANGELOG.md`.
-3. Adjust downstream phase boundaries accordingly.

package/.codex/skills/genesis-mvp-planning/agents/openai.yaml

@@ -1,6 +0,0 @@
-interface:
-  display_name: "Genesis MVP Planning"
-  short_description: "— Xây dựng lộ trình 5 Phase phát triển sản phẩm MVP"
-  default_prompt: "Use $genesis-mvp-planning to map out the 5 essential phases of a production-ready MVP."
-policy:
-  allow_implicit_invocation: true