# Codex Project Notes

## Project

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

Repository:

```text
Toxic/Robocopy_Overhaul
```

Remote:

```text
https://git.wilkensxl.de/Toxic/Robocopy_Overhaul.git
```

## Commands

No stack-specific commands are defined yet.

Use this section as the source of truth once the project has implementation code:

```text
lint: PENDING
test: PENDING
build: PENDING
audit: PENDING
readme: manual README
```

Do not invent commands that cannot run.

Heavy project commands must run through Gitea Actions on supported Ubuntu runners once CI exists. Local checks should stay lightweight and avoid dependency installation or build artifact creation.

Supported CI runner labels:

```text
ubuntu-latest
ubuntu-24.04
ubuntu-22.04
```

## Stack

```text
PENDING
```

Package manager or build tool:

```text
PENDING
```

## Build Artifacts

Release artifacts are not defined yet.

Expected files:

```text
PENDING
```

Repository-maintenance files such as `AGENTS.md`, `.codex/`, template blueprints, template workflow files, and `docs/agent-handoff.md` should not be included in user-facing release artifacts unless explicitly requested.

## Security Rules

- Do not commit secrets, tokens, `.env` files, certificates, or private keys.
- Treat generated credentials as sensitive.
- Prefer local generation and local processing for user data.
- Keep dependency audit results visible in CI where possible after a stack is chosen.
- Do not add external network calls unless the feature explicitly requires them.

## Release Rules

Before a release:

1. run the release checklist,
2. verify CI is green,
3. verify download links,
4. update README and changelog,
5. create a tag,
6. create the release.

Do not create releases unless the user explicitly asks for a release.