Add a --health-check flag to the daemon that prints 'ok' and exits

[rotemmiz]

Request

Add a CLI flag to the opcode42 daemon. When run with this flag, it should:

1. Check if the daemon is running (or just print 'ok')
2. Exit with code 0 if healthy, 1 if not

This is a trivial change for testing the agentic pipeline. Just add the flag to the root command and print 'ok' + exit 0.

Context

• Main entry point: cmd/opcode42/main.go
• CLI framework: cobra (check go.mod for the dependency)

[github-actions]

Proposed plan

Files

• cmd/opcode42/main.go — add --health-check flag to the root cobra command

Approach

1. In cmd/opcode42/main.go, locate the root cobra command definition.
2. Add a bool flag --health-check (short form optional) to the root command's Flags().
3. In the RunE (or Run) of the root command, check the flag value at the top, before any daemon-startup logic. If true, print ok to stdout and os.Exit(0).
4. No daemon startup, no config loading, no port binding — the flag short-circuits immediately.
5. Build and verify: go build ./cmd/opcode42 && ./opcode42 --health-check should print ok and exit 0; echo $? → 0.
6. No new tests strictly required (trivial), but a smoke test in cmd/opcode42/ or a simple TestMainHealthCheck could be added if the project convention expects it.

Risks

• Flag name collision: if --health-check is already used elsewhere (unlikely in a daemon CLI). Verify with grep -r health-check cmd/.
• Adding the check too late in the RunE chain (after config/server init) would defeat the purpose. It must be the first thing evaluated.
• If the root command delegates to serve as the default subcommand, the flag needs to be on whichever command actually runs. Confirm the command structure.

Conformance impact

None. This is a pure CLI-side flag; it never starts the HTTP server and touches no wire protocol. The plan's GET /global/health HTTP endpoint (plan 01, reference contract) is a separate concern. This flag does not affect wire compatibility.

Scope confirmation

This issue is not explicitly described in any plan section — it is a trivial pipeline-test change. It does not contradict any plan. Plan 01 (daemon-core) is the closest related area, but the flag is orthogonal to the daemon's HTTP health endpoint. Proceed as a small, self-contained addition.

---

Reply /approve to proceed (repo owner only).

[rotemmiz]

/approve