Fresh static --dir deploy called pid_alive before record_state; missing pidcheck fell back to agent-system and failed with 「进程即退」.
Evidence
SELF: python3 -m unittest tests.test_svc -v 17/17 PASS (on card)
Test plan
New static fresh-deploy case
Dev CI green
Refs: .task/fix-svc-static-pidcheck-fresh-start.md (independent of #450)
## Summary
- `pid_alive` now prefers in-memory `SVC_PIDCHECK` before `svc.env` / `agent-system`.
- `write_static_reg` persists `pidcheck=--directory <htdocs>` so first-boot health probes do not misread `python http.server` as exited.
- Regression: `test_static_fresh_deploy_registers_pidcheck_and_starts`.
## Why
Fresh static `--dir` deploy called `pid_alive` before `record_state`; missing pidcheck fell back to `agent-system` and failed with 「进程即退」.
## Evidence
- SELF: `python3 -m unittest tests.test_svc -v` 17/17 PASS (on card)
## Test plan
- [x] New static fresh-deploy case
- [ ] Dev CI green
Refs: `.task/fix-svc-static-pidcheck-fresh-start.md` (independent of #450)
Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/fix-svc-static-pidcheck-fresh-start.md; R0=0d224ffcab82cab7def2c0b0cc36d2e6d02ce3dd.
Impact: task metadata only; the feature workspace starts at 0d224ffcab.
Refs: .task/fix-svc-static-pidcheck-fresh-start.md
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.
Summary
pid_alivenow prefers in-memorySVC_PIDCHECKbeforesvc.env/agent-system.write_static_regpersistspidcheck=--directory <htdocs>so first-boot health probes do not misreadpython http.serveras exited.test_static_fresh_deploy_registers_pidcheck_and_starts.Why
Fresh static
--dirdeploy calledpid_alivebeforerecord_state; missing pidcheck fell back toagent-systemand failed with 「进程即退」.Evidence
python3 -m unittest tests.test_svc -v17/17 PASS (on card)Test plan
Refs:
.task/fix-svc-static-pidcheck-fresh-start.md(independent of #450)