codex-genesis-harness 0.1.6 → 0.1.8

package/.codex/skills/genesis-observability-automation/references/workflow-phases.md

@@ -0,0 +1,78 @@
+# Observability — Phase-by-Phase Workflow
+
+Tài liệu chi tiết từng giai đoạn triển khai observability.  
+Được gọi bởi `genesis-observability-automation/SKILL.md` → `## Workflow Detail: Phase-by-Phase Execution`.
+
+---
+
+## Phase 1: Observability Architecture Generation
+
+**Goal**: Thiết kế và tài liệu hoá toàn bộ topology observability trước khi viết bất kỳ config nào.
+
+### Architecture components
+
+| Pillar | Component | Purpose |
+|--------|-----------|---------|
+| Metrics | Prometheus / Datadog Agent | Scrape and store numeric time-series |
+| Metrics | Grafana / Datadog Dashboards | Visualize and alert on metrics |
+| Logs | Structured logging library | Produce machine-readable log events |
+| Logs | Log aggregator (Loki/ELK/CloudWatch) | Collect and index logs |
+| Logs | Kibana/Grafana/Datadog | Search and visualize logs |
+| Traces | OpenTelemetry SDK | Instrument service for tracing |
+| Traces | Jaeger/Zipkin/Datadog APM | Collect and visualize traces |
+
+### Service instrumentation by language
+
+- **Node.js**: `prom-client` (metrics), `winston`/`pino` (structured logs), `@opentelemetry/sdk-node` (traces).
+- **Python**: `prometheus_client` (metrics), `structlog`/`python-json-logger` (logs), `opentelemetry-sdk` (traces).
+- **Go**: `prometheus/client_golang` (metrics), `zap`/`logrus` (logs), `go.opentelemetry.io/otel` (traces).
+
+---
+
+## Phase 2: Dashboard Generation
+
+**Required panels (RED metrics)**:
+- **Rate**: Requests per second (total and per endpoint)
+- **Errors**: Error rate percentage (4xx and 5xx separately)
+- **Duration**: Response time as histogram with p50, p95, p99
+
+**SATURATION metrics**:
+- **CPU**: Process CPU utilization %
+- **Memory**: Heap and RSS memory
+- **Connection pool**: Active connections vs. pool limit
+- **Queue depth**: Job queue length (background workers)
+
+See `templates/monitoring-dashboard-template.md` for complete Grafana JSON scaffold.
+
+---
+
+## Phase 3: Alerting Policy Generation
+
+**SLO-based alert thresholds (99.9% availability = 43.8 min/month error budget)**:
+
+```
+Fast burn (1h):   error_rate > 2%   → P1 page immediately
+Medium burn (6h): error_rate > 0.5% → P2 business hours
+Slow burn (3d):   error_rate > 0.1% → Slack + ticket
+```
+
+See `templates/alerting-policy-template.md` for complete Prometheus alerting rules.
+
+---
+
+## Phase 4: Health Check Automation
+
+**Standard health endpoint specification**:
+- `GET /health`     → 200 always (load balancer basic routing)
+- `GET /readiness`  → 200 if dependencies healthy, 503 if not
+- `GET /liveness`   → 200 if process alive + event loop not stuck
+- `GET /metrics`    → Prometheus text format
+
+---
+
+## Phase 5: Incident Response Runbook Generation
+
+**Runbook structure requirements** (every runbook must have):
+Severity definition → Detection signals → Triage steps (with commands) → Escalation triggers → Resolution steps → Rollback procedure → Communication templates → Post-mortem checklist.
+
+See `playbooks/incident-triage-playbook.md` for complete P0/P1/P2/P3 runbooks.

package/.codex/skills/genesis-performance-profiling/SKILL.md

@@ -486,25 +486,4 @@ Default thresholds:
 
 **Goal**: Produce a prioritized, actionable list of optimizations ranked by expected impact vs implementation effort.
 
