tmp-resp.txt and tmp-dedicated.cfg are leftover debug files.
static/agent/ is a generated copy that npm run dev doesn't refresh.
Fix
Delete tmp-resp.txt and tmp-dedicated.cfg
Regenerate static/agent/ as part of npm run dev (or stop committing it and generate it at build time)
- `tmp-resp.txt` and `tmp-dedicated.cfg` are leftover debug files.
- `static/agent/` is a generated copy that `npm run dev` doesn't refresh.
**Fix**
- [x] Delete `tmp-resp.txt` and `tmp-dedicated.cfg`
- [x] Regenerate `static/agent/` as part of `npm run dev` (or stop committing it and generate it at build time)
Reviewed e9be3f7177. Both fix items are done, so I'm closing this.
Checklist
Debug files deleted.tmp-resp.txt and tmp-dedicated.cfg are gone, and nothing in the repo refers to them.
static/agent/ regenerated by npm run dev.predev now runs agent:package first (package.json:25). That writes all four files in static/agent/: the agent, the updater, install.sh and the checksum manifest (package_release.py:26-31). The README and development guide drop the manual npm run agent:package step, and they say to restart dev or rerun it after editing agent code.
Review notes
Running npm run build, which packages the agent the same way, left the working tree clean. The committed static/agent/ copy matches agent/ today.
Minor and non-blocking: the committed copy can still drift if agent source is committed without running dev or build. A test comparing static/agent/ with agent/ would catch that, and it could go with the CI work in #77.
Reviewed e9be3f7177b2810c2ca688501f360ef24cf29ac1. Both fix items are done, so I'm closing this.
**Checklist**
- [x] **Debug files deleted.** `tmp-resp.txt` and `tmp-dedicated.cfg` are gone, and nothing in the repo refers to them.
- [x] **`static/agent/` regenerated by `npm run dev`.** `predev` now runs `agent:package` first (`package.json:25`). That writes all four files in `static/agent/`: the agent, the updater, `install.sh` and the checksum manifest (`package_release.py:26-31`). The README and development guide drop the manual `npm run agent:package` step, and they say to restart dev or rerun it after editing agent code.
**Review notes**
- Running `npm run build`, which packages the agent the same way, left the working tree clean. The committed `static/agent/` copy matches `agent/` today.
- Minor and non-blocking: the committed copy can still drift if agent source is committed without running dev or build. A test comparing `static/agent/` with `agent/` would catch that, and it could go with the CI work in #77.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
tmp-resp.txtandtmp-dedicated.cfgare leftover debug files.static/agent/is a generated copy thatnpm run devdoesn't refresh.Fix
tmp-resp.txtandtmp-dedicated.cfgstatic/agent/as part ofnpm run dev(or stop committing it and generate it at build time)Reviewed
e9be3f7177. Both fix items are done, so I'm closing this.Checklist
tmp-resp.txtandtmp-dedicated.cfgare gone, and nothing in the repo refers to them.static/agent/regenerated bynpm run dev.predevnow runsagent:packagefirst (package.json:25). That writes all four files instatic/agent/: the agent, the updater,install.shand the checksum manifest (package_release.py:26-31). The README and development guide drop the manualnpm run agent:packagestep, and they say to restart dev or rerun it after editing agent code.Review notes
npm run build, which packages the agent the same way, left the working tree clean. The committedstatic/agent/copy matchesagent/today.static/agent/withagent/would catch that, and it could go with the CI work in #77.