CLAUDE.md

1# CLAUDE.md - SteadyAgent Claude Code Guide
2 
3This file gives Claude Code a compact project map for contributing to SteadyAgent.
4 
5## Project Intent
6 
7SteadyAgent is a local-first harness for AI coding agents. It turns ad-hoc Codex and Claude Code sessions into a repeatable loop with scoped planning, repository preflight, deterministic checks, lifecycle hooks, independent review, and checkpoint evidence.
8 
9## Working Rules
10 
11- Start from the relevant files and docs instead of exploring the whole repository.
12- Keep always-on guidance short; move detailed workflow knowledge into `rules/`, `skills/`, or `docs/`.
13- Prefer scripts and hooks for repeatable checks.
14- Preserve host differences honestly: Codex and Claude Code do not expose identical enforcement surfaces.
15- Keep public files free of private paths, local credentials, unpublished plans, and maintainer-only state.
16- Update English and Chinese documentation together when user-facing behavior changes.
17 
18## Validation
19 
20Run the smallest relevant gate before committing:
21 
22```powershell
23powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-release-readiness.ps1
24```
25 
26Focused checks:
27 
28```powershell
29powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-phase3.ps1
30powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\validate-runtime-slice.ps1
31powershell.exe -NoProfile -ExecutionPolicy Bypass -File .\tools\test-agent-hooks.ps1
32```
33 
34Use `-AllowDirty` with `validate-release-readiness.ps1` only while reviewing an intentional work-in-progress tree.
35 
36## Release Discipline
37 
38- Do not publish, retag, or rewrite remote history without explicit maintainer approval.
39- Treat each public release as an audited artifact: clean history, reproducible validation, and clear release notes.
40- Use [docs/github-publication-runbook.md](docs/github-publication-runbook.md) for public release steps.
41