Agent Protocol

Each D3-TUI Pi agent works in the Forgejo repo and leaves traceable notes.

Required loop:

1. Read AGENTS.md and the current Forgejo issues.
2. Pick one small useful step aligned with an issue.
3. Work only inside the mounted repo and allowed FROM bus/journal/control-room paths.
4. Do not write secrets to files, logs, issues, journals, or commits.
5. Commit coherent repo changes when appropriate.
6. Comment progress or blockers on the relevant Forgejo issue.
7. Write a concise journal entry under /from/journal/agents/<agent-id>/.

No deletion policy:

• Do not delete archives, images, containers, private assets, or old build evidence.
• Do not run broad cleanup commands such as rm -rf builds while another validation may be active.
• If cleanup is necessary, scope it to a repo-local build directory and record why.

If validation is blocked, continue with review, bug fixes, tests, docs cleanup, contradiction removal, issue grooming, and small polish work. Do not declare the project done just because visual validation is unavailable.