Strengthen agent commit and deploy rules · 7d6ff53

+4 -0

agents.md

@@ -19,6 +19,10 @@ Operational rules:
 - Push committed code to `jumper-runtime` for live testing on jumper.
 - Push committed code to `origin`/GitPrep for archival/canonical history.
 - `scripts/deploy_to_jumper.sh` is available for explicit rsync deploys, but the normal development loop is commit plus push.
+- Agent work is not complete while there are uncommitted local changes, local commits not pushed to both `jumper-runtime` and `origin`, or a jumper `BUILD` that does not match the intended commit.
+- Before ending a change task, verify `git status -sb`, `git ls-remote origin refs/heads/main`, `git ls-remote jumper-runtime refs/heads/main`, and `ssh jumper.madagascar.xdev.ro 'cat /usr/local/xdev-host-manager/BUILD'`.
+- If `git push jumper-runtime HEAD:main` is blocked by dirty tracked files on jumper, inspect and compare the jumper diff before clearing it. Only reset or remove jumper files after confirming the changes are already represented by the commit being pushed or after saving a backup patch under `/usr/local/xdev-host-manager/backups/`.
+- Do not report success until the same commit is visible locally, in GitPrep, in `jumper-runtime`, and in the served build badge/`BUILD`, unless the user explicitly asks to stop before deploy or archive.
 - Runtime registry and Work Orders live in `var/host-manager.sqlite` on jumper.
 - Do not deploy `config/` unless the user explicitly asks to replace seed/snapshot/export files.
 - Treat `config/hosts.yaml`, `config/local-hosts.tsv`, and `config/work-orders.yaml` as compatibility exports/seeds, not the live source of truth.


	@@ -19,6 +19,10 @@ Operational rules:
19	19	- Push committed code to `jumper-runtime` for live testing on jumper.
20	20	- Push committed code to `origin`/GitPrep for archival/canonical history.
21	21	- `scripts/deploy_to_jumper.sh` is available for explicit rsync deploys, but the normal development loop is commit plus push.
	22	+- Agent work is not complete while there are uncommitted local changes, local commits not pushed to both `jumper-runtime` and `origin`, or a jumper `BUILD` that does not match the intended commit.
	23	+- Before ending a change task, verify `git status -sb`, `git ls-remote origin refs/heads/main`, `git ls-remote jumper-runtime refs/heads/main`, and `ssh jumper.madagascar.xdev.ro 'cat /usr/local/xdev-host-manager/BUILD'`.
	24	+- If `git push jumper-runtime HEAD:main` is blocked by dirty tracked files on jumper, inspect and compare the jumper diff before clearing it. Only reset or remove jumper files after confirming the changes are already represented by the commit being pushed or after saving a backup patch under `/usr/local/xdev-host-manager/backups/`.
	25	+- Do not report success until the same commit is visible locally, in GitPrep, in `jumper-runtime`, and in the served build badge/`BUILD`, unless the user explicitly asks to stop before deploy or archive.
22	26	- Runtime registry and Work Orders live in `var/host-manager.sqlite` on jumper.
23	27	- Do not deploy `config/` unless the user explicitly asks to replace seed/snapshot/export files.
24	28	- Treat `config/hosts.yaml`, `config/local-hosts.tsv`, and `config/work-orders.yaml` as compatibility exports/seeds, not the live source of truth.