codeharness 0.25.0 → 0.25.2

package/templates/otlp/nodejs.md

@@ -0,0 +1,53 @@
+# Node.js OTLP Auto-Instrumentation
+
+## Packages to Install
+
+```bash
+npm install --save-dev \
+  @opentelemetry/auto-instrumentations-node \
+  @opentelemetry/exporter-metrics-otlp-http \
+  @opentelemetry/exporter-logs-otlp-http \
+  @opentelemetry/exporter-trace-otlp-http
+```
+
+## Start Script Modification
+
+Add `--require @opentelemetry/auto-instrumentations-node/register` to the project's start script in `package.json`.
+
+Before:
+```json
+"scripts": {
+  "start": "node dist/index.js"
+}
+```
+
+After:
+```json
+"scripts": {
+  "start": "node --require @opentelemetry/auto-instrumentations-node/register dist/index.js"
+}
+```
+
+## Environment Variables
+
+Set these in the project's environment or `.env` file:
+
+```
+OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
+OTEL_SERVICE_NAME={project_name}
+OTEL_TRACES_EXPORTER=otlp
+OTEL_METRICS_EXPORTER=otlp
+OTEL_LOGS_EXPORTER=otlp
+```
+
+## Verification
+
+After starting the application, verify instrumentation:
+
+```bash
+# Check logs are flowing
+curl 'localhost:9428/select/logsql/query?query=*&limit=5'
+
+# Check metrics are flowing
+curl 'localhost:8428/api/v1/query?query=up'
+```

package/templates/otlp/python.md

@@ -0,0 +1,51 @@
+# Python OTLP Auto-Instrumentation
+
+## Packages to Install
+
+```bash
+pip install opentelemetry-distro opentelemetry-exporter-otlp
+opentelemetry-bootstrap -a install
+```
+
+## Start Script Modification
+
+Wrap the application start command with `opentelemetry-instrument`.
+
+Before:
+```bash
+python -m myapp
+```
+
+After:
+```bash
+opentelemetry-instrument python -m myapp
+```
+
+If using a framework runner (gunicorn, uvicorn):
+```bash
+opentelemetry-instrument gunicorn myapp:app
+```
+
+## Environment Variables
+
+Set these in the project's environment or `.env` file:
+
+```
+OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
+OTEL_SERVICE_NAME={project_name}
+OTEL_TRACES_EXPORTER=otlp
+OTEL_METRICS_EXPORTER=otlp
+OTEL_LOGS_EXPORTER=otlp
+```
+
+## Verification
+
+After starting the application, verify instrumentation:
+
+```bash
+# Check logs are flowing
+curl 'localhost:9428/select/logsql/query?query=*&limit=5'
+
+# Check metrics are flowing
+curl 'localhost:8428/api/v1/query?query=up'
+```

package/templates/otlp/rust.md

@@ -0,0 +1,80 @@
+# Rust OTLP Instrumentation
+
+## Packages to Install
+
+```bash
+cargo add opentelemetry opentelemetry-otlp tracing-opentelemetry tracing-subscriber
+```
+
+## Setup Code
+
+Add the following to your `main.rs` to initialize the OTLP tracing pipeline:
+
+```rust
+use opentelemetry::trace::TracerProvider;
+use opentelemetry_otlp::WithExportConfig;
+use tracing_subscriber::layer::SubscriberExt;
+use tracing_subscriber::util::SubscriberInitExt;
+
+fn init_tracing() {
+    let otlp_exporter = opentelemetry_otlp::SpanExporter::builder()
+        .with_http()
+        .with_endpoint(
+            std::env::var("OTEL_EXPORTER_OTLP_ENDPOINT")
+                .unwrap_or_else(|_| "http://localhost:4318".into()),
+        )
+        .build()
+        .expect("failed to create OTLP exporter");
+
+    let provider = opentelemetry::sdk::trace::TracerProvider::builder()
+        .with_batch_exporter(otlp_exporter)
+        .build();
+
+    let tracer = provider.tracer("app");
+    let otel_layer = tracing_opentelemetry::layer().with_tracer(tracer);
+
+    tracing_subscriber::registry()
+        .with(otel_layer)
+        .with(tracing_subscriber::fmt::layer())
+        .init();
+}
+```
+
+Call `init_tracing()` at the start of `main()`.
+
+## Function Instrumentation
+
+Use the `#[tracing::instrument]` attribute to trace individual functions:
+
+```rust
+#[tracing::instrument]
+fn process_request(id: u64, payload: &str) -> Result<(), Error> {
+    tracing::info!("processing request");
+    // ...
+    Ok(())
+}
+```
+
+## Environment Variables
+
+Set these in `.env.codeharness` or your environment:
+
+```
+OTEL_EXPORTER_OTLP_ENDPOINT=http://localhost:4318
+OTEL_SERVICE_NAME={project_name}
+OTEL_TRACES_EXPORTER=otlp
+OTEL_METRICS_EXPORTER=otlp
+OTEL_LOGS_EXPORTER=otlp
+```
+
+## Verification
+
+After starting the application, verify traces are being exported:
+
+```bash
+# Check logs are flowing
+curl 'localhost:9428/select/logsql/query?query=*&limit=5'
+
+# Check metrics are flowing
+curl 'localhost:8428/api/v1/query?query=up'
+```

package/templates/prompts/ralph-prompt.md

@@ -0,0 +1,37 @@
+You are an autonomous coding agent executing a sprint for the codeharness project.
+
+## Your Mission
+
+Run the `/harness-run` command to execute the next story in the sprint.
+
+## Instructions
+
+1. **Run `/harness-run`** — this is the sprint execution skill that:
+   - Reads sprint-status.yaml at `{{sprintStatusPath}}` to find the next story
+   - Picks the first story with status NOT `done` (handles `backlog`, `ready-for-dev`, `in-progress`, `review`, and `verified`)
+   - Executes the appropriate BMAD workflow for the story's current status
+
+2. **Follow all BMAD workflows** — the /harness-run skill handles this, but if prompted:
+   - Use `/bmad-dev-story` for implementation
+   - Use code-review workflow for quality checks
+   - Ensure tests pass and coverage meets targets
+
+3. **Do not skip verification** — every story must pass verification gates
+   (tests, coverage, showboat proof) before being marked done.
+
+## Verification Gates
+
+After completing a story, run `codeharness verify --story <id>` to verify.
+If verification fails, fix the issues and re-verify. The story is not done
+until verification passes.
+
+## Project Context
+
+- **Project directory:** `{{projectDir}}`
+- **Sprint status:** `{{sprintStatusPath}}`
+
+## Important
+
+- Do NOT implement your own task-picking logic. Let /harness-run handle it.
+- Do NOT write to sprint-state.json or sprint-status.yaml. The orchestrator owns all status writes.
+- Focus on one story per session. Ralph will spawn a new session for the next story.