Agent Instructions

Project

Robocopy_Overhaul: Codex-ready repository baseline for a Robocopy overhaul project.

Start by reading AGENTS.md and .codex/project.md.
Keep changes scoped to the user's request.
Prefer existing project patterns once application code exists.
Do not commit secrets, .env files, private keys, certificates, or tokens.
Do not rewrite history or run destructive git commands unless explicitly requested.
Do not create a release unless explicitly requested.
Check the working tree before editing and before finishing. Preserve unrelated user changes.
If GITEA_TOKEN is available locally, use it only for read-only Gitea API checks such as private repository metadata, package-read visibility, and Actions run status. Never print, commit, or store the token.
Repository cleanup automation must be non-destructive if added later.
Dependency, compliance, and release dry-run automation must report findings only unless the user explicitly asks for write actions.

No stack-specific commands are defined yet.

When code is added, update this file and .codex/project.md with the real commands for:

lint
test
build
audit

No release artifact output directory is defined yet.

Review docs/security-review.md before release work.
Treat generated credentials and config files as sensitive.
Keep external network calls documented.
Prefer local processing for user data.
Keep CI publishing secrets in repository or organization secrets, not in tracked files.
Ensure .gitignore covers local config, build outputs, logs, temporary files, and secret material for the detected stack.

git diff --check passes when the directory is a Git repository.
The cheapest reliable verification command has been run, or the reason it could not run is documented.
README, changelog, security review, and release checklist are updated when the change touches release behavior.
docs/agent-handoff.md is updated when work is interrupted, risky, or spans multiple sessions.