# Current Repo Notes

## Identity

- This repository currently reads as a Codex Harness runtime plus package templates, not as a finished business application.
- The root runtime surface includes `AGENTS.md`, `tools/install/bootstrap-codex-harness.ps1`, `tools/harness/codex-loop.ps1`, `tools/harness/doctor.ps1`, `tools/install/env-check.ps1`, `tools/harness/verify.ps1`, `task.json`, `tools/harness/templates/project-task-template.json`, `progress.txt`, and `docs/harness/trace.schema.json`.
- `.agents/` is the active capability surface used inside this repo.
- `docs/codex-harness-engineering/templates/` and package-assets are the distributable template/package surfaces used to install the harness into other projects.
- `docs/harness/` contains runtime usage rules for installed projects.
- `docs/testing/` contains verification and test-planning truth sources.
- For thin install projects, the same deep docs may live only under `.codex-harness/state/config.json` -> `packageRoot`, not under the project root.

## Commands Worth Surfacing

- Bootstrap root runtime:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/install/bootstrap-codex-harness.ps1`
- Environment check:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/install/env-check.ps1`
- Verification:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/harness/verify.ps1`
- Doctor:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/harness/doctor.ps1`
- Driver once / until done:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/harness/codex-loop.ps1`
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools/harness/codex-loop.ps1 -RunUntilDone`
- Install from package:
  `powershell -NoProfile -ExecutionPolicy Bypass -File .\tools\install\install-agent-here.ps1 -Mode full -InitSmoke -InitGitIfNeeded`

## Content Signals

- The root `README.md` is still placeholder content generated by `tools/install/install-agent.ps1`.
- The root `task.json` is still the smoke template with `SMOKE-001`.
- `tools/harness/templates/project-task-template.json` already contains the real driver-first handoff template.
- `.codex/task-run-profile.json` defines the fresh-process default, context sources, and allowed writer/read-only roles.
- `tools/install/bootstrap-codex-harness.ps1` copies root runtime files, `.codex/agents`, `docs/harness/`, and `docs/testing/` from template sources.
- `tools/install/install-agent.ps1` installs `.agents/` from `docs/codex-harness-engineering/templates/package-assets/` and then bootstraps the project root.

## Implications For Root Docs

- `README.md` should position the repo as a harness/package repo and explain both runtime and distributable-package surfaces.
- `AGENTS.md` should remain operational, but add a short project overview and explicit truth-source boundaries when that helps agents avoid reading the wrong copy.
- When a new skill is intended to ship with installed projects, syncing only `.agents/skills/` is incomplete in this repo; the package-facing copies may also need to be updated.
