Why: establish the authorized task workspace and its initial baseline.
Evidence: preserved precheck receipt in .task/feature-svc-deploy-u1-account-binding.md; R0=9a9665b458916179df6d94066dfb9aa657a13d60.
Impact: task metadata only; the feature workspace starts at 9a9665b458.
Refs: .task/feature-svc-deploy-u1-account-binding.md
Why: include the current integration baseline before verification.
Evidence: fetched origin/main=ae465d24441ab349c961a55e9b04f8c4ccaf6de8.
Impact: integrate upstream changes without rewriting task history.
Refs: task-sync
Why: PR URL is the task主记录 after push; keep the card discoverable for review.
Evidence: Gitea API created pulls/429
Impact: Card header points at open PR; no merge.
Refs: pulls/429; Backend pulls/171
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: U1 svc user depends on --open-existing; Dev #429 conflicted on modules/backend against main.
Evidence: Backend #171 merged as 1d9e8f4 on origin/main
Impact: Unblocks task-sync; svc.sh content conflicts remain to resolve against main backup work.
Refs: Dev pulls/429; Backend #171
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: Dev #429 conflicted on scripts/svc.sh (U1 user vs main backup) and Backend gitlink.
Evidence: conflict hunks resolved; actions include init|user|backup|backups
Impact: PR #429 should become mergeable after push; both U1 binding and agent backup entrypoints preserved.
Refs: Dev pulls/429; main backup #417; Backend #171
Co-authored-by: Cursor <cursoragent@cursor.com>
Why: #428 landed the same svc-deploy specs; U1 branch still had parallel copies causing add/add conflicts.
Evidence: U1 docs kept branch「已启动」; U4 docs took main (#428) versions
Impact: PR #429 should become mergeable.
Refs: Dev pulls/429; merged #428
Co-authored-by: Cursor <cursoragent@cursor.com>
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
svc_lock: missing flock / lock timeout → reject (no passthrough)svc <env> user …: resolve manifest/ENV_DATA+DSN, force--open-existing, forbid caller--data/--dsntests/test_svc_user_binding.pyT1–T5 + identity regression; pin Backend OpenExisting tipWhy
Approved proposal r1 §7 U1; account ops must hit the same storage as start/stop and never fall back to
./data.Evidence
python3 -m unittest tests.test_svc_user_binding tests.test_svc_identity -v(exit 0) — task card.task/feature-svc-deploy-u1-account-binding.mdImpact
Operators use
scripts/svc.sh <env> user …against instance storage. Full install binary/source remains U2.Refs
docs/svc-deploy/u1-instance-account-binding.mdfeature/svc-deploy-u4-login-keyDo not merge — owner double-key. Prefer merge order Backend #171 → Dev U4 → Dev U1 (or pin-compatible).