Move public maintainer policy and automation guidance into maintainers/, shrink root AGENTS.md into an audience router, and ignore internal .agent scratch state.
Delete tracked internal ExecPlans from .agent and scrub personal/private references from public RFC examples.
Checks: git diff --cached --check; scripts/check-flake-lock-owners.sh; node scripts/select-openclaw-release.test.mjs; bash -n scripts/update-pins.sh; ruby -e 'require "yaml"; YAML.load_file(".github/workflows/yolo-update.yml"); YAML.load_file(".github/workflows/ci.yml")'
1.4 KiB
1.4 KiB
Maintainer Agent Guide
This directory is public maintainer guidance for agents working on nix-openclaw.
It is not consumer setup documentation and must not contain private deployment state.
Boundaries
- Keep consumer onboarding in
README.md, templates, and module docs. - Keep private deployments, bots, hosts, local worktrees, tokens, and personal automation details out of this repo.
- If a private deployment exposes a public packaging bug, fix the public package here and keep deployment-specific repair elsewhere.
- Treat
README.mdas the product direction source of truth.
Read Order
packaging.mdfor Nix-owned package invariants.release-policy.mdfor the split-track publishing invariant.automation.mdfor the maintainer repair loop.gates.mdfor verification and CI expectations.- Root
AGENTS.mdfor repo-wide rules.
Maintainer Workflow
- Work on
mainby default and push small, surgical commits directly tomainwhen maintainer policy allows it. - Use branches only when a maintainer asks, direct push is blocked, or a disposable local experiment is needed.
- For multi-issue work, commit and push one issue at a time, then verify GitHub Actions for that pushed commit before continuing.
- Do not leave completed maintainer work parked on an agent branch.
- No force push. No weakening package checks just to get green.