docs: pin cwd meaning in attribution footer

Mirror of command-center clarification: first dogfooding round stamped the build worktree instead of the session's own working directory. Rule text now says which one, and to note the build worktree in the body.
docs: attribution footer for machine-opened issues and PRs
2026-10-18 16:41:21 -07:00 · 2026-10-18 16:32:59 -07:00
1 changed files with 9 additions and 0 deletions
@@ -71,6 +71,15 @@ the same regime.
 7. **Pull** on the target (`deploy.sh` does this)
 8. **Deploy** — `scripts/deploy.sh` plans and dispatches only changed services

+**Attribution footer (issues and PRs)** — every issue or PR body you open MUST end with:
+
+```
+---
+cwd: <working directory> · session: <omp session id>
+```
+
+Session id from `/status`; `cwd` is that session's own working directory — not the build checkout, when they differ (note the build worktree in the body instead). Machine-made artifacts stay attributable to the box and session that spawned them.
+
 ## Deployment

 ```