# 0→hero CI harness

This directory owns the no-secret reference scenario for the Go Micro
services → agents → workflows lifecycle. It is intentionally small and
scripted so CI can run it on every push without external services or model keys.

`run.sh` verifies the complete first-agent 0→hero contract together:

1. **Scaffold** — the maintained `micro new` 0→1 contract still creates
   runnable services from a clean workspace.
2. **First agent** — `micro agent demo`, `micro examples`, `micro agent preflight`,
   `micro run`, `micro chat`, and `micro inspect agent <name>` remain available
   as the documented first-agent walkthrough path.
3. **Run** — `micro run` remains available as the local development entry point.
4. **Chat** — `micro chat` remains available as the interactive agent entry point.
5. **Inspect/debugging** — `micro inspect agent <name>`, `micro agent history <name>`,
   and `micro inspect flow <name>` remain available as the local run-history
   inspection step. The no-secret debugging smoke seeds durable agent run history
   and memory, then runs the documented inspect/history commands without provider
   credentials; `micro flow runs` preserves durable workflow history inspection.
6. **Deploy** — `micro deploy --dry-run <target>` remains available as the
   deployment-boundary checkpoint. The dry run resolves configured deploy targets
   and services and prints the remote build/copy/systemd/health plan without
   building binaries, opening SSH connections, running `rsync`, or touching
   remote infrastructure.

After the CLI boundary smoke checks, the script runs the deterministic harnesses
that boot real services, agents, workflows, store-backed run history, plan/delegate,
and A2A with only the LLM mocked.

## Local and CI entry points

The default GitHub harness workflow runs this script on every push and pull
request after the install smoke check and 0→1 scaffold contract. Developers can
verify the first-agent on-ramp links and CLI command-output parity with
`make docs-wayfinding` whenever README or website first-agent breadcrumbs,
`micro agent demo`, `micro examples`, or `micro zero-to-hero` change. That
check is provider-free and fails if documented command names, guide links, or
maintained no-secret example paths drift from the CLI outputs. To verify the
installed first-run CLI seam alone, use `make install-smoke`; to run just the documented
agent debugging quickcheck with
`go test ./internal/harness/zero-to-hero-ci -run TestNoSecretFirstAgentDebuggingSmoke -count=1`,
or run the same no-secret contract locally with:

```sh
make harness
```

That target intentionally exercises the first-agent docs wayfinding guard, the
install script smoke path, both 0→1 scaffold variants, the 0→hero scenario, the
event-driven agent-flow harness, and mock provider conformance, so
the public scaffold → run/chat → inspect → deploy lifecycle stays executable
outside CI as well. Live provider checks remain separate and gated by configured
API keys (`make provider-conformance` or the scheduled/manual CI job).