lifeos-cli: Instructions file for Codex

AGENTS.md

The following rules apply to coding agent collaboration in this repository. These complement the general CONTRIBUTING.md workflow.

1. Core Principles

• Keep repository governance, release safety, and Python compatibility aligned.
• Prefer small, traceable changes that preserve a releasable main branch.

2. Collaboration Workflow

• Follow the Git, Issue, and PR workflow defined in CONTRIBUTING.md.
• Create a new worktree based on the latest main for development work: first git fetch origin and fast-forward local main to origin/main, then create the worktree from main.
• Use gh CLI for all issue and PR operations. Do not edit through the web UI.
• Never use the Codex GitHub connector or any connector-backed GitHub mutation workflow. At any time, issue and PR operations must go through gh CLI only.
• If GitHub permissions, authentication, policy, or environment constraints block a required gh operation, stop and ask the human collaborator to perform or authorize the needed step. Do not switch to the Codex GitHub connector as a fallback.
• Create a tracking issue only for substantive development work that does not already have one, and link it in the PR description with Closes #xx or Related #xx. Trivial or mechanical changes — dependency bumps, CI/workflow tweaks, documentation fixes, small refactors, or other low-risk adjustments — do not require an issue; opening one for every small change adds noise. When in doubt, a PR alone is sufficient.
• Keep issue and PR status synchronized when work scope changes.
• Begin every issue and PR description with a TL;DR section that states the intent and expected outcome in plain language, so human readers can grasp the point at a glance before reading the full description.

3. Text and Language Conventions

• Use Simplified Chinese for issue and PR descriptions, comments, and review notes; keep technical terms in English.
• Always use English commit-message style for PR titles.
• Use English for code, comments, commit messages, and canonical repository documents.
• Localized Markdown companions are allowed when they are explicitly scoped, linked from the canonical English document, and kept aligned with it.
• Keep the root README.md in English as the canonical repository entrypoint. Localized companions such as README.zh-Hans.md must link back to README.md, and README.md should link to the available localized companion documents.
• Do not hard-wrap text in repository documents; keep each paragraph on a single line and let the editor soft-wrap long lines. Markdown tables, code blocks, and ASCII art are exempt because their line layout is meaningful.
• For multi-line PR bodies or comments, write to a temporary file first and pass it through gh.