agent-notify: Instructions file for Codex

AgentNotify agent workflow

These instructions apply to every coding agent working in this repository.

Start or resume work

1. Read docs/ARCHITECTURE.md, docs/FEATURE_BACKLOG.md, TODO.md, and the relevant security documentation.
2. Inspect git status, the current branch, and recent commits before editing.
3. Preserve user changes and runtime secrets. Never read or print the bearer token unless direct API debugging was explicitly requested.
4. Record durable outcomes in the document that owns them, not in a running log: a constraint the implementation is held to belongs in docs/ARCHITECTURE.md, what was actually run and what remains unproven in docs/VERIFICATION.md, and remaining work in TODO.md or docs/FEATURE_BACKLOG.md. Do not reintroduce a session/handoff state file; git history is the record of what happened, and a second copy of it goes stale.

Local Git workflow

• This repository is local-only unless the user explicitly asks to configure or use a remote.
• main is the stable release line. Never edit or commit while checked out on main.
• dev is the integration branch. Do not implement features directly on dev.
• Create each branch from an up-to-date local dev:
  • feature/<short-name> for product capabilities;
  • fix/<short-name> for defects;
  • docs/<short-name> for documentation;
  • test/<short-name> for test-only work;
  • chore/<short-name> for tooling and maintenance.
• Keep commits focused and use imperative Conventional Commit subjects such as feat: add webhook delivery.
• Build and test the branch in proportion to its risk. Update documentation and migrations in the same branch as the behavior they describe.
• Merge a verified branch into local dev with git merge --no-ff. Delete the local topic branch after the merge when safe.
• Start the next topic branch from the newly merged dev.
• Never rewrite shared history, force-push, or use destructive Git commands.

Required quality gates