codex-genesis-harness 0.1.5 → 0.1.7

package/.codebase/RECOVERY_POINTS.md

@@ -1,438 +1,83 @@
-# Recovery Points
-
-**Purpose**: Document where implementation can be paused and resumed without losing context or creating inconsistencies.
-
-**Use When**: Work needs to be paused, passed to another developer, or interrupted by higher priority work.
-
----
-
-## Quick Reference: Current Recovery Points
-
-| Phase | Status | Resumption File | Last Updated |
-|-------|--------|-----------------|--------------|
-| Planning | ✓ Complete | `.codebase/CURRENT_STATE.md` | _date_ |
-| Design | ✓ Complete | IMPLEMENTATION_HANDOFF.md | _date_ |
-| Contracts | ✓ Complete | `.codebase/API_CONTRACTS.md` | _date_ |
-| Tests | ⏸️ In Progress | `tests/auth.test.ts` | _date_ |
-| Implementation | ⏸️ In Progress | `src/auth/` | _date_ |
-| Documentation | ⏸️ Pending | `docs/AUTH.md` | _date_ |
-
----
-
-## Phase: Planning
-
-**Status**: ✓ Complete  
-**Start Date**: _date_  
-**End Date**: _date_  
-**Resumption**: Not needed
-
-### What Happened
-
-All requirements gathered, validated, and documented.
-
-### To Resume (If Needed)
-
-Not applicable - planning is complete and locked.
-
----
-
-## Phase: Design & Architecture
-
-**Status**: ✓ Complete  
-**Start Date**: _date_  
-**End Date**: _date_  
-**Resumption**: Not needed
-
-### What Happened
-
-System design completed, contracts defined, technology choices made.
-
-### Artifacts
-
-- `.codebase/ARCHITECTURE.md` - Final design
-- `.codebase/API_CONTRACTS.md` - API specifications
-- `IMPLEMENTATION_HANDOFF.md` - Design decisions
-
-### To Resume (If Needed)
-
-Not applicable - design is frozen and approved.
-
----
-
-## Phase: Test Contracts & Fixtures
-
-**Status**: ✓ Complete  
-**Start Date**: _date_  
-**End Date**: _date_  
-**Resumption**: Not needed
-
-### What Happened
-
-Test contracts created, fixtures built, test infrastructure ready.
-
-### Artifacts
-
-```
-tests/
-├── contracts/
-│   ├── auth-api.contract.json
-│   └── session-manager.contract.json
-├── fixtures/
-│   ├── oauth-responses.json
-│   └── user-data.json
-└── setup/
-    ├── test-db-init.sql
-    └── mock-providers.ts
-```
-
-### To Resume (If Needed)
-
-Not applicable - test infrastructure is ready.
-
----
-
-## Phase: Core Implementation (CURRENT PAUSE POINT)
-
-**Status**: ⏸️ In Progress (50% complete)  
-**Start Date**: _date_  
-**Current Date**: _YYYY-MM-DD_  
-**Estimated Completion**: _date_
-
-### What Was Done (Completed)
-
-```
-✓ src/auth/oauth-provider.ts
-  - OAuth 2.0 flow implementation
-  - Provider callback handling
-  - Token management
-
-✓ src/db/migrations/
-  - New users table fields
-  - oauth_provider, oauth_id columns
-
-✓ tests/auth.test.ts
-  - 15 tests written and passing
-  - 90% coverage of oauth-provider.ts
-```
-
-### What Remains (To Do)
-
-```
-⏳ src/auth/session-manager.ts
-  - Session creation and validation
-  - Session timeout handling
-  - Concurrent session management
-
-⏳ src/ui/pages/
-  - Login component
-  - Registration component
-  - Error handling UI
-
-⏳ API endpoints
-  - POST /auth/login
-  - POST /auth/register
-  - POST /auth/logout
-
-⏳ Integration tests
-  - End-to-end OAuth flow
-  - Database state consistency
-```
-
-### Pause State
-
-**What's Safe to Pause Here:**
-
-The OAuth provider module is isolated and complete. Can pause safely at this point.
-
-**Before Pausing:**
-
-```bash
-# 1. Commit current progress
-git add -A
-git commit -m "feat: OAuth provider implementation (50% complete)"
-
-# 2. Verify tests pass
-npm test
-
-# 3. Document pause point
-# (You are reading this file!)
-
-# 4. Create recovery checklist
-# (See section below)
-```
-
-### To Resume From Here
-
-**Step 1: Environment Setup** (5 min)
-
-```bash
-# Pull latest changes
-git pull origin main
-
-# Verify you're on the right branch
-git branch -v
-
-# Install dependencies
-npm install
-
-# Check database is migrated
-npm run db:status
-```
-
-**Step 2: Verify Previous Work** (5 min)
-
-```bash
-# Run existing tests
-npm test -- auth.test.ts
-# Expected: 15 passing
-
-# Check module compiles
-npm run build
-
-# Verify no uncommitted changes
-git status
-```
-
-**Step 3: Review What's Next** (10 min)
-
-```bash
-# Read the handoff document
-cat IMPLEMENTATION_HANDOFF.md
-
-# Check what was planned next
-cat .codebase/CURRENT_STATE.md
-
-# Review test contract
-cat tests/contracts/auth-api.contract.json
-```
-
-**Step 4: Resume Implementation** (30 min+)
-
-Start with session-manager.ts:
-
-```bash
-# Create new branch (if needed)
-git checkout -b continue/auth-session
-
-# Open the next module
-code src/auth/session-manager.ts
-
-# Reference the test contract
-code tests/contracts/session-manager.contract.json
-
-# Start implementing...
-```
-
----
-
-## Phase: Session Management (NEXT PHASE)
-
-**Status**: ⏳ Ready to start  
-**Estimated Start**: _date_  
-**Estimated Duration**: 4-6 hours  
-**Estimator**: Original developer
-
-### What Needs to Happen
-
-1. **Implement session-manager.ts**
-   - Create session on login
-   - Validate session on requests
-   - Handle timeout
-
-2. **Write session tests**
-   - Session creation tests
-   - Validation tests
-   - Timeout tests
-   - Concurrent session tests
-
-3. **Update database**
-   - Add sessions table migration
-   - Add indexes for performance
-
-### Acceptance Criteria
-
-```
-- [ ] Session manager module complete
-- [ ] 12+ session tests written and passing
-- [ ] Coverage ≥ 85%
-- [ ] No performance regressions
-- [ ] Integrated with OAuth provider
-```
-
-### Dependencies
-
-- ✓ OAuth provider complete (already done)
-- ✓ Database migrations (already done)
-- ⏳ Needs: Node.js session library installed
-
-### Blockers
-
-None identified. Ready to proceed.
-
----
-
-## Phase: UI Components (AFTER SESSION)
-
-**Status**: ⏳ Ready to start  
-**Estimated Start**: _date_ (after session phase)  
-**Estimated Duration**: 6-8 hours
-
-### What Needs to Happen
-
-1. **Build Login Page**
-   - OAuth provider buttons
-   - Error messaging
-   - Loading states
-
-2. **Build Register Page**
-   - Form validation
-   - Provider linking
-   - Success messaging
-
-3. **Update Layout**
-   - Add auth header
-   - Add logout button
-   - Add user menu
-
-### Files to Modify
-
-```
-src/ui/pages/
-├── login.tsx (new)
-├── register.tsx (new)
-└── layout.tsx (modify)
-
-src/ui/components/
-├── oauth-button.tsx (new)
-├── auth-error.tsx (new)
-└── user-menu.tsx (modify)
-
-styles/
-├── auth.css (new)
-```
-
-### Acceptance Criteria
-
-```
-- [ ] Login page working
-- [ ] Register page working
-- [ ] OAuth provider flow works E2E
-- [ ] Error messages display correctly
-- [ ] Mobile responsive
-- [ ] Browser compatibility tested
-```
-
----
-
-## Phase: Documentation & Testing (FINAL PHASE)
-
-**Status**: ⏳ Ready to start  
-**Estimated Start**: _date_ (after UI phase)  
-**Estimated Duration**: 4 hours
-
-### What Needs to Happen
-
-1. **Update Documentation**
-   - README auth section
-   - Setup guide
-   - API documentation
-   - Troubleshooting guide
-
-2. **Final Testing**
-   - Full E2E test suite
-   - Performance testing
-   - Security testing
-   - Browser compatibility
-
-3. **Code Review & QA**
-   - Team code review
-   - QA testing
-   - Security review
-
-### Acceptance Criteria
-
-```
-- [ ] All documentation complete
-- [ ] All E2E tests passing
-- [ ] Code review approved
-- [ ] No security issues
-- [ ] Performance acceptable
-- [ ] Ready for production
-```
-
----
-
-## Rollback Points
-
-### If Implementation Gets Stuck
-
-**Rollback Level 1: Last Commit**
-```bash
-git reset --hard HEAD
-npm install
-npm test  # Should pass
-```
-
-**Rollback Level 2: Before This Feature**
-```bash
-git checkout main
-npm install
-npm test
-# Verify everything works on main
-```
-
-**Rollback Level 3: Database Rollback**
-```bash
-npm run db:rollback -- auth-v1
-# Removes auth tables/fields
-# App reverts to state before auth changes
-```
-
----
-
-## Checklist: Before Pausing Work
-
-- [ ] All current tests passing
-- [ ] Code builds without errors
-- [ ] No uncommitted changes
-- [ ] Commit message written (describe state)
-- [ ] This Recovery Points file updated
-- [ ] Next developer notified
-- [ ] Slack message sent with status
-
----
-
-## Checklist: When Resuming Work
-
-- [ ] Pull latest git changes
-- [ ] Run `npm install` (if dependencies changed)
-- [ ] Run existing tests (verify they still pass)
-- [ ] Read IMPLEMENTATION_HANDOFF.md
-- [ ] Read this Recovery Points file
-- [ ] Update status in this file (what phase are you on?)
-- [ ] Begin implementation from current phase
-
----
-
-## Known Issues That Might Affect Resumption
-
-| Issue | Severity | Workaround | Fixed? |
-|-------|----------|-----------|--------|
-| OAuth token refresh timing | Low | Add 5s buffer | ⏳ TODO |
-| Database connection pooling | Medium | Use pool size 10 | ✓ Fixed |
-| Rate limiting missing | Low | Not blocking | ⏳ TODO |
-
----
-
-## Contact For Questions
-
-**Original Developer**: _Name_ (_email_)  
-**Current Owner**: _Name_ (_email_)  
-**Slack Channel**: #auth-feature  
-
----
-
-**Last Updated**: _YYYY-MM-DD HH:MM_  
-**Updated By**: _Name_  
-**Next Review**: _YYYY-MM-DD_  
-**Paused At**: _Phase: Core Implementation_
+# Recovery Points
+
+**Purpose**: Document where harness architecture implementation can be paused and resumed without losing context or creating inconsistencies.
+
+**Use When**: Evolution of the Codex harness (verification loops, CLI tools, scripts) needs to be paused, or when a rollback is necessary due to environment breakage.
+
+---
+
+## Quick Reference: Current Recovery Points
+
+| Phase | Status | Resumption File | Last Updated |
+|-------|--------|-----------------|--------------|
+| TUI Mockup Viewer Integration | ✓ Complete | `.codebase/CURRENT_STATE.md` | 2026-06-01 |
+| Harness Verification Streamlining | ✓ Complete | `.codebase/CURRENT_STATE.md` | 2026-06-01 |
+| Bead Memory Regression Tests | ✓ Complete | `scripts/run-evals.sh` | 2026-06-01 |
+| Harness Engineering Overhaul | ⏸️ Idle (Stable) | `scripts/verify.sh` | 2026-06-01 |
+
+---
+
+## Phase: Harness Verification Streamlining & Memory Evals
+
+**Status**: ✓ Complete  
+**Last Updated**: 2026-06-01  
+
+### What Happened
+
+- Cleaned up legacy/deprecated skills (e.g., `genesis-mvp-planning`, `genesis-release-orchestration`) from `scripts/verify.sh`, `scripts/uninstall.sh`, and `scripts/run-evals.sh`.
+- Removed hard-coded skill name mappings (`expected_name` switch statements), enabling dynamic mapping directly based on directory names.
+- Added test coverage in `run-evals.sh` for the local bead memory commands (`remember`, `recall`, `prime`, `forget`).
+- Enforced `state-machine.md` presence in `verify_harness_skill()`.
+
+### Safe State Confirmation
+
+The harness currently passes all structural tests cleanly.
+```bash
+# Verify structure
+./scripts/verify.sh
+
+# Verify regression
+./scripts/run-evals.sh
+
+# Dry-run package integrity
+npm run pack:check
+```
+
+---
+
+## Rollback Points
+
+### If A Future Harness Evolution Breaks the CLI/Environment
+
+**Rollback Level 1: Last Stable Run (Current State)**
+If a new change to `bin/genesis-harness.js` or `scripts/verify.sh` creates infinite loops or immediate failures:
+```bash
+git checkout -- bin/genesis-harness.js scripts/verify.sh scripts/run-evals.sh
+npm install
+./scripts/verify.sh
+```
+
+**Rollback Level 2: Full Repository Reset**
+If tests are failing in a manner that contaminates local fixtures or memory:
+```bash
+git reset --hard HEAD
+git clean -fd
+npm install
+./scripts/verify.sh
+```
+
+---
+
+## Checklist: Before Pausing Work on Harness Evolutions
+
+- [ ] `scripts/verify.sh` passing cleanly (Exit Code 0)
+- [ ] `scripts/run-evals.sh` passing cleanly (Exit Code 0)
+- [ ] Script files verified for POSIX/LF line endings
+- [ ] No uncommitted changes in core scripts that break existing workflows
+- [ ] `.codebase/CURRENT_STATE.md` updated with exact phase details
+
+---
+
+## Contact For Questions
+**Owner**: Codex Harness Engineering Team
+**Last Validated**: 2026-06-01

package/.codebase/beads.json

@@ -0,0 +1,16 @@
+[
+  {
+    "id": "212329",
+    "category": "general",
+    "fact": "Always use PORT 8080 when running development servers locally.",
+    "timestamp": "2026-06-01T07:22:12.428Z",
+    "git_commit": "92d8138"
+  },
+  {
+    "id": "25d72a",
+    "category": "api",
+    "fact": "Verify request.json schema before running visual regression tests.",
+    "timestamp": "2026-06-01T07:22:33.273Z",
+    "git_commit": "92d8138"
+  }
+]

package/.codex/skills/genesis-ai-provider/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: ai-provider-skill
+name: genesis-ai-provider
 description: Define reliable AI provider harnesses with mock providers, schemas, retries, invalid JSON recovery, persistence tests, and provider contracts. Use for LLM, image, voice, subtitle, render, and pipeline provider work.
 ---
 

package/.codex/skills/genesis-api-contract/SKILL.md

@@ -1,5 +1,5 @@
 ---
-name: api-contract-skill
+name: genesis-api-contract
 description: Create and verify API contracts before endpoint implementation. Use for API routes, service interfaces, validation rules, error shapes, snapshots, and endpoint tests.
 ---