-**Recommendation template:**
-
-```markdown
-### [BOTTLENECK-001] Slow database query on /api/users (N+1 pattern)
-
-**Evidence**: EXPLAIN ANALYZE shows sequential scan on `users` table (150,000 rows).
-DB query time = 145 ms (81% of total response time).
-Identified via: slow query log + pg_stat_statements.
-
-**Recommended fix**: Add composite index on (tenant_id, status, created_at).
-Fix N+1 ORM query pattern: use eager loading (`include: ['profile']`).
-
-**Estimated impact**: HIGH — Expected p95 improvement: 100–140 ms (55–78% reduction).
-
-**Implementation complexity**: EASY — Index creation: 1 migration file.
-ORM fix: 3 lines of code change.
-
-**Validation method**: Re-run baseline after migration. Confirm p95 ≤ 80 ms.
-Run regression-detection phase against new baseline.
-
-**Risk**: Index creation on large table requires `CREATE INDEX CONCURRENTLY` to avoid table lock.
-```
+Use `templates/performance-report-template.md` for recommendation shape and include evidence, fix, impact, complexity, validation, and risk for each bottleneck.

package/.codex/skills/genesis-performance-profiling/agents/openai.yaml

@@ -3,4 +3,4 @@ interface:
   short_description: "Automate performance baseline, profiling, and load testing"
   default_prompt: "Use $genesis-performance-profiling to establish baseline and identify bottlenecks."
 policy:
-  allow_implicit_invocation: false
+  allow_implicit_invocation: true

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

@@ -1,5 +1,5 @@
 ---
-name: pipeline-orchestration-skill
+name: genesis-pipeline-orchestration
 description: Run end-to-end Codex harness orchestration phases from repository analysis through tests, fixtures, implementation, contracts, memory, docs, and change summaries. Use for autonomous multi-phase work.
 ---
 

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

@@ -1,5 +1,5 @@
 ---
-name: planning-skill
+name: genesis-planning
 description: Create decision-complete plans for Codex harness work, including tests, fixtures, contracts, memory updates, verification, and recovery. Use for new features, refactors, bug fixes, audits, or multi-phase autonomous work.
 ---
 
@@ -44,3 +44,33 @@ Planning implementation before tests, omitting fixtures, and leaving verificatio
 ## Recovery workflow
 If a plan becomes invalid, update the failing test and fixture first, then revise phases.
 
+## MCP Automation Requirements
+
+To ensure plans are grounded in long-term project context and not just short-term conversation history, you **MUST** use the following MCP server:
+1. **`@modelcontextprotocol/server-memory`**: Use this MCP tool to automatically query the Knowledge Graph for past bugs, developer preferences, and architectural rules *before* drafting the implementation phases. Any new plan must respect the persistent memory graph.
+
+---
+
+## 🏗️ 5-Phase MVP Roadmap Standards
+
+When decomposing large-scale features or initializing new project modules, you must enforce the **5-Phase MVP Roadmap Standard** using the provided templates:
+
+1. **Phase 1: Core Foundation & Base Setup** (Templates: `phase-1-core.md`, `phase-2-auth.md`)
+   - Establish environment skeletons, base CLI arguments, dependency configurations, and contract JSON structures.
+   - Core DB migrations, model schemes, and basic configurations.
+2. **Phase 2: Contract-First & Skeletal Tests** (Template: `phase-3-features.md`)
+   - Compile exhaustive contract endpoints (`contracts/api/`) and mock fixture skeletons (`fixtures/api/`).
+   - Auto-generate test skeletons in `tests/integration/` (RED state).
+3. **Phase 3: Logic Implementation & Self-Healing** (Template: `phase-3-features.md`)
+   - Implement minimal code handlers, controllers, or service endpoints.
+   - Execute closed-loop Verify-Fix cycles autonomously until all tests turn GREEN. **CRITICAL**: Do NOT just run `npm test`. You MUST run `npx genesis-harness heal "<test-command>"`. If the test fails, this command will output an `[AGENT_DIRECTIVE]`. You must read the directive and automatically fix the code until it passes without stopping.
+4. **Phase 4: Multi-Agent & External Integrations** (Template: `phase-4-integrations.md`)
+   - Wire up external components, API sync triggers, or media providers.
+5. **Phase 5: E2E Visual QA & Release Readiness** (Template: `phase-5-readiness.md`)
+   - Execute full Playwright E2E smoke tests, visual regression checks, and packaging checklists.
+
+### Related Planning Assets
+* **Checklist**: `checklists/mvp-readiness.md`
+* **Example**: `examples/5-phase-roadmap-example.md`
+* **Templates**: `templates/phase-1-core.md`, `phase-2-auth.md`, `phase-3-features.md`, `phase-4-integrations.md`, `phase-5-readiness.md`
+

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

@@ -1,5 +1,5 @@
 ---
-name: release-skill
+name: genesis-release
 description: Prepare Codex harness package releases with version checks, package dry-runs, npm publish readiness, release notes, verification evidence, and rollback notes. Use before publishing or tagging releases.
 ---
 
@@ -44,3 +44,31 @@ Publishing cache files, missing executable scripts, and omitting npm 2FA/token r
 ## Recovery workflow
 If publish fails, capture error, update known problems, do not change version until root cause is fixed.
 
+## MCP Automation Requirements
+
+To ensure zero human error in releases and tags, you **MUST** use the following MCP server:
+1. **`@modelcontextprotocol/server-github`**: Use this MCP tool to automatically retrieve the list of closed Pull Requests since the last release tag to draft the `CHANGELOG.md` and Release Notes. You must also use it to automatically create the Git Tag and GitHub Release via the API. Do NOT ask the user to do this manually in the browser.
+
+---
+
+## 🚀 Automated Release & Deployment Orchestration
+
+This skill incorporates the **Release & Deployment Orchestration Standard** to manage production-ready releases and rollbacks using the provided templates and playbooks:
+
+1. **Release Checklists** (`checklists/pre-release-validation.md`, `checklists/post-deployment-verification.md`)
+   - Mandatory gates before staging/production merges.
+   - Comprehensive post-deployment validations (health checks, API connectivity).
+2. **Release Playbooks** (`playbooks/semantic-versioning-automation.md`, `playbooks/canary-deployment-orchestration.md`)
+   - Executable guidelines for version bump calculations (v1.0.0 → v1.1.0) and git tags.
+   - Closed-loop canary deployments (5% to 100% routing steps, metrics checks, instant triggers).
+3. **Observability Tracking** (`observability/release-tracking.md`)
+   - Structured release audits, recording versions, commit hashes, pipelines results, and rollout windows.
+4. **Release Templates** (`templates/deployment-strategy-template.md`, `templates/release-runbook-template.md`)
+   - Runbooks for critical steps and standardized strategy sheets.
+
+### Related Release Assets
+* **Checklists**: `checklists/checklist.md`, `checklists/pre-release-validation.md`, `checklists/post-deployment-verification.md`
+* **Playbooks**: `playbooks/semantic-versioning-automation.md`, `playbooks/canary-deployment-orchestration.md`
+* **Observability**: `observability/release-tracking.md`
+* **Templates**: `templates/release-checklist-template.md`, `templates/deployment-strategy-template.md`, `templates/release-runbook-template.md`
+

package/.codex/skills/genesis-research-first/SKILL.md

@@ -84,6 +84,12 @@ Format:
   - Next Steps: What to verify?
 ```
 
+## MCP Automation Requirements
+
+To prevent hallucinations and avoid manual terminal scraping, you **MUST** use the following MCP servers during research:
+1. **`@modelcontextprotocol/server-fetch`**: Use this MCP tool to natively fetch and read the contents of external documentation URLs or Stack Overflow threads. Do NOT guess the API structure.
+2. **`@modelcontextprotocol/server-github`**: Use this MCP tool to search for existing issues, pull requests, or trending repositories related to the task.
+
 ## Output
 
 Each research produces